Related
I'm new to the Android world, but not to Linux/Solaris/BSD; even though they are supposedly cousins I still have that doubt in my mind.
Therefore, can some one with more coding experience tell me if it's safe to assume we can recompile anything made for Linux to work in Android? or it's not as simple as it seems say like Linux/Unix/Solairs/BSD ?
Android is Linux.
Android runs on a linux kernel, but it is not a traditional gnu/linux system. There is not even a glibc.
On top of the kernel is a managed virtual machine based on (but not compatible to) the Java platform, and a completely different api stack against which you build applications.
See http://developer.android.com/guide/basics/what-is-android.html
AllGamer said:
I'm new to the Android world, but not to Linux/Solaris/BSD; even though they are supposedly cousins I still have that doubt in my mind.
Therefore, can some one with more coding experience tell me if it's safe to assume we can recompile anything made for Linux to work in Android? or it's not as simple as it seems say like Linux/Unix/Solairs/BSD ?
Click to expand...
Click to collapse
yes, you can cross compile linux stuff to run on your android device (but there could be limitations since it's not running a complete linux OS).
a good example is busybox.
you can also install Android Scripting Engine to run python, ruby, perl & shell scripts from the android UI.
Yes, but not in the way you think.
Android doesn't have standard libraries and no x windows (so no gui apps).
Basically you still have to do a full port unless its a simple CLI app
Thanks for all the helpful info.
I'm sure that most apps or "replacement" apps are already available for anything we can imagine, but there will always be that one app that you need but it's not available.
in those cases, it might be easier to recompile the application to run in Android, asuming it is compatible; in the worst case scenario, it might require a complete port as mentioned above.
You can, but you have two (or three, if my trials are worth it ) ways to do it:
1 - You statically compile (cross-compile, actually) all linux application you want (be careful of the dependencies tho ). This way isn't what I prefer since applications become huge when they're statically linked.
2- You compile Bionic C library (which is embedded to android system) for your cross compiler first, then you can compile applications with it. This is one way to do it, but Binoic library is a trimmed library, so you might not compile everything.
3* (still developmental ) - You can compile GlibC first for your device, then compile your applications. The problem with that is GlibC is huge and you have to find a way to tell your Android system to look for GlibC libraries as well.
I'm currently working on step 3 now; will see what it brings : http://forum.xda-developers.com/showthread.php?t=1299962 . You can read it here.
kexec is now fully working!
Kexec host kernel: https://github.com/willcast/ubuntu-kernel-tenderloin branch is "kexec"
Graphical bootloader: https://github.com/willcast/kexecboot
Compiled host kernel uImage UPDATED: https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
THE ATTACHED KERNEL PATCH (decomp_copy_atags.diff) _MUST_ BE APPLIED for ANY kernel to be bootable FROM kexec.
YouTube: http://www.youtube.com/watch?v=ko_4cOj_5iM
Kexec kernel and OS installation is best performed through SmackMe2, which is available in its own thread on this site.
I have no idea what you are saying, but keep up the great work!
Keep up the good work man , one question with you work in the future can we delete web os from the touchpad forever?
I imagine that's already possible. Use lvm to delete all the logical volumes not tied to another OS and then delete the uImage.webOS symlink. That deletes webOS, frees mostof its space and removes it from the moboot menu.
If you choose to do that, though, using the doctor to restore WEBOS will be even more difficult because you'll have to wipe out everything AND potentially need to "unbrick" your TP (using the method involving NovaCom, the small boot image ripped from the doctor and a string of LVM commands that is posted on sone or other forum.)
Lvm? Can you make a tutorial? How to remove webos from touchpad?
Thank you
Before this is complete or posted for testing, I think we will need a tutorial and links to files of how to fix the tp from a full brick such as issues with removing and restoring webos.
Great job if your boot loader works as planned we will have a full multi-boot device with a few restrictions(drivers for untested ports, etc).
Keep it up.
Sent from my cm_tenderloin using xda app-developers app
Awesome that you're resuming development castrwilliam! Can't help you with kexec though, sorry. I hang around in the Motorola Defy forums and some developers like Quarx have tried pursuing the kexec route in order to load custom kernels onto the Defy, might be worthwhile to throw him a PM. Would be great to have a more flexible bootloader!
I anyone needs a full restore, this thread helped me out. I followed the instructions when I screwed up and doctored without removing partitions. I believe WebOS Doctor handles repartitioning, so it should work:
http://forum.xda-developers.com/showthread.php?t=1426244
WORKING (but non-Kexec) Android multiboot for TouchPad.
DON'T TRY ANYTHING UNTIL YOU HAVE READ THE WHOLE POST!!
Beta 2 Updated with support for my Froyo Qcom kang.
I created a script that can install multiple versions of Android on the HP Touchpad, side by side, such that they can be selected at the MoBoot menu and operate independently. The script modifies them, on the Touchpad itself, to work with the new names for the partitions.
I want your feedback on this installer. It is used in the same way as ACME Installer but only shares one line of actual code with it (and it also uses the same binaries and config files on the initial ramdisk image, but they are Open Source so that should'nt matter.) I'll be posting this on XDA in a minute, my username there is also "castrwilliam".
If you do choose to use (TEST!) this:
- You need to create a folder on your media partition (the one that is shown when you select USB mode) with the following zips:
moboot [moboot_0.3.5.zip]
(the rest are optional but I recommend using them all so that you can help me test everything)
Froyo Test [Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip]
CM7 alpha3.5 [update-cm-7.1.0-tenderloin-a3.5-fullofbugs.zip]
CM9 latest nightly [cm-9-xxxxxxxx-NIGHTLY-tenderloin.zip]
CM10 latest preview [cm-10-xxxxxxxx-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM.zip]
2.3.x gapps [gapps-gb-xxxxxxxx.zip]
4.0.x gapps [gapps-ics-xxxxxxxx.zip]
4.1.x gapps [gapps-jb-xxxxxxxx.zip] MAKE SURE not to use 4.2 gapps!
(NO Android Recovery will work yet, so don't try. It will reject TWRP and CWM at least.)
- If you already have Android and/or Moboot and/or native Linux (Ubuntu, etc.) installed:
* back up any data on your media volume. webOS should back up your apps for you.
* make both a nandroid (which WON'T work to restore in a multiboot config, but if you go back to single boot, it will be fine) and a Titanium backup [which should be portable to the same OS.]
* run ACMEUninstaller and then run SmackMe-Installer.
* if you have native Linux, backup your /etc and /home (I recommend the lovely GNU tar and gzip/bzip2). That should be the majority of what to keep.
* ALSO uninstall any native Linux you may be using after you back it up.
* lastly unzip and novacom boot the SmackMe-Installer.
If you don't already have Android, MoBoot OR native Linux, just:
* back up any data on your media volume. webOS should back up your apps for you.
* then unzip and novacom boot the SmackMe-Installer.
youtube demo:
http://www.youtube.com/watch?v=8Hhy20lzhR4&feature=youtu.be
File should be attached. Report bugs by PM'ing me, or posting in this thread
Can i remove webos with this multiboot? And stay only on android and ubuntu?
This is strictly an installer. I was going to write a webOS removal script. However, android doesn't have the needed binaries. That leaves me two options: make another thing like SmackMe to do it or do it under whatever version of native Ubuntu you are running. Either way, I really don't want to have to test it myself. If I need to I'll have to doctor my touchpad EVERY TIME I do it. That's a lot of doctoring and a lot of flash write wear. So the answer is basically "find me a dev that wants to remove webos too. They'll either make you one or beta test mine." Sorry man.
Amazing keep up the good work castrwilliam !
Strange request
Hey, does anyone here still have the 2011 Froyo (2.2.1) system dump for Touchpad? It wasn't CM6, just something that HP accidentally released and someone over at Rootzwiki dumped. I'm posting this here because I have no account and they'd think I'm a noob there. All the links are down to it and I want to try messing around with its files, just for kicks. Maaaaybe I can get it to boot, and add support for it to the SmackMe installer, so at least I can have *four* versions of Android on my touchpad.
http://forum.xda-developers.com/showthread.php?t=1234381
You know, 'cause I'm just that crazy.
Wow it's been hard to find it but i think this is the good dump:
http://download.digiex.net/Consoles/Tablets/HP-Touchpad-Android2.2.1-Disk-Images.zip
sources:
http://digiex.net/downloads/downloa...hpad-android-2-2-1-system-image-download.html
it's alive! (sorta)
Somebody on XDA found a link that I thought was dead. It was the mmc dump of someone who had Froyo leaked by HP onto their fire-sale Touchpad.
FAQ:
"Obviously nobody wants this. Everybody's running Jelly Bean."
That's exectly why I did it. My point is to do the most outrageous and downright unnecessary things possible with commonplace hardware.
"What doesn't work?"
Rotation, sound, wi-fi, softkeys (i.e. Home, Back, Menu, Search.)
"What does work?"
Camera (OH HAYULL YA), touchscreen, battery reading, power button, volume button (but it dosen't matter b/c sound is borked).
"I can haz Modded Froyo?!"
Not yet.
YouTube: http://www.youtube.com/watch?v=zX29IcTIB14
Hah awesome work, I think you hold the record of most different OS'es on one device now! It looks quite functional already.
Oh and about the "Obviously nobody wants this. Everybody's running Jelly Bean." quote, I only run WebOS and your Ubuntu 12.10 port on the TP!
As soon as I get my power button sorted out I am on this!
Sent from my slim_tenderloin using xda app-developers app
Hey everyone! Froyo here!
I've just zipped up my Froyo kang such that it will work if flashed from SmackMe, and if you're crazy enough to run it alone, hopefully also Android recovery.
sound works!!
The Wi-Fi works now BUT YOU NEED A STATIC IP ADDRESS. (problems with dhcpcd)
The buttons are hacked to work (by my new shell script: /system/bin/buttond, check it out) as follows:
Volume Down is Back
Volume Up is Menu
Center is Home.
Obviously once the audio works (if ever) that will be an issue. My embarrassing secret (at least probably to the devs here) is that I don't know Java. That makes it difficult to mod on any touchscreen buttons...
The real audio library is /system/lib/libaudioflinger.real.so and the stub one (default via a symlink) is /system/lib/audioflinger.so. Using the real one causes bootloops.
Auto rotation still won't function.
Google Apps and even Facebook are included in this ROM. (It's not CM6.) So are some potentially geeky Qualcomm apps.
Don't set up your Google Account during first boot, because it will ask you to slide the keyboard open. That sounds pretty impossible onn this device. Set it up from Settings later, and you shouldn't have that issue.
UPDATED due to install issues with actual Android Recovery. Redownload.
Download Initial Version (Alpha Minus-One-Point-One): https://www.dropbox.com/s/wcs2mra8aedj1hf/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip
Download Second Version (Alpha 0.2): https://www.dropbox.com/s/t1cptjj5i02epas/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.2-incl-gapps.zip
^^^
I wanted to try froyo soo bad when I heard about those dumps last year (I think) lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
jacobas92 said:
^^^
I wanted to try this soo bad when I heard about it last year lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
Click to expand...
Click to collapse
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
castrwilliam said:
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
Click to expand...
Click to collapse
Ok, thanks!
Hi everyone,
I have a Sony Z3 compact I just received, model D5803 running Android 6.0.1 with Firmware 23.5.A.0.575.
I really dislike Google and want to run a phone with the minimum of proprietary software (I guess blobs to communicate with the hardware are mandatory). I guess AOSP (any version, but a recent one would be better ) with F-Droid is a good solution.
Unfortunately when checking the sony website but it tells my the bootloader is not unlockable. What should I do? I'm running Ubuntu and have adb and fastboot installed.
I found [this topic](https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714) which tells it roots the phone (and has a GNU/Linux script) but how does that help me to install a Rom, for example the AOSP provided by Sony at /open-devices/list-of-devices-and-resources/ if the bootloader is still locked? What are TWRP and busybox, is that supposed to help?
Flaburgan said:
I found [this topic](https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714) which tells it roots the phone (and has a GNU/Linux script) but how does that help me to install a Rom, for example the AOSP provided by Sony at /open-devices/list-of-devices-and-resources/ if the bootloader is still locked? What are TWRP and busybox, is that supposed to help?
Click to expand...
Click to collapse
TWRP is a custom recovery that allows you to flash a ROM and other files, that are stored on the normal internal or external storage.
Busybox is a binary that gives you command line tools that are often included in a Linux install and some of which aren't included on normal Android. These are commands that other things may make use of, or that you can make use of at a terminal app or run from Tasker or similar app.
You want to look at backing up your TA partition, which stores your DRM keys, before unlocking the bootloader to install a custom ROM because some functionality, camera quality and anti-distortion, sound quality, and some other stuff which I don't remember, won't work if you go back to the stock ROM unless you have these keys backed up and then restored later. You need to unlock the bootloader in order to flash a custom ROM and doing this erases, permanently, these DRM keys, so they need to be backed up and then put back later if you relock the bootloader and flash a stock ROM.
If you look in the Original Development section, Jaguar Aries ROM has no Google Apps, had the latest patches up to Febuary, and had the best battery life of any custom ROM I've seen for this phone, right on par with stock. There are some builds of Lineage OS that are probably closer to being up to date as well and may have a better camera than Jaguar. The developer of Jaguar has moved on to another phone. That said, if you aren't experienced and don't know what TWRP is, then installing it is an extra step from other ROMs as well since it requires you to setup a firewall app to permit connections on data or wifi before you can use the wifi or data at all. I doubt Lineage OS has this, but presume that battery life would not be good.
Also, if you install microg apps, you can still use things such as cell and wifi based location, google push services, and ... I don't remember what else, however it hasn't been updated recently and many apps will complain and refuse to run saying that you need to update google play services, especially annoying for anything that uses push especially. Microg essentially sits in the place of where some functionality of Google Apps would and fills in some blanks.
When you don't have Google Apps installed, many paid apps will refuse to run as well, specifically the ones you paid for, because they can't verify the purchase with Google servers. There should be a **** list for any developers that don't cooperate when this is a problem for a user. I've only had one app developer help me on this, ever.
Thanks for your detailed answer!
You need to unlock the bootloader in order to flash a custom ROM and doing this erases, permanently, these DRM keys, so they need to be backed up and then put back later if you relock the bootloader and flash a stock ROM.
Click to expand...
Click to collapse
Does that mean that I can't use the DRM keys with another ROM? So I will never have the full quality of my hardware? Would using the AOSP rom provided by Sony solve that problem?
On which version of Android Jaguar Aries ROM is based? I searched for a lineageOS image but didn't find any for the Z3 Compact.
I had another z3c which died and was running Firefox OS, I'm fine with not having access to the Google Play store, I plan to install F-Droid and use only FOSS apps. In fact I would even prefer to go back to Firefox OS even if it is not maintained anymore, its UX is so much better than Android... That said, thanks for telling me about Microg, I didn't know it and that's true that many apps use Play services especially for push. Even Signal had that as a dependency (fortunately not anymore). Still, I would avoid any data coming out from my phone to by sent to Google servers, so I will probably avoid it.
Flaburgan said:
Thanks for your detailed answer!
Does that mean that I can't use the DRM keys with another ROM? So I will never have the full quality of my hardware? Would using the AOSP rom provided by Sony solve that problem?
On which version of Android Jaguar Aries ROM is based? I searched for a lineageOS image but didn't find any for the Z3 Compact.
I had another z3c which died and was running Firefox OS, I'm fine with not having access to the Google Play store, I plan to install F-Droid and use only FOSS apps. In fact I would even prefer to go back to Firefox OS even if it is not maintained anymore, its UX is so much better than Android... That said, thanks for telling me about Microg, I didn't know it and that's true that many apps use Play services especially for push. Even Signal had that as a dependency (fortunately not anymore). Still, I would avoid any data coming out from my phone to by sent to Google servers, so I will probably avoid it.
Click to expand...
Click to collapse
When you unlock the bootloader the DRM keys get erased permanently, so you'd need to root the phone and back up the partition where they are held before unlocking it. As far as I know, every custom ROM needs to have the bootloader unlocked. If there is an alternative way to install a ROM on a locked bootloader then it would be one of those scenarios where its installed while keeping the stock one, and I don't know if this has been done on the Z3c or not.
I also don't know if Sony's AOSP requires unlocking the bootloader or not.
Jaguar is based on 5.1.1
Its a mix of AOSP, Lineage, and was getting monthly backports of the latest security patches until Febuary when the developer no longer had a Z series phone for his own use. The only criticism it met was that the developer never released the source code for the entire ROM, just the kernel. He never replied to why that was. A lot of the custom ROMs out there are like this, so its still a case of who you choose to trust when it comes to this a lot of times. I liked it because the battery life was really good and assuming the security was what was advertised then that was also a real plus.
Many apps, by the way, were working fine with microg push but then with updates to apps, they complained about needing to update google services framework, which obviously was spoofed and microg hasn't been updated, and it happened to a lot of apps in a short period of time, so I assume there was a change enforced by Google for their requirements in the Play Store. If you just want it for location, for example if you use Osmand maps, then you don't have to enable the feature for push notifications nor have a google account associated with the phone, and it all works as user installed apps, so it can be undone without any real fear of the system getting modified after you try it out. There's a microg repo that can be added to fdroid. The location is based on either databases you download to the phone, which aren't very good, or also you can opt for cell location from Mozilla servers, and if you have to have wifi based location as well then you can hook into the Apple servers but the latter doesn't sound like something you want, if you want to do any of it at all that is.
I think most likely that GPS location would work without any need for microg.
The post you linked to with the Linux script installs TWRP to the /data partition, then you root it, then you back up the DRM keys after its rooted, then unlock the bootloader, install normal TWRP, and go from there. In Linux you'lle want to use the dd command to back up the DRM keys as all that's available on the forum is a Windows script (I think). There is info on it somewhere but it would be hard to find it. If you search my posts the thread will come up somewhere in the history. Anyway, the reason I broght this up is because the script in the thread for installing TWRP and rooting didn't work properly. I don't remember why, but I had to go through it line by line and enter the commands in from a termnial to get it right, I think there was some bad syntax. If you can't figure it out, quote one of my posts and ask, that way I get a notification that I was replied to, I think I have a fixed version of it on my drive somewhere if it causes a problem.
For the DRM keys you want to backup the TA partition bit for bit to a file. I backed up my Fota partition as well as I was unclear what role it plays. You also want to keep a copy of that particular Sony ROM file, and the two kernels involved, to flash with Flashtool in case you relock and restore so you can get root access to restore the partition while the bootloader is locked again.
May I ask why are you going FOSS only? if that's because privacy concerns, then FF OS is not the best solution... Because any Cloud-based OS is a little bit creepy, doesn't matter if it's ChromeOS from Google, or FirefoxOS from Mozilla.
There are plenty of Linux distros dedicated to run on Android phones, but it's not the best UX.
And yes, you can enjoy clean AOSP install (LOS is fine) without flashing G-Apps. But you won't have Google play at all! F-Droid is fine but you won't find there Gmail alternatives, you can't find Gmail even on Amazon AppStore... Sadly if you install Gmail then you'll find out that it installed bunch of google apps and hidden services behind the scenes... So only option is to use Gmail web app.
But then again, F-Droid is fine, there are many FOSS alternatives to youtube and other apps.
And if privacy (and security) is your concern, use LOS privacy guard / Android's builtin Permission Manager, and on Rooted ROMs you can use AFwall firewall which is the best.
Good luck
GadgetAvi said:
Because any Cloud-based OS is a little bit creepy, doesn't matter if it's ChromeOS from Google, or FirefoxOS from Mozilla.
Click to expand...
Click to collapse
Firefox OS is not a Cloud-based OS at all. It runs perfectly without internet connection.
GadgetAvi said:
F-Droid is fine but you won't find there Gmail alternatives, you can't find Gmail even on Amazon AppStore...
Click to expand...
Click to collapse
Be sure that if I don't want Google on my phone, my e-mails are already **not** on GMail...
Ok, if so, then you'll be fine with any AOSP clean rom. LOS is great, and F-Droid as well. Cheers!
PantsDownJedi said:
The post you linked to with the Linux script installs TWRP to the /data partition, then you root it, then you back up the DRM keys after its rooted, then unlock the bootloader, install normal TWRP, and go from there. In Linux you'lle want to use the dd command to back up the DRM keys as all that's available on the forum is a Windows script (I think).
Click to expand...
Click to collapse
I ran the commands and the phone is now booted on TWRP from the /data partition. I did a backup with TWRP of all proposed options (Boot, TrimArea, Recovery, System, Cache and Data). Is that "TrimArea" enough to have a backup of the DRM keys? The other topic talks about Backup-TA but looking at their github https://github.com/DevShaft/Backup-TA/releases it looks very old and unmaintained.
The current TWRP I'm running is 3.1.0-0.
Also, it looks like I'm not root (at least, su is not available). Do I have to install SuperSu by giving this zip https://download.chainfire.eu/696/supersu/ to TWRP?
Flaburgan said:
I ran the commands and the phone is now booted on TWRP from the /data partition. I did a backup with TWRP of all proposed options (Boot, TrimArea, Recovery, System, Cache and Data). Is that "TrimArea" enough to have a backup of the DRM keys? The other topic talks about Backup-TA but looking at their github https://github.com/DevShaft/Backup-TA/releases it looks very old and unmaintained.
The current TWRP I'm running is 3.1.0-0.
Click to expand...
Click to collapse
I don't know. I haven't looked at a TWRP backup to see what format it is. Back when Clockwork Mod was all that was available, it merely made a tar.gz of partitions. Ideally you want a bit for bit image of the TA partitions to make sure it was exactly what it was when you restore it. I don't know if that's necisarry, or if TWRP does this anyway, but using the dd command is still prudent.
You want to either use a terminal emulator app or run 'adb shell' at a linux terminal (much easier), run 'su' once in the phone environment, allow it at the phone supersu app popup, and then do it like this.
https://forum.xda-developers.com/showpost.php?p=61307511&postcount=6
And store a copy of the image file where it won't get lost.
Edit: Sorry, I didn't see the other post. Yes, you need to flash that supersu zip file. When you try to access root from an app or the command line, it will have a popup on the phone screen asking you if you want to allow access or not, so when you run it from a terminal, 'adb shell' to get into the phone OS, there will be a popup for allowing that often times. Then 'su' there's a popup from the supersu app you just flashed. Then 'cd' to the sdcard or external sd. Then the 'dd' command. The dd command in what I linked to is inevitbaly what all those .bat files in the Windows TA Backup thing does after it does a bit of looking around to find the TA partition for a particular phone model.
The md5sum part of what I linked to compares the partitionn itself to the image file you just wrote, you just look at it to see that there are two of them (that it didn't fail) and that they are the same.
The last part pulls the image file to the hard drive, but there are other ways to accomplish this obviously. If you have a cloud storage you can upload it there, or send it as an email attahment, put it on the external sd, etc etc.
Also, in many cases, once you unlock the bootloader to flash something else, you'lle need to install TWRP again from the command line, pushing it straight to a phone partition. You'lle need help with this if you haven't done it before.
First of all i highly recommend you update your phone to latest version of Flyme as of day i write this guide newest stable version is 7.0.0.0G. It brings various bug fixes as well as security update and new functions. It fixed the weather problem too when it would not appear on secondary screen. This is my experience based on the standard model with Helio P25 chip.
JUST IN CASE BACKUP ALL OF YOUR DATA FIRST
Grab it at http://www.flymeos.com/firmwarelist?modelId=88&type=1
Installation is pretty straightforward:
-switch off your phone
-now press volume up button and power button at same time, then release power button when meizu logo appears
-phone now will enter update mode, connect it to pc and it should show up as removable drive named recovery, copy the update.zip over it
-once copied tap the start button to begin. the process itself and first boot will take a while
-when done and phone boots up just log in to your accounts and set up everything as normal or whatever
ta-dah ! you should be running latest software now.
Next problem i've encountered was big number of unwanted apps and you will need working ADB for that. I've always used custom roms which did not contain bloatware. Now im giving you one of the way of disabling them (not permanent removal).
For this to be done you need to activate developer mode and usb debugging, simply go to settings->about phone->and now tap on your build number several times
After you activate it it will be available in accessibility options under developer settings. just check the usb debugging and you're good to go
DISCLAIMER: dont ask me about adb drivers for your phone, since i had issues installing them under win 10 x64 build 1803 i thought "aw f*ck it" and just did it on linux where everything worked out of the box.
The application you will need is called Ice Box (you will find it here https://play.google.com/store/apps/details?id=com.catchingnow.icebox&hl=en_US) and install it.
After you install the app its necessary that you remove ALL of your accounts including your Google account. We will need to grant the app device owner permission. Also if multi-user or guest mode has been set on your device, it need to be closed or deleted.
When you have that done just type in your command line , terminal or whatever "adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver "
Now reboot and add your accounts back, and disable/freeze uwanted apps.
Last - the night mode. As its no longer availble in Flyme 7 if you want to use it you need to manually bring it back by installing Flyme Lab and enabling it trough quickshortcutmanager. Install both apps, then open quickshortcutmanager and search for Flyme Lab. expand it and choose the activity named com.meizu.flymelab/com.meizu.flymelab.component.nightmode.NightModeSettingsActivity .Create shortcut and open it. You should be able to enter the night mode.
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
cris2d2 said:
Nice guides, thanks.
It's also nice that Flyme 7 still supports rooting, therefore I'm using Titanium Backup to freeze unwanted apps. I bought it when I was using another phone so, for me, it's still worth it. Altough, for uninstalling system apps I'm using separate ADB commands for each app.
Click to expand...
Click to collapse
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
non.verbal said:
Its first time for me writing a guide so good word is always appreciated. What im trying to show here is the no root way of getting rid of apps for ppl like me who dont want to root their phone. As i bought it literally two days ago and i dont want to mess with it too much and loose warranty or/and OTA updates.
I also been considering posting a root guide once i tried it myself to confirm it working.
Click to expand...
Click to collapse
Well, before I discovered a rooting method for Flyme 7, I used to uninstall apps by using ADB commands. So, yes, it is possible to remove unwanted system apps without root. But now, after rooting Flyme 7, I'm only using Titanium Backup to freeze unwanted system apps, not removing them.
As far as I know, rooting Meizu phones by the official method (from Settings) does not lead to losing warranty. Only OTA updates are lost, but this is not important, at least to me, because I can always check Flyme website for new updates and, if I want to update, I just download the file and flash it through standard Flyme recovery. There is no need, for me, to maintain OTA capability. Anyhow, Flyme updates are slow to non-existent, so we can't really complain about losing an update.
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
pask876 said:
Thank you all. I'm happy with this phone at all, but software has few shortcomings and design flaws, in my opinion. Especially related to the integration with "flyme login" and Touchpal. This last one is very annoying because although I try to stop it, at each software update it comes back, more annoying than ever. So, I have some questions: which is the adb command to stop and freeze bloatware without rooting? Which is the official way to root the phone? Once rooted, is it possible to revert to the unrooted state? Some apps, actually, do not work on rooted phones. Thanks
Click to expand...
Click to collapse
I can't freeze (or disable) apps with ADB commands, only uninstall.
You need [email protected], App Inspector or similar (to find exact name of package for an app) and these commands:
adb devices
adb shell
pm uninstall -k --user 0 name_of_package
Example, for gmail:
pm uninstall -k --user 0 com.google.android.gm
Regarding rooting, as far as I know, the only method that works on Pro 7 / Pro 7 Plus is also supported by Meizu (but it breaks OTA updates).
The method is described in this video (in russian) but it's quite easy.
If you want to remove root (or if root breaks functionality) you have to reflash the same ROM from Recovery (without wipe).
Any air update coming soon? Or manually installation single option?
I rooted my pixel 7 the other day, but I was surprised to discover I couldn't sync some folders in my root directory using Syncthing.
Every other device I have rooted as well as an unrootable A70 running Android 11 permits this.
Is this normal behaviour for a rooted device running Android 13 or Android 12?
Do I just need to elevate permissions for an app to access these directories, in my case "Syncthing"?
Quoddity said:
Do I just need to elevate permissions for an app to access these directories, in my case "Syncthing"?
Click to expand...
Click to collapse
yes
did it here to sync my OSMap files because permission to read/write was disabled after update to Android 11 (I think)
DHGE said:
yes
did it here to sync my OSMap files because permission to read/write was disabled after update to Android 11 (I think)
Click to expand...
Click to collapse
Sorry for the noob question, haha, but how do I elevate permissions in this context?
I haven't used UNIX or Linux in years, so I'm very rusty with bash and phones are probably a little different from regular Linux anyway.
Do I use a Magisk module?
Or is it simply something like the following in the adb shell:. pm grant <app> android.permission.INTERACT_ACROSS_USERS_FULL ?
Run syncthing as root.
settings/verhalten(behaviour?;3rd from top)