Now that Dev Preview of Android 11 was published I would love to test it. Of curse I don't want to install it on my phone since it's my daily driver and especially the first previews are buggy as hell besides not working apps. Emulators are just slow as hell.
Now, Google did introduce Dynamic System Updates https://developer.android.com/topic/dsu a few month back to let GSIs run like a Linux Live distribution and to get rid of it via a simple reboot without any trouble like having to reset the device to flash the ROM.
Has anybody tested DSU installation in general and especially with the GSI of the Dev Preview? I followed it step by step, I even tried using simg2img system.img system_raw.img on the img but only got "Invalid sparse file format at header Failed to read sparse file" back.
On my phone the Dynamic update does start and asks me for my fingerprint but the notification just says "installation failed". Sadly I couldn't find a way to make adb shell print any information why it failed. Did anybody else have more success?
PS: since the commands seem to be written for Linux I tested it with Debian 10 inside the Windows Subsystem for Linux. I don't think it should make a difference though.
Have you unlocked the bootloader of your phone? DSU requires an unlocked bootloader.
I successfully installed the Android 11 GSI on my Pixel 3 XL using DSU.
MishaalRahman said:
Have you unlocked the bootloader of your phone? DSU requires an unlocked bootloader.
I successfully installed the Android 11 GSI on my Pixel 3 XL using DSU.
Click to expand...
Click to collapse
Did you download the GSI from here?
Might give it a go through DSU on my phone.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
Did you download the GSI from here?
Might give it a go through DSU on my phone.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Yes.
MishaalRahman said:
Yes.
Click to expand...
Click to collapse
Sweet, thanks :good:
Sent from my Pixel 3a XL using XDA Labs
To both questions yes. I fear magisk is the one that might cause the falling. That would be sad
Artim_96 said:
To both questions yes. I fear magisk is the one that might cause the falling. That would be sad
Click to expand...
Click to collapse
That would make sense.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
That would make sense.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Sideloaded DP1 yesterday and running nicely tbh
Skittles9823 said:
That would make sense.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
It would make sense, but it doesn't seem to be true. Deactivated magisk by flashing stock boot image, tried again... Same result
Artim_96 said:
It would make sense, but it doesn't seem to be true. Deactivated magisk by flashing stock boot image, tried again... Same result
Click to expand...
Click to collapse
Are you current running stock Android 10?
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
Are you current running stock Android 10?
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Yes. Latest stock Android, never had a custom ROM or recovery installed on my Pixel
Artim_96 said:
Yes. Latest stock Android, never had a custom ROM or recovery installed on my Pixel
Click to expand...
Click to collapse
Well, looking at the DSU documentation it does suggest you to be on a userdebug build. Stock is generally user unless you've built it yourself.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
Well, looking at the DSU documentation it does suggest you to be on a userdebug build. Stock is generally user unless you've built it yourself.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
It only says when you have a userdebug build you can activate that in the Flags. Else, you activate it via ADB shell
Artim_96 said:
It only says when you have a userdebug build you can activate that in the Flags. Else, you activate it via ADB shell
Click to expand...
Click to collapse
Ahh, fair enough. In that case I'm unsure, I'm currently running a custom rom I plan to stay on so I can't really fiddle around with flashing stock to test DSU.
Sent from my Pixel 3a XL using XDA Labs
Ok, I've made a log of the installation (with magisk still installed), from what I see it might abort because of too little space.
The question is only: is it too little space where I can make space or is it missing free space in a partition where it's not possible? And how much space do I have to free up? (Aka do I see it right I have to free up about 4 GB?)View attachment DSU.txt
Artim_96 said:
Ok, I've made a log of the installation (with magisk still installed), from what I see it might abort because of too little space.
The question is only: is it too little space where I can make space or is it missing free space in a partition where it's not possible? And how much space do I have to free up? (Aka do I see it right I have to free up about 4 GB?)
Click to expand...
Click to collapse
4gb probably isn't enough to install it.
Sent from my Pixel 3a XL using XDA Labs
Additionally, calculated from the numbers I've found in the log. I can free up nearly 6 GB additionally to what's already free by just deleting a Titanium Backup
From Stock 10 to RPP
Artim_96 said:
Additionally, calculated from the numbers I've found in the log. I can free up nearly 6 GB additionally to what's already free by just deleting a Titanium Backup
Click to expand...
Click to collapse
I went directly from stock 10 to RPP - and did NOT rely on an on-phone backup (which you are trying to do). Stock 10 backs up to the cloud (as has Android since 8) - this is by default. Samsung Experience included cloud backup, which OneUI retained (this is via the Samsung Members app). Dependng on your settings, you may not NEED to rely on on-phone backups any more. I use RPP as a daily driver - and have since it launched; however, Google doesn't recommend it - and I won't recommend it for anyone that hated Android 10 (The RPP is a superset of 10.)
PGHammer said:
I went directly from stock 10 to RPP - and did NOT rely on an on-phone backup (which you are trying to do). Stock 10 backs up to the cloud (as has Android since 8) - this is by default. Samsung Experience included cloud backup, which OneUI retained (this is via the Samsung Members app). Dependng on your settings, you may not NEED to rely on on-phone backups any more. I use RPP as a daily driver - and have since it launched; however, Google doesn't recommend it - and I won't recommend it for anyone that hated Android 10 (The RPP is a superset of 10.)
Click to expand...
Click to collapse
Of course I hope that I won't need Titanium Backups, because Google had more than enough time to figure out that problem themselves, especially on their own devices. It's more like a "better safe than sorry" solution. I just saved the backup to cloud so I hope I can try to install it tomorrow afternoon. Let's see if it was really only a problem of too little space
There are good news and bad news: the good news is I finally found out why the installation always immediately failed: you are required to have at least 40% free space on your phone. Now that I freed up enough space the installation starts.
There comes the bad news: the notification disappears shortly before the progress bar reaches the end, the installation falls again. At first I tried to install it with magisk still present, so I was able to make a log on device. It shows that it fails because it "failed to create or open data/gsi/dsu/userdata_gsi.img" and "File is too fragmented, needs more than 512 extents" (log attached). But I can't find a reason why. The same happened with stock boot.img flashed, I logged out through adb. (had to upload the log to GDrive since it's too big for xda and for pastebin: https://drive.google.com/open?id=1WEp5jydjYF2UmuLgOvx_fs4KGpJ1hKAq)View attachment 2020-02-26-19-00-05.txt
Related
***DEPRECATED***
THERE ARE FAR MORE FUNCTIONAL ROMS AT THIS POINT!
PLEASE VISIT http://www.kfsowi.com FOR MUCH BETTER ROMS!
I'm going to leave this up just because.
ROM
•°•KINDLE WATER Beta•°•
Beta 2
Based on 11.3.2.1, and I recommend NOT doing this on http://11.3.2.2/11.3.1.0 as I don't know if the kernel has changed to be incompatible. UPDATE: this IS compatible with other versions, there is just an extra step I added below.
Special thanks to Gran PC. Without his help, this wouldn't be possible.
So, what is Kindle Water Beta? Kindle water beta is a far superior firmware to the one that comes stock on our Fire HD's. Why you ask? This is why:
FEATURES:
•No Amazon Garbage
•No Lockscreen Ads.
(They show up again. Turn them off by going to /data/securedstoragelocation/ in a file explorer, select the adunits folder, and remove all permissions)
•No Unwanted Updates
•Wallpaper
•AOSP settings
•Cyanogenmod Gallery App
•Google Play Store & services included & working
•XPOSED Included
•Better navbar using UDN. (Configure in UDN app. Setting it to appear by swiping up from the bottom of your screen is the best way to configure it)
•Gravity box included (Set it to hide Navbar or you will get a double Navbar)
•APEX Launcher
BUGS:
•Not everything is set up perfectly on first boot. You may need to play with Gravity Box, Apex Settings, and UDN to get everything working right. (Specificaly: Set UDN's Trigger to be a swipe from the bottom of the screen, Hide Navbar in Gravity Box, and Turn on tablet ui in Apex if you'd like)
•Some Settings Menus don't work. (Only nonessential ones)
•"Wireless" and "Help" status bar pulldown shortcuts are broken
-------------
CHANGELOG:
•Beta 2- More internal Amazon things have been removed from the ROM.
•Beta 1- First release (Removed)
-------------
INSTALLATION:
(Disclaimer: I take no responsibility for broken devices, but I will try to help you fix it if it does not work)
(Downloads below)
(REPLACE "PATH/TO/DOWNLOADED" WITH THE PATH TO YOUR DOWNLOADED FILE!!!)
•Download Gran PC's minisystem image from his Google Drive page. (Link is posted below)
•Move my system.img (each beta version is in its own named folder in my Google drive, the link is below) to your kindle's SD card.
•Plug powered-off kindle into your computer with fastboot cable.
*•If coming from a version NOT 11.3.2.1, download the boot-prod.img from my Gdrive, (Same link as
Roms down below) Then type "fastboot -i 0x1949 flash boot /path/to/downloaded/boot-prod.img" and hit enter and wait for it to complete.*
•fastboot flash the minisystem image. (fastboot -i 0x1949 flash system /path/to/downloaded/minisystem.img)
•when it finishes, unplug the Kindle and turn it off.
•plug it in with a REGULAR micro-usb cable.
•It will boot up into a very minimal system. (No UI at all I believe)
•type "adb shell" hit enter.
•type "su" hit enter
•type "dd if=/sdcard/system.img of=/dev/block/mmcblk0p9" hit enter.
WAIT FOR IT...
•When it finishes, hard reboot your tablet.
•It should boot up and you're good to go.
•activate ALL xposed modules in the xposed installer app. This will enable wallpaper and block updates. Goto gravitybox's lockscreen area and enable rotation to fix it not rotating.
•lockscreen ads will show again. Turn them off by going to /data/securedstoragelocation/ in a file explorer, select the adunits folder, and remove all permissions).
Thats all.
DOWNLOAD ROM: https://drive.google.com/folderview?id=0B0MtKyW31T-BeGNva05paGJoRVE&usp=sharing
EACH ROM VERSION HAS ITS OWN FOLDER!!!
BOOT-PROD.IMG IS IN THE SAME LINK AS ABOVE! ^^^^ (I take no credit for this file. It is unmodified, Amazon code. Use at your own risk)
Minisystem.img: https://gmf.dabbleam.com/KFSOWI/minisystem.img
Shouldn't you be making backups before flashing.
Maromi said:
Shouldn't you be making backups before flashing.
Click to expand...
Click to collapse
Yeah, but I think that's a given.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
Will surely try this later on tonight.
The link to the minisystem img file is a 404
Flashing a ROM with no disaster recovery or at least a backup is risky. @Mineturtle33 do you have a source code for this? It's a nice start though. That tablet may get a full makeover yet.
Edit: If there is a source code available.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
The 2013 has a method to recover to stock, making backups its useless though because the system image is too big for fastboot's buffer, hence we have a weird recovery procedure. This is interesting, I'll have to check how big the system.img is out of curiosity.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
The 2013 has a method to recover to stock, making backups its useless though because the system image is too big for fastboot's buffer, hence we have a weird recovery procedure. This is interesting, I'll have to check how big the system.img is out of curiosity.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
The image is 1.22 GB
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
LinearEquation said:
Flashing a ROM with no disaster recovery or at least a backup is risky. @Mineturtle33 do you have a source code for this? It's a nice start though. That tablet may get a full makeover yet.
Edit: If there is a source code available.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
No source for the ROM, but I believe there is for the minisystem.img. Feel free to modify/redistribute this as much as you'd like.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
juanfers said:
Will surely try this later on tonight.
The link to the minisystem img file is a 404
Click to expand...
Click to collapse
Fixed the 404 error. Sorry about that.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
LinearEquation said:
Flashing a ROM with no disaster recovery or at least a backup is risky. @Mineturtle33 do you have a source code for this? It's a nice start though. That tablet may get a full makeover yet.
Edit: If there is a source code available.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
We have a recovery method.
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
stunts513 said:
The 2013 has a method to recover to stock, making backups its useless though because the system image is too big for fastboot's buffer, hence we have a weird recovery procedure. This is interesting, I'll have to check how big the system.img is out of curiosity.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Well,not quite. Gran PC found something called "fastboot multiflash" which allows you to flash ridiculously large system images. I don't know how it really works. You can check it out in his Google Plus post.
Sent from a piece of KitKat
The reason I use the minisystem to dd the system.img to /system instead of fastboot flashing is because the img file can't fit in the fastboot buffer. @Anonymous.123
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
Hi,
I've try to upgrade my kindle, but when I connect it with fastboot cable the system (Win7 32bit) configure it like Adb Android but the command adv devices not recognize any.
I also try with on Ubuntu 13.10 and also here the adb devices not recognize any.
Can you send me the driver you have used to install ?
Thanks a lot.
First of all. Make sure adb is on in settings. Secondly. You don't need adb until you install minisystem with fastboot. Use Ubuntu. I do not give drivers support for windows. @slim_s200
Sent from my KFSOWI Running The Kindle-Water Beta 1 ROM
Anonymous.123 said:
Well,not quite. Gran PC found something called "fastboot multiflash" which allows you to flash ridiculously large system images. I don't know how it really works. You can check it out in his Google Plus post.
Sent from a piece of KitKat
Click to expand...
Click to collapse
o.0 this is interesting i looked it up on google, very interesting way to implement that, if what i read is that same, then fastboot on the pc would split it up into several segments and then send them in multiple flashes. Thats pretty cool.
slim_s200 said:
Hi,
I've try to upgrade my kindle, but when I connect it with fastboot cable the system (Win7 32bit) configure it like Adb Android but the command adv devices not recognize any.
I also try with on Ubuntu 13.10 and also here the adb devices not recognize any.
Can you send me the driver you have used to install ?
Thanks a lot.
Click to expand...
Click to collapse
When you plug it in with a fastboot cable, you don't need adb commands, and adb won't see it. You need to use fastboot commands.
Sent from my Galaxy Nexus using Tapatalk
This is great!
Would you mind posting some screenshots of the AOSP settings and status/nav bars?
Forgive my ignorance, but what is the advantage does this have over CM11?
Sent from my GT-I9300 using XDA Premium 4 mobile app
bryanchapman9999 said:
Forgive my ignorance, but what is the advantage does this have over CM11?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well,none. But at least it is better than the stock Amazon OS. And by better I mean REALLY good? .
Sent from a piece of KitKat
Mineturtle33 said:
When you plug it in with a fastboot cable, you don't need adb commands, and adb won't see it. You need to use fastboot commands.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, but, I've ask fot the drivers because when I've try to type the fastboot command it returned the error "File minisystem,bin" not found!
I've check the path, but this is ok, /storage/sdcard0/FILE.bin and also try /sdcard/FILE.bin nothing change, any ideas?
Thanks.
Hi,
A while back I rooted my phone because I had had enough of missing out on xposed modules and had had enough with all the Ads!! When did Android become so riddled with adverts. (i know its not android itself before you say anything)
Anyway I managed to root my phone using the methods highlighted in the forum. I've got xposed working perfectly but I am still seeing averts in apps and on web pages. Correct me if I'm wrong but I should be able to hide these now. I've come from Galaxy S4 which I had rooted from day 1 so I never saw a single advert (in app or webpage) but now on my rooted Z5 I am still seeing a lot. Many apps (baconreader for example) have had the ads in there hidden but many still persist.
I've tried all the options I can see to be available to me
In no particular order and never installed at the same time incase they conflict.
- Adaway (this errors when applying the host file saying the copy failed)
- Adblock plus (app not browser)
- Adfree (this is what I used on my S4)
- MinMinGuard (tried different modes on this one and still no luck and no errors to speak of)
None of them error apart from AdAway.
Have any of you guys got a totally adfree experience on the Z5? If so how have you managed this?
I am using Adguard, it costs 8$ a year. That's almost free I think.
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Funkmasterchilla said:
I am using Adguard, it costs 8$ a year. That's almost free I think.
Click to expand...
Click to collapse
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
TimDawg said:
Thanks. I am aware of that option as it's what I was using before I rooted. (free version)
Not that $8 is a lot I don't see the point in paying for something when I can get a permanent solution for $0 so I'd like to know why the host method isn't working on my current setup.
Is there anybody with a rooted Z5 that has blocked all adverts using the host modification method?
Click to expand...
Click to collapse
AdAway is working for me.
Like I said ensure you can remount /system as r/w.
Sent from my E6683 using Tapatalk
_Dennis_ said:
I just installed AdAway, the host file applied fine as far as I can tell (haven't rebooted).
Did you make sure you have a kernel that disables RIC, or disable it your self in a terminal emulator?
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
TimDawg said:
I used the kernel that is on the dirty root guide. I was meaning to use the AndroPlus on but didn't in the end. Flashing a new kernel doesn't affect any of the data on it does it?
If I can disable RIC via terminal could you advise me how please. I've had a quick google and can't find anything.
Cheers
Click to expand...
Click to collapse
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
See MOAAB (mother of all ad block) in Android Development and Hacking. Costs 0 bucks and blocks hosts. That's the best if you are rooted bro
_Dennis_ said:
Thanks to @tobias.waldvogel for this. Use the following in a terminal emulator to disable RIC, will need to be done on reboot (you can make it a boot script if you know how.)
Code:
su
echo 0 >/sys/kernel/security/sony_ric/enable
mount - o remount, rw /system
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
I get an error saying no such directory. if i try to create it manually it fails...
TimDawg said:
I get an error saying no such directory. if i try to create it manually it fails...
Click to expand...
Click to collapse
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
_Dennis_ said:
It worked for mine....
You did it one line at a time? And approved super user for the terminal emulator?
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
TimDawg said:
yep one line at a time.
It's almost like my phone isn't totally rooted. I can do a lot of things that require root. If it try to create any folder inside /sys it fails.
Click to expand...
Click to collapse
What super user app do you use? How was it installed?
_Dennis_ said:
What super user app do you use? How was it installed?
Click to expand...
Click to collapse
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
TimDawg said:
SuperSU and it was installed via ADB
I think I must have messed up the kernel install somehow.
I'm busy tomorrow and not risking anything tonight so I'll give a fresh kernel a go on Monday. Already looking at AndroPlus kernels and there are a lot of options now. Enforcing and Permissive. I'm sure a Google will let me know what the difference is though.
Click to expand...
Click to collapse
Probably your best bet. Sorry I couldn't be of any help.
Sent from my E6683 using Tapatalk
How did you rooted your z5?
luisfillipe said:
How did you rooted your z5?
Click to expand...
Click to collapse
I used the method for Z5 dual SIM posted in the dirty root thread in development section. There are other simpler methods for the regular Z5, again in development section. It requires bootloader unlocks for all of them and that causes you to lose some Sony DRM keys.
Sent from my SM-T710 using Tapatalk
I tried Adblock since i'm not rooted, but it occasionally drain battery in sleep mode so I removed it..
I've always used Lucky Patcher for that. It has hosts blocking as well as disabling google ad modules inside apps, making everything clean and bull$hit free.
Gotta say I was starting it get a be pissed off with how much more complicated it is to do root this phone than any other android phone I've tried to do in the past...
so I came to the assumption that I'm supposed to be booting into recovery and installing the zip through there like I used to do to install ROMs on my older android phones.
I've flashed a few AndroPlus kernels and no luck. One of them left me stuck in bootloop which I let go around roughly 10 times until I decided it was getting nowhere. I did eventually manage to get one installed without a bootloop.
I wanted to know what Kernel I was running so I installed 'Kernel Adiutor' which required BusyBox to be installed alongside it. I found I was unable to install BusyBox which I guess was caused by the same thing causing all my other issues.
I've tried going through this whole over complicated process again and I hit a problem was trying to execute these two lines:
Code:
adb shell mount /dev/block/platform/soc.0/by-name/system /system
adb shell mount /dev/block/platform/soc.0/by-name/userdata /data
I read through everything I could find again to see if I could work out what was going on. While looking for this I can across this line of code:
Code:
fastboot flash boot boot.img
which is to be run if you want to flash the kernel via adb. (you need to extract the zip provided by AndroPlus)
Once this line had been executed I booted up again and was able to install BusyBox which let me see which kernel I had which showed AndroPlus (v3 incase you're interested) so I then tried AdAway again.
BINGO
Only thing is on some websites, particularly xda there is still a gap showing where the Advert would be displayed if not blocked. This I can live with.
I can't beleive how much more complicated this phone is to root compared to my HTC Desire, Galaxy S2 & S4. All of them were plug phone in. Click a few times and the jobs done. Is there a reason this hasn't been done for the Z5?
Just want to say thanks to all that have tried to help.
Thanks to AndroPlus for his kernel which has sorted me out.
Not so much thanks to Sony as this whole process has put me off ever getting another Sony phone. Mainly the fact I've lost some functionality what with having to unlock the bootloader. Overall I'm happy though.
Cheers
Does anybody know why Open GApps still hasn't added support for the Pixel and Pixel XL?
After playing around with my new Pixel XL all day, I don't entirely see the problem stopping Open GApps from working. Can they not just tell the installer to install to /system/system on Pixel devices? I know one of the major issues is that there is no easy way to tell which slot to flash to, but I feel like if someone is flashing GApps, they are probably competent enough to switch slots in TWRP, and if they don't, it'll just install GApps to the other slot, which shouldn't hurt anything.
As a side note, does anyone know if it's possible to build an Open GApps package of our own that would flash to /system/system of the currently selected slot? BeansGapps aren't customizable and don't contain all of the apps I want.
admiralspeedy said:
I feel like if someone is flashing GApps, they are probably competent enough to switch slots in TWRP, and if they don't, it'll just install GApps to the other slot, which shouldn't hurt anything.
Click to expand...
Click to collapse
But it hurts ppls brains when they have to answer the question of "Why are my gapps not loading" kinds of questions people raise often because they dont like following directions.
Also, I'm not sure. I think there is a modified OpenGapps installer floating around the forum somewhere that can be used to install to Pixel. I thought I read a not to long back, but not 100%.
uodii said:
But it hurts ppls brains when they have to answer the question of "Why are my gapps not loading" kinds of questions people raise often because they dont like following directions.
Also, I'm not sure. I think there is a modified OpenGapps installer floating around the forum somewhere that can be used to install to Pixel. I thought I read a not to long back, but not 100%.
Click to expand...
Click to collapse
Well, I can not find it for the life of me if a modified version exists. I spent most of yesterday searching.
admiralspeedy said:
Well, I can not find it for the life of me if a modified version exists. I spent most of yesterday searching.
Click to expand...
Click to collapse
I cannot find any either, and I wish there was. I much prefer to be able to remove any kind of aosp and lineage app and replace it with Google's app. 1st world problem I know, but it bugs me that the aosp and lineage app is there on the rom of my choosing. I want an easy way to flash the Google apps and replace them in the system partition.
jkashuba07 said:
I cannot find any either, and I wish there was. I much prefer to be able to remove any kind of aosp and lineage app and replace it with Google's app. 1st world problem I know, but it bugs me that the aosp and lineage app is there on the rom of my choosing. I want an easy way to flash the Google apps and replace them in the system partition.
Click to expand...
Click to collapse
I actually figured out how to mod it myself and could give you a modified package if you want. I don't even use the flashable packages anymore because I started building my own copy of Lineage with a bunch of mods and Open GApps included and configured exactly how I want.
admiralspeedy said:
I actually figured out how to mod it myself and could give you a modified package if you want. I don't even use the flashable packages anymore because I started building my own copy of Lineage with a bunch of mods and Open GApps included and configured exactly how I want.
Click to expand...
Click to collapse
I also have the same problem, I want to install Dirty unicorns on my Pixel , but I hate ASOP apps, but I am. not able to install OpenGapps after flashing the ROM, in order to remove ASOP apps from that ROM. So I have to use Pure Nexus....
admiralspeedy said:
I actually figured out how to mod it myself and could give you a modified package if you want. I don't even use the flashable packages anymore because I started building my own copy of Lineage with a bunch of mods and Open GApps included and configured exactly how I want.
Click to expand...
Click to collapse
Wow, that be wonderful.
I basically want stock packages if possible. That replaces the aosp and lineage ones. If that's what you have or could give it would be much appreciated. If you have a guide or cheat sheet on how you did it, that would be ok too.
I have a Pixel XL Google Store Edition 128GB
jkashuba07 said:
Wow, that be wonderful.
I basically want stock packages if possible. That replaces the aosp and lineage ones. If that's what you have or could give it would be much appreciated. If you have a guide or cheat sheet on how you did it, that would be ok too.
I have a Pixel XL Google Store Edition 128GB
Click to expand...
Click to collapse
Give me like 15 minutes to do it an upload it and then it will work exactly like a normal Open GApps package and you can use a gapps-config.txt file to configure it exactly how you want.
admiralspeedy said:
Give me like 15 minutes to do it an upload it and then it will work exactly like a normal Open GApps package and you can use a gapps-config.txt file to configure it exactly how you want.
Click to expand...
Click to collapse
Thanks so much!
jkashuba07 said:
Thanks so much!
Click to expand...
Click to collapse
Ok, I modded it but it's taking a bit longer to upload than expected
admiralspeedy said:
Ok, I modded it but it's taking a bit longer to upload than expected
Click to expand...
Click to collapse
No worries
Here you guys go: https://mega.nz/#!4owiRa5a!j4hbQrGlK0Ugz6HoTn33kcKpkaauajKeMcXkzBVxz9g
It's the stock package and it will work on the Pixel and Pixel XL (and theoretically any other A/B device). You can use the standard gapps-config file to configure the installation. Also, it needs to be flashed on which ever slot the ROM is on, not the opposite like TWRP.
admiralspeedy said:
Here you guys go: https://mega.nz/#!4owiRa5a!j4hbQrGlK0Ugz6HoTn33kcKpkaauajKeMcXkzBVxz9g
It's the stock package and it will work on the Pixel and Pixel XL (and theoretically any other A/B device). You can use the standard gapps-config file to configure the installation. Also, it needs to be flashed on which ever slot the ROM is on, not the opposite like TWRP.
Click to expand...
Click to collapse
Thx. I am uploading it to my drive. I am currently using RR. Next time they update their rom, I'll do a clean install and let you know how I made out.
Thanks again!
admiralspeedy said:
Here you guys go: https://mega.nz/#!4owiRa5a!j4hbQrGlK0Ugz6HoTn33kcKpkaauajKeMcXkzBVxz9g
It's the stock package and it will work on the Pixel and Pixel XL (and theoretically any other A/B device). You can use the standard gapps-config file to configure the installation. Also, it needs to be flashed on which ever slot the ROM is on, not the opposite like TWRP.
Click to expand...
Click to collapse
Hi, was wondering if you could share how you modified the zip?
I downloaded a new aroma package and would like to be able not to bug you if I ever need a new one lol.
Glsoto said:
I also have the same problem, I want to install Dirty unicorns on my Pixel , but I hate ASOP apps, but I am. not able to install OpenGapps after flashing the ROM, in order to remove ASOP apps from that ROM. So I have to use Pure Nexus....
Click to expand...
Click to collapse
jkashuba07 said:
Thanks so much!
Click to expand...
Click to collapse
jkashuba07 said:
Wow, that be wonderful.
I basically want stock packages if possible. That replaces the aosp and lineage ones. If that's what you have or could give it would be much appreciated. If you have a guide or cheat sheet on how you did it, that would be ok too.
I have a Pixel XL Google Store Edition 128GB
Click to expand...
Click to collapse
jkashuba07 said:
Hi, was wondering if you could share how you modified the zip?
I downloaded a new aroma package and would like to be able not to bug you if I ever need a new one lol.
Click to expand...
Click to collapse
I've never modified the Aroma one but I assume it's similar. All you have to do is open the install script and replace "/system" with "/system/system", but you can't just replace all because there are several instances of "/data/system", where it would change to "/data/system/system" incorrectly (you could probably stop that with regex). Also, there were two lines with "/system" in regards to mounting that don't need to be changed (I don't remember the exact line numbers but you'll probably know as soon as you see them).
admiralspeedy said:
Well, I can not find it for the life of me if a modified version exists. I spent most of yesterday searching.
Click to expand...
Click to collapse
admiralspeedy said:
I've never modified the Aroma one but I assume it's similar. All you have to do is open the install script and replace "/system" with "/system/system", but you can't just replace all because there are several instances of "/data/system", where it would change to "/data/system/system" incorrectly (you could probably stop that with regex). Also, there were two lines with "/system" in regards to mounting that don't need to be changed (I don't remember the exact line numbers but you'll probably know as soon as you see them).
Click to expand...
Click to collapse
thanks, I actually found a super simple way while I waited for your reply, I assumed it was the installer file, so I tried just overwriting it with the one provided with your package and it worked lol.
jkashuba07 said:
thanks, I actually found a super simple way while I waited for your reply, I assumed it was the installer file, so I tried just overwriting it with the one provided with your package and it worked lol.
Click to expand...
Click to collapse
That will work so long as file names remain the same, but if they ever change the name of a file or add/remove an app it will probably break.
admiralspeedy said:
That will work so long as file names remain the same, but if they ever change the name of a file or add/remove an app it will probably break.
Click to expand...
Click to collapse
Ok thx, if that happens then I'll go your route with tweaking the file with /system/system
admiralspeedy said:
That will work so long as file names remain the same, but if they ever change the name of a file or add/remove an app it will probably break.
Click to expand...
Click to collapse
So,
I think Open-Gapps finally put support in for Pixel and all other A/B partition devices. I found this in the Installer.sh code for their latest (5-28-17) super package for ARM64
# Detect A/B partition layout https://source.android.com/devices/tech/ota/ab_updates
if [ -n "$(cat /proc/cmdline | grep slot_suffix)" ];
then
device_abpartition=true
SYSTEM=/system/system
else
device_abpartition=false
SYSTEM=/system
fi
That is something I could not find in the Installer.sh file you modified. Unless you took that out and manually changed system/system?
jkashuba07 said:
thanks, I actually found a super simple way while I waited for your reply, I assumed it was the installer file, so I tried just overwriting it with the one provided with your package and it worked lol.
Click to expand...
Click to collapse
jkashuba07 said:
So,
I think Open-Gapps finally put support in for Pixel and all other A/B partition devices. I found this in the Installer.sh code for their latest (5-28-17) super package for ARM64
# Detect A/B partition layout https://source.android.com/devices/tech/ota/ab_updates
if [ -n "$(cat /proc/cmdline | grep slot_suffix)" ];
then
device_abpartition=true
SYSTEM=/system/system
else
device_abpartition=false
SYSTEM=/system
fi
That is something I could not find in the Installer.sh file you modified. Unless you took that out and manually changed system/system?
Click to expand...
Click to collapse
Yes they did. I actually posted about it in the news/announcement forum when the devs told me they added it on their Gitter chat.
This really should be asked in the dev forum, But my post count is not high enough or worthy!
I have several Nexus Players I plan on selling with the oreo update pre installed, There are 2 addl non playstore apps I need to include as part of the package.
I'm trying to avoid "profiling" the devices to add the 2 extra apps. I have flashed the oreo upgrade to all 8 of them.
I cannot push the apks without profiling to enable adb nor can I seem to find a good zip template to make use the bootloader recovery adb function.
I have tested a few and they all fail with footer and signature failures? I'm only left with a few ideas. Please comment if you can help with any of the options below or suggest a better one..
1. Find a proper update.zip template that works with nexus player..Oreo 8.0 or can bypass the check..
2. Can apps installed in a profiled device be preserved thru a reset method that would allow the device to startup with the first run screens re-instated? Remote setup, WiFi, User account.. Out of the box experience?
3. Can an APK or ZIP be copied to a location on the Nexus Player that would allow it to be installed on first run? (I seem to think Youtube does this)
4. Least popular... Modify the Oreo upgrade img to have the 2 apps pre installed? <--This option looks messy..
Any suggestions appreciated!! Thanks
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
rufy93 said:
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
After careful examination, #2 and #4 are really the same thing. Without root, I would have to mount the oreo system.img file in linux and add the 2 apks to root/system/app then repack the img file to re-burn the rom. Not exactly sure if that would be enough, I assume there is some checksum or signing in the image file to prevent guys like me from modifying it. Also what would happen after google hits it with an update? would these apps survive? Finding the answer to why the stock Oreo bootloader recovery adb fails to accept the typical update zip format will end up being the right solution.
If you wish to flash using the stock recovery, the update zip must be properly signed. This usually means by the oem private keys.
I haven't been following the modding scene for a long time, but I'm sure these are still inaccessible.
Sent from my KFFOWI using Tapatalk
Hey all,
I unlocked bootloader, installed TWRP and installed Magisk just fine.
As far as I was aware, I had disabled encryption on the sdcard, and this makes sense as I flashed Magisk from its installation zip in my sdcard.
However, I just rebooted to recovery in order to make a backup
It prompts me to input password in order to decrypt data.
I don't need to input password, I can click cancel and get to TWRP, but then, using its file manager, I see that all file names are in gibberish. Obviously the personal data Partition is also read only
I don't know how it got encrypted, and it was after I installed Magisk from sdcard, showing it was not encrypted at some point.
Well I can't make a TWRP back in this state.
Anyone know how it got encrypted again and how to undo that so I can make backups?
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Ajaykumar21066 said:
for decryption you have to do fastboot format userdata . and till the time you have stock rom you will have encrption coz it comes with encryption enabled.
Click to expand...
Click to collapse
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone. ?
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
drakenabarion said:
Thanks for replying!
That's sounds very "destroy all settings". I wish I knew that before I really moved into the phone.
But then, I am confused as to how I could install from sdcard before. It included a manual system update zip, twrp and magisk. There was a point when I could read the sdcard content in twrp. At what point did it change?
I don't suppose anyone knows a way to backup while twrp can't access sdcard? Adb sideload probably only allows flashing a zip, and probably can't transfer data in the opposite direction. USB otg could be an option I suppose!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
only change was you didnt have any lockscreen pin setup on your phone, And now you have one i think. its the same pin twrp is asking for.
Ajaykumar21066 said:
only change was you didnt have any lockscreen pin setup on your phone, And you have one i think. its the same pin twrp is asking for.
Click to expand...
Click to collapse
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison! ??
Sent from my OnePlus 6 using XDA Labs
drakenabarion said:
Oh right! That's great. I guess I come from phones where the encryption was not so user friendly. Huawei phones have encrption keys that they never share with the user because they have no desire to help with modding or customisation. So if it asks for a password, there was almost no way a user could know it.
OnePlus feels so so open in comparison!
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Ajaykumar21066 said:
Yeah , things have changed quite a bit, we can decyrypt the device with the command i mentioned , and twrp wont ask for the password. but the only problem is we dont have any other stable rom to flash after that , and if flash stock rom it encrypts the data again.
For now thats the thing, but it will change once we have new roms that are not based on stock or a flashable zip can be used on top of stock to prevent encryption, but all this development will take time since we have Treble A/B partitions now.
Click to expand...
Click to collapse
The important thing for me now is that I have a stable backup. It can take me days to setup a new phone to my comfortable default setting, so now I feel secure that I have a saved image of my idea of a good install. So thank you for helping with that!
But it will be interesting to see how custom roms not based on OOS will be.
Up until my last phone (Honor 6x - proprietary soc, therefore limited rom support), I would flash a custom rom ASAP (typically LineageOS or before that, CyanogenMod). But I already get that kind of experience (with good historical reasons I guess) from OOS. It would take a bit to tempt to flash something else. ?
Sent from my OnePlus 6 using XDA Labs
And might I just say that woohoo for large storage! My previous 32gb phone took 10 gb for firmware and left me struggling after installing a normal set of apps, typically leaving me about 10gb to put music etc into. My backup that I just made took 18gb, because I installed alot of games I couldn't before, is bigger in general than base free space before!