{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You flash this rom at your own risk,
i take no responsibility for any mishaps.
Subscribe to update notifications and general chat by clicking the button below
WETA Pixel TELEGRAM CHANNEL
This here is my personal setup and thought i'd share. Usually i test extensively before releasing to public, but if you do find something detrimental to the usage of your device that is either Force Closing or simply not working, let me know and i will in turn inform whether that is something i will tend to.
WETA is made for Music geeks like me, its main focus is stability and Audio. It is Based off latest firmware currently, and will always be using the most up to date firmware base.
Audio mods...
ViPER4Android 2.3.4.0 with Super quality audio driver or the new 2.5.0.5 with driver pre-installed (credit to @viper520 + @zhuhang)
- for more info on V4A, visit the WEBSITE or XDA thread
Sony Xperia� Z5 Premium audio system
Beats� libraries and effects
Dolby Atmos�
All mods are System Wide
Rom also includes...
3Minit Battery Mod Option - (credit to @gharrington)
- for more info on 3Minit Battery, visit the WEBSITE or XDA thread
Center Clock
QS tile options
Navbar swap back and menu buttons
All display rotations
Navbar size options
Headphone volume warning disabled
How to install...
See post #4 - HERE
Changelog...
V1.0
Initial release, based off NDE63V
WETA Audio
- V4A 2.5.0.5
- V4A 2.3.4.0
3Minit Battery
Center Clock
QS tile mods*
SystemUI tuner mods
- navbar tuner
- brightness slider toggle
V1.0.1
Fixed V4A 2.3.4.0 install bug
V1.0.2x
Added Boot slot options
V1.1 beta
Based off NPF26J
includes double tap to wake etc
No status bar mods at this stage - process broken
Navbar height included
Be sure to flash the new vendor.img BEFORE the rom!
V1.0.3
All rom zips, from now on, will be based off of the international/unlocked version of firmware.
This version is based off of NDE63V for instance. You can flash the radio from any version, but you need the V vendor img.
Added Walkman Music Player
Added V4A convolvers and profiles
Added Adblocking hosts file
Added Tethering hack (may work)
Added 1 Verizon apk to debloat
V1.0.4
Added AdAway adblocking app
Added Busybox install to system
Added System tweak scripts, zipalign + sqlite
V1.0.5
Added Verizon sim option
- hopefully eliminates update nag
V2.0
I firmly recommend updating to full stock NMF26O, and booting into it. Then rooting before flashing the ROM
Based off Dec update NMF26O
All mods working
V2.1
Added Remove NavBar option
Updated Google TTS
Updated/Added GBoard (First boot GBoard will crash, fine after its libs are initialized)
Added Dark Boot Animation option
V2.2
Updated to NMF26Q
V2.2.1
Fixed V4A convolver and profile permissions
� FYI this will wipe out your /sdcard/ViPER4Android folder
V2.3
Deodexed Framework (smaller zip size)
Debloated apps available on playstore
Zipaligned all apks
Different system install method
- No more need for 1.8gb of tmp space for install
*GoogleTTS will still crash on first boot on a clean install until you update all your google apps. Thats just the way it is. If you ask about this, i slappa yo face.
**Flash a fresh vendor.img BEFORE the rom. Just do it. If you don't, and you post about V4A or Dolby issues, i slappa yo face.
***Volume control issues are related to janky google tts updates. Not a rom issue
Flashing of vendor.img should be done BEFORE flashing the rom if you want all functionality! The WETA rom zip modifies files on the vendor partition. Meaning if you flash vendor after the rom, you will break WETA features.
Do not flash Gapps with this ROM!
Because this is based off of stock android, gapps are included.
See pot 2 for more info and FAQ
ROM Download Page
Wiping data, cache and dalvik is recommended.
Wipe Data if you are coming from another rom or version base, have crashes or other issues before reporting.
Kernel source - https://android.googlesource.com/device/google/marlin-kernel/
WETA Reboot source - https://github.com/daxgirl/6thGear-Reboot-App
If you like my work, please consider buying this poor guy a craft beer for his efforts
This rom is built from a stock google rom image and doesn't require source links.
------------------------------------------------------------>
XDA:DevDB Information
WETA Marlin, ROM for the Google Pixel XL
Contributors
Mentalmuso, mentalmuso
Source Code: [url]https://android.googlesource.com/device/google/marlin-kernel/[/URL]
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2016-11-17
Last Updated 2016-11-16
Welcome....
I just wanted to start by saying, we all know things are a little bit different with the setup of a pixel device. I think i have a handle of things though there is always a chance of death... i mean crash. Just please, always backup.
Also i am pointing scripts etc to partition slot system_a. Im still not exactly sure if you will come across problems when things update but i suppose we will see.
Now with regards to TWRP and Root. Please read up carefully on these two subjects as they are both pretty young at the moment. Flashing TWRP will be the first thing you need to do. After that, flashing a kernel as i am not including one at this point. Maybe later... If you have come from the same firmware then you wont need to flash a kernel, or vendor etc for that matter. Just boot into TWRP and flash the rom. If you wipe data, you will need to flash SuperSU SR4 after the rom, just to get the SuperSU app back into your app drawer. If you dont wipe data, then the SuperSU apk should still be there along with root binaries.
The zip is big, and will get smaller as time goes on. At this stage there is no real debloating, unpacking and repacking of the system.img hasnt been done yet, so the whole thing is in there at this stage. Also because this rom is based off of stock a stock google android prebuilt image, this means you dont need to flash Gapps. In fact dont, itll break things.
On a wiped data, first boot, i did notice Google TTS crashes though after the play store updates, this goes away. Also if other google apps are crashing because you're lazy and didn't wipe data. Then try uninstalling the apps updates in the play store and reinstalling.
EDIT - One more caveat, you are going to need an extra 1.7gb of free space just for the rom flash, this is on top of the actual size of the zip. I have had to have the system.img extract to a tmp folder before flashing, this gets wiped on boot, so you get that space back after reboot.
I think thats all....
--->
Odds and Ends, Tricks to getting broken things working again
This is a very general post, and can possibly be used on other phones and roms.
My SystemUI keeps crashing, even after a fresh stock install...
If SystemUI is modified, and this modification causes a crash, this can damage the runtime data for systemui. This means that even though you flash a bone stock systemui, it may still crash on boot. Wiping all data fixes this, though that is a pain in the butt. All you need to do is go to, and delete /data/system/users/0/runtime_permissions.xml. You can do this in TWRP file manager. Reboot, job done. This will reset your wallpaper but who cares.
V4A keeps asking to install drivers, or V4A stops processing...
This is a constant issue people have, except for me...... what does this mean? it means i, as a rom dev, am constantly and consistently wiping data and sdcard for testing purposes. This tells me one thing i think is obvious, but of course i may be wrong, bad data will kill V4A. But i will say that flashing a stock vendor.img AFTER the rom will break V4A and Dolby (flash vendor.img before rom). SuperSU is crucial. If in doubt, flash the supersu zip again after rom install. V4A and Dolby both need selinux to be set to permissive. This is achieved with SuperSU and its boot scripts. Also Spotify will stop processing sometimes if a track plays through to the next by itself. (Skipping tracks isnt affected). This bug can be remedied by turning off gapless playback.
--->
<--- Installation Instructions --->
This is a dynamic post, or in other words, it may change from build to build, when it does, i will inform users with the new ROM link post.
First off, this post is a little late, i should have done this earlier but it is what it is and its here now. At this time this is directly related from updating from WETA 1.0.5a (may work on others) to WETA 2.0.
- Boot Slots -
If you are new to the Pixel and are about to start flashing, there is something you need to realize. The Pixel devices have two sets of partitions to boot from. This allows seamless updating on googles part. Google it.. Anyway, in the ROM aroma menu you will notice options to select which boot slot to flash to, A or B. You need to flash to the correct slot, which would be the slot you are already booting into. You need to check this by booting into bootloader and it will be listed there. It states your boot slot in TWRP also when you select reboot. Though i would trust Bootloader more at these early stages.
Both methods below will work also if you are coming from stock. You just need to get yourself TWRP'd and Rooted.
Method #1 - No Wipe (dirty)
This method isn't usually recommended when jumping bases, but worked ok this time around. These are the steps i took that were successful for me.
I started out being on NDE63V WETA 1.0.5, TWRP, Rooted
1. Boot into bootloader and check what boot slot is active, take note of it.
2. Boot into TWRP
- dont do any wiping whatsoever.... the weta install automatically wipes dalvik and cache.
3. Flash NMF26O vendor.img using TWRP
4. Flash WETA 2.0 selecting the correct boot slot from step one in aroma.
5. Reboot system, this can take 5-6min as it rebuilds Dalvik
--->
Method #2 - Clean install (Wiped data) or (img flash only no wipe)
OK, so we are jumping from 7.1 to 7.1.1. There are going to obviously be some changes, thats why i was surprised that Method #1 actually works without issue.. Having said this, when using the method above (method #1) but wiping all your data instead.. This creates a problem with acore crashing constantly on boot. This led me to trying to understand the system apps a little better, and from what i can see, all the system apps are odexed but the odex files live on another partition that gets loaded up on first boot. With changes between the old and the new firmware and its apps there is a good chance the odex file from the old firmware doesnt play well with the updated apk. And the only way to get those odex files onto your device is to flash the firmware package. Regardless... if you want a clean install this time around, follow these steps
1. Backup everything, because you may lose everything, or you may not.
2. You are going to need the stock firmware package and a pc, (aosp download page)
3. You are going to need fastboot drivers, google how to install adb and fastboot. You should already have them if you own this or any nexus devices.
4. OK this is where you flash the whole firmware package. If you do it as is, you will wipe all data on your phone. This includes photos and music. So again backup if you care.
- NOTE, you can preserve all of your data by opening the flash-all.sh(linux) or flash-all.bat(windows) script in a note pad and deleting the (-w) in the line (fastboot -w update image-marlin-nmf26o.zip)
- the process goes like this, open a terminal, cd into the firmware folder, and run the flash-all script (sh flash-all.sh for linux) (double click the flash_all.bat file for windows)
- Now you have all the stock img's flashed to your device on the active boot slot
5. You can now start the rom install process, you are going to need to re flash TWRP and SuperSU.
6. Now all you have to do is Flash the WETA rom. Select the boot slot that you have active in bootloader. Check it first then flash to it.
7. Reboot system, boot may take 5-6min
--->
First user on the first ROM first thread. yah Mentalmuso.
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
I think you should add my Trumpimation to your ROM.
http://forum.xda-developers.com/pixel-xl/themes/trump-boot-animation-t3501515
Mine
CZ Eddie said:
First user on the first ROM first thread. yah Mentalmuso.
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
I think you should add my Trumpimation to your ROM.
http://forum.xda-developers.com/pixel-xl/themes/trump-boot-animation-t3501515
Click to expand...
Click to collapse
How is it?
seshaz said:
How is it?
Click to expand...
Click to collapse
I dunno, I just spent two hours setting up my current 100% stock ROM, including adding some of his WETA mods to it.
I'm done flashing for the evening.
His mods work great though.
ReUploading
I forgot to copy some mods into a folder.... re uploading
Edit.. link is back up
--->
My only question is about the kernel part. I am on the latest v verizon rom already, do I need to flash a kernel or just flash the rom then su?
Correction, I'm on the x verizon build.
thewebsiteisdown said:
My only question is about the kernel part. I am on the latest v verizon rom already, do I need to flash a kernel or just flash the rom then su?
Correction, I'm on the x verizon build.
Click to expand...
Click to collapse
I looked at the aosp images site today and it states that V isn't the Verizon one but in fact that X firmware is. It's pretty confusing. But regardless, if you are already on V, and you are already twrp and rooted, then you can literally just flash the ROM over the top. If you also don't wipe data, then you will keep the SuperSU app.
Edit.. all the firmwares seem to have all the apks needed for Verizon anyway.
Sent from my Pixel XL using Tapatalk
Mentalmuso said:
I looked at the aosp images site today and it states that V isn't the Verizon one but in fact that X firmware is. It's pretty confusing. But regardless, if you are already on V, and you are already twrp and rooted, then you can literally just flash the ROM over the top. If you also don't wipe data, then you will keep the SuperSU app.
Edit.. all the firmwares seem to have all the apks needed for Verizon anyway.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
That's my fault bub. I'm actually on X which is Verizon. Sorry for any confusion.
thewebsiteisdown said:
That's my fault bub. I'm actually on X which is Verizon. Sorry for any confusion.
Click to expand...
Click to collapse
x has pretty much the same everything besides a different radio...you will be fine without flashing any extra firmware bits
Dope bruh. Gonna give this a go after dinner.
Sent from my Pixel XL using XDA Labs
Just flashed it and everything went good. I like the installer. Thanks sir!
It's telling me there's a system update. I just turned the auto system updates off in the developer options.
thewebsiteisdown said:
Just flashed it and everything went good. I like the installer. Thanks sir!
It's telling me there's a system update. I just turned the auto system updates off in the developer options.
Click to expand...
Click to collapse
Really? System update? That may be because your were on X
Sent from my Pixel XL using Tapatalk
Mentalmuso said:
Really? System update? That may be because your were on X
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
X is later than V. I wouldn't think it would want to go back to the V radios.
Thanks for the first flashable ROM!
Mentalmuso said:
Really? System update? Were you on V previously? That may be because your were on X.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I should take it lol.. It says it's only 18MB. I did wipe data cache and dalvik through twrp just so you know, before flashing.
I get an error saying there's an internal problem with your device contact your manufacturer for details when I reboot for some reason to but, I click ok and everything seems to be working? Verizon pushed their apps to my phone when it all booted up but I removed them and they were not there at first.
Either way I love it so.
Added screenshots in case you want to see what I am referring to. The LTE service kicks in fine just so you know, I see it captured no sim blah. I just captured the screen shot to fast is all.
Rev C
found another bug and squished it, V4A 2.3.4.0 wasnt installing properly when selected.
--->
thewebsiteisdown said:
Maybe I should take it lol.. It says it's only 18MB. I did wipe data cache and dalvik through twrp just so you know, before flashing.
I get an error saying there's an internal problem with your device contact your manufacturer for details when I reboot for some reason to but, I click ok and everything seems to be working? Verizon pushed their apps to my phone when it all booted up but I removed them and they were not there at first.
Either way I love it so.
Added screenshots in case you want to see what I am referring to. The LTE service kicks in fine just so you know, I see it captured no sim blah. I just captured the screen shot to fast is all.
Click to expand...
Click to collapse
the internal error problem comes from a mismatch with vendor build.prop and system build.prop. This kinda indicates that you didnt flash vendor. Or if you did it didnt flash. Try that again.
--->
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Custom ROM GB.XXKPH.WT-0.4.0
This is a rework of my previous ROM using a new EU stock ROM (XXKPH). The biggest change from my previous ROM is the installation. I am now using the AROMA installer that has been popping up in many different Android phones. It turns our that the AROMA installer works pretty well with Galaxy Player. It will open up more options for ROM developers in packaging their ROM.
Latest News & Status
[06/14/2012] V0.4.0 is now up for testing.
[06/10/2012] Added a screenshot of RTL support in the coming (V0.4.0) release.
[06/06/2012] V0.3.0 is now up for testing.
[06/01/2012] Added a few screenshots of the installer. V0.3.0 is coming!
[05/04/2012] v0.2.2 is confirmed to be working on US devices.
[05/03/2012] The installation issue is fixed in v0.2.2. So far it is tested on Intl device only. US device users please report back whether the fix is working or not.
[04/29/2012] There is still an installation issue with US devices. [FIXED]
[04/29/2012] Release of v0.2.1. Creating "rom-settings" folder on internal sdcard for used with device id hack.
[04/28/2012] Release of v0.2.0.
Latest Version
GB.XXKPH.WT-0.4.0(International or US)
md5sum: 3ae1f94aa1c99e86d42051199975d32c
Previous Versions
GB.XXKPH.WT-0.3.0(International or US)
md5sum: 4bf58cec58dd2cb3082a8cfcb986d825
GB.XXKPH.WT-0.2.2(International or US)
md5sum: b519a5b603c5dc3e0bb7879d543b348c
Features:
(new) Right to left language support. MultiLing keyboard is added if you need one to enter middle east languages.
Refactoring of device ID hack
Included "WT ROM Tweaker" app for modifying phone parameters
Derived from XXKPH 2.3.6 EU ROM
AROMA Installer
Deodexed, Rooted & Busybox
No kernel (so that it works for both US & Intl)
Advanced power menu (added Reboot, Recovery & Download)
Lidroid Quick Panel (aka 13 status bar toggle buttons with long press)
Device ID hack (Similar to Meticulus' hack but a different implementation. See more info below)
Change ro.product.model to GT-I9000 for better market compatibility
Three choices of boot animation
TW Launcher 4.5, GO Launcher EX
Whatsapp (good for testing device ID hack)
Additional Tools
Format-ext4 (i.e. lagfix) This will format /system, /data, /datadata (dbdata) and /cache to ext4. You can use this to wipe your device before installing the base ROM.
Format-rfs This will format /system, /data, /datadata (dbdata) and /cache to rfs. You can use this to wipe your device before installing the base ROM.
Version History:
Code:
Change Log:
V0.4.0
- RTL support
- Include MultiLing keyboard
V0.3.0
- Refactoring of device ID hack.
- Added WT ROM Tweaker app for modifying phone parameters.
V0.2.2
- Fixed mount/unmount issue on US devices.
V0.2.1
- Create "rom-settings" folder on sdcard for used by device id hack.
V0.2.0
- Device ID hack
- Changed ro.product.model to GT-I9000 for better compatibility
- Optional boot animations
(ICS, Glowing Android & Bios)
- Optional launchers
(TW Launcher 4.5, GO Launcher EX)
- Apps
(Whatsapp)
V0.1.0
- AROMA Installer
- No kernel
- Deodexed
- Rooted
- Busybox
- Advanced power menu
(added Reboot, Recovery & Download)
- Lidroid Quick Panel
(13 status bar toggle buttons)
Prerequisites
You have a Galaxy Player 5.0 International or US (YP-G70).
For US device, you need to have Entropy's kernel. You can get the kernel in this thread.
For international device, you need to have rumirand's kernel. You can get the kernel in this thread.
Your internal SD card has more than 200M bytes free.
Installation Instructions
Copy the zip package you downloaded from the link above to your internal sd card.
Turn off your device.
Boot your device into recovery mode by pressing Vol Up+Home+Power. You can release your buttons once you see the Samsung logo.
In main menu, use "wipe data/factory reset" clean up your data directory.
In advanced menu and do a "Wipe Dalvik Cache".
In main menu, select "install zip from sdcard".
Then select "choose zip from internal sdcard".
Pick the zip file you put on the internal sdcard.
Select "Yes" to start the flashing.
Now the AROMA installer will start. Follow the installation steps shown.
At the end of the installation, press 'Finish' and you will go back CWM Recovery.
DO NOT WIPE data after the installation! Otherwise you will wipe out apps installed in the data partition!
If it is a success, go back to main menu and select "reboot system now".
Installation Instructions for Mods
Install the base ROM first using the instructions as shown above.
Install the additional mod using "install zip from sdcard" in CWM.
No need to do data wipe after the installation.
If you want to revert to the base ROM, flash the uninstaller (if available).
Acknowledgement
rumirand - For his big contribution in rj's kernel, make sure you visit his kernel thread for latest kernel goodies!
Entropy512 - For his big contribution in CWM and kernel deveplopment and helpful comments in the forum. If you have a Galaxy Player 5.0 US, you may find something useful in his kernel thread.
dsixda - For his marvelous ROM Kitchen. If you are a newbie like me, make sure you check out his ROM Kitchen thread.
Daneshm90 - For his wonderful Auto_Deodexer script. Particularly useful if you want to understand the command behind the scene. See his thread here.
untermensch - For his guide on advanced power menu.
clockworx, Decad3nce & racks11479 - For their guide on device ID hack.
Fr4gg0r - For his TW Launcher 4.5.
lidroid - For his 14 status bar toggle buttons.
amarullz - For his AROMA Installer.
madmack - For his Arabic patch.
And countless people who posted on XDA.
Information for ROM users
Device ID Hack - I have made quite a lot of changes to the device id hack. The phone parameters are now moved from "rom-settings" on sdcard to "/data/property" which is a much more standard way to handle properties. Another important feature is the "WT ROM Tweaker" app. The app gives you the ability to change phone parameters like network operator, SIM card serial no. and etc.
Below are some other Network Operators that you can try
Network Operator/ Network Operator Name/Network Country ISO
----------------------------------------------------------------
310260 T-Mobile us
310004 Verizon us
302720 Rogers ca
22802 sunrise ch
22801 swisscom ch
22803 orange ch
26207 o2 - de de
26203 simyo de
22201 Telstra au
23203 T-Mobile at
20416 T-Mobile nl
27203 Meteor ie
45419 PCCW hk
Using Whatsapp - Whatsapp is still not showing up on market therefore I have included the apk in the ROM. With the device ID hack, the Whatsapp can be run on Galaxy Player. After accepting the Whatsapp's agreement, you will be asked for a phone number. You need to enter a REAL phone number for the verification to work. It will try to send a sms to your phone number for verification. But of course the sms verification will fail because the phone number does not belong to the Galaxy Player. After a few minutes, Whatsapp will present you with another option by calling your phone number. You will receive a call from Whatsapp playing back the verification code to you. You can then use the code to register Whatsapp. Now you are set. However, this registration is tied to the IMEI generated by the device id hack. Therefore DO NOT delete the "rom-settings" folder under your sdcard. Otherwise you need to do it all over again when a new IMEI is generated.
13 status bar toggle buttons - To use the toggles, slide down the notification and you can slide the buttons left and right. Pressing the button will toggle the item. Long press the button will bring you to the setting. You can also use the include Quick Setting app to enable and reorder these buttons.
Installation Log - If you experience installation issues, you can save the installation log at the last step of your installation. It should be located at the same folder as your ROM zip.
Information for Developers
Going to test this right now. Sounds awesome!
EDIT: Tried this ROM. It is very smooth, I like it a LOT. However, I'm having some trouble. I can't seem to pick an optional launcher. It doesn't work; it just brings me to the regular TouchWiz 3.0 interface. :L Otherwise, this ROM is great.
This looks great on paper. Gonna try it now and report back later.
Thank you for the effort!
EDIT: The installation went well, but I can't turn on WiFi and Bluetooth. When I try to turn WiFi, it only says "Error".
I have an US version of the SGP 5.0
Trae329 said:
Going to test this right now. Sounds awesome!
EDIT: Tried this ROM. It is very smooth, I like it a LOT. However, I'm having some trouble. I can't seem to pick an optional launcher. It doesn't work; it just brings me to the regular TouchWiz 3.0 interface. :L Otherwise, this ROM is great.
Click to expand...
Click to collapse
Can you provide more information on the steps you did? Also the TW 4.5 looks very similar to 4.5.
SirRhor said:
This looks great on paper. Gonna try it now and report back later.
Thank you for the effort!
EDIT: The installation went well, but I can't turn on WiFi and Bluetooth. When I try to turn WiFi, it only says "Error".
I have an US version of the SGP 5.0
Click to expand...
Click to collapse
I only have an Intl version. You are probably the first one try it on US device. Can you give some more information on your installation steps?
WT Ho said:
I only have an Intl version. You are probably the first one try it on US device. Can you give some more information on your installation steps?
Click to expand...
Click to collapse
I tried it flashing the ROM from the internal SD card as noted on the instructions.
On the Aroma installer I picked the Stock SGP Boot animation, Touchwiz 4.5 and the Device ID hack.
Once it was completed, I went back to CWM and I rebooted the device.
Everything went well, until I tried to turn WiFi on, then Bluetooth.
After that I tried flashing the ROM from the external SD Card.
I then picked the Stock SGP Boot animation, Default Launcher and the Device ID hack. Same results.
I will keep trying with different configurations.
I hope it helps. Thank you again for this new option.
SirRhor said:
I tried it flashing the ROM from the internal SD card as noted on the instructions.
On the Aroma installer I picked the Stock SGP Boot animation, Touchwiz 4.5 and the Device ID hack.
Once it was completed, I went back to CWM and I rebooted the device.
Everything went well, until I tried to turn WiFi on, then Bluetooth.
After that I tried flashing the ROM from the external SD Card.
I then picked the Stock SGP Boot animation, Default Launcher and the Device ID hack. Same results.
I will keep trying with different configurations.
I hope it helps. Thank you again for this new option.
Click to expand...
Click to collapse
That's odd. Can you capture the installation log at the last step of the installation? You should see a button for saving the log.
On my device, wifi and bluetooth seems to be working correctly. One possibility is that there are some files that are leftover from previous ROM in /system. In addition to full data wipe, you can try mounting /system and format it under "mounts and storage" in CWM. This will ensure everything got wiped.
WT Ho said:
That's odd. Can you capture the installation log at the last step of the installation? You should see a button for saving the log.
On my device, wifi and bluetooth seems to be working correctly. One possibility is that there are some files that are leftover from previous ROM in /system. In addition to full data wipe, you can try mounting /system and format it under "mounts and storage" in CWM. This will ensure everything got wiped.
Click to expand...
Click to collapse
I will provide you with log, but tomorrow, sleepy time here.
And yes, everytime I flash a new ROM, I do wipe everything, including Dalvik's, and I never had any problems.
Let's hope tomorrow more users will try this ROM on a US device and see if they too have the same issues as me.
SirRhor said:
I will provide you with log, but tomorrow, sleepy time here.
And yes, everytime I flash a new ROM, I do wipe everything, including Dalvik's, and I never had any problems.
Let's hope tomorrow more users will try this ROM on a US device and see if they too have the same issues as me.
Click to expand...
Click to collapse
Thanks for trying it out.
What is the version of the android?
2.3.6?
Sent from my YP-G70 using xda premium
kfirbep said:
What is the version of the android?
2.3.6?
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Yes. It is based on 2.3.6 XXKPH EU ROM.
Oh, I love AROMA Installer~ THX
@WT Ho,
I tried the ROM and selected Go Launcher the next time, and still gave me TW Launcher 3.0. It didn't even install Go Launcher. Also, the Play Store worked for me on Stock ROM. WiFi might have problems with this ROM, but I'll try it again from Stock ROM and give results.
I tried many configurations.
I was not able to reproduce the WiFi problem not turning on, same for Bluetooth.
When I choose to install the Device ID hack is when problems arise. I can connect to wifi but I can't log in to my Google account or my Amazon app store app account.
I choose different launchers and boot animations but I get no problems.
Here's the link for my installation log:
http://db.tt/bS4vPtjs
Sent from my YP-G70
SirRhor said:
I tried many configurations.
I was not able to reproduce the WiFi problem not turning on, same for Bluetooth.
When I choose to install the Device ID hack is when problems arise. I can connect to wifi but I can't log in to my Google account or my Amazon app store app account.
I choose different launchers and boot animations but I get no problems.
Here's the link for my installation log:
http://db.tt/bS4vPtjs
Sent from my YP-G70
Click to expand...
Click to collapse
Yes. Actually I can reproduce the Google log in problem when Device ID hack is selected. This is because the hack requires a directory "rom-settings" on the internal sdcard (i.e. /sdcard/rom-settings). You can manually create that folder on the sdcard.
I will upload a patched release that will create that folder automatically.
Trae329 said:
@WT Ho,
I tried the ROM and selected Go Launcher the next time, and still gave me TW Launcher 3.0. It didn't even install Go Launcher. Also, the Play Store worked for me on Stock ROM. WiFi might have problems with this ROM, but I'll try it again from Stock ROM and give results.
Click to expand...
Click to collapse
I wonder if you have done a data wipe AFTER installing the ROM? If you do that, you will wipe all the apps that are stored on /data including the launcher you installed.
If that's not what happen, I have to look at your installation log, which can be saved at the last step of the installation.
Just uploaded a patch release V0.2.1. That should solve the Google login problem.
Bad news, I've tried 3 times already, with and without the Device ID hack, but it goes no further than the Samsung Logo.
My log:
http://db.tt/amy2ayTR
Sent from my YP-G70
[ROM]FOXHOUND DIAMONDDOGS 3.65UPDATED4MDKtoMK2&AnyCarrier-SS-NOKNOX-CLEAN-FAST-THEMED
Gogolie'sROM Port: Foxhound Diamond Dogs 3.6 MDK THRU MK2 COMPATIBLE & ANY CARRIER COMPATIBLE = VZW - AT&T - TMO - SPR THERE IS NO FORCED KERNEL OR MODULE INSTALL! (NECESSARY FOR SAFESTRAP PLEASE MODERATORS DON'T MAKE ME INCLUDE ONE ITS NOT NECESSARY FOR OUR PHONES!)
This very quick little TW rom is awesome its my daily. New update allows for zip install to any slot on SafeStrap or through any custom recovery. AT&T and other carriers may need to flash your MK2 modules or add in TMO APN/ AT&T APN / SPRINT APN settings to get this beast working 100%. If that didn't fix your problem then you need to install the GSM / LTE carrier modem (just guessing that your GSM if you can't get this going as thats been only complaint of lost data and he was able to fix it with proper carrier modem). If these options are too difficult I'll be posting my own comp packs for major carriers below in download sections zip install immediately after installing ROM.
Known issues/Not Working (only for select users):
No known issues exist, if you find a reoccurring bug that has not been addressed here or in the Int section please post.
Issues with not having "stockish on stock slot" may occur by having a heavily modified/themed ROM in stock slot using SafeStrap.
If it doesnt work for you I'm sorry your best bet if your on VZW is SS but with thousands of downloads and hardly any issues across the board with the 1st release I think that speaks for itself... ALL My ROMs rock and are fixed ports or originals and bug free for me or I wouldn't release them. Otherwise this thread would be a mile long like some other Roms that need constant support! Enjoy took me some time to put together so if it works thank me or better yet donate so you can see updates and more roms!
This is a port of the Foxhound Diamond Dog Team's v3.6 w/ ML6 base using a essential only install w a lot of mods and a clean diamond boot animation, included 4.4 apps and a sound/volume mod with the ultra sharp Foxhound theme. Updated all parts of ROM like Xposed / Play Store ect that were giving users some issues before.
Remember I myself nor XDA is responsible for any actions or mistakes or decisions you make with your phone. Installing a custom ROM is a personal decision I say flash it all but thats my decision. However a bit of insight would tell you there is no kernel forced installed like most ROMs try to do so there is much less chance of any errors or issues or bricking because of this. I recommend installing MK2 stock or your favorite kernel and trying and experimenting with this yourself.
Lil about me: I'm a now broke, technically I'm disabled (w/ 4 crushed discs in spine the gov says I'm too young to get disability and shouldn't admit that MMJ medicine works for me they=heartless pricks)I'm a full time single parent of a 1 yr old so Idon't get a lot of time for my passions anymore. ex award winning programmer (lost the love for it, be sure to copyright anything you intellectually own especially when it comes to working with G or MS. they'll steal your everything claim you signed it over and hang you out to dry) now i'm just a fellow android lover with a knack for making things work when they normally won't, experimenting, coding,scripting, anything I feel like doing so if this or any of my other creations or additions to your phone helped you in any way help keep my kid in fresh diapers or put a beer in my hand please. Anything is better than nothing I have spent countless hours learning testing and everything in between to bring you cool stuff like this. Thanks!
PS Sorry to all the fans of my ROM ports I had promised updates and made them but wasn't able to post on here because I didn't offer support or own a sprint phone (even though I fix/root and install my roms for customers of my home business on all national carriers without issues:!) Let em hate eh if I suddenly vanish and stop responding or supporting my threads (give me a few days to respond to PMs and questions) or my accounts not active find me at Infamous Forums. Thanks again for all the donations and support. I do this for the users that like their phones to have options. Not for the money or fame (LOL get treal i love the accusations they funny but come on play nice other devs lying about my stuff)
NEW DOWNLOADS: (Install .zip in any Custom Recovery. Tested on Philz and TWRP.)
UPDATED ZIP FOR "GOGOLIE'S UNOFFICIAL SLIM" VERSION 3.65: LINK(Ignore the .zip header info it says Phoenix 7.3 I forgot to modify its not it is Foxhound DD 3.65 too much work being done to update)
NEW WALLPAPERS TO TRY:
#1, #2, [URL="http://feb.imghost.us/G7oG.jpg"]#3[/URL], #4, #5
ALTERNATIVE LOCKSCREENS:
#1
OPTIONAL GPS FIX INTL: LINK (thx poeypresents/thedoman/jrkruse)
MORE DLs SOON LIKE COMP PACKS FOR SPRINT, TMOBILE AND AT&T **THESE ARENT NEEDED TO INSTALL IF OP IS FOLLOWED
OLD VERSION Download SS/TWRP Install by Restores:
https://docs.google.com/uc?id=0BwL6-n3ZMcedTzY1WFJ4N1dEQ2s&export=download
or
https://docs.google.com/file/d/0BwL6-n3ZMcedTzY1WFJ4N1dEQ2s/
Install:
Unzip into your new SS backup dir into your backup Safestrap folder in a folder like gogolies-Foxhound3.6 make sure all files are simply in 1 folder and that folder is in your backup directory and restore to a ***blank/newly created or STOCK*** rom slot. I went super small as small as SS would allow for slot creation. If your getting an error on restoring be sure to try deleting the slot and re-adding it then restoring the system files. If your WiFi doesn't work try flashing MJ7 or MK2 SS modules but only flash modules after 1st booting up rom and knowing wifi isnt working. 1st boot takes time plz allow a minute after loading up 1st time after 1st boot. Startup time is fastest SS rom I've seen. FH Apps and Settings contain xposed and modules for it and can help u customize and tweak it a bit but are installed as system files and don't let you update easily but it can be done I suggest just leaving it until another release or read down in the thread for details on how to update if you must..
Special thanks to: you fools that downloaded this to help test and found little to no actual issues... or specific user issues... THCX boys!
Surge1223, Hashcode, rarffaele88, snakes, jrkruse, ktoonsez,open1your1eyes, sbreen94, k1mu, old&slow, beanstown106, Dubbsy, invisiblek, nitroglycerine33, jovy23, andybones and anyone else contributing anything toward development!
-gogolie
Screens from VZW:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below is a copy of what raffaele88 said in his original thread please thank him and anyone associated.
raffaele88 said:
Based on last firmware
Deodexed & Rooted
Unlimited SMS recipient list
Disabled scrolling cache
Removed bloatwares (Available on zip)
Large APN list
Insert Xposed Framework
Battery 1% mod
Insert module for Xposed
DPI Changer
Market multi DPI inverted
Rom are Themed and costumizable with Xposed
Insert Rom Control in Settings
Enabled Call recording
4 Way reboot (Recovery,Download…
Hacked Stock Email App
Latest SuperSu update
Ota Update
Enabled all supported languages
Enabled call button on Contacts list
Auto wipe cache & dalvik-cache before flashing
Insert back button in Browser
Removed boot sound
MultiCSC
Busybox
More...
Installation
Full wipe or without wipe
Essential Rom or Normal
Theme
Foxhound Black theme
Samsung
Keyboard*
Google
Samsung
Camera*
Samsung
Google
Kernel
Stock
faux
Launchers
Nova launcher
Apex
Touch Wiz
Performance Mod
SQlite
EXT4
GPU
Boot Animation
FoxHound Diamond Dogs
Google edition
Font
Foxhound (smaller)
Stock
Google Edition AOSP 4.4 Kitkat
Calculator
MMS
Calendar
Clock
Sound Mod
Viper4Android
Boost Audio
* Both application can be installed
1.Downalod Rom
2.Put in your Phone memory
3.Reboot in Recovery
4.Wipe data in you came from other rom (optional)
5.Select Zip and install
6.Reboot enjoy
LINK
Donate Rya Engel: Link
Donate Denny: Link
Rixsta for theme base link
Nottach for module link
Wanam for kernel
Rovo89 for Xposed framework link
Vertmus for Domination theme
Click to expand...
Click to collapse
Dude you are awesome!
Sent from my SCH-I545 using XDA Premium HD app
looks absolutely amazing man! I will be hitting this up on my next day off, thank you for this!
im confused where to place the folder once i download the zip. i dl'd the zip. extracted it to my phone. made slot 2. went to restore in SS but cant find the folder to restore? how do i go about this?
chrismyu said:
im confused where to place the folder once i download the zip. i dl'd the zip. extracted it to my phone. made slot 2. went to restore in SS but cant find the folder to restore? how do i go about this?
Click to expand...
Click to collapse
unzip the file you just downloaded into the folder where your backups are saved. for me its TWRP>BACKUPS>6056c852.Then you select rom slot 2(or make a slot 2).In the main menu select restore and you should see the file you unzipped with the rest of your backups if you have any. I just did it and this maybe my new favorite! Hope this helps you out
Downloading!
Sent from my SCH-I545 using xda app-developers app
This looks very nice. Looks like I may be updating to mk2 if /when I find the time. Thanks
Sent from my SCH-I545 using XDA Premium 4 mobile app
Working great on MK2 SS AT&T S4!!!!!!!
Is there a possibility of a version for those of us still running mdk/lokid?
Sent from my SCH-I545 using Tapatalk
Mine keeps failing, says no partition selected.
The rom is great but it keeps screwing with my hangouts. One minute it'll work then the next it won't show
Sent from my SCH-I545 using XDA Premium HD app
How do I increase the system partition, when I hit the + sign nothing happens.
Looking forward to another choice!
It looks like a very slim and smooth rom but still packed with features we need. But may i ask why rom slot 2? What, your roms too good for slot 1? , Also, how many ppl on MJ7 have tested it without updating? (Just curious). Thanks again for the new toy!
Got this one up and running and I suppose the others I had tried in the past would work now to.
After some input in various threads by @Surge1223 , it came to my attention that I should try ODIN back to MJ7 and stick there instead of updating to the MK2 bootloader if wanting to run HD RLS12 in stock side which is my preference.
After I did that and restored my Nandroid of HD RLS12 to stock side then had to apply the MJ7 module, all was well.
Created a slot, and this time was able to get this up and running via restore to slot. 1st time of success with that with any ROM whether via Nandroid Restore or flashing to.
Monkeying around with it now, so far so good. One thing I notice is with Xposed Installer, In the settings under 'update' , there is an update available for it but it won't install - says something about package with that name and different signature found.
---------- Post added at 08:43 AM ---------- Previous post was at 08:23 AM ----------
Update: Root Explorer shows nothing as in will not load up directories just black screen?
Update #3: Nevermind about Root Explorer. User error. I mistakenly restored app & data from it via TIBU. I uninstalled and restored App only and all is well now!
shindiggity said:
How do I increase the system partition, when I hit the + sign nothing happens.
Click to expand...
Click to collapse
The system partition size is pre-set in the app code. To my knowledge you can't resize it. Maybe if you rewrote the script but im not there yet. Ppl tend to forget safestrap 3.7x is still beta.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seems like a sweet rom. I havent had time to restore my apps and what not but im looking forward to a test drive. On MJ7 btw...
Restoring this ROM to my slot failed. I'm rooted on MK2 with SS 3.71 installed. Was able to load the Omega ROM, but not this one.
Sent from my SCH-I545 using xda app-developers app
This ROM is awesome! Super slick and good looking.
You may want to put this in your instructions.
If you can't find where the backup folder is go into safestrap and make a backup of the cache on stock ROM.
Then extract the .zip file to the folder with the cache backup and has allot of numbers and letters on it.
Sent from my SCH-I545 using XDA Premium 4 mobile app
rslu2 said:
Restoring this ROM to my slot failed. I'm rooted on MK2 with SS 3.71 installed. Was able to load the Omega ROM, but not this one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I know I said I wouldnt be offering support on this one but since you were kind enough to try my first omega version that and I really really like this rom over any others and I've ported a good 10 new ones to the phone now
have you tried deleting the slot and then remaking it? not sure why but that seems to work if its failing restore. then just restore system files I actually just had to do this earlier after finishing up omega v19 sorry I am not able to see whats the issue I believe its something with the way safestrap is "formatting" or something. hope that helps no Idea if that doesnt work you might be in the restoring boat like lazer9 had to do that method will work for those unable to install this as is. odin mj7 reroot then ss then whatever. Oh and you don't have to put this on Slot 2 I just included it incase it still mattered in safestrap whether or not you restored to same slot but it does not matter apparently. So install to any slot should work fine probably even stock if someone dared try? same with MJ7 users just flash modules if it doesn't boot up first try. obviously theres some different issues with various parts of the rom plz continue to post your findings guys. I promise nothing but I'll help if I can.
I found the first problem,
For me you can't download apps from play store, any tips?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Well here's the continuation of BarRin. But now with ZV8!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Proudly Presents...
Courtesy of and Thanks to @BonezMontana!!
See post #2 for additional files
See post #3 for possible bugs/ issues and fixes
Anyone can use this as a base to build from. Just give credit.
What is has:
This is the ROM, Kernel, Modem, and rpm,tz partitions
Rooted
busybox
Install
In TWRP, select Advanced, Wipe, then /system, /cache, /dalvic, and /data.
You can wipe internal and ext SD. BUT MAKE A BACKUP OF YOUR FILES FIRST!! And don't wipe Ext SD with TWRP. Format it FAT32 on a computer.
Flash Rom
Update profile/prl
Go to "Settings, More, Mobile network, and select anything but "Global
"L" needs to settle in. Don't get in too big of a hurry adding all your apps.
Change logs :
Code:
[B]BarePops_Updates_DPI-580[/B]
Nothing big, Just changing the DPI to 580. With Updates_V1 included
[B]BarePops_Updates_V1[/B]
Just a little update that should work with Any/All ZV8 Rom - dirty flash OK
Stock kernel with init.d support
init.d scripts - sqlite3 and zipalign for /data/apps only
build.prop tweaks - not really sure about these, but we'll see
[B]TE_V1 - Themers Edition[/B]
Same as V2 +
As deodexed as it can be - LGSettings isn't working deodexed yet
Updater-script change - lets see if this fixes some install issues for some
NOW USING ZV4/6 rpm,tz partitions - should fix restores to KK Roms and some reboot issues
[B]V2[/B]
Same as below +
More bloat removed - Weather and Concierge/SmartCards gone
SD Card fix
[B]V1[/B]
Odexed
Removed most Sprint and LG Bloat and tattletales
Apps moved to /data
Oversharpening fix
busybox - trying a different way because L in so new. Updatable through this app.https://play.google.com/store/apps/details?id=stericson.busybox
removed Sprint boot ani and sounds
increased mixer paths
fixed build prop - All Splitwindow, increased Qslide
Concierge board and LG Weather are still in it
Donators - THANK YOU - Never asked for, but very much appreciated!!!
@budeone
@AlwaysLucky
@nkyer
@RustedRoot
@mjjcb
@cabbieBot
@AcE XBOX
@FerretPD
__________________________
Downloads - Full Roms:
BarePop_TE_V1 - Themers Edition - Deodexed - Full Rom - Clean install - Rom, Kernel, Modem, ZV4/6 Partitions
Just another flavor - As deodexed as we can for now.
Possible issue- on install, Apps may automatically hide. Just choose show in settings.
BarePop_V2 - Full Rom - Clean install - Rom, Kernel, Modem, ZV8 rpm,tz Partitions
BarePop_V1 - Full Rom - Clean Install - Rom, Kernel, Modem, ZV8 rpm,tz Partitions.
__________________
Downloads - Updates for all above
Barepops_Updates_DPI-580
BarePops_Updates_V1 - Just an update for the above Roms and it SHOULD work with any ZV8 Rom. Dirty flash is just fine
XDA:DevDB Information
BarePop, ROM for the Sprint LG G3
Contributors
engine95, HPTesla, seanskiT!
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2015-02-20
Last Updated 2015-02-19
Additional files
Additional files and what-not'sFor V1 or Stock. V2 already has it SD_Card_fix - This should fix the SD Card issue people are having. But if not, see Post #3
For V1 only SmartCard_fix - This will fix Smart Cards/Notifications in V1. Just flash it.
This SHOULD work for ANY ZV8 Rom. ZV8_Stock_init.d_Kernel - if you are stock, you may need busybox installed.
To see if it's working, in a rooted explorer, look in /data and see if it has "Test.log."
For any ZV8 stock based ROM. BarePop bootani Courtesy of @HPTesla
If you have issues installing it, see post below.
Can't download anything? Flash THIS - stock host files.
Bugs/Possible issues and fixes
To remove the Sprint boot animationIf you want to remove the Sprint bootani. Or just be able to install a custom bootani. You will need to do this:
1. In a rooted explorer, go to /carrier/cust/poweron/ and delete those files so the folder is empty.
2. Then do the same with /carrier/cust/poweroff.
3. Go to /system/media and delete the "Sprint_bootanimation.zip". Make sure you leave the "bootanimation.zip" in there.
4. If you don't have anything in the /carrier/cust/ poweron/poweroff folders, don't worry.
If you use Flashtool, they will be there again. That's the only way to get Sprintbootanimation back.
Read this post also. Cleanest install
This will give you the cleanest install without using Flashtool.
Of note, if you do this, when finished, you'll need to reinstall the ROM. The apps in /data get wiped. So you will be missing some stuff.
Bugs/Possible issues:1. This is gonna sound weird, but....sometimes it boots too fast and the lockscreen will freeze. Just give it a minute. All is well
2. The LG Keyboard, may not be able to be removed until it is updated by LG. It can't be moved to /data yet - Just be aware if you remove it.
Install, TWRP, ReceptionI don't know if it's a TWRP thing or not. Here's what I've seen, but it is few and far between but does happen on occasion:
1. As was said earlier, if you need to wait longer than 5 min to get the setup screen, you'll need to pull the battery. Then you can try and flash it again dirty, or do all the wipes again and it'll flash. Really weird.
2. Rarely, but when making a backup in TWRP, it'll take forever. I just pulled the battery, rebooted to the ROM, and let it sit for a few minutes. Then the backup worked fine in TWRP.
3. Sometimes reception just wont work. So update profile/prl and if it still doesn't work, reboot and update them again. That will fix it. And I'm using the rpm,tz partitions.
I don't recommend pulling your battery while in recovery, but sometimes you just have too. Just be forewarned you may need to use Flashtool to fix it.
I've been using TWRP 2.8.3 I think is the version.
SD cardsSD cards are becoming an issue for some reason. If you've followed ALL the instructions in the OP, and are still having issues, you may need to wipe your ext SD. And sometimes Internal as well.
Some people are using an app from the Playstore to fix SD issues. SeLinux Changer, and set it to permissive.
Remove your ext SD and boot up.
If the problems are solved then you need to format your SD card in Windows or Linux as Fat32 no matter what size your card is. DO NOT USE TWRP to format Ext SD.
RootIf SuperSU has issues updating it's binaries, you may need to flash This when you flash the ROM.
GSM UseSome people are able to use this ROM on GSM. YMMV and I can't/don't support this. HERE
Cant wait
Sent from my LGLS990 using XDA Free mobile app
Downloading now! Thank you!
GREAT!!! WORKS PERFECTLY!! THANK YOU FOR YOUR HARD WORK!!!!:thumbup:
Sent from my LGLS990 using XDA Free mobile app
Testing
Will toy with this after work. Was running ZV8 perfectly until I flashed Xposed without a backup and kept getting Circle Case force closes and went back to ZV6. Hopefully I can make this my daily though. Can't wait for G3 toolbox to return for the L.
Sweeet! You blow my mind. Thank you.
This looks like my new home for a while.. cant wait to get into work so I can play!!
CyanJustice said:
Will toy with this after work. Was running ZV8 perfectly until I flashed Xposed without a backup and kept getting Circle Case force closes and went back to ZV6. Hopefully I can make this my daily though. Can't wait for G3 toolbox to return for the L.
Click to expand...
Click to collapse
You couldn't just re-flash zv8 on top of it to eliminate the changes xposed made to /system?
---------- Post added at 08:13 AM ---------- Previous post was at 07:56 AM ----------
This uses SuperSU by chainfire as default root app, correct?
RandomPooka said:
This uses SuperSU by chainfire as default root app, correct?
Click to expand...
Click to collapse
If that's directed at me, yes.
That's the one Team Codefire recommends with Bump. So I'll stay with it.
Thanks a lot for this Engine. Hopefully theming Zv8 will go easier than extracting/assembling it did. A quick question... I flash the zv8 partition zip right before Barepop, correct?
Thanks
:highfive:
RandomPooka said:
You couldn't just re-flash zv8 on top of it to eliminate the changes xposed made to /system?
---------- Post added at 08:13 AM ---------- Previous post was at 07:56 AM ----------
This uses SuperSU by chainfire as default root app, correct?
Click to expand...
Click to collapse
Ah crap, wouldn't that format data?
Since i already installed stock zv8 can i flash this over it?
Sent from my LGLS990 using XDA Free mobile app
Thanks!
Followed the simple instructions and flashed with no problems.
Updated all and going to let stock run over the weekend before I try Xposed or any other customizations.
CyanJustice said:
Ah crap, wouldn't that format data?
Click to expand...
Click to collapse
Typically, no. Not with AOSP and stock based KK ROMs. I don't know off the top of my head if @engine95 had put a data wipe in his install script to make the craziness that is L work properly.
Also, that SuperSU question was directed at you
Does this ROM have anything done to it to alleviate the 5.0.1 stock ROM issue of massive memory leaks that cause apps to close quite aggressively in the background? My brother has 5.0 on the Sprint S5 and his issue is actually worse than mine.
Thanks for this engine95 and the rest of team Stooge ?
Tried running ##Update# in the dialer when phone shut off it would not turn back on. I removed the battery for a min and tried again it still wouldnt turn back on. After 5 mins with battery pull phone finally turned back on. I dont know if this was just something weired with my phone or could been caused by the rom. Either way just thought i would bring it to your attention. Im currently up and running again with no problems. Thanks engine for bringing us Lollipop :victory:
Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.
so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)
New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid
Thanks you for the ROM!
This is This is stable or beta or testing? Thanks
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....
Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.
yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...
New build 18032016 is up on basketbuild and Google shares
Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.
drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF
PpPmod for Realme UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About PpPmod
PpPmod is a port of the excellent xXx NoLimits magisk ROM for Oxygen OS. It's a systemless modification to the default Realme UI that allows the user to get much more out of his device than the default configuration allows.
But why a magisk ROM?
For two reasons:
1. Realme devices offer good price to performance ratio, but in many cases they lack a developer community around them to build those ROMs the users want.
2. Realme UI is not that bad honestly. It offers good performance, it's not too crazy aesthetically and its bloatware isn't baked deep into the system.
It's also a much safer way to modify Mediatek devices. As long as you've managed to root your phone, you are good to go. If something goes wrong, just wipe data and no harm, no foul.
Supported devices
While in theory, any Realme device with Realme UI v1, Android 10 and a full HD screen resolution should be compatible, the only two devices this has been tested on are a Realme 6 and a Realme 6 Pro. For the curious, i own the later.
Ok, but what does it do?
- Port of xXx NoLimits for Oxygen OS
- Fully systemless Realme UI ROM mod for magisk
- Designed to work with all phones that run RealmeUI v1, Android 10 on full HD screens, including MTK ones
- Fully configurable installation, every component is optional
- Includes comprehensive debloating options
- Optional build.prop tweaks
- Many kernel tweaks that can be adjusted and combined, in order to target different degrees of performance and battery life
- 90hz/120hz for ALL apps when the display is set to its high refresh rate
- GMS Doze included
- Ability to disable analytics
- Ability to disable wakelocks
- Can enable full screen gestures (swipe up) for 3rd party launchers
- Ability to set custom bootanimations from a built in list, or as a user selected bootanimation.zip
- Includes extra launchers, sounds and icons from popular device brands like Pixel and OnePlus
- Gcams for both Qualcomm and Mediatek devices are included (by Urnyx and onFire)
- Youtube Vanced, detached from the playstore so no pesky updates can override it
- Google Dialer and Contacts, both old and new versions
- Custom density modes
- Ability to systemize apps
In order to set your own bootanimation, place a bootanimation.zip inside /sdcard/PpPmod. You can also place a shutdown/restart animation named rbootanimation.zip there. Make sure that your bootanimations are 1080 pixels in width, or they won't work as you'd expect. If you set option CustomBootAnimation to 1 in PpP.profile, your animations will be used during start up and/or reboot, instead of the default ones. For more information about the PpPmod folder and the PpP.profile file go to Installation Instructions.
If you want to systemize an app for whatever reason, just place the apk inside /sdcard/PpPmod/apps., before flashing.
Concerning debloating there is a master switch you should toggle if you want your individual options to work. Set IndividualDebloatSelection to 1.
Installation Instructions
You will find detailed installation instructions along with download links on post #3
Screenshots
For screenshots, press here
Thanks to:
xXx
ahmed_radaideh
dustintinsley
gloeyisk
k1ks
andip71
linuxct
Mostafa Wael
mrRobinson
osm0sis
rufus.wilson
snowwolf725
topjohnwu
Zackptg5
ZaneZam
Kevin Saiza
Tytydraco
XDA:DevDB Information
PpPmod, ROM for the Realme 6
Contributors
FatherJony
ROM OS Version: Android 10
ROM Firmware Required: RealmeUI
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-09-14
Created 2020-09-03
Last Updated 2020-09-14
Changelog
Version 1.1
Fixed a bug where enabling HighRefreshRate had no effect on the first boot after installation.
Updated Google Dialer to the latest version.
Updated sqlite to the latest version.
Reworked kernel tweaks, with some inspiration from Ktweak by tytydraco.
New ReadAhead option added. This allows the user to disable, or set the readahead cache to a percentage of the device's memory. Default is 1 (cache disabled).
New CPUGovernorTweaks option added. When this is enabled, schedutil and interactive governor tunables are tweaked in order to increase performance. The default governor will also switch to schedutil or interactive depending on availability. Default is 1 (enabled).
Reworked CPUInputBoost option to make it more granular. You can now select from small, medium, high and max presets. For more info about them read the profile description.
Reworked CPUStuneBoost option to make it more granular. You can now select from small, medium, high and extreme presets. For more info about them read the profile description.
Installation
PpPmod allows for a fully customizable installation. The way this works is via a configuration file called PpP.profile. You will always be able to find the latest version of this file on this post. Make sure you edit this file on Notepad++ if you are opening it on Windows in order to preserve the Unix EOL format.
Requirements:
Realme UI v1 on Android 10 and display width of 1080 pixels
A working Magisk installation of v20.4 or higher
PpPmod should only be flashed via Magisk Manager
First time installation:
Place PpP.profile in /sdcard/PpPmod/ and edit it to personalize the installation to your liking
Flash the PpPmod zip via Magisk Manager
Reboot. Wait for at least a minute to let all installation options take effect.
Done
The first time you install, chances are that the PpPmod folder will not be in /sdcard, so you have to create it yourself. If you don't place PpP.profile there, the mod will be installed with the default options when you flash it and place the default PpP.profile inside /sdcard/PpPmod/.
Update to a newer version:
Open Magisk Manager and uninstall the previous version
Reboot
Wait for a couple of minutes after reboot as the uninstallation process can take some time
Install the newer version via Magisk Manager. Don't worry about changes to PpP.profile, they will be merged to your older version profile
Reboot. Wait for at least a minute to let all installation options take effect
Done
Uninstallation:
Press the waste bin icon next to the mod's name on the Magisk Manager
Reboot. Wait for a couple of minutes after reboot as the uninstallation process can take some time
Done
Downloads:
PpPmod v1.1
PpP.profile v2
PpPmod v1.0
PpP.profile v1
FAQ
Q: I just installed PpPmod and my phone has heated up and stutters, is this normal?
A: Yes, the installation process is fairly intense, and during the first boot following the installation, a lot of stuff happens in the background. Just let your phone settle for 10 minutes and it should be fine.
Q: I did all that and my phone still heats up, you liar!
A: Well, check your settings. PpPmod offers many options for tweaking, but not every one of them is suitable for all phones, or all usage patterns. In general, the higher performance settings may be fine for general usage and offer you a flagship like experience along with a high refresh rate, but will cause excessive heat and throttling during gaming.
For example, maybe a 12nm chipset shouldn't be pushed aggressively by enabling CPU boost options, especially if you game alot. You may gain a brief performance boost that will sooner or later be the cause of intense overheating, which will cause throttling, which will cause stutters. In short, try to be reasonable with your settings and expectations, PpPmod will not magically turn your mid range chipset into an SD865.
PpPmod is also not designed to work along with other magisk mods that adjust performance by altering kernel behavior. If you want to use such mods with it, try disabling every PpPmod performance setting, like:
KernelTweaks
LMK_RAM_Management
ReadAhead
DisablePeWq
DisableHotplugging
IncreaseMinGPUFreq
CPUGovernorTweaks
CPUStuneBoost
CPUInputBoost
The result may still not be ideal, but this is your best bet.
Q: My debloating options aren't working!
A: You forgot to set option IndividualDebloatSelection to 1.
Q: I think i found a bug, what is the best way to report it?
A: You should always include a detailed description of what triggers the bug, its effects, your specific phone model (including hardware characteristics like RAM and storage), firmware version, your PpP.profile and preferably a logcat from when the bug occurred.
Q: Can i be a beta tester? I swear i am awesome!
A: As long as you meet certain conditions, sure! The conditions are:
First and foremost, you must understand that beta testing doesn't mean early access. Most of the time you will have to do things that may be inconvenience you, or lead to loss of time and data (factory resets)
You should know at the very least how to setup and use adb
You should have A realme device with Android 10 and Realme UI v1
Q: Can i ask for a feature?
A: Sure, but keep in mind that PpPmod isn't primarily geared towards a specific device. So while device specific features are not out of the question, priority will be given to features that affect a range of devices.
Q: My phone isn't listed in supported devices, but it's a Realme device with Realme UI v1, Android 10 and a full HD resolution, should i give this a try?
A: Yes, as long as you don't mind resetting your data if something goes wrong, you should. That's exactly what i am trying to achieve with this mod. Normally, a new phone like for example the Realme X7 Pro would not have any options for customization on release, and may never get much due to the Mediatek soc. But PpPmod should work immediately, at least in theory. Even if there are some device specific issues i will do my best to fix them, and in the worst case scenario the phone is still safe from any permanent harm. Just reboot to recovery and reset data.
Q: PpPmod sucks and i wanna uninstall it. Must i also remove magisk?
A: NO, you don't have to and in fact you shouldn't if you don't have a reason unrelated to PpPmod, as magisk resides in your boot partition and thus unlike PpPmod, can mess with your device if you aren't careful.
Q: What does PpP mean?
A: No one knows fo sure. Some thik that it means Pro Plus Prime. Some other, less charitable persons claim it means PapaPowah instead. We may never know the truth.
Q: What do you plan for your next project?
A: Rewriting Android in Objective Cobol
Q: Is it true that you are actually a boomer?
A: Ok, that's enough. You guys have crossed the line and now i am forced to conclude this QA session.
FatherJony said:
Reserve
Click to expand...
Click to collapse
Good job dude
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
PapaSid26.12 said:
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
Click to expand...
Click to collapse
Yes, it works. But the whole point of a systemless mod is that you CAN'T brick your phone. Worst case you will just have to wipe data via recovery.
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
marvinvvh said:
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
Click to expand...
Click to collapse
I am sorry to hear that about the EU version. I thought that this would have been resolved by now. Unfortunately this is a magisk mod, thus it doesn't work without magisk.
Even after making changes in PpP.profile I'm getting default settings
Shanpatil said:
Even after making changes in PpP.profile I'm getting default settings
Click to expand...
Click to collapse
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
FatherJony said:
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
Click to expand...
Click to collapse
Can u give some SS??
I bricked my phone...
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
fraillesgeon said:
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
Click to expand...
Click to collapse
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
FatherJony said:
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
Click to expand...
Click to collapse
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
fraillesgeon said:
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
Click to expand...
Click to collapse
I did the same mistak. Howevre here is a solution.
If you have sd card, download latest ozip file from realme wessbite and place in root of sd card. Then insert it into your realme 6 and boot into recovery using power and vol down. After that install zip from total storage and install from sd card. Hopefullt it will be back.
On an another note there shall be some key combo for booting into fastboot mode
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
I'm back!
FatherJony said:
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
Click to expand...
Click to collapse
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Can you do the step by step process on how to flash it using magisk?
fraillesgeon said:
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Click to expand...
Click to collapse
Great news! I am really glad you were able to save your phone. As a rule, only use internal storage (/sdcard) for important operations.
I am looking forward to your impressions!