P20 Pro - demo variant - how to make it usable - Huawei P20 Pro Guides, News, & Discussion

Hello,
After being the "proud" owner of a P20 Pro which is a demo unit, I have looked for ways to make it usable and as close as the retail variant.
Things to do:
On Phone:
- go to Settings -> Device administrators and disable the administrator for the Demo apps
On Computer:
- install ADB and connect your phone to computer
Run the following commands:
- pm uninstall -k --user 0 com.huawei.retaildemo
- pm uninstall -k --user 0 com.huawei.retail.assistant
This will stop the annoying video that is playing everytime you lock your device.
The Explore P20 PRO app can be disabled from the settings.
However, there are some other issues with the phone:
1. it charges till 75% then stops
The key to charge it to 100% is to let it charge to 75%, then, without unplugging the cable, restart the phone.
2. there is no lock screen and no posibility to add a fingerprint or a passcode
I installed a lockscreen from the PlayStore that got this issue fixed; still no fingerprint though ...
3. You will have a demo notification in the status bar
To remove this, install Quick Shortcut Maker from Playstore
Search for DEMO -> You will find SystemUI - Demo mode
Click on AppInfo then Notifications
Disable all of them
Go back and click on Force Stop ( you have to do this last part everytime you restart the phone if you want it to be hidden )
4. You get tons of appointments in the Calendar and numbers in the Contacts.
The solution is to delete all of them.
5. Apps do not have permision to access the mobile data, you receive a confirmation everytime and you have to click accept
The solution is to go to Settings -> Wireless and networks -> Mobile data -> Networked apps, and select all the checkboxes for Installed apps and System apps tabs. ( this has to be done each time after you restart your phone )
This is everything I could think of now.
If some of you have other suggestions I can try, please feel free to let me know.
Right now, the phone is usable and works pretty well.
P.s: After restoring it to factory defaults, everything will be lost

How do you end up with a demo device?

Bought it very cheap, of course ... It was not a scam or anything, just a P20 PRO at a very good price.
Phone was brand new, never powered on.

Thanks a lot. It solved my issue.

Al3xxxinho said:
Bought it very cheap, of course ... It was not a scam or anything, just a P20 PRO at a very good price.
Phone was brand new, never powered on.
Click to expand...
Click to collapse
Be robbed from a shop mate. If it's got demo content rolling.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
Unlock bootloader, root, remove demo or flash with huru

Already did that before it was released to the public.
Cost: 50 usd.

Al3xxxinho said:
Already did that before it was released to the public.
Cost: 50 usd.
Click to expand...
Click to collapse
Then you need for flash a normal OS.
No need to retain the demo software, if it is OS based.
Or you could maybe delete the demo content using root explorer.

I already flashed the regular OS.

How you did that?
Al3xxxinho said:
I already flashed the regular OS.
Click to expand...
Click to collapse
How did you do that? Can you please write the steps.

Here you go: https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326

Al3xxxinho said:
Here you go: https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
Click to expand...
Click to collapse
Thank you very much dear Just want to know, my phone is UK based, so which firmware should I use to install on my Demo P20 Pro? Any link?

Hi, how i can buy a demo model? It is new for me

Hey, did you find any more tweaks or issues with the Demo version?
I followed all your steps and other than not being able to use Fingerprint it runs okay.
Still hoping that Bootloader unlock codes will make a return

I have p30 pro with similar problems
As for the lockscreen, if u install google's Find my phone it will enable your lockscreen code. Then u can enable the fingerpring access.
Only problem i have now is i cant enable mobile data and thats a big problem
Anyone know that issue and how to fix it?: (

Maybe a silly one - but in 'Developer Options' there is a section 'Demo Mode' - did you try turning that off?

Kosomoars said:
I have p30 pro with similar problems
As for the lockscreen, if u install google's Find my phone it will enable your lockscreen code. Then u can enable the fingerpring access.
Only problem i have now is i cant enable mobile data and thats a big problem
Anyone know that issue and how to fix it?: (
Click to expand...
Click to collapse
Could be the radio is not complete in which case it'll never work.
You could try flashing a firmware via fastboot, I did this a while back, I had a guide I wrote in my sig, not sure if it's still there?
Check a few guides.
My guess is the physical components are intact it's just the firmware you're on

Hello, I once found a way to block and fingerprint
1.Apk Find my device
2.protect the device
Active lock option

Just buy a new phone instead of a robbed one..
Surprised you're allowed to bake a thread on XDA for this

Related

Bypass Gmail sign-in, Bypass passwords, Bypass screen lock drawing!!!!!

I read this over at tmonews...
"While playing with my G today, I found a way to enter "safe mode" which will bypass the initial gmail signin and allow you to straight to the good stuff with out activating via google. You can also bypass the security drawing pattern.
1. Power off your device
2. While device is powering back on press and hold the "menu" key, keep holding it past the G1 and android splash screen.
Phone will boot all the way to the main screen and display "safe mode" in lower left corner.
I have confirmed that data is still fully operational and all of my downloaded programs."
Very interesting
bps725 said:
I read this over at tmonews...
"While playing with my G today, I found a way to enter "safe mode" which will bypass the initial gmail signin and allow you to straight to the good stuff with out activating via google. You can also bypass the security drawing pattern.
1. Power off your device
2. While device is powering back on press and hold the "menu" key, keep holding it past the G1 and android splash screen.
Phone will boot all the way to the main screen and display "safe mode" in lower left corner.
I have confirmed that data is still fully operational and all of my downloaded programs."
Very interesting
Click to expand...
Click to collapse
How about a ROM DUMP?
I think there's already a thread or two about that.
im sorry to say this but the safe mode does not allow to bypass the initial activation screen but it sure does bypass the security screen
artyr0x said:
im sorry to say this but the safe mode does not allow to bypass the initial activation screen but it sure does bypass the security screen
Click to expand...
Click to collapse
Correct I already posted about this. You still have to activate service with Tmobile and Google. Safe mode on the phone is just like on a regular computer help you fix issues.
speoples20 said:
Correct I already posted about this. You still have to activate service with Tmobile and Google. Safe mode on the phone is just like on a regular computer help you fix issues.
Click to expand...
Click to collapse
It runs exactly as u would have it if it wasnt in safe mode the only difference is that u can bypass the security screen and attempt to change the security lock i'll play around wit it later on today
Well being the moder I am. I was smart enough to download that converter program floating around before reading about it and I get non stop errors on the home screen.. but for w/e reason running the phone in safe mode does not let the program load so I get no errors now but I can't unintsall it from the applications uninstall from settings.. it gives me an error when iit treys to compute the program sizes so I I can not run the phone when not in safe mode.. would be awesome if someone could help me here
try connecting it to the computer in debug mode and uninstall using adb
i have been google searching for two hours and i have yet to find how to put commands into the g1 i got the drivers and everything and its recoginzed by my comp but i dont know where i type adb shell uninstall or w/e can you direct me in the right direction?
you need to download the SDK from google. You should see some threads with the SDK or the Emulater... it is all the same. adb is in the tools thread. Ohh and you need to enter "adb -d uninstall (name of apk)"
i tried this and no luck the system still crashes... and you know i wouldnt mind loading factory defaults its just i use shazam and i already have over 150 tags that i do not want to lose and thats all i really need to back up... but i can not access the file system on the phone unless i am missing something :/ this is really killing me i hate when i cant fix something
Disabled said:
i tried this and no luck the system still crashes... and you know i wouldnt mind loading factory defaults its just i use shazam and i already have over 150 tags that i do not want to lose and thats all i really need to back up... but i can not access the file system on the phone unless i am missing something :/ this is really killing me i hate when i cant fix something
Click to expand...
Click to collapse
you sure it doesn't save that info on the memory card?
no nothing application saves to the memory card.. well besides amazon for the mp3 market i think. unless those are the tags? i dont know can you confirm? again thanks for the help man
I just tested and you are correct it doesn't save to the SD card... weird why it wouldn't a couple other applications do besides amazon.
I have G1 in my Hand in India but sad thing is its an Unactivated Phone.
I can easily unlock Sim by using Remote Unlock code for my IMEI provided by some Sellers on web. But how can a Activate the phone in India.
I know the t-mobile Activated SIM Trick for phone using some borrowed Sim card but in India its Impossible.
Help, please Help
google g1
ok i really need help i got my phone from the U.S and i live in canada it is unlcoked but it wont work i cant bypass the gmal sign in i tried the steps for the safe mode but the safe mode sign comes up at the bottom but it just stays at the one creen where it says touch to begin your setup for gmail i try to setup but it says my sim is wrong how do i fix this please help
JayMan26403 said:
ok i really need help i got my phone from the U.S and i live in canada it is unlcoked but it wont work i cant bypass the gmal sign in i tried the steps for the safe mode but the safe mode sign comes up at the bottom but it just stays at the one creen where it says touch to begin your setup for gmail i try to setup but it says my sim is wrong how do i fix this please help
Click to expand...
Click to collapse
google is your best friend. try searching for a solution. all you have to do is change the APN settings to rogers/fido and go through the gmail activation.
hetaldp said:
I have G1 in my Hand in India but sad thing is its an Unactivated Phone.
I can easily unlock Sim by using Remote Unlock code for my IMEI provided by some Sellers on web. But how can a Activate the phone in India.
I know the t-mobile Activated SIM Trick for phone using some borrowed Sim card but in India its Impossible.
Help, please Help
Click to expand...
Click to collapse
im in Mumbai using my G1 for the last few weeks. read here
safe mode works on the M580 but FAILS to bypass the lock screen password.
HTC Android Tool
★★★ WORLD FIRST ★★★
Bypass Google Account Just ONE CLICK
http://forum.gsmhosting.com/vbb/f75...bypass-google-account-just-one-click-1556888/​

[APP][2.2+] AdbToggle (ROOT) - beta test is over!

Attention: The beta test is over now!
Warning: Please read everything properly before you install anything!
Here's the developer of APP QUARANTINE. I'm just about to release a new app called AdbToggle and I need you guys to help me out testing the beta version. The final release will be a paid version that will be available in Google Play. But before throwing around with details about the beta test let me first tell you why I have developed this app!
First, what is the app doing?
AdbToggle like the name already says allows you to toggle the USB debug settings. You can do this in the app or by using a homescreen widget. Furthermore there's an automatic mode: when you unplug your device then USB debug mode is turned off. When you plug it in again then USB debug mode is still disabled, it will only be enabled again if you unlock your screen.
Why should I need to have this tool?
Maybe you already figured out that when you plugin your phone to your PC then the contents of your SD card are only accessible when your screen is unlocked. This is very good, however there's a major security risk that still allows an unwanted person to access your data.... and if you are rooted even allows for total control over your phone, like for instance bypassing the screen lock. When buying a new Android phone then this is of course not enabled by default, but if you are an Android developer or otherwise just like to play around with Custom ROMs and root apps, then the USB debug mode is usually enabled and voilà....
What are the requirements for AdbToggle
Since I posted this here on XDA-Developers you probably already figured out that you need to have a rooted phone. You even need to have full write access to the system partition (e.g. no NAND protection like on some HTC phones) because AdbToggle is only working when installed as system app. This is maybe for the downside.... however the good thing is that AdbToggle doesn't need root access anymore after you have installed it.
What do you expect from people who take part in the beta test?
If you are ready to take part in the beta test and help me in finishing a great security tool for Android then I'm more than happy! Please let me know what device you have and what Android version you are currently running! And then of course I'm awaiting your comments, ideas for improvements, bug reports, etc. You can post directly in this thread or use PMs.
How does it work? What should I test?
When launching AdbToggle then a nice blue Android shows up and holds your usb plug. Just hit it to toggle USB debug mode, however it will first tell you that it needs to install itself as system app. If you have a working busybox installation (Busybox is a set of Linux command line tools) then it will just copy itself to the system partition and then asks you to reboot your phone. If there's no busybox available then it will guide you to Sterickson's busybox installer, which is available in Google Play as well. Once you have used it to install busybox, launch AdbToggle again and it will succeed.
After the reboot open the app and toggle USB debug mode. You will see the standard Android USB notifications popup and disappear as you toggle, and at the same time the USB connection to your PC is made available or reset. You should also try to use the homescreen widget to just do the same.
Now to the automatic mode. Launch AdbToggle, click the settings icon in the action bar, enable the checkbox. From here you can try out different test scenarios:
1. Unplug your phone from your PC and turn of the screen. When you connect it you'll see the lock screen but USB debug mode is disabled. You can recognize this as the USB debug notification will not popup. You can verify this by typing "adb devices" from your PC and no device should be visible. Now unlock your screen and USB debug mode will be enabled.
2. Turn your screen off and on again. The lock screen appears but USB debug mode is still enabled. Why? You are still connected to your PC so it's rather impossible that someone took away your phone. Also when your screen goes off you probably don't want to loose your USB connection when you are working on something....
3. Unplug your phone from your PC and plug it in again. USB debug mode is still enabled. Why? Your screen is still unlocked. Again it's rather unlikely that someone took away your phone during this time. Actually what really happens is that USB debug mode is disabled when you unplug it, but it's enabled when you plug it in again and AdbToggle figures out your screen is unlocked....
4. Reboot your phone and verify if everything is still working fine without manually launching the app.
Further test cases
You should check if AdbToggle is still working after an update! As the beta test goes on probably there will be one or another update. You should be able to install the update through Google Play as usual and the new version should be working immediately. You must NOT reboot and NOT install the updated version as system application again. So at this point AdbToggle should just behave the same like your built in Google apps.
What about the UI? Does everything show up well on your phone? Is the Android always blue when USB debug mode is on, and gray when it's off? Does the widget always show the proper state as well?
Limitations / Known issues:
The automatic mode is currently not working on tablets with a separate power plug-in. I'm trying to solve this at some point but for the moment please test it on phones only!
Now please let me start!
Sure, go ahead and download AdbToggle from Google Play and have fun! However keep in mind that the beta version will expire and not working anymore in 05/2012.
https://play.google.com/store/apps/details?id=com.ramdroid.adbtoggle
The first update has just been published!
The following issues were fixed:
- improved Busybox and Root detection
- AdbToggle service didn't work anymore after a while
- more reliable detection whether screen is unlocked or not
Besides, I have received a crash report which I have tried to fix... however the bug never happened on my devices so I'm not sure if I really got it. So if AdbToggle still crashes on your phone after the update then please get back on me with more information!
ramdroid77 said:
and if you are rooted even allows for total control over your phone, like for instance bypassing the screen lock.
Click to expand...
Click to collapse
Well, this tool is a must have... You think you're protected and then everything could be down just because the back door (the USB debugging) is enabled.
Some applications can disable USB debegging remotelly (like avast! Mobile Security), but it could be late...
Installation went well and the mobile (Samsumg Galaxy Nexus I9250 with Android 4.0.2 maguro official Google release) rebooted ok.
ramdroid77 said:
1. Unplug your phone from your PC and turn of the screen. When you connect it you'll see the lock screen but USB debug mode is disabled. You can recognize this as the USB debug notification will not popup.
Click to expand...
Click to collapse
Worked.
ramdroid77 said:
You can verify this by typing "adb devices" from your PC and no device should be visible.
Click to expand...
Click to collapse
Sure... no adb device plugged.
ramdroid77 said:
Now unlock your screen and USB debug mode will be enabled.
Click to expand...
Click to collapse
Worked.
ramdroid77 said:
2. Turn your screen off and on again. The lock screen appears but USB debug mode is still enabled. Why? You are still connected to your PC so it's rather impossible that someone took away your phone. Also when your screen goes off you probably don't want to loose your USB connection when you are working on something....
Click to expand...
Click to collapse
Worked.
ramdroid77 said:
3. Unplug your phone from your PC and plug it in again. USB debug mode is still enabled. Why? Your screen is still unlocked. Again it's rather unlikely that someone took away your phone during this time. Actually what really happens is that USB debug mode is disabled when you unplug it, but it's enabled when you plug it in again and AdbToggle figures out your screen is unlocked....
Click to expand...
Click to collapse
Worked.
ramdroid77 said:
4. Reboot your phone and verify if everything is still working fine without manually launching the app.
Click to expand...
Click to collapse
ramdroid77 said:
You should check if AdbToggle is still working after an update! As the beta test goes on probably there will be one or another update. You should be able to install the update through Google Play as usual and the new version should be working immediately. You must NOT reboot and NOT install the updated version as system application again. So at this point AdbToggle should just behave the same like your built in Google apps.
Click to expand...
Click to collapse
Waiting for an update.
ramdroid77 said:
What about the UI? Does everything show up well on your phone? Is the Android always blue when USB debug mode is on, and gray when it's off? Does the widget always show the proper state as well?
Click to expand...
Click to collapse
Seems ok, but it would be easier if it is a really widget, just toggle not open.
The application crashed twice, I've sent the reports.
When I click the widget, it gets blue/gray correctly but the icon does not show in system tray (i.e., you can't see the original icon of the USB debugging mode.
ramdroid77 said:
However keep in mind that the beta version will expire and not working anymore in 05/2012.
Click to expand...
Click to collapse
Any possibility of beta testers get a Pro
Everything is working as you described. I'm on a Desire HD with BlackICE 1.50 Rom.
Thanks for your feedback!
Technical said:
Seems ok, but it would be easier if it is a really widget, just toggle not open.
The application crashed twice, I've sent the reports.
When I click the widget, it gets blue/gray correctly but the icon does not show in system tray (i.e., you can't see the original icon of the USB debugging mode.
Click to expand...
Click to collapse
On my devices, when I hit the widget it turns off USB debugging, the Android notification disappears, and the icon is gray. I hit it again, USB debugging is enabled, Android notification appears, icon is blue.
Can you please ellaborate what is different on your phone? 'What' is opening? Or maybe you can post a screenshot?
About the crash: I've received the report and published a fix. Version 0.9.2 is the newest right now.
Technical said:
Any possibility of beta testers get a Pro
Click to expand...
Click to collapse
I agree that everyone who comes back to me with some feedback should receive the pro version for free. However I have to find a good way to make this possible. I have send some people the apk of my other app 'App Quarantine Pro' for free and got a report that they were not able to update to the newest version through Google Play. So I have to verify on one of my phones when I do my next update, but under these circumstance I would not be satisfied with this solution. And I don't really want to manually push APKs for each update since I plan to keep this going for a couple years, and there will be more apps in the future as well, so...
Another idea is to try and refund the money through Google Play after purchase but at this point I also don't know yet if this will stop further updates or not. Probably it will....
A completely different idea is not sending the pro version to testers at all, but instead donate the first month's income of AdbToggle to xda developers. I'm using the App Quarantine user base (16K active users) to promote my own apps. For App Quarantine Pro this has been roughly 60 Euro in the first month so I guess with AdbToggle I'd be able to submit a fair amount as well...
ramdroid77 said:
On my devices, when I hit the widget it turns off USB debugging, the Android notification disappears, and the icon is gray. I hit it again, USB debugging is enabled, Android notification appears, icon is blue.
Can you please ellaborate what is different on your phone? 'What' is opening? Or maybe you can post a screenshot?
Click to expand...
Click to collapse
Well, I got only the icon to start the application. Then I remembered I should add the widget icon. Now it's working as it should.
I suggest you make the background transparent. It's ugly over a non-black wallpaper.
ramdroid77 said:
About the crash: I've received the report and published a fix. Version 0.9.2 is the newest right now.
Click to expand...
Click to collapse
I cannot update it using Google Play. It's not shown there.
ramdroid77 said:
I agree that everyone who comes back to me with some feedback should receive the pro version for free. However I have to find a good way to make this possible. I have send some people the apk of my other app 'App Quarantine Pro' for free and got a report that they were not able to update to the newest version through Google Play. So I have to verify on one of my phones when I do my next update, but under these circumstance I would not be satisfied with this solution. And I don't really want to manually push APKs for each update since I plan to keep this going for a couple years, and there will be more apps in the future as well, so...
Click to expand...
Click to collapse
I understand... Some app works with a "license" apk for another (free) apk. I can remember of ROM Manager (and ROM Manager Premium License), for instance. I don't know if the Market issue will arise the same.
ramdroid77 said:
Another idea is to try and refund the money through Google Play after purchase but at this point I also don't know yet if this will stop further updates or not. Probably it will....
Click to expand...
Click to collapse
Yes, refund cancel the updates (generally).
ramdroid77 said:
A completely different idea is not sending the pro version to testers at all, but instead donate the first month's income of AdbToggle to xda developers. I'm using the App Quarantine user base (16K active users) to promote my own apps. For App Quarantine Pro this has been roughly 60 Euro in the first month so I guess with AdbToggle I'd be able to submit a fair amount as well...
Click to expand...
Click to collapse
I'd liked the idea of App Quarantine, but I bought recently Ultimate Backup Pro and it does freeze/defrost app.
new version 0.9.3
- removed widget background/border kind of thing
- make sure app is revived after it's been killed
- update widget state during automatic toggle
Technical said:
I cannot update it using Google Play. It's not shown there.
Click to expand...
Click to collapse
It really should be there. Please check again. Otherwise try to restart market, clear cache or reboot your phone. But I see no reason why it should not be available for you....
Technical said:
I understand... Some app works with a "license" apk for another (free) apk. I can remember of ROM Manager (and ROM Manager Premium License), for instance. I don't know if the Market issue will arise the same.
Click to expand...
Click to collapse
yet another possible option. I hate that you have to install two APKs to make the app run, however it might be one of the easiest solutions. Well, I still have left some weeks to figure out the best solution!
Technical said:
I'd liked the idea of App Quarantine, but I bought recently Ultimate Backup Pro and it does freeze/defrost app.
Click to expand...
Click to collapse
Everyone as he prefers Though AQ's sole purpose is to freeze apps and therefore it also offers more unique features than traditional System app removers or Backup tools.
I received a crash report with a comment "Changed to AOKP 28 and App crashed."
Can the guy who sent the report please give me more details....
- did you flash a new ROM without clearing Dalvik cache? are other apps crashing too?
- is AdbToggle still installed on the system partition?
- what were you exactly doing when it crashed?
new release 0.9.4
- fixed bug when widget stopped working after some time
- fixed crash in license info dialog on Android 2.x
- allow other apps to use AdbToggle (see App Quarantine)
- generally improved stability
Final two weeks of beta test!!!
When the beta test is over then the free version will still be available, however the automatic mode will only work in the paid version.
All testers who submit(ted) reports in this thread will receive the pro version.
AdbToggle now allows other apps to enable/disable USB debugging mode. This is already working with App Quarantine.
A free SDK will soon be available so other developers can add support as well!
Well seems to be a must have, as I often forgot to deactivate USB debugging when I'm finished with it. I tested it on my Samsung Galaxy S2 (GT-I9100).
So first, installation from Play, and installed fine as system app (don't needed the install of busybox as CF-ROOT for Galaxy S2 includes it). And next the testing :
ramdroid77 said:
1. Unplug your phone from your PC and turn of the screen. When you connect it you'll see the lock screen but USB debug mode is disabled. You can recognize this as the USB debug notification will not popup. You can verify this by typing "adb devices" from your PC and no device should be visible. Now unlock your screen and USB debug mode will be enabled.
Click to expand...
Click to collapse
Works.
ramdroid77 said:
2. Turn your screen off and on again. The lock screen appears but USB debug mode is still enabled. Why? You are still connected to your PC so it's rather impossible that someone took away your phone. Also when your screen goes off you probably don't want to loose your USB connection when you are working on something...
Click to expand...
Click to collapse
Works.
ramdroid77 said:
3. Unplug your phone from your PC and plug it in again. USB debug mode is still enabled. Why? Your screen is still unlocked. Again it's rather unlikely that someone took away your phone during this time. Actually what really happens is that USB debug mode is disabled when you unplug it, but it's enabled when you plug it in again and AdbToggle figures out your screen is unlocked...
Click to expand...
Click to collapse
Works.
ramdroid77 said:
4. Reboot your phone and verify if everything is still working fine without manually launching the app.
Click to expand...
Click to collapse
Works.
Further test cases
ramdroid77 said:
You should check if AdbToggle is still working after an update! As the beta test goes on probably there will be one or another update. You should be able to install the update through Google Play as usual and the new version should be working immediately. You must NOT reboot and NOT install the updated version as system application again. So at this point AdbToggle should just behave the same like your built in Google apps.
Click to expand...
Click to collapse
Not yet tested. No update since installed, this morning, will wait on next update to report.
ramdroid77 said:
What about the UI? Does everything show up well on your phone? Is the Android always blue when USB debug mode is on, and gray when it's off? Does the widget always show the proper state as well?
Click to expand...
Click to collapse
The UI is all fine, nothing is lost.
The droid is always blue and grey according to the situation, between reboots, disconnecting and ticking in the settings, tested different cases.
Widget seems ok too.
No crash to report, all fine after testing for the moment. This shows that beta will end soon, as there is nothing to report.
julroy67 said:
No crash to report, all fine after testing for the moment. This shows that beta will end soon, as there is nothing to report.
Click to expand...
Click to collapse
Thanks for your report.
I received 2-3 weird crash reports that are never reproducible on my phones and so I have no idea what's happening. There's also a one-star rating at Google Play but probably the guy didn't read this thread and was not rooted or something.
Otherwise I suppose the app is in a release-ready state!
This is a great app! Tried it out on GSM Gnex 4.0.4 and everything works as expected. If you're gna make it paid, honestly I'll pay Max $1 for these kind of apps, not being rude just saying, don't make it more!
Not installing on Samsung S2 official Android 4.0.3 I9100XWLP7 (KIES)
ramdroid77 said:
When launching AdbToggle then a nice blue Android shows up and holds your usb plug. Just hit it to toggle USB debug mode, however it will first tell you that it needs to install itself as system app. If you have a working busybox installation (Busybox is a set of Linux command line tools) then it will just copy itself to the system partition and then asks you to reboot your phone. If there's no busybox available then it will guide you to Sterickson's busybox installer, which is available in Google Play as well. Once you have used it to install busybox, launch AdbToggle again and it will succeed.
Click to expand...
Click to collapse
The app says it installs as a system app, restarts the phone but no app in /system/app directory.
Running the app again takes me through the whole process again, with no install.
I use SuperSU to grant the root permission and it shows it is granted. I will continue digging and find out why.
imani said:
The app says it installs as a system app, restarts the phone but no app in /system/app directory.
Running the app again takes me through the whole process again, with no install.
I use SuperSU to grant the root permission and it shows it is granted. I will continue digging and find out why.
Click to expand...
Click to collapse
I have tested AdbToggle with SuperSU successful. My guess is rather a problem with busybox. What busybox installer did you use? It would also be interesting to get your logcat output when you try to install it.
Tasker-compatible?
Do you plan to support Tasker?
I'd prefer to see this be a plugin, but as long as it is controllable via intent broadcasts, then Tasker would be able to toggle debug mode.
See http://tasker.dinglisch.net/developers.html for more info.
cheshyre said:
Do you plan to support Tasker?
I'd prefer to see this be a plugin, but as long as it is controllable via intent broadcasts, then Tasker would be able to toggle debug mode.
See http://tasker.dinglisch.net/developers.html for more info.
Click to expand...
Click to collapse
I've just added the Tasker plugin on my To-Do list!
So far I haven't done anything with Tasker so I don't know if AdbToggle is working without a plugin... yes there are intents to toggle debug mode, but you need to have a permission in order to use them.
Attention!
The beta test is over now and ADB Toggle is available in both a free and paid version. In the free version the automatic mode is not available.
Everyone who reported in this thread has received a download link for the PRO license key!
There will soon be a new thread for the full version of AdbToggle!
Everyone needs to update AdbToggle in Google Play! If you don't update then the app will not work anymore in Mai!
Thanks for the pro key, received it and works.
Now I just report what I missed last time (even if beta has ended), updating with the new APK via Google Play also works fine, all works fine on the Galaxy S2 (GT-i19100).
hi people,
in the meanwhile there's a new thread about ADB Toggle Access. With this developer library it's possible that other root apps (that require USB debug settings) can use AdbToggle. Currently this is only implemented in App Quarantine but I'd love to see more apps jumping on it...
Visit the thread here:
http://forum.xda-developers.com/showthread.php?t=1637009
It's a bit lost so far, so I would be greatful if you could all click the "Submit this thread as a news tip" button in the new thread!
A post on the XDA Portal would really help this idea along!
Thanks in advance!
Help...
ramdroid77 said:
Attention: The beta test is over now!
Warning: Please read everything properly before you install anything!
Here's the developer of APP QUARANTINE. I'm just about to release a new app called AdbToggle and I need you guys to help me out testing the beta version. The final release will be a paid version that will be available in Google Play. But before throwing around with details about the beta test let me first tell you why I have developed this app!
First, what is the app doing?
AdbToggle like the name already says allows you to toggle the USB debug settings. You can do this in the app or by using a homescreen widget. Furthermore there's an automatic mode: when you unplug your device then USB debug mode is turned off. When you plug it in again then USB debug mode is still disabled, it will only be enabled again if you unlock your screen.
Why should I need to have this tool?
Maybe you already figured out that when you plugin your phone to your PC then the contents of your SD card are only accessible when your screen is unlocked. This is very good, however there's a major security risk that still allows an unwanted person to access your data.... and if you are rooted even allows for total control over your phone, like for instance bypassing the screen lock. When buying a new Android phone then this is of course not enabled by default, but if you are an Android developer or otherwise just like to play around with Custom ROMs and root apps, then the USB debug mode is usually enabled and voilà....
What are the requirements for AdbToggle
Since I posted this here on XDA-Developers you probably already figured out that you need to have a rooted phone. You even need to have full write access to the system partition (e.g. no NAND protection like on some HTC phones) because AdbToggle is only working when installed as system app. This is maybe for the downside.... however the good thing is that AdbToggle doesn't need root access anymore after you have installed it.
What do you expect from people who take part in the beta test?
If you are ready to take part in the beta test and help me in finishing a great security tool for Android then I'm more than happy! Please let me know what device you have and what Android version you are currently running! And then of course I'm awaiting your comments, ideas for improvements, bug reports, etc. You can post directly in this thread or use PMs.
How does it work? What should I test?
When launching AdbToggle then a nice blue Android shows up and holds your usb plug. Just hit it to toggle USB debug mode, however it will first tell you that it needs to install itself as system app. If you have a working busybox installation (Busybox is a set of Linux command line tools) then it will just copy itself to the system partition and then asks you to reboot your phone. If there's no busybox available then it will guide you to Sterickson's busybox installer, which is available in Google Play as well. Once you have used it to install busybox, launch AdbToggle again and it will succeed.
After the reboot open the app and toggle USB debug mode. You will see the standard Android USB notifications popup and disappear as you toggle, and at the same time the USB connection to your PC is made available or reset. You should also try to use the homescreen widget to just do the same.
Now to the automatic mode. Launch AdbToggle, click the settings icon in the action bar, enable the checkbox. From here you can try out different test scenarios:
1. Unplug your phone from your PC and turn of the screen. When you connect it you'll see the lock screen but USB debug mode is disabled. You can recognize this as the USB debug notification will not popup. You can verify this by typing "adb devices" from your PC and no device should be visible. Now unlock your screen and USB debug mode will be enabled.
2. Turn your screen off and on again. The lock screen appears but USB debug mode is still enabled. Why? You are still connected to your PC so it's rather impossible that someone took away your phone. Also when your screen goes off you probably don't want to loose your USB connection when you are working on something....
3. Unplug your phone from your PC and plug it in again. USB debug mode is still enabled. Why? Your screen is still unlocked. Again it's rather unlikely that someone took away your phone during this time. Actually what really happens is that USB debug mode is disabled when you unplug it, but it's enabled when you plug it in again and AdbToggle figures out your screen is unlocked....
4. Reboot your phone and verify if everything is still working fine without manually launching the app.
Further test cases
You should check if AdbToggle is still working after an update! As the beta test goes on probably there will be one or another update. You should be able to install the update through Google Play as usual and the new version should be working immediately. You must NOT reboot and NOT install the updated version as system application again. So at this point AdbToggle should just behave the same like your built in Google apps.
What about the UI? Does everything show up well on your phone? Is the Android always blue when USB debug mode is on, and gray when it's off? Does the widget always show the proper state as well?
Limitations / Known issues:
The automatic mode is currently not working on tablets with a separate power plug-in. I'm trying to solve this at some point but for the moment please test it on phones only!
Now please let me start!
Sure, go ahead and download AdbToggle from Google Play and have fun! However keep in mind that the beta version will expire and not working anymore in 05/2012.
https://play.google.com/store/apps/details?id=com.ramdroid.adbtoggle
Click to expand...
Click to collapse
I have try to Install your app on my Sony Ericsson Xperia Pro MK16a. But when I click "Install AdbToggle as system app" receive "Not enough memory on system partition", although there is 124 MB of free memory. My phone is rooted but bootloader continues locked. Do I need to unlock the bootloader? Please help

1 week old Mate 9 bricked?

So after performing a factory reset on the device it booted normally the 1st time and asked me for my PIN (??). It accepted my usual PIN (!) and took me to a clean slate (all Play Store apps gone) BUT the wallpaper was still the same, my username was still there and the other user profile was also still there. What was missing was a keyboard so there was nothing I could do with the device.
OK no problem, lets perform another factory reset. So once again I hold volume up & the power button, select reset to factory settings, reboot... and this time it boots to a black screen with only the android navigation bar at the bottom and the words emergency mode on the bottom left.
Any ideas on what to do now, short of sending it back to the store?
This is a brand new unit, running EMUI 5 from the box, bought from an authorised dealer. It was not rooted or tampered with in any way or form.
I've seen those symptoms and I had to perform an erecovery. If you have the Chinese version you can do that if you have the international version I think erecovery isn't working just yet.
Sent from my MHA-L29 using XDA-Developers mobile app
I have a MHA-L29 bought in Europe. I assume erecovery is the mode enabled by pushing volume up, volume down & power button at the same time? At that point I would need the full OS in a microSD inside the device, correct? Apologies, I'm not well versed in Android...
Huawei's website offers very little help . All one can find is a link to the 'quick start manual', a link to EMUI's source code (Mate 9 is absent), a mobile wifi inspection tool, and HiSuite. I'm assuming HiSuite is of no help in this case?
Have I run out of options here? Is my next step returning the device to the shop?
Governa said:
I have a MHA-L29 bought in Europe. I assume erecovery is the mode enabled by pushing volume up, volume down & power button at the same time? At that point I would need the full OS in a microSD inside the device, correct? Apologies, I'm not well versed in Android...
Huawei's website offers very little help . All one can find is a link to the 'quick start manual', a link to EMUI's source code (Mate 9 is absent), a mobile wifi inspection tool, and HiSuite. I'm assuming HiSuite is of no help in this case?
Have I run out of options here? Is my next step returning the device to the shop?
Click to expand...
Click to collapse
The easiest choice for you is returning the device to the shop, but it can definitely be fixed.
Huawei made some very stupid decisions with the Mate 9. You cannot flash firmware from SD card anymore. You have to use eRecovery (boot the phone plugged into a computer holding the volume up key) to recover. However, this eRecovery has not launched for the european model, so you can't restore.
I might be able to help you using my DNS server because I have reverse-engineered a lot of how the Mate 9 works, but I don't have a European model to test with. If it's easy for you to return it to the store, that's probably the best option.
I've contact Huawei support and they'll be picking up the device by courier. They expect to have it returned in 5 days max. I did test the eRecovery mode that you've described and indeed it fails to gather the needed files ("Getting package info failed").
I appreciate you input, what would your method involve? I've seen firmware (B122) floating around the web, how are people flashing it if the SD card method isn't working for this unit? Having said that I wouldn't personally attempt anything that could possibly void the warranty.
Governa said:
So after performing a factory reset on the device it booted normally the 1st time and asked me for my PIN (??). It accepted my usual PIN (!) and took me to a clean slate (all Play Store apps gone) BUT the wallpaper was still the same, my username was still there and the other user profile was also still there. What was missing was a keyboard so there was nothing I could do with the device.
OK no problem, lets perform another factory reset. So once again I hold volume up & the power button, select reset to factory settings, reboot... and this time it boots to a black screen with only the android navigation bar at the bottom and the words emergency mode on the bottom left.
Any ideas on what to do now, short of sending it back to the store?
This is a brand new unit, running EMUI 5 from the box, bought from an authorised dealer. It was not rooted or tampered with in any way or form.
Click to expand...
Click to collapse
when you make a factory reset in recovery on first boot you see lost the google service and also the keyboard (i know well i have done it two time in 4 days cause bootloop) how got the google service back? simply download from apkmirror a google keyboard (you need it for next step) and install it then go to settings/advanced settings and make a factory reset(need a pin in my case that why have installed a keyboard) when the device boot again you have the google service again
I see, thank you. I'll keep that in mind next time I reset the device. :good:
I then ask, if I do reset the device to factory settings and it craps out again, how would one know if eRecovery is able to recover European models? As of 3 days ago this option would throw a 'Getting package info failed' error. Short of trying it myself when I get my device back, has anything changed in the meanwhile? Is eRecovery working now?
hi mate, I only know what I've tried: eRecovery delete google service, eRecovery not erase password.factory reset from settings does reappear google services .... likely these problems are software bugs or are linked to nougat that has different partitions than to the past....sorry for now thats it
Inviato dal mio MHA-L29 utilizzando Tapatalk
So I just got my phone back from the service center and the first impressions were not good. Before returning the phone they called me to ask for my Google username and password (!!) to make sure the device was successfully recovered. I obviously refused and just told them to kindly return the device and I would test it myself.
Well the package arrived today and is missing the SIM ejector and the IMEI back sticker. Not only that but it now refuses to install the Amazon Shopping app and Google PhotoScan app because "this app is incompatible with your device". How can this be if I had these two apps installed before??
I also noticed that the device claims to be an "Orange MHA-L29"... have these guys just flashed it with a firmware meant for Mate 9s sold through Orange?
Governa said:
So I just got my phone back from the service center and the first impressions were not good. Before returning the phone they called me to ask for my Google username and password (!!) to make sure the device was successfully recovered. I obviously refused and just told them to kindly return the device and I would test it myself.
Well the package arrived today and is missing the SIM ejector and the IMEI back sticker. Not only that but it now refuses to install the Amazon Shopping app and Google PhotoScan app because "this app is incompatible with your device". How can this be if I had these two apps installed before??
I also noticed that the device claims to be an "Orange MHA-L29"... have these guys just flashed it with a firmware meant for Mate 9s sold through Orange?
Click to expand...
Click to collapse
mmmm too bad mate,your M9 is no brand? Orange is a carrier ....my opinion is ask why this change and ask for phone replacement
Yep, unbranded bought from an authorised dealer.
I am now going to escalate it and try to have this unit rejected and exchanged for a brand new one. I sure hope they don't propose replacing it with a refurbished unit, after all we're talking about a €700 device here and it has spent more time in the service center than in my hands. Very frustrating.
And this whole "no way to use eRecovery yet" and "no way to flash it from MicroSD" is just the last nail in the coffin... I mean what were they thinking? Even Apple devices allow me pick up the corresponding firmware and flash it at home from day 0. I hear the P9 Plus is less restrictive, maybe I should have gone for one of those instead?
I've got a real lemon here... let's see how they handle my case, I'll keep you all updated.

Just updated to Oxygen OS 9.5.9 and the *#808* Factory Mode is no longer working.

I just updated to the latest OOS build and Factory Mode seems to no longer work. *#800* still works though. Does anyone know if 1+ disabled it with this update, or is it just me?
*#801# is also not working.
*#801# Does not work. So QPST / PDC VoLTE doesn't work ...
Following. Maybe someone can download the apk from 9.5.8 to port on 9.5.9.
Edit: Looks like somebody already did it: https://forum.xda-developers.com/showpost.php?p=79868445&postcount=188
Switching on Serial on EngineerMode doesn't work, but Full-port switch looks like it's enough for VoLTE.
Where is the ROM link? I hate it that this company doesn't keep their stupid website updated
photolarry said:
Where is the ROM link? I hate it that this company doesn't keep their stupid website updated
Click to expand...
Click to collapse
wtf. Show me where other OEMs update their page instantly.
matze19999 said:
wtf. Show me where other OEMs update their page instantly.
Click to expand...
Click to collapse
Google does and this OEM should. There's a hidden link but I found it. I just think it's stupid they hide it and don't place it online from their website. Goes against what they told me about being very developer friendly and updates every three weeks etc. Not to mention this slot confusion.... Where you get boot loops if you don't fastboot the old boot image. It's caused me many headaches which I didn't get with a pixel.
Can anyone confirm that it is safe to install this apk? It won't break anything?
They don't put this up for nothing...
"This OTA will have a staged rollout, the OTA will be received by a limited number of users today and will have a broader rollout in a few days after making sure there are no critical bugs"
But yes, let's push an update out to everyone, day one of release, and potentially screw up many phones.
Google used to do the same thing. They changed that and problems occured a few times. Both OEMs are not at fault for others sharing links to get the updates.
proa_p said:
Can anyone confirm that it is safe to install this apk? It won't break anything?
Click to expand...
Click to collapse
Safe!
SpasilliumNexus said:
They don't put this up for nothing...
"This OTA will have a staged rollout, the OTA will be received by a limited number of users today and will have a broader rollout in a few days after making sure there are no critical bugs"
But yes, let's push an update out to everyone, day one of release, and potentially screw up many phones.
Google used to do the same thing. They changed that and problems occured a few times. Both OEMs are not at fault for others sharing links to get the updates.
Click to expand...
Click to collapse
Case in point lol
https://www.androidpolice.com/2019/07/10/get-your-pixels-ready-android-q-beta-5-is-landing-today/#2
Tompi-droid said:
*#801# Does not work. So QPST / PDC VoLTE doesn't work ...
Click to expand...
Click to collapse
Have you found a solution for this?
I can enter to engineering mode after install the apk, but when I enable serial, it just close.
sixtybi said:
Have you found a solution for this?
I can enter to engineering mode after install the apk, but when I enable serial, it just close.
Click to expand...
Click to collapse
Full-port switch: ON, dont Touch the Serial.
I would like to enable the Serial from the *#801#, however the engineer menu crashes every time.
Is there a solution to enable the Serial?
Ultimately, I would like to enable the serial to use the QPST application.
Works even when it closes ...
mine also closes when I press "Serial Off", however, it seems it's enough for the USB driver to talk to the device.
I was able to talk to the device and switch providers back to a working VOLTE/VOWIFI profile.
BTW, I now have a OnePlus Last - it's not a OnePlus 6 anymore, because it's the last device I will ever have bought from OnePlus.

Question incoming call notification delay

I don't know when it has started, but now when everyone try to call me the phone ring but i have to wait about 3-5 seconds before i get the notification on screen and i can answer
I have got the MIUI global 12.5.1.0 (RJUEUXM) and i know it is quite buggy, but i have googled a bit and none seems to have my same problem.
I read that i could try to wipe the system cache (on a oneplus one forum) but the standard recovery mode doesn't have this option, and i really don't want to wipe the phone to get another one
Any suggestion? Is there a way to wipe the system cache without formatting? Do anyone had my same issue?
Thank you
MIUI is trash that's why. And it's related to agressive memory management. (killing apps in background, even system ones)
k3lcior said:
MIUI is trash that's why. And it's related to agressive memory management. (killing apps in background, even system ones)
Click to expand...
Click to collapse
I have tried in the built-in power manager to set the power saving option for the dialer app to none, but no luck
Try disabling "Turn on MIUI optimisation" in the Developer options (scroll to the bottom of the page). It may work, or it may not work. Xiaomi thinks that disabling it can cause issues ...
Updated at 12.5.2.0 (RJUEUXM) and the problem is still present.
Do anyone have the same problem?
surcof said:
I don't know when it has started, but now when everyone try to call me the phone ring but i have to wait about 3-5 seconds before i get the notification on screen and i can answer
I have got the MIUI global 12.5.1.0 (RJUEUXM) and i know it is quite buggy, but i have googled a bit and none seems to have my same problem.
I read that i could try to wipe the system cache (on a oneplus one forum) but the standard recovery mode doesn't have this option, and i really don't want to wipe the phone to get another one
Any suggestion? Is there a way to wipe the system cache without formatting? Do anyone had my same issue?
Thank you
Click to expand...
Click to collapse
Similar problem with notification delays, in my case it affect sms and clock, dunno if this the same as your, however i post anyway, just disable via ADB the DOZE feature for apps affected with delays (do not work if i disable battery optimization in the normal settings).
Enable developer options in the device, enable usbdebug, connect the phone to the pc, install the correct usb MI drivers (use the MiUsbDriver.exe command), surf to adb directory and whitelist the system apps you want to have instant notifications.
To retrieve the list:
adb shell dumpsys deviceidle whitelist
To whitelist apps affected:
adb shell dumpsys deviceidle whitelist +com.xxxxxxxx.xxxxxxxx
Of course replace the apps name xxxxxxx with the correct name of system apps installed in your device.
Use the first command and check again if the apps you whitelist are now in the list as "user". Setting is permanent until you do a clean flash or flash a new rom.
No idea if you need to unlock the bootloader to apply such change, try it if work.
kd276 said:
Similar problem with notification delays, in my case it affect sms and clock, dunno if this the same as your, however i post anyway, just disable via ADB the DOZE feature for apps affected with delays (do not work if i disable battery optimization in the normal settings).
Enable developer options in the device, enable usbdebug, connect the phone to the pc, install the correct usb MI drivers (use the MiUsbDriver.exe command), surf to adb directory and whitelist the system apps you want to have instant notifications.
To retrieve the list:
adb shell dumpsys deviceidle whitelist
To whitelist apps affected:
adb shell dumpsys deviceidle whitelist +com.xxxxxxxx.xxxxxxxx
Of course replace the apps name xxxxxxx with the correct name of system apps installed in your device.
Use the first command and check again if the apps you whitelist are now in the list as "user". Setting is permanent until you do a clean flash or flash a new rom.
No idea if you need to unlock the bootloader to apply such change, try it if work.
Click to expand...
Click to collapse
thanks for your replay, but no look for me.
surcof said:
thanks for your replay, but no look for me.
Click to expand...
Click to collapse
Sorry this isn't helping for your specific case.
Hi,
yes my brother has this problem when a friend calls his second sim card ... he uses two SIM cards at once, you also use two cards at once? (At once=two sim cards in mobile)
I only use one sim and I don't have this problem. the above advice did not help my brother, the problem is definitely in the dual sim function (implementation). Please report it to someone on xiaomi to fix it.
PS: can you try to use only one SIM card? if your problem goes away. let us know if this is the core of the problem. Thank you.
Ochrana said:
Hi,
yes my brother has this problem when a friend calls his second sim card ... he uses two SIM cards at once, you also use two cards at once? (At once=two sim cards in mobile)
I only use one sim and I don't have this problem. the above advice did not help my brother, the problem is definitely in the dual sim function (implementation). Please report it to someone on xiaomi to fix it.
PS: can you try to use only one SIM card? if your problem goes away. let us know if this is the core of the problem. Thank you.
Click to expand...
Click to collapse
i only use one sim card, never used two
I have the same problem but in my case I think it's about having Zepp app giving notifications to my watch. Do you have a similar app? You can try to disable phone access to all apps except dialer and see if works...
DrunphO said:
I have the same problem but in my case I think it's about having Zepp app giving notifications to my watch. Do you have a similar app? You can try to disable phone access to all apps except dialer and see if works...
Click to expand...
Click to collapse
Nop, the only app i use is the dealer
Have you found any solution?
Happen to me as well on mi9t pro. Further googling led me to believe this was issue with phone app by google. You can check theor review on playstore and most people having this issue.
i have factory reset my phone and problem is still there.
Little update: i have had this issue for all the time when i was in holiday with a poor interbet connection, now that i'm returned home, where i have quite alwais signal the issue seems gone.
May be that the dialer need internet access to work properly?
Hi,
I'm having the same issue with my poco x3 i keep having a delay before my screen turns on when i'm receiving call. Is someone still having this issue or it's just me ?
I don't think there's a link with Wifi, at least that's really strange to me.
Thanks
Answer is in second post, this doesn't happen on custom ROM's. (unless they are based off MIUI)
Same problem with Xiaomi mi 11
Try to remove all the email accounts from the gmail app, it should fix.
Same issue... POCO X3...
3/4 secs delay in notifications...
the phone rings and I can't see who is calling... After 3/4 sec it shows the notification...
It's very funny how everyone is ignoring @k3lcior 's posts, when he is just spitting truth in your face.
Sorry, guys, but you can't just ignore the real cause and look for a cheap workaround that might fix it in theory. In reality, ROMs like the official one from Xiaomi (MIUI) are extremely aggressive in terms of killing background apps, etc. They want to reduce battery strain, no matter how much stuff it breaks.
This is a problem across different apps. There are tons of issue reports from app users, that can't use some apps properly, because MIUI keeps killing it, even though it already has been whitelisted in the power saving list, as not allowed to be killed. It still gets killed, though.
So, if you guys want to keep your apps alive and not getting killed all the time, you have no choice but to switch to a different ROM. Even if you find a workaround on the official ROM, then it's still very unreliable.
To be clear, once again:
Even if you whitelist your app, it can still get killed, because MIUI does not give a crap, if you need the app. It still may get killed!

Categories

Resources