Related
Update (5/18/2019)
Since the first tool was released, HappyZ has improved many features so I think I can just refer to
* HappyZ's rooting guide: https://github.com/HappyZ/dpt-tools/wiki/The-Ultimate-Rooting-Guide
- The only thing I want to add as Windows user is (because the guide is for Mac/Linux users) it gets much easier if you use Linux terminal like cygwin, and the port name should be something like COM# where # can be found in Device Manager by comparing before/after you attach the device.
* HappyZ's upgrade guide: https://github.com/HappyZ/dpt-tools/wiki/The-Upgrade-Guide (Recommend to read this before/after you update the new firmware.)
You may donate a cup of coffee to him there Thanks to all others who contributed a lot.
--
Update (12/02/2018) -- These are outdated.
Finally we manage to root the device! Many thanks to all of your efforts.
Just refer to HappyZ's well written guide: https://github.com/HappyZ/dpt-tools
For whom have never used python like me (and probably using Windows):
(1) Install Python 3 and add it to PATH.
(2) Install MINGW64 and run scripts here instead of Powershell due to xxd issue if you are on Windows.
(2) pip httpsig pyserial on bash.
(3) Download HappyZ's dpt-tools and unzip.
(4* this issue is fixed by HappZ)
(5) Follow HappyZ's guide. You should execute dpt-tools.py in the folder you unzipped to use get-su-bin because of how the script is written.
Some suggestions after rooting (let me know if you have better ideas):
Here is my setup: install "E-ink Launcher" and "Multi action home button" using adb install.
Use adb shell am start -a android.intent.action.MAIN to change the main launcher to your launcher.
Then change the setting of Multi Action Home button (say, the height should be large to be visible in the bottom) and assign its function to be Home for click and Back for double-click.
Whenever you want to use Sony's apps (these are good for pdf markup), just push the home button to open the pop-up menu.
Otherwise, touch the Multi Action Home Button to access to other Android apps. So far I've never experience any crash.
Yet more tips:
Some complain fonts are too small after installing generic apps.
adb shell wm density 320 changes your DPI by 2 times (160 is a default value.) EDIT: I found 200 is quite enough that does not distort Sony apps too much.
My application is using "Tasker" to execute the above code when specific apps are open and execute wm density reset when the apps are closed.
The reason why we cannot change the global DPI is sadly because it makes the default apps by Sony so awkward.
Alternatively, I could successfully install Xposed to try App Settings but this app crashed.
You can also install Gboard (but it has no hide button, so prepare with virtual back button) if you need another keyboard.
Enjoy your DPT devices
--
Sony recently released a new digital paper device DPT-RP1, apparently using their own linux firmware but underlying on Android 5.1.1. Few weeks ago, some Chinese successfully hacked it to jailbreak for third-party apps (without changing the original firmware), but they don't share any information to sell those hacked devices. I'm willing to pay for it, but it is too risky to send my device to China so I'm trying to root it by myself.
I don't know much about this world, but I found some information that might be helpful. It uses Marvell A140 IoT Processor a.k.a. PXA1908. There are two Android smartphones (as the same version 5.1.1) with this chip - Samsung Xcover 3 and Samsung Galaxy Grand Prime. Fortunately, they have been both rooted in the past here.
Is this information really helpful to root my device? If so, is there any way to apply the previous methods to easily jailbreak DPT-RP1? I think the problem here is that it does not look like Android at all, so has no setting menu or developer tools. And not sure how to enter to the recovery mode since it only has two buttons - power/menu.
I'd appreciate any help or advice. Thanks!
And here you can find source codes.
oss.sony.net/Products/Linux/dp/DPT-RP1.html
sartrism said:
Sony recently released a new digital paper device DPT-RP1, apparently using their own linux firmware but underlying on Android 5.1.1. Few weeks ago, some Chinese successfully hacked it to jailbreak for third-party apps (without changing the original firmware), but they don't share any information to sell those hacked devices. I'm willing to pay for it, but it is too risky to send my device to China so I'm trying to root it by myself.
I don't know much about this world, but I found some information that might be helpful. It uses Marvell A140 IoT Processor a.k.a. PXA1908. There are two Android smartphones (as the same version 5.1.1) with this chip - Samsung Xcover 3 and Samsung Galaxy Grand Prime. Fortunately, they have been both rooted in the past here.
Is this information really helpful to root my device? If so, is there any way to apply the previous methods to easily jailbreak DPT-RP1? I think the problem here is that it does not look like Android at all, so has no setting menu or developer tools. And not sure how to enter to the recovery mode since it only has two buttons - power/menu.
I'd appreciate any help or advice. Thanks!
Click to expand...
Click to collapse
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
Click to expand...
Click to collapse
Thanks for suggesting a general principle! I just use the word jailbreaking not because I'm an iPhone user. What I actually want to do as the first step is not rooting an android system, but revealing it from the current customized linux system. Rooting is the next step if necessary. If the word choice is still not accurate and bothers you, I apologize.
It has apparently no typical bootloader, and neither PC nor adb recognize it as an android device. In fact, direct USB file transfer is blocked so I need to use Sony's designated software. But an android system surely coexists according to the hacker who already rooted it.
sartrism said:
Thanks for suggesting a general principle! I just use the word jailbreaking not because I'm an iPhone user. What I actually want to do as the first step is not rooting an android system, but revealing it from the current customized linux system. Rooting is the next step if necessary. If the word choice is still not accurate and bothers you, I apologize.
It has apparently no typical bootloader, and neither PC nor adb recognize it as an android device. In fact, direct USB file transfer is blocked so I need to use Sony's designated software. But an android system surely coexists according to the hacker who already rooted it.
Click to expand...
Click to collapse
Without some kind of way to flash or interface with the device there isn't much you can do.
I have a kindle fire HD that didn't come with a typical android system but does have a typical bootloader. The Amazon OS was removed and now it's full blown android but it required a "second" bootloader. You don't have a bootloader so I'm not sure what your options are with that device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Jailbreaking is the process of modifying any electronic device in order to remove restrictions imposed by a manufacturer (Apple) or operator (to allow the installation of unauthorized software).
Rooting is the act of gaining access to the root account of a device (such as a smartphone or computer).
There is a huge difference between the two. You can't just say that rooting is Android's version of jailbreaking. Not accurate in the least.
https://www.androidpit.com/jailbreak-android
Sent from my SM-G928T using Tapatalk
MarkBell said:
Jailbreaking is the process of modifying any electronic device in order to remove restrictions imposed by a manufacturer (Apple) or operator (to allow the installation of unauthorized software).
Rooting is the act of gaining access to the root account of a device (such as a smartphone or computer).
There is a huge difference between the two. You can't just say that rooting is Android's version of jailbreaking. Not accurate in the least.
https://www.androidpit.com/jailbreak-android
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
You're reading too much into what I said.
Basically, what I said was that jailbreaking isn't an android thing, it's an Apple thing(didn't say it was exclusively an Apple thing, just NOT an android thing). It applies to more than just Apple devices but on this website dedicated to mobile platforms, I'm only referring to its application in the mobile device world. For the mobile world it's pretty much only an Apple thing(still not exclusively but mostly so).
Then I said that in the android world it's called rooting(not exclusively an android thing, just NOT an Apple thing). And that jailbreaking and rooting aren't the same thing(this does not say that rooting is android's version of jailbreaking, that would imply that they are the same thing, I'm saying they aren't the same thing)
Basically, explaining what they "aren't", you explained what they "are".
I understand the difference, but thank you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You're reading too much into what I said.
Basically, what I said was that jailbreaking isn't an android thing, it's an Apple thing(didn't say it was exclusively an Apple thing, just NOT an android thing). It applies to more than just Apple devices but on this website dedicated to mobile platforms, I'm only referring to its application in the mobile device world. For the mobile world it's pretty much only an Apple thing(still not exclusively but mostly so).
Then I said that in the android world it's called rooting(not exclusively an android thing, just NOT an Apple thing). And that jailbreaking and rooting aren't the same thing(this does not say that rooting is android's version of jailbreaking, that would imply that they are the same thing, I'm saying they aren't the same thing)
Basically, explaining what they "aren't", you explained what they "are".
I understand the difference, but thank you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I tend to read too deeply into everything. It's the way I am. Lol.
Sent from my SM-G928T using Tapatalk
Could you please post some information about usb device? Just like PID & VID.
Do it like:
Connect DPT-RP1 to Linux, and then type this command 'lsusb'
P.S. Under Windows or MacOS system, you can find the information from system settings...
happy to help with simple things
thisvip said:
Could you please post some information about usb device? Just like PID & VID.
Do it like:
Connect DPT-RP1 to Linux, and then type this command 'lsusb'
P.S. Under Windows or MacOS system, you can find the information from system settings...
Click to expand...
Click to collapse
Bus 001 Device 008: ID 054c:0be5 Sony Corp.
It is good to see some people have been interested in this thread.
So far, I realized that the hacker used a hardware hacking method. I actually obtained the hacked system apps from one of his customer. I guess he did sometihng like directly modifying eMMC to root and put "USBDeviceSwitcher.apk" to allow an usual USB connection. Since I don't want to take such risk, I decided to wait until the first firmware to see if there could be an indirect way to penetrate the system files. But if you want to analyze the hacked system, contact me.
sartrism said:
It is good to see some people have been interested in this thread.
So far, I realized that the hacker used a hardware hacking method. I actually obtained the hacked system apps from one of his customer. I guess he did sometihng like directly modifying eMMC to root and put "USBDeviceSwitcher.apk" to allow an usual USB connection. Since I don't want to take such risk, I decided to wait until the first firmware to see if there could be an indirect way to penetrate the system files. But if you want to analyze the hacked system, contact me.
Click to expand...
Click to collapse
Does it have a web browser? Maybe you can utilize for example the Stagefright Exploit + DirtyC0W to get root.
I have found out some interesting stuff about the device with the help of the Digital Paper App.
The app is built using electron and there is a file: /Applications/Digital\ Paper\ App.app/Contents/Resources/app.asar
This file contains the electron javascript files, which handle all the communication with the device.
It can be extracted with: sudo asar extract app.asar output
(github_com/electron/asar)
This also requires node to be installed: with e.g. brew install node (changelog_com/posts/install-node-js-with-homebrew-on-os-x)
The app communicates with the device via Restlet-Framework/2.3.7 on port 8443 with tcp (no matter if it is the bluetooth, wifi or usb connection).
This is the only port that is open.
In the file: /Applications/Digital\ Paper\ App.app/Contents/Resources/output/node_modules/mw-error/lib/codeparams.js you can find all the relative paths, which are getting called during e.g. file transfer, firmware update and stuff.
Running the app and placing breakpoints reveals that before you can transfer files and stuff:
'/auth'
'/auth/nonce/'
are called in order to authenticate, which looks e.g. like url digitalpaper.local:8443/auth/nonce/1e9ee24d-6613-433a-9770-76b04333ac95
the last part of the call is the "client_id": "1e9ee24d-6613-433a-9770-76b04333ac95", which is retrieved via the url digitalpaper.local:8443/auth call.
digitalpaper.local:8443/auth/
Important:
In /Applications/Digital\ Paper\ App.app/Contents/Resources/output/lib/config.js
change the line
config.DEVBUILD = false;
to
config.DEVBUILD = true;
After you finished your modifications you have pack the output folder again:
sudo asar pack output app.asar
I did not have time to continue, but the following relative urls look promising (especially recovery_mode):
'/testmode/auth/nonce',
'/testmode/auth',
'/testmode/launch',
'/testmode/recovery_mode',
'/testmode/assets/{}',
mcplectrum said:
I have found out some interesting stuff about the device with the help of the Digital Paper App.
The app is built using electron and there is a file: /Applications/Digital\ Paper\ App.app/Contents/Resources/app.asar
This file contains the electron javascript files, which handle all the communication with the device.
It can be extracted with: sudo asar extract app.asar output
(github_com/electron/asar)
This also requires node to be installed: with e.g. brew install node (changelog_com/posts/install-node-js-with-homebrew-on-os-x)
The app communicates with the device via Restlet-Framework/2.3.7 on port 8443 with tcp (no matter if it is the bluetooth, wifi or usb connection).
This is the only port that is open.
In the file: /Applications/Digital\ Paper\ App.app/Contents/Resources/output/node_modules/mw-error/lib/codeparams.js you can find all the relative paths, which are getting called during e.g. file transfer, firmware update and stuff.
Running the app and placing breakpoints reveals that before you can transfer files and stuff:
'/auth'
'/auth/nonce/'
are called in order to authenticate, which looks e.g. like url digitalpaper.local:8443/auth/nonce/1e9ee24d-6613-433a-9770-76b04333ac95
the last part of the call is the "client_id": "1e9ee24d-6613-433a-9770-76b04333ac95", which is retrieved via the url digitalpaper.local:8443/auth call.
digitalpaper.local:8443/auth/
Important:
In /Applications/Digital\ Paper\ App.app/Contents/Resources/output/lib/config.js
change the line
config.DEVBUILD = false;
to
config.DEVBUILD = true;
After you finished your modifications you have pack the output folder again:
sudo asar pack output app.asar
I did not have time to continue, but the following relative urls look promising (especially recovery_mode):
'/testmode/auth/nonce',
'/testmode/auth',
'/testmode/launch',
'/testmode/recovery_mode',
'/testmode/assets/{}',
Click to expand...
Click to collapse
Hope you get some result from wifi side. I also realized they use the port 8443 but couldn't get further as you.
For whom trying to hack it, here is the link for the already 'hacked' system apps (including the original files) - that of the famous hacked RP1 video. Inside the subfolder S1, there are also the hacked system apps for DPT-S1 just in case.
https://www.dropbox.com/sh/dvtvokdzrgwjc83/AACXOJA-E56nUpUfiWUOzrM3a?dl=0
George Malas said:
Does it have a web browser? Maybe you can utilize for example the Stagefright Exploit + DirtyC0W to get root.
Click to expand...
Click to collapse
The stock device has no web browser, no sd-card, no usb connection, and no typical system. I think SONY was haunted by some security issues maybe because they thought the major users are lawyers or very important people? lol
Any chance to create a buffer overflow PDF to attack RP1's pdf reader?
I am unable to help, but wanted to let you know I am definitely interested in and supportive of this. If this device can be unlocked as suggested in that one youtube video then I would buy it, despite the steep price.
jess91 said:
I am unable to help, but wanted to let you know I am definitely interested in and supportive of this. If this device can be unlocked as suggested in that one youtube video then I would buy it, despite the steep price.
Click to expand...
Click to collapse
If you're interested and supportive of this then go buy one anyway and apply yourself to going forward figuring out how to get it done. Other than that, you're not supportive, you're just hopeful that someone figures it out and then you'll probably go get one.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hey guys,
I also recently got the RP1 and am also looking for ways to mod it. Big kudos and thanks to all of you for posting this! This alread is amazing. @sartrism: can you maybe give me a hint how to load the files on the rp1? Sorry if this might be a stupid question but I'm new to adroid and that stuff.
Paderico said:
Hey guys,
I also recently got the RP1 and am also looking for ways to mod it. Big kudos and thanks to all of you for posting this! This alread is amazing. @sartrism: can you maybe give me a hint how to load the files on the rp1? Sorry if this might be a stupid question but I'm new to adroid and that stuff.
Click to expand...
Click to collapse
Just a little update from my side. I'm currently tryng to recreate the steps @mcplectrum was using. It seems that my RP1 also uses other ports. I tried to wireshark the USB and WiFi connection. By that I saw that often GET /registration/information is called for Host: localhost:58052. Moreover the first call is GET /register/serial_number also on port 5808. This was via USB.
Trying to trigger the /auth/ call via Telnet returns nothing unfortunately. But also the 8080 port is open. Trying to call digitalpaper.local:8443/auth/ returns nothing on firefox.
@mcplectrum: how did you get the client_id and what would one need that for?
I also tried to change the config.DEVBUILD to true but that seemed to change nothing at all.
So to sum up what we know:
The device is using some kind of android structure, the source code seems to use the uboot bootloader, all communication is done by a rest restlet framework. So actually there should be some kind of way to use the restlet framework to PUT or POST the modified files.
The other option would be directly flash the eMMC right? I would take the risk and just load it on my device and see what happens. Any hints on how to do that?
I got the Mate 20 X from Italy, delivered two weeks after order on November 12 for € 829, VAT and 2-years warranty included. It is a nice silver device 6/128 (don’t need more memory). My first hands-on impression? I was shocked.
I had pure Chinese phones before (Huawei and Lenovo) and I know how to deal with them. That wasn’t what upset me. And it wasn’t EMUI either, I like some of its functionality and I know how to customize it.
But my previous phone was Mate 10 pro (international, not Chinese), which really works well and comparison with a newcomer is what really shocked me. The EVR_AL00 came slow and clumsy with those big fat letters and ugly ios-like icons on the screen. I tried to improve the look with increasing the smallest width in the developer options, but original resolution came back with every reset.
So what I did first, is factory reset (I usually perform it on every new phone). I lost Google Play but I didn’t care, I intended to install and adjust Google apps anyway.
And then I started to customize the phone. Basically, it means “dechinezed” and “deiosinezed” it and make it usable for my purposes as the daily driver. Eventually, I succeeded and like before I don’t regret that I bought the Chinese phone as I never regretted before. I believe that my customization demands would request almost the same amount of work and effort with the “international” version.
And with “dechinezed” I don’t mean to be impolite, actually, I like some of the features of China phones, some of them after years comes to western phones as well (night sight, close all apps etc). I just prefer the more Android look of the phone (even more than currently, Google delivers).
The actual status of my phone is as follows:
In the beginning, when I started phone manager, the performance never exceeded 69%. It seems that later it adapted and healed itself (maybe with help of AI) and now performance is usually over 90, close to 100% and the phone suddenly becomes snappy and smooth, slightly better than Mate 10 pro. As expected, the battery life is due to its capacity and with my way of use it could easily survive two days. I don’t have exact data on SOT and other parameters of the battery performance yet. By adjusting the text and display size (both too small) under settings/display the phone gets a nicer look and more usable size of applications.
I had decided to keep EMUI launcher before I learned that the phone has a hard time with other launchers. I bought Nova Prime once, I consider it a great launcher, maybe the best, but even on my previous phone I used EMUI. The reason is in its features that I don’t want to sacrifice: dedicated Accuweather, swype gestures (now with 9), dark mode. I was never a fan of ios-like white themes, I always considered that Android’s color is black. Besides, what even Google admits now (and started to return black mode into its apps accordingly), the white mode consumes a lot more energy (especially with AMOLED). What is yet to admit is that it burns your eyes.
So, what I have now, is a fully customized EVR_AL00 that perfectly suits my needs. That means that it looks like Android, works like Android and behaves like Android. I replaced most Chinese apps with Google’s ones, installed additional that I use and tune the system. With tuning the system I mean screen adjustment and customization. Under Settings/Display/text and display size, I changed both values to small and thus converted ugly appearance of the display into something that suits size and purpose of the phone. I replaced IOS icons with the Android ones. Adjusted notifications and permissions for each application.
First I was thinking about keeping some Chinese apps that I considered useful, like Sky Mobile and a few others. But trying them I found out that all of them are more or less connected either with Chinese environment or payment system and therefore eventually I removed them all. After I had to perform the factory reset I was only got more careful with apps that I disabled. And according to my orientation, I kept Email, at least until Google implements dark color in Gmail. And kept useful utilities: (Manager, Gallery, Remote…).
Otherwise, I use Google Phone (the amazing last beta from: https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218, thank you Martin), Messages, Translate (removed nonfunctional MS Translate), Auto, Duo, Voice, Photos, Trips, Pay, Assistant, Lens, Google, Chrome, and of course all Google system apps. I also use third-party apps like VLC, Xiaomi calculator and YouTube vanced. Pretty much everything works as expected, including notifications to the extent that suits my way of use. After I erased Hivoice, Assistant works together with the hot word, if the screen is turned on (never wished to use it from turned off screen). The red mic on notification bar of the attached picture shows that assistant is active.
All banks application work. Google Play is not working at the moment but I expect that it will eventually. Currently, failure is the result of poor synchronization between Chinese EMUI and Google Android. No point to call the bank, it is the last one to solve the problem. The problem will be solved with the new EMUI or Play Services, because there is no material obstacle for G Play (SafetyNet passed and bank card is recognized and could be used online). I have another identical payment system installed (Inteso SP) and it works flawlessly.
CUSTOMIZATION
In order to adapt the phone to my needs, I had to deal with existing Chinese application first. I had to either: 1) remove them, 2) hide them, or 3) disable (erase) them.
Removing apps
Removing apps was easy. Just uninstall Chinese in Settings/Apps. As I said, I did it thoroughly and indiscriminately.
Hiding apps
My overall objective is to have only one home screen page. I’m fed up with slippery pages interfering with gestures. And besides, I decided to use gestures (swype) as system navigation and therefore swyping between homepages could be annoying even more.
In order to have only one home page, I have to use folders and hide auxiliary functional apps (like download, OTA, backup, clock..etc).
Surprisingly I found that Tweaker for Huawei works pretty well with EMUI9, although it is an old application: https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.emuitweaker&hl=en. One of its functions is triggering the abandoned EMUI gesture that enables hiding any application and thus removing it from the home screen without affecting its functionality.
Disabling (erasing) apps
To “remove” any nonremovable application without root you need a computer with the adb command-line tool. In fact, this method never removes any application, rather disables and hides it for the current user. So it doesn’t affect OTA and it doesn’t revert after reset either. It does come back after factory reset though.
The method of erasing an app works through adb (so adb must be installed on the computer – either Windows or Linux) and it requests the following syntax in command line:
1. adb devices (and after that setting permission on the phone)
2. adb shell
3. pm unistall -k --user 0 <package name>
where <package name> is not the name of the application as it shows but the name of the installed package, which must be discovered and one of the apps which could do that effectively could be found here: https://play.google.com/store/apps/details?id=pl.itto.packageinspector&hl=en.
(for example: pm uninstall -k --user 0 com.huawei.wallet)
A basic idea what to disable could be found here: https://forum.xda-developers.com/note-10/how-to/guide-to-remove-apps-root-t3828324. Of course, what to disable always depends on personal preferences and therefore this list should be taken with a grain of salt.
So, after arranging applications there comes the final stage of making the phone Android again. EMUI makeover. For that, we need this EMUI editor: https://play.google.com/store/apps/details?id=com.mixapplications.themeeditor.
But there is a bad news. It doesn’t work with EMUI 9 (yet). What now? There are two possibilities: either finding a good theme and simply installing it (there are plenty of them, only I didn’t test if they are working with EMUI 9 (some of the android likes are to be found in the Playstore under Hamzio7 or here: https://forum.xda-developers.com/mate-10/themes/pure-black-theme-emui-8-t3719904.
The other possibility is to find a phone with EMUI 8 and compile the hwt file there and transfer it to Mate 20 X. That is what I did. The system will warn you that it is an old version of the theme and it might not work well but skip that. It works just fine.
Don’t judge the solution by my design. I’m a modest guy, more practically oriented. You may have almost any design that you wish.
And of course, if you decide to experiment with this stuff yourself, you should be aware that you are the only one taking the risk. I honestly believe that you can’t, if you are not extremely innovative, irretrievably destroy anything, but even factory reset might be sometimes really annoying.
Good luck with your brand new Chinese Mate 20 X.
Great post Just a couple of questions:
1) Are your notifications working perfectly? By that, I mean without delay under both wi-fi and mobile networks, with screen on and screen off? If so, what did you do to achieve this?
2) Do you mind sharing where did you buy the device from?
Nice job! Looking even more forward to the arrival of my Mate 20 X!
@piskr
Would you mind give some steps to get google phone and Messages to work properly. When phone call comes in, my phone call screen does not come on. Messages only works sometime and sometime message does not send. Thanks.
Genoveffo said:
Great post Just a couple of questions:
1) Are your notifications working perfectly? By that, I mean without delay under both wi-fi and mobile networks, with screen on and screen off? If so, what did you do to achieve this?
2) Do you mind sharing where did you buy the device from?
Click to expand...
Click to collapse
1) Yes, notifications work flawlessly in my extent of use, both with the screen on and off. I don't use exotics like telegram or whatsapp though. It's a matter of permissions and notification settings. Be aware that each notification had to be set separately and checked under application and under notification sector under settings. And also have in mind that if you install the third party phone, it is just addition of original phone (under app/system processes), and the later must remain active and has its own permissions and notification as well. Phone app has different system structure than SMS. You can simply erase Huawei messaging and replace it with the Google one (haven't tried others).
2) You can find here both color and memory variants: https://www.ilmultistoredelzazza.eu...l_Sim_EMUI_9_Android_9/p1748191_19236868.aspx
wingzero said:
@piskr
Would you mind give some steps to get google phone and Messages to work properly. When phone call comes in, my phone call screen does not come on. Messages only works sometime and sometime message does not send. Thanks.
Click to expand...
Click to collapse
You should really carefully check and set both permissions and notifications for each application. And remember that you mustn't neglect the system phone app.
piskr said:
You should really carefully check and set both permissions and notifications for each application. And remember that you mustn't neglect the system phone app.
Click to expand...
Click to collapse
I checked all the settings and seem to be correct unless I missed some steps.
wingzero said:
I checked all the settings and seem to be correct unless I missed some steps.
Click to expand...
Click to collapse
OK. Here are my settings.
You do know there's an EVR-L international models, right? Why not just get that instead? That's what I have.
piskr said:
OK. Here are my settings.
Click to expand...
Click to collapse
Thanks for taking the time to post the screen shots. All my the settings are the same except I don't the phone app on your last screen shot. Did you download it or it's a stock app?
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
MishaalRahman said:
You do know there's an EVR-L international models, right? Why not just get that instead? That's what I have.
Click to expand...
Click to collapse
It's too late. I already bought the China version. It's too much hassle try to sell it.
wingzero said:
Thanks for taking the time to post the screen shots. All my the settings are the same except I don't the phone app on your last screen shot. Did you download it or it's a stock app?
---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------
It's too late. I already bought the China version. It's too much hassle try to sell it.
Click to expand...
Click to collapse
That's right, the last one is Google phone from the link I published and it works just fine (I really recommend it, it has so many opportunities). But you have managed to get notifications neither on the home screen nor on the lock screen? Neither for messages nor for the phone? If I were you I would go from setting to setting for this two apps and inspect every item very carefully. It is possible in this early stage of EMUI9 that it has some weird glitches occurring randomly on some phones but it is not very likely. A small overlooked detail in settings could mean everything.
Otherwise, I don't regret that I bought the Chinese version. Now I've got everything that I would have with the international variant. Only I don't have working Google pay yet, but so far I haven't seen a clear statement that it really works on international Mate 20x either. To work means to be able pay with the phone not only loading a card, that's what I did too. Otherwise, I got a good price (€660 before VAT), integrated call recorder and rooting opportunity.
And regarding crap, international one has it too. I've got international Mate 10 pro and I know it. Besides Chinese one additional western, baked in (MS, Facebook, Google's and third party's).
@piskr
The phone will ring on the google phone app but the screen does not come. I will play with the settings and figure it out. Thanks for all the help.
Thank you. This helped get me to a non-Chinese specifc phone.
Attachin my ADB run.
UPDATE: Please check out AJ's great thread https://forum.xda-developers.com/mate-20-x/how-to/guide-remove-apps-adb-t3870727
I mistakenly removed one item (com.huawei.android.hwouc) I shouldn't have and I amnot getting OTAs (which I also turn off automatic ones in dev options, but if I want one, I lost it them).
Rudolpht said:
Thank you. This helped get me to a non-Chinese specifc phone.
Attachin my ADB run.
Click to expand...
Click to collapse
As I'm not well schooled on ADB. How would you apply this? And why 2 Zips? Gracias
See beginning of the thread and other threads on ADB. Same list, mine in txt or zip, same file, not necessarily good for everyone.
Sent from my HWEVR using XDA Labs
def-g said:
As I'm not well schooled on ADB. How would you apply this? And why 2 Zips? Gracias
Click to expand...
Click to collapse
Here's my Spreadsheet with a quick guide in it along with the adb files you'll need.
https://forum.xda-developers.com/mate-20-x/how-to/guide-remove-apps-adb-t3870727
Once you get the list of packages on your AL00 just run the fastboot command to remove each one.
wingzero said:
@piskr
The phone will ring on the google phone app but the screen does not come. I will play with the settings and figure it out. Thanks for all the help.
Click to expand...
Click to collapse
Wondering if you had any luck. Some people actually use a phone as a phone
Sent from my HWEVR using XDA Labs
Rudolpht said:
Wondering if you had any luck. Some people actually use a phone as a phone
Sent from my HWEVR using XDA Labs
Click to expand...
Click to collapse
I got it working. I am using the stable v.25 version. What I did was after selected the google phone as default dialing app, I go back to default apps and click the stock phone and then click the google phone again. I did this by chance and luck. Hope this will solve your issue. The stock phone app is horrible. Make sure you use the stable version. Good luck.
wingzero said:
I got it working. I am using the stable v.25 version. What I did was after selected the google phone as default dialing app, I go back to default apps and click the stock phone and then click the google phone again. I did this by chance and luck. Hope this will solve your issue. The stock phone app is horrible. Make sure you use the stable version. Good luck.
Click to expand...
Click to collapse
Thanks man.
Sent from my HWEVR using XDA Labs
Now it's 27. And so far everything work. Regarding comments on the forum we are on the privileged side. Just be sure to set notifications and permissions right.
On Joying headunits with CAN Bus, it is not possibile to use resistor based USWC: this thread aims to overcome the limitation by using an Arduino MICRO connected to the receiving unit of the USWC and to the headunit via USB to simulate a hardware keyboard.
reserved 1
Github repository: https://github.com/MobeedoM-opensource/android-auto
reserved 2
reserved 3
surfer63 said:
In your code you also use the BOOT_COMPLETED broadcast. You know that with the Joying deep-sleep option, you will see that only on rare occasions? This is: only on reboots or power (dis)connects?
Click to expand...
Click to collapse
Yes i know thank you, i noticed that for some strange reason the firmware deactivates the accessibility service even at reboot (at true boot not only with ACC_OFF).
You use the "com.fyt.boot.ACCON" intent filter in your services. If it doesn't have serious consequences please also add the "com.glsx.boot.ACCON" for those users on Sofia that might want to start using your app as well. But this in turn would also require the "minSdkVersion 23" instead of "minSdkVersion 24" like you have now. My PX5 is on 8 so I have api level 26, but my old Sofia on the bench is on 6.0.1 and it would be handy to test there first. (I tried to build your code, but there are many "hurdles" in your app/build.gradle, so I need to dive a little deeper into it)
Click to expand...
Click to collapse
Yes of course i'll add the intent filter, but please note that the current version of the app doesn't use those intents on api level 26+ (my headunit), because of the background execution limits (the implicit intent is simply not received).
The only intent that i was able to trap, but i still need to investigate because it doesn't always work and I haven't figured out why yet, is the android.hardware.usb.action.USB_DEVICE_ATTACHED.
For the build.gradle, if you tell me what are the hurdles maybe i can help, also via PM if you prefere.
You have the method startAccessibilityService with the rooted system call: What does that actually do? Is it for the user to give access? Or the system to give access (as it is rooted)? Is it for the root_preference "OnlyBroadcast"?
Click to expand...
Click to collapse
An accessibility service cannot be started programmatically in android, the user must manually activate it with the switch in the accessibility services section.
That command is used to simulate the behavior of the user who changes the state of the switch, it requires root and it is not granted to work on all roms.
You use the "getCurrentForegroundPackage()". I guess this still works if your have (for example) your navi app in the foreground and your media player in the background and you want to skip to the NEXT, as you automatically come to the last "if" statement in your MediaKeysMapper. But does this also work when your navi app is the foreground program and you are listening to the radio or some "generic_syu" program in the background?
Click to expand...
Click to collapse
Yes you are right, the last use case is not covered. To manage it correctly you need to know which app is currently playing, maybe it is possbile to distinguish syu apps by non syu apps by checking the android AudioManager which i think is only used by non-syu apps.
bambapin said:
Yes of course i'll add the intent filter, but please note that the current version of the app doesn't use those intents on api level 26+ (my headunit), because of the background execution limits (the implicit intent is simply not received).
The only intent that i was able to trap, but i still need to investigate because it doesn't always work and I haven't figured out why yet, is the android.hardware.usb.action.USB_DEVICE_ATTACHED.
For the build.gradle, if you tell me what are the hurdles maybe i can help, also via PM if you prefer.
Click to expand...
Click to collapse
I know about the implicit intents, but on a Sofia on Android 6.0.1 (api level 23) they should still work.
W.r.t. the build.gradle.
I had to remove the private.gradle import statement, some signing statements, defProd and the like, and finally (also literally in time) upgrade my sdk from 27 to 29 to be able to do a simple "./gradlew assembleDebug".
So no issues anymore.
(Of course I had set compile version to 27 in the build.gradle, but I ran into "missing" xmls, which I first blamed on being not committed to the repo (your fault, not mine of course ), but which turned out to be part of sdk 28 and up, so still my fault ).
surfer63 said:
W.r.t. the build.gradle.
I had to remove the private.gradle import statement, some signing statements, defProd and the like, and finally (also literally in time) upgrade my sdk from 27 to 29 to be able to do a simple "./gradlew assembleDebug".
Click to expand...
Click to collapse
Ah yes, the private.gradle... it contains my private keys passwords so i preferred not to publish them on the internet .
Indeed that file must be placed next to the app build.gradle with this content:
Code:
ext {
my_keyAlias = 'YOUR_KEY_ALIAS'
my_keyPassword = 'YOUR_KEY_PASSWORD'
my_storeFileName = 'YOUR_KEYSTORE_FILEPATH'
my_storePassword = 'YOUR_KEYSTORE_PASSWORD'
}
bambapin said:
Yes you are right, the last use case is not covered. To manage it correctly you need to know which app is currently playing, maybe it is possbile to distinguish syu apps by non syu apps by checking the android AudioManager which i think is only used by non-syu apps.
Click to expand...
Click to collapse
Maybe I insult you with providing this link , but anyway: here it is: https://developer.android.com/guide/topics/media-apps/mediabuttons
And the image in post #1. How is red and black connected, and to what?
surfer63 said:
Maybe I insult you with providing this link , but anyway: here it is: https://developer.android.com/guide/topics/media-apps/mediabuttons
And the image in post #1. How is red and black connected, and to what?
Click to expand...
Click to collapse
No insults at all don't worry and even if it were i hardly get offended
Actually i'm not expert on this particular topic, at the beginning i tried to use the standard Android MediaControllers but it seemed to me that when it came to "syu" APPS everything was bypassed, but if you think it's a viable way i'll try again.
The photo is the final version that is now installed in the car.
I noticed that there was enough room inside the SWC receiver to insert the arduino, i made a little hole for the usb socket and i connected the arduino directly (yes i admit, i soldered to save the space of dupont ).
What you see is the inside of the receiver + the arduino. The black and red cables are the power supply of the receiver, the orange and blue are KEY1 and KEY2 (the white and gray of the video). The arduino is simply glued with a removable glue (patafix).
@surfer63 i was thinking again about the autostart after the ACCON.
In the end i managed to make the intent android.hardware.usb.action.USB_DEVICE_ATTACHED always work so the accessibility service is always restarted, but i'm still looking for a better alternative (using the navi app would work but it interfere with the audio mixing level).
I looked again at the code of syu.ms and saw that when the unit wakes up, a series of apps are always launched with hard-coded package names: eg. "com.yh.devicehelper" and "com.cpsdna.mirror" which i don't seem to find installed in the headunit.
Do you have any idea what they are?
If they are never installed, perhaps it is enough to create an app with one of those package names and the system will take care of starting it at ACCON.
bambapin said:
No insults at all don't worry and even if it were i hardly get offended
Actually i'm not expert on this particular topic, at the beginning i tried to use the standard Android MediaControllers but it seemed to me that when it came to "syu" APPS everything was bypassed, but if you think it's a viable way i'll try again.
The photo is the final version that is now installed in the car.
I noticed that there was enough room inside the SWC receiver to insert the arduino, i made a little hole for the usb socket and i connected the arduino directly (yes i admit, i soldered to save the space of dupont ).
What you see is the inside of the receiver + the arduino. The black and red cables are the power supply of the receiver, the orange and blue are KEY1 and KEY2 (the white and gray of the video). The arduino is simply glued with a removable glue (patafix).
Click to expand...
Click to collapse
I do indeed think that the SYU apps do nothing according standard Android rules, so the MediaController would only be helpful for any other app. I do think you need to check if "some" SYU app is active by using something like "this" or by checking the com.syu.ms apk (via jadx(-gui)) or so, because that one also checks on several places whether one of its own SYU app is active or not, and on top or not.
So the bottom side of of the plate with the red led and condensator (or so), is the bottom of the SWC controller circuit?? If so, the image now makes sense.
surfer63 said:
So the bottom side of of the plate with the red led and condensator (or so), is the bottom of the SWC controller circuit?? If so, the image now makes sense.
Click to expand...
Click to collapse
Yes, it is the bottom, when it is inserted it rests on the 4 pillars and leaves enough space below, there will be almost 1cm from the arduino.
The only negative thing i noticed is that with the arduino so close to the antenna the reception distance of the buttons is a little lower than before, but they still work.
bambapin said:
@surfer63 i was thinking again about the autostart after the ACCON.
In the end i managed to make the intent android.hardware.usb.action.USB_DEVICE_ATTACHED always work so the accessibility service is always restarted, but i'm still looking for a better alternative (using the navi app would work but it interfere with the audio mixing level).
I looked again at the code of syu.ms and saw that when the unit wakes up, a series of apps are always launched with hard-coded package names: eg. "com.yh.devicehelper" and "com.cpsdna.mirror" which i don't seem to find installed in the headunit.
Do you have any idea what they are?
If they are never installed, perhaps it is enough to create an app with one of those package names and the system will take care of starting it at ACCON.
Click to expand...
Click to collapse
It worked!!! :laugh:
The app attached is automatically launched by the syu.ms at ACC_ON.
I used the package name "com.cpsdna.mirror", i have no idea what the original app was supposed to do, but now we have a real autorunner at our disposal.
bambapin said:
It worked!!! :laugh:
The app attached is automatically launched by the syu.ms at ACC_ON.
I used the package name "com.cpsdna.mirror", i have no idea what the original app was supposed to do, but now we have a real autorunner at our disposal.
Click to expand...
Click to collapse
:good: Very nice.
There are many apps in this ms.apk that no longer exist. Some are hardcoded called inside the app, some are called via the text files in the assets/property, but no longer exist.
I assume it is related to http://www.cpsdna.com/solutions1.html and a previous "mirrorlink" application. zlink is now by another company.
What I would do (and did in the past) is making a "micro starter app" (11~16Kb) , that only starts the app you want. So the "com.cpsdna.mirror" started by ACC_ON, starts your "com.mobeedom.android.auto.jyhuremote".
If Joying/FYT updates their list of started apps, you can simply take another "old" app and still call your own app without having to rewrite all the packages inside your own code.
(And please don't use the appcompat for such a microstarter . It explodes your code from ~11-16Kb to 1.5MB. I really hate how Studio always adds that to your project even if you target APIs that don't need it, or your app as such doesn't need it)
It would only need something like:
Code:
PackageManager pManager = context.getPackageManager();
Intent intent = pManager.getLaunchIntentForPackage("com.mobeedom.android.auto.jyhuremote");
if (intent != null) {
context.startActivity(intent);
}
surfer63 said:
:good: Very nice.
There are many apps in this ms.apk that no longer exist. Some are hardcoded called inside the app, some are called via the text files in the assets/property, but no longer exist.
I assume it is related to http://www.cpsdna.com/solutions1.html and a previous "mirrorlink" application. zlink is now by another company.
What I would do (and did in the past) is making a "micro starter app" (11~16Kb) , that only starts the app you want. So the "com.cpsdna.mirror" started by ACC_ON, starts your "com.mobeedom.android.auto.jyhuremote".
If Joying/FYT updates their list of started apps, you can simply take another "old" app and still call your own app without having to rewrite all the packages inside your own code.
(And please don't use the appcompat for such a microstarter . It explodes your code from ~11-16Kb to 1.5MB. I really hate how Studio always adds that to your project even if you target APIs that don't need it, or your app as such doesn't need it)
It would only need something like:
Code:
PackageManager pManager = context.getPackageManager();
Intent intent = pManager.getLaunchIntentForPackage("com.mobeedom.android.auto.jyhuremote");
if (intent != null) {
context.startActivity(intent);
}
Click to expand...
Click to collapse
Ok ok, no AppCompat
Maybe i could also put a minimum of parameterization with the ability to choose what to launch, maybe even more than one app.
Do you think something like this could be useful in your JET?
bambapin said:
Ok ok, no AppCompat
Maybe i could also put a minimum of parameterization with the ability to choose what to launch, maybe even more than one app.
Do you think something like this could be useful in your JET?
Click to expand...
Click to collapse
I don't see it yet. What would be useful to start from my Jet apk? Can you explain?
Please also note that when I started the JET apk I knew absolutely nothing about java (and didn't want to know anything about java) and started in appinventor/thunkable, as that was easy enough. But it is a big mess of all kind of shell scripts called from my app using the "rootexec" plugin, because that was the only way to make it work.
If I would start again I would rewrite it immediately in java.
So perhaps your own app would be a much better basis than my JET apk.
Please don't think I'm against it, but I do not understand (yet?) why that would be useful.
surfer63 said:
I don't see it yet. What would be useful to start from my Jet apk? Can you explain?
Please also note that when I started the JET apk I knew absolutely nothing about java (and didn't want to know anything about java) and started in appinventor/thunkable, as that was easy enough. But it is a big mess of all kind of shell scripts called from my app using the "rootexec" plugin, because that was the only way to make it work.
If I would start again I would rewrite it immediately in java.
So perhaps your own app would be a much better basis than my JET apk.
Please don't think I'm against it, but I do not understand (yet?) why that would be useful.
Click to expand...
Click to collapse
Don't know, i thought of your JET because i see it as a great collection of tools dedicated to Joying head units.
Given that on android 8 the intents ACC_ON and ACC_OFF are not usable, it could be an additional tool that allows you to schedule actions to be performed on wakeup without without the need to set Tasker as an NAVI app and without Xposed, since it still doesn't work on SC9853i.
BTW about Xposed i am also afraid, but i really hope i'm wrong, that with the code obfuscation of the firmwware, the maintenance of the Xposed modules will become increasingly difficult.
However, i will make a mini app with a list of apps to launch at ACC_ON (in my case the Accessibility Service, Poweramp and the NAVI), the code will be available if you change your mind .
bambapin said:
Given that on android 8 the intents ACC_ON and ACC_OFF are not usable, ...
Click to expand...
Click to collapse
Based on your work on USB, I also started to work on that idea again and built a "UsbReceiver" in my FytHWOneKey. It works great on my old sofia (6.0.1), but the usb event (""android.hardware.usb.action.USB_DEVICE_ATTACHED"") is never triggered on my 8.0.0 PX5. It doesn't work there.
Does this USB still work for you on 8.1.0?
bambapin said:
BTW about Xposed i am also afraid, but i really hope i'm wrong, that with the code obfuscation of the firmwware, the maintenance of the Xposed modules will become increasingly difficult.
However, i will make a mini app with a list of apps to launch at ACC_ON (in my case the Accessibility Service, Poweramp and the NAVI), the code will be available if you change your mind .
Click to expand...
Click to collapse
Xposed will no longer be feasible indeed when you look at the code obfuscation.
Your list of apps to be started: An internal list or external list (ascii config/ini file?), or preferences list?
surfer63 said:
Based on your work on USB, I also started to work on that idea again and built a "UsbReceiver" in my FytHWOneKey. It works great on my old sofia (6.0.1), but the usb event (""android.hardware.usb.action.USB_DEVICE_ATTACHED"") is never triggered on my 8.0.0 PX5. It doesn't work there.
Does this USB still work for you on 8.1.0?
Click to expand...
Click to collapse
Yes, it's the intent i'm still using to re-activate the accessibility service. It seems strange to me that it is not triggered at all, do you have any other app installed that could "steal" it? Torque for example?
EDIT: did you fetch the last version from github? i added a .xml with the filtered devices, it could be required (it depends on the firmware implementation)
Xposed will no longer be feasible indeed when you look at the code obfuscation.
Your list of apps to be started: An internal list or external list (ascii config/ini file?), or preferences list?
Click to expand...
Click to collapse
Internal, stored in the shared preferences.
bambapin said:
Yes, it's the intent i'm still using to re-activate the accessibility service. It seems strange to me that it is not triggered at all, do you have any other app installed that could "steal" it? Torque for example?
EDIT: did you fetch the last version from github? i added a .xml with the filtered devices, it could be required (it depends on the firmware implementation)
Click to expand...
Click to collapse
No other apps, only my own FytHWOneKey.
I did see the xml, but did not understand it and wanted to ask later. Those vendor id's / product id's: Are those from your usb devices or are they from (internal) Joying devices?
I can only find one vendor-id in the USB device database.
Hi,
Not even two months after device was released, it seems that the Support page for the Gobal devices is closed !
When I click on the "Support" on the redmagic.gg homepage, I am taken to a new page that says : "This support site doesn't exist anymore"...
That looks really promising !
So to sum it up :
- Specs announced : brilliant ;
- Global ROM : disaster ;
- Updates to expect : none => the ones given do no apply to the end ;
- Since 2 days no more ability to transfer files over USB ;
- Support site closed...
This device is a pure waste of money.
As a lawyer I'll ask them where they are located and I'll sue them unless they give back support or refund.
Regards.
Wow, i hope This is just a "fail" with the Support Center. If not i will refund also. Could You give us Information what You do now?
Sadly im over the 14 Days..
But is There another way to get refund?
"Oops! This help centre no longer exists
The company you're looking for is no longer using our help centre. We suggest reaching out to them directly via their official website."
I suppose they are switching the support centre, which is a good thing, since support was a joke .
Regarding the global rom being a disaster, the updates not coming ( I just received one ) or the usb not working ( it does for me ) I disagree with you.
NexusPenguin said:
Hi,
Not even two months after device was released, it seems that the Support page for the Gobal devices is closed !
When I click on the "Support" on the redmagic.gg homepage, I am taken to a new page that says : "This support site doesn't exist anymore"...
That looks really promising !
So to sum it up :
- Specs announced : brilliant ;
- Global ROM : disaster ;
- Updates to expect : none => the ones given do no apply to the end ;
- Since 2 days no more ability to transfer files over USB ;
- Support site closed...
This device is a pure waste of money.
As a lawyer I'll ask them where they are located and I'll sue them unless they give back support or refund.
Regards.
Click to expand...
Click to collapse
Support is back
https://global.redmagic.gg/blogs/news/update-on-support-07-01-support-is-back-up
em902566 said:
Support is back
https://global.redmagic.gg/blogs/news/update-on-support-07-01-support-is-back-up
Click to expand...
Click to collapse
Hi,
Sorry, but it is not.
They're talking about their support MAIL server.
What happens when you click on "Support" on the redmagic.gg page ?
For me it's : "Sorry, this support service is not available anymore".
Regards.
When I click the support icon it opens my facebook messenger...
Nightpwish said:
"Oops! This help centre no longer exists
The company you're looking for is no longer using our help centre. We suggest reaching out to them directly via their official website."
I suppose they are switching the support centre, which is a good thing, since support was a joke .
Regarding the global rom being a disaster, the updates not coming ( I just received one ) or the usb not working ( it does for me ) I disagree with you.
Click to expand...
Click to collapse
Hi,
Here is the thing for me (my own point of view).
The Global ROM lacks a lot of features you may expect from such a device.
Among other things :
- working dark mode ;
- gesture navigation ;
- always on display ;
- immersive mode (the one here just displays 3 lines in Chinese...) ;
- app lock / persistent apps in Recents ;
- front LED control...
I think all those can be considered as "must-have".
And funny thing is, Chinese ROM has some of them...
Some of the features can be added by installing apps from the Play Store, but most of those require a rooted device.
But if the device is rooted, it seems you won't be able to apply the updates
Speaking of updates : there has been one update.
But if I lok at the changelog, it seems they're focusing on... I could not really determine on what.
But certainly not on adding the missing features everyone is complaining about in the threads here.
But OK, we've had one update... How many others will we get ? And will they gring us the missing features ?
I could do with just ONE addition : the App-lock in recents to make the app persistent.
Of course, you can consider that the ROM is superb : a stripped bare AOSP that allows you to customise to your likings, with 0 bloatware and 0 uneccessary features.
I agree about the USB cable... It stopped working for some reason yesterday. It reworks now. What happened ? That will remain a mystery...
Then about support :
- did you ask them one question ?
- if so, did you get an answer ?
- how long did it take to get an answer ?
- can you access the support page from the official webpage (redmagic.gg) ?
- can you download the Europe/UK version of the ROM ?
I am sorry to say that I am not confident at all that we may have regular updates. And ZTE's reputation in the area is a hard one
Regards.
I would love to have proper dark mode on my phone.
Also, official AOD would be nice, as the AOD apps from the store can't compare with the official AOD of my previous phone ( Samsung S10+ ).
Locking an app in recent is a normal thing, I don't know why it's missing.
Support, as I said, is inexistent. I sent a couple of questions to them and realised from the answer they haven't even undestood me ( probably using Google translate eng - chinese ).
Weirdly, apart from these issues, I love the phone, its build quality, its speed...
And receiving 1 update in 1 month of ownership is something...
Nightpwish said:
I would love to have proper dark mode on my phone.
Also, official AOD would be nice, as the AOD apps from the store can't compare with the official AOD of my previous phone ( Samsung S10+ ).
Locking an app in recent is a normal thing, I don't know why it's missing.
Support, as I said, is inexistent. I sent a couple of questions to them and realised from the answer they haven't even undestood me ( probably using Google translate eng - chinese ).
Weirdly, apart from these issues, I love the phone, its build quality, its speed...
And receiving 1 update in 1 month of ownership is something...
Click to expand...
Click to collapse
Hi,
Well, all I have mentioned except the locking app in Recents can be added if your phone is unlocked and rooted.
There's even an AOD Theme for Substratum, and it looks like it doesn't eat up too much battery as the apps from the app store do...
But there is one problem doint things this way.
Most of the apps used need to be enabled in "Accessibility" settings.
So if you can't pin the apps in Recents, deleting all recents just disables all those from accessibility.
So you may loose the dark mode from substratum... but you also may loose any navigation ability !
To be honest : if they could add the app lock in recents (that already is there in the Chinese ROM), I could live with all the limitations...
Good for us : it has 8GB RAM, so even with a lot of apps listed in Recents we're go short on memory.
Regards.
NexusPenguin said:
Hi,
Well, all I have mentioned except the locking app in Recents can be added if your phone is unlocked and rooted.
There's even an AOD Theme for Substratum, and it looks like it doesn't eat up too much battery as the apps from the app store do...
But there is one problem doint things this way.
Most of the apps used need to be enabled in "Accessibility" settings.
So if you can't pin the apps in Recents, deleting all recents just disables all those from accessibility.
So you may loose the dark mode from substratum... but you also may loose any navigation ability !
To be honest : if they could add the app lock in recents (that already is there in the Chinese ROM), I could live with all the limitations...
Good for us : it has 8GB RAM, so even with a lot of apps listed in Recents we're go short on memory.
Regards.
Click to expand...
Click to collapse
You can easily fix your problem
You have to install your app as system app
System apps won't die or close when you kill them in recent app
You can download application called "link2sd"
https://play.google.com/store/apps/details?id=com.buak.Link2SD
You must have root access
Open the application and press and hold on any application you want and press convert to system app
And then reboot
Your application won't die at all and the accessibility menu wont rest
Hi,
Thanks for your advice...
I've tried it and.... IT WORKS !!!!
I think I can now use this device exactly as I want... and will NOT send it back
Regards.
NexusPenguin said:
Hi,
Thanks for your advice...
I've tried it and.... IT WORKS !!!!
I think I can now use this device exactly as I want... and will NOT send it back
Regards.
Click to expand...
Click to collapse
Ur welcome ?
@NexusPenguin,
By reading all your posts,it seems that you're quite frustrated about your purchase,and I'm sorry to see you're so dissapointed...
But this device is primary aimed for gamers,and @ this price point,Nubia had to make concessions.....
TBH,for getting all bells and whistless,people should buy a REAL flagship,not a -500$ phone and then expect the same behavior of it as a +1000$ machine.........
roadworker said:
@NexusPenguin,
By reading all your posts,it seems that you're quite frustrated about your purchase,and I'm sorry to see you're so dissapointed...
But this device is primary aimed for gamers,and @ this price point,Nubia had to make concessions.....
TBH,for getting all bells and whistless,people should buy a REAL flagship,not a -500$ phone and then expect the same behavior of it as a +1000$ machine.........
Click to expand...
Click to collapse
Hi @roadworker,
Sorry, but I do not understand what you're saying.
I am not complaining about the hardware, but about the software.
And what I am asking about does really not seem extraodinary to me !
Navigation gestures ? Is that extravagant ? I think not => Chinese ROM has it, not global. Why ?
Lock apps in recent ? Is that extravagant ? I think not => Chinese ROM has it, not global. Why ?
Immersive mode ? Is that extravagant ? I think not. It is even expected in the Global ROM. But what do we have ? 2 lines of chinese...
Working dark mode ? Is that extravagant ? I think not => it is there but is not working.
A support page that actually shows up on the website ? Is taht extravagant ? I think not. It used to be there... Now it is gone.
I think those features SHOULD BE INCLUDED ESPECIALLY IN A GAMING PHONE...
Gestures to hide navigation bar ; theming of phone to make is "cooler gamer" ; locking gaming apps so they launch more quickly ?
So your argument is not relevant at all to me...
Regards.
easy fix for the problem:
go to Settings > System > Advanced > disable Deep process clean.
you're welcome
majidamiri15300 said:
easy fix for the problem:
go to Settings > System > Advanced > disable Deep process clean.
you're welcome
Click to expand...
Click to collapse
Hi,
Will try that. If that works, that is super cool
Regards.
EDIT : done it. It seems it is working : thanks so much... Love for the phone beginning to come back... Even better : rooted phone + stripped AOSP = customize exactly as you wish it.
A lawyer should know better
If your a lawyer, I feel sorry for your clients...
There should be an established process with your bank to reverse a charge and a consumer protection agency for you to be able to return a product.
However, Red Magic have stated via Twitter and Blog that they have lost their Support system. That is a bad thing, and probably shouldn't happen to a big company but they have said it has.
https://global.redmagic.gg/blogs/news/update-on-support-07-01-support-is-back-up
If you raise a new call on the system you would probably get a better response. I would imagine they also lost self service and probably have not realised it is still down.
majidamiri15300 said:
easy fix for the problem:
go to Settings > System > Advanced > disable Deep process clean.
you're welcome
Click to expand...
Click to collapse
What does " Deep Process Clean" do? is it aggressive ram management?
famoustito said:
What does " Deep Process Clean" do? is it aggressive ram management?
Click to expand...
Click to collapse
Something like that.
With deep process clean on I wasn't receiving any WhatsApp or Outlook notifications.
For those who are not happy with the bare Android experience and for example,about the lack of gestures and immersive mode,check out the apps of Manuel Wrage @ Google Play......
After paying to have my phone flashed (Honor 20e), how do I know if the person really did the agreed job or simply did a hard reset?
Flashed with what? Why?
With stock ROM, to eliminate spyware.
by risking more spyware ignoring that stock always has spyware?
my guy, flash it your self with an aftermarket OS like GrapheneOS, /e/OS or OmniROM.
you don't avoid espionage by walzing into the spymaster's den!
Ok… factory resetting would also remove bad software…
traman124 said:
Ok… factory resetting would also remove bad software…
Click to expand...
Click to collapse
LMAO no, Android (from google or honor or any other phone maker) comes with "bad software", a factory reset won't do anything!
again, get /e/OS or grapheneOS or OmniROM for your phone and flash it your self! get rid of anything that comes from Honor/Google like GMSCore that can be replaced by MicroGapps
though I very much congratulate you on wanting to escape the goolag! now get to hacking!
I think he was referring to bad software that he installed and wanted to clean wipe his phone.... I don't think he was trying to degoogle...
If you were, Lineage OS or /e/OS with microG and Aurora let's you get apps without Google services
@burbank_ what do you mean by bad software?
Yep, I meant spyware that the perpetrator installed on my phone, allowing them to monitor my activity, listen to my calls, and possibly even control my phone.
So yes, I want to clean wipe, and I don't think I can be sure to have removed the spyware with just a hard reset..?
There's no way I know of to check, but a factory reset would remove all the apps from the user partitions (including the spyware).
I looked for stock firmware for the 20e everywhere and found nothing (except a sketchy download link that downloaded some random firmware for the Honor 8X) so your person probably cheated you (unless he works for huawei/honor and has access to some files that the Internet does not).
A factory and cache reset from Android Recovery (press Power + Volume Up and select factory reset, cache reset, reboot in order) would remove spyware for the most part.....
Ok, thank you (and qwerty too)!
I'll probably install a custom ROM myself then, just to be sure. Can you recommend what to install, I'm interested in something with all the Android functionality I've gotten used to...?
It's a huawei... You can't unlock the bootloader
traman124 said:
It's a huawei... You can't unlock the bootloader
Click to expand...
Click to collapse
maybe only through the phone, I did a quick search and allegedly huawei maybe would allow you to unlock it, but as I suspected there is always a BROM exploit to be had: https://www.xda-developers.com/huawei-honor-bootloader-unlock-potatonv/
though the link is a bit dated, I do believe potatonv should support the Kirin 710F SoC
also, if you want to remove spyware, you remove anything that contains data collection I.E. google services and whatever the CCP mandates their OEMs install
Thnx, I'll look into it. What about other custom ROMs you've mentioned, though, would there be difficulties in flashing it with one of them?
Also, I've another question. I contacted another mobile repair service and they've told me they have special access to stock ROMs through "programmers they hire", so they can install a stock ROM for my Honor 20e. Is this possible/ unlikely/ trying to cheat me?
well I don't know about the other ROMs, ever since AOSP introduced Projet Trebble the promise was of Generic System Images, but they don't exactly exist because just like with UEFI, the OEMs implementation is broken so you still have to look for an aftermarket OS that is speciffically tailored for your device
that repair shop are likely trying to scam the heck out of you or actully know what they are doing and have a fresh image they pulled from a brand new phone and that "programmers they hire" thing that sets off alarms in my head is likely just them explaining it as simple as possible
burbank_ said:
After paying to have my phone flashed (Honor 20e), how do I know if the person really did the agreed job or simply did a hard reset?
Click to expand...
Click to collapse
Yes, it seems there is a way to find out about the last flashing date - provided it was followed by a Google account initialization:
Go to the Google Dashboard, login with your Google account.
Scroll to the section labeled "Android" and expand it (by clicking its title / the LGM [little green man])
Check for the device in question
Associated, you will find a date of registry. That doesn't reflect the first time a device was added, but the last time the Google account was activated on the device. So if you activate your Google account following a Factory-reset, this field is updated and thus reflects this point-in-time.
Additionally, if phone's Android is rooted, you always can check a directory's creation time below /data/data.
burbank_ said:
After paying to have my phone flashed (Honor 20e), how do I know if the person really did the agreed job or simply did a hard reset?
Click to expand...
Click to collapse
why pay for something you can do?
tutibreaker said:
why pay for something you can do?
Click to expand...
Click to collapse
because you dont want to