Database Info

[APP|2010-07-31] ANDROID BOOTCAMP v1.1 - NOT just another Android-loader... :D

A few weeks ago when the Android-on-HD2-hype started i made this small app. This piece of software was inspired by GenYDualboot (author: YOZGATG) so some credit should go to him...
To make it clear: I wrote this software by myself (basic4ppc) from the scratch so no code or other intellectual property has been stealed.
ANDROID BOOTCAMP v1.1
System Requirements:
* WVGA (VGA/QVGA not supported!)
* WinMob 6.5.X (not tested on WinMob 6.5)
* min. NETCF 2.0
* a SD-card containing working Android-build
Basic Functionality:
* WinMob based Android loader
* possible to "boot" ANDROID or to stay in Windows
* possible to "autoboot" with countdown (10sec)
* possible to choose if CLRCAD.EXE is loaded prior to HARET.EXE or not
* Autodetection of HARET.EXE and CLRCAD.exe on the SD-Card (checks if files are present in root or "\Android")
* possible to modify the path to your Android-build by changing the path in the registry
* possible to boot at systemstart (the app puts itself to "launch52" in the registry)
* possible to save your settings
* fully functional on non-WWE-Roms (checks the registry for the name of your sd-card)
* full multi-language-support (by editing the "language.ini"; at this time only german an english are buildin)
* full landscape/rotation support
* fully skinable (by modifing the PNGs in the app-folder, i'm going to release a GTX based skin or some other skins if it's wanted by the community)
* new: change font color (black/white)
* new: switchable progressbar (showed during countdown)
* new: ClearAndroid! removes Android-related junk-/tempfiles and cache!
* new: TotalClean! totally ereases your Android environment (for a clean upgrade to a new build) - USE WITH CARE!
Disclaimer:
This piece of software is free and can freely be downloaded here. You are allowed to modify, cook in or distribute my work as long as you give me some credit.
YOU ARE NOT ALLOWED TO CHARGE ANY KIND OF FEE NEITHER FOR THIS SOFTWARE ALONE NOR BY INCLUDING IT OR ANY MODIFICATIONS OF IT INTO A ROM/ANDROID-BUILD OR ANY OTHER "SERVICE"!​
(see threat "STOP THE STEALING" in the Android subforum for more details...)
I'm not responsable for any kind of damage or data loss on your device. The software is provided as it is and you are going to use it on your own risk.
Credits:
* the developers here and at htc-linux.org for HARET.EXE/CLRCAD.EXE and for their amazing work!
* YOZGATG for GenYDualboot
Roadmap / future functions to come in Android Bootcamp v1.2 (if wanted by the community):
* GUI-overhaul to a nicer / modern look
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add support to select androit installation (if more than one installation present on SD)
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder) integrated into v1.1!
* add option "TOTALCLEAN" (ereasing all android related files and folders incl. thumbnails/cache/etc) integrated into v1.1!
More inf
o to come....
Feel free to make your suggestions!

FAQ / Userguide
Q: How do I install Android Bootcamp?
A: Just download the CAB attached to the firs post and install it to your device. It's recommended to put it into your phone-storage not to the sd-card.
Q: How do I boot into Android?
A: Click on the Android-button (the picture).
Q: The Android-button is greyed out and the app says "no Android!"
A: Make sure that there is a sd-card plugged into your device containing Android in the root or in the "\Android" subfolder. Also HARET.EXE/zHARET.EXE is required in the same folder to successfully boot Android. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to HARET.EXE/zHARET.EXE. If HARET not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder. If you want to modify the path to your own needs go to the registry and alter the value "Haret" in the key "HKLM\Software\Android Bootcamp".
Q: How do I make sure that CLRCAD.EXE is started prior to HARET.EXE
A: Click on the checkbox next to activate CLRCAD or select the option in the settings-menu. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to CLRCAD.EXE. If CLRCAD not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder and after that it takes the CLRCAD.EXE in the Android-Bootcamp program folder. If you want to modify the path to your own needs go to the registry and alter the value "CLRCAD" in the key "HKLM\Software\Android Bootcamp".
Q: How do I stop the countdown?
A: Just tap on the countdown-message or tap on the checkbox next to "activate AutoBoot".
Q: How do i activate/deactivate AutoBoot?
A: Check or uncheck the checkbox next to "activate AutoBoot" or select the corresponding option in the settings-menu.
Q: What does "execute at Boottime" mean?
A: The App makes 2 entries to the registry ("HKLM\init\Launch52" and "HKLM\init\Depend52"). These entries make sure that Android-Bootcamp is started during the WinMob boot procedure with the saved settings as soon a possible. Please note that the boot process does not stop and continues loading system processes after Bootcamp is started. I suggest also to check the "AutoBoot" option so that Android/WinMob is loaded automatically after 10sec. To disable this option uncheck the option (registy changes made immediately - no "save settings" is needed)
Q: How do I save my settings? Why are my settings not saved?
A: Your settings are not saved automatically - choose "Save settings" in the settings-menu prior to booting Android or closing the app.
Q: How do I activate the landscape support?
A: Landscape and screen-rotation is fully supported by the app itself but it's possible that you have to add the app to the rotation-whitelist. If you don't know how to do this - google for TouchTools or BSB-Tweak. With the help of these apps you can enable rotation service easily to any program.
Q: The program gives me the error-message "No Registry-values found, create them now?"!
A: Possibly you deleted one/some reg-values needed by the app. Just click to "YES" and all settings/RegKeys will be created with default values.
Q: I'm not naturally speaking english/german. How do I add my own language?
A: This can be done very easily by modifing the file "language.ini" in the Android Bootcamp - program folder. Please make sure that the first line is the name of the language and that the ini's structure isn't altered (NO SPACES between value, "=" and translation!!)
Q: How do I add my own skin?
A: Modify the PNG-files in the Android Bootcamp prgram folder to your own needs after making a backup of the orginal files (recommended). Feel free to post your files compressed to a ZIP-file here!
Q: I still don't get "execute at Boottime" to work!!
A: First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless if Bootcamp is in fore- or background. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
Q: Is it possible if you can code it so it can find CLRCAD and Haret in the "cm6-htcleo" folder for the CyanogenMod release / in some other custom folder?
A: Yes, it's already possible - open your registry with a regeditor and go to the key "HKLM\Software\Android Bootcamp". Check and edit the VALUE "Haret" and put the FULL PATH to your HARET.EXE / zHARET.EXE in there. After this modification Bootcamp should be able to find your Android-Installation. The feature of selecting a custom folder is added with the next release of Bootcamp.
NOTE: Be aware that "CleanAndroid!" and "TotalClean!" doesn't work with custom Android folders - these two options look for an Android-environment in the root of your storage card or in the "Storage Card\Android" folder respectively. So keep an eye on those two (probably dangerous) features, so that not the wrong files get lost...

SKINS
Q: How do I install a skin?
A: Download the zipped skin-file here and extract all files to the Android Bootcamp program folder overwriting the orginal files.
Q: How do I add my own skin?
A: Modify the JPG/PNG-files in the Android Bootcamp program folder to your own needs after making a backup of the orginal files (recommended). Make sure that your files have the same dimensions and keep their file format! Feel free to post your files compressed to a ZIP-file - I will add them here!
NOTES:
* GTX-based skin is beta/for testing only and does not look very good - better version will be uploaded with the next program version (see text color issue above)
* Text color can't be changed a this time - going to add an option in the next version to switch between black/white fixed in v1.1
* there is some minor picture-misallignment regarding the android button. This is already fixed in the code an will be included in the upcomming update fixed in v1.1

nice work! good to see several alternatives out there for dual booting

Don't need it...
But really great job!
Pretty GUI !

beautiful my fav booting app so far,
thanks

hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR

Best Dual boot for Android/Winmo out there at the moment.

essojay said:
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Click to expand...
Click to collapse
Please explain this issue to me because i don't have this kind of problem in my setting. Do you want to have an option to "automatically clean" the root/android folder of your sd-card after rebooting (to WinMob)? What kind files should be cleaned? I easyly could add an option to clean the "*.REC" files and the "LOST+Found" folder if this is wanted.

each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR

essojay said:
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
Click to expand...
Click to collapse
Hmm, I looked at the given threat and this issue seems strange to me. I never had this kind of problem and this could be BECAUSE my Android-installation resides in the folder "SD-CARD\ANDROID". Darkstone and Dani recommend to put their builds (Froyo) into the Android subfolder and not directly to the root-folder of the sd-card.
Adding a option to clear or to delete the android folder seems not acceptible to me because - like I said - many people including myself have their Android installation in this specific folder and consecutively would destroy their Android environment.
But i'm considering to add a TOTALCLEAN-feature so the user can easily prepare the sd-card for a new android build by ereasing his android installation and all corresponding files and folders (thumbnails, cache, etc.) without the need of formatting the sd-card.

Epic
Very nice GUI! I will be giving this a try. Seems like a good time to experiment with some different flavors of Android...Weekend Project! w00t!

Yes Ironheart...am going to try the sdcard/android way and let you know.. just read somewhere about everything in the android folder.. thanks.. will let you know
bR

really nice man, i will jump ship to your loader

Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup

Zell Dinch said:
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Click to expand...
Click to collapse
First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless whether Bootcamp is in foreground or or not. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.

my contribution to the theming

ironheart said:
Future functions to come in Android Bootcamp v1.1 (if wanted by the community):
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder)
* add option "TOTALCLEAN" (easy preparation of your SD-Card without formatting by ereasing all android related files and folders incl. thumbnails/cache/etc)
* add support to select androit installation (if more than one installation present on SD)
Click to expand...
Click to collapse
+1 Want have

[/QUOTE]
voiceofid said:
my contribution to the theming
Click to expand...
Click to collapse
Nicely done! going to put your skin to post#3...
Thank you!
EDIT:
I testet your theme and i had to lightly modify it to keep text-readability (blur filter, less light, htc-logo removed)... i hope you are ok with my modifications. Still good job done (added to skins)

HD2_Noob said:
+1 Want have
Click to expand...
Click to collapse
Some of the new features are already working in my beta-build und are going to be released to public soon (ETA for final 1.1-release maybe 1-2 days)...
Stay updated!

[PORT] Pixel NavBar with animations

Disclaimer:
I am not responsible for bricked devices or you getting fired because the alarm app failed. Please do some research before making any system modification. You are choosing to make these changes at your own risk and if you point the finger at me for messing up your device, I will laugh at you.
I noticed that most users wanted to have the Pixel Experience for this device and one main reason why we don't was because of those hardware keys which is not in line with Google's stock android.
Thanks to @Tulsadiver for providing the zip which works fine with a/b partition, giving me less work to do.
Below, you'll find how to:
- Enable On-Screen Navigation Bar
- Disable Hardware Capacitive Keys
- Disable Hardware Capacitive Key Lights
- Install Pixel Navigation Bar with animation
Your device needs to be rooted and with TWRP installed
A file manager app with root access
There is no other way to achieve this without having root access
1. To enable on-screen navigation bar:
Navigate to this path: root/system/
Edit the file: build.prop
Insert below code anywhere or at the bottom then save changes.
qemu.hw.mainkeys=0
2. To disable hw keys:
Navigate to this path: root/system/usr/keylayout/
Edit the file: ft5435_ts.kl
At the bottom you'll find below:
key 139 MENU VIRTUAL
key 172 HOME VIRTUAL
key 158 BACK VIRTUAL
To disable those, just put # before the word "key" then save changes.
3. To disable hw key lights:
Navigate to this path: sys/devices/soc/leds-qpnp-10/leds/button-backlight/
Edit the values of below from 10 to 0 then save changes
brightness
max_brightness
Reboot your device for the changes to take effect.
To enable Pixel Navigation Bar with animation, just download the file: [PORT]PixelNavBar-tissot.zip and flash it via TWRP.
(Note: the ozop.zip file is to revert back the changes)

When I try to open the brightness and max_brightness with MiXplorer I get a "failed" message. I am rooted using CFAutoroot.

tosmopolitan said:
When I try to open the brightness and max_brightness with MiXplorer I get a "failed" message. I am rooted using CFAutoroot.
Click to expand...
Click to collapse
Use x-plore app from Play Store.

MarkerBeanXDA said:
Use x-plore app from Play Store.
Click to expand...
Click to collapse
Thanks, worked perfectly!!

MarkerBeanXDA said:
I noticed that most users wanted to enable the on-screen navigation bar and disable the hardware keys including its light to get a better stock android experience.
Below you'll find the steps on how to do just that:
First of all, you need to be rooted and and install a file manager app with root access
There is no other way to achieve this without having root access.
1. To enable on-screen navigation bar:
Navigate to this path: root/system/
Edit the file: build.prop
Insert below code anywhere or at the bottom then save changes.
qemu.hw.mainkeys=0
2. To disable hw keys:
Navigate to this path: root/system/usr/keylayout/
Edit the file: ft5435_ts.kl
At the bottom you'll find below:
key 139 MENU VIRTUAL
key 172 HOME VIRTUAL
key 158 BACK VIRTUAL
To disable those, just put # before the word "key" then save changes.
3. To disable hw key lights:
Navigate to this path: sys/devices/soc/leds-qpnp-10/leds/button-backlight/
Edit the values of below from 10 to 0 then save changes
brightness
max_brightness
Reboot your device for the changes to take effect.
Click to expand...
Click to collapse
Nice
But when we reboot, Lights are enabled.
We have to bring down max brightness to 0 once again.
Is there any permanent method to disable backlight?

Wow thanks. Can you also guide on how to enable night light?

Vasu Netha said:
Nice
But when we reboot, Lights are enabled.
We have to bring down max brightness to 0 once again.
Is there any permanent method to disable backlight?
Click to expand...
Click to collapse
Are you rooted with CF-Auto-Root?

MarkerBeanXDA said:
Are you rooted with CF-Auto-Root?
Click to expand...
Click to collapse
Yes

Vasu Netha said:
Nice
But when we reboot, Lights are enabled.
We have to bring down max brightness to 0 once again.
Is there any permanent method to disable backlight?
Click to expand...
Click to collapse
same problem, how to permanently off the button light?

NavBar not giving animation
i recently try this method to add nav button. then i installed xposed and pixel nav button module. but, the animation not running well. on my other device the home button's ring rotating while charging. but on mi a1 its not animating

How to swap back and recent key?

Please find out a way to disable hw key lights permanently..

Ripon Raihan said:
Please find out a way to disable hw key lights permanently..
Click to expand...
Click to collapse
Looking into it.

Aman301582 said:
How to swap back and recent key?
Click to expand...
Click to collapse
Try swapping their values.
key 139 BACK VIRTUAL
key 172 HOME VIRTUAL
key 158 MENU VIRTUAL

MarkerBeanXDA said:
Try swapping their values.
key 139 BACK VIRTUAL
key 172 HOME VIRTUAL
key 158 MENU VIRTUAL
Click to expand...
Click to collapse
Swap is working!

Ripon Raihan said:
same problem, how to permanently off the button light?
Click to expand...
Click to collapse
Pretty sure you change the permission to read only so the system can't edit it. Could be wrong. Do it at your own risk.

envy63 said:
i recently try this method to add nav button. then i installed xposed and pixel nav button module. but, the animation not running well. on my other device the home button's ring rotating while charging. but on mi a1 its not animating
Click to expand...
Click to collapse
Try to flash the zip provided in this thread instead

Can you create a magisk version?

+1 for a Magisk version

another +1 for a magisk version

It has begun - KangVip/Hrt Team custom roms for Android Pie (rooted)

It has begun - KangVip/Hrt Team custom roms for Android Pie (rooted)
For the moment - version 9.0.125.
And for china firmware (CLT-ALC00, CLT-ALC01 and others)
Original thread - (use google translate, or chrome with automatic translation)
Thanks for their great rom.

tamaskurti said:
It has begun - KangVip/Hrt Team custom roms for Android Pie (rooted)
For the moment - version 9.0.125.
And for china firmware (CLT-ALC00, CLT-ALC01 and others)
Original thread - (use google translate, or chrome with automatic translation)
Thanks for their great rom.
Click to expand...
Click to collapse
Only for Chinese residents/visitors

forever_lol said:
Only for Chinese residents/visitors
Click to expand...
Click to collapse
Yes, unfortunately.
Hovewer, @bowlandspoon and @other members of 4pda (sorry but the credits go there) have make it universally available.
This means, that it will work practically with ANY region.
Please add to the cap!
Switch to pure android 9.0 for Huawei p20 pro!
Instructions checked and translated by me from XDA to a sleepless night =)
( Unlocked bootloader is required, you perform all actions at your own peril and risk, make backups )
And so, let's go:
#
Step-by-Step Actions
1 - We will need to download:
#
- 7-ZIP v18.5 - Here (1MB)
- AndroidPlatformTools-P20Pro.zip - Here (30MB)
- RemoveEncryption-P20Pro.zip - Here (1MB)
- FirstEver-Android-9.0-charlotte-20181026.rar - Here (1.94 GB)
2 - We install a native, clean firmware (This is not in the instructions, but I learned by experiment what to do better)
#
- Turn off the phone when the menu appears, where you need to press the power button or hold the volume up, hold down the sound key up.
- And if you have the original firmware, do "Factory Reset" and proceed to the next step.
- If not, then select the section "Download latest version and recovery", where we press the "Download and recovery" button, then connect to WiFi
and wait for the process to finish.
- When it's all over, make a "Factory Reset"
3 - We install TWRP sharpened for our needs:
#
- Extract the AndroidPlatformTools-P20Pro.zip archive, for example, on the C: \ drive.
- Open the command line and write: "CD C: \ APT-P20Pro " (Or your path to the files)
- Turn off the phone
- Hold the volume down, connect the cable and wait until the fastboot
is loaded - We write in the command line:
"fastboot flash recovery_ramdisk twrp-3.2.1-0-charlotte-mod.img"
- So we have the installed TWRP for Android 9.0 on the phone
- Reboot the device via the command line, we write: "fastboot reboot "
4 - Disable encryption:
#
- Turn off the phone
- Hold the volume up and on, wait for the Recovery to load
- In TWRP, press the "Wipe" button, then "Format Data"
- Print: "yes" and press the blue button to apply
- Next, click on the house below, go to the "Reboot" "in it we select" Recovery "
- Again we boot into Recovery and connect the phone to the cable
- Copy the archive" RemoveEncryption-P20Pro.zip "into the phone memory
- In TWRP click the" Install "button
- Choose" / sdcard ", then our file" RemoveEncryption -P20Pro.zip "
- Swipe to the right to confirm the firmware and wait for the process to finish
- Again, click on the house below, go to the" Reboot "item in it, select eat "
- We print: "yes" and press the blue button to apply
- your "Data" section is no longer encrypted.
5 - Create a backup
#
- In TWRP, press the "Backup" button
- Put a daw on "Kernel" (if you want, you can choose everything else)
- Swipe to the right for confirmation and wait for the process to finish
- Next, wait for the house button to return to the TWRP main menu
6 - "Installation" pure Android 9.0
#
- Extract the archive "FirstEver-Android-9.0-charlotte-20181026.rar" to any location and copy the folder "FirstEver-Android-9.0-charlotte-20181026" to your
phone in the "\ Backup \ TWRP \ BACKUPS \ (Folder with literal name) \ "
- In TWRP confidently press the" Restore "button
- Choose" FirstEver-Android-9.0-charlotte-20181026 "
- And before starting the process - MANDATORY, remove the checkbox from" KERNEL "!!!
- Then swipe right and wait for the end of the process
- And finally click on the house, select the item "Reboot" and in it "System"
- Done! Enjoy Android 9.0 with a Pixel 3 camera!
P / s
The first time I write instructions, so do not scold much, if something is wrong.
And of course, which is also not unimportant, a couple of words:
#
About the performance of the firmware
What pleases, the workability is almost complete. Everything flies, just go.
And lo and behold, they even managed to get into the Pixel 3 camera, transfer the full port of the native Huawei camera, and all the modes from night to photo, such as water, should be present.
In general, I am very impressed and enjoy all the tactile sensations and freedoms of pure android.
But, of course, there is something that still doesn’t work, but only for the time being, it is:
- NFC
- Taking photos in RAW
- Double tap to start the phone
- And it seems that with a stereo sound you need to conjure a little.
Despite this, I personally am delighted and back to EMUI, I don’t want to. We will wait for the final fixes and full firmware. Those who
do not idle talk, instructions for help =)
I hope someone will come in handy, please yourself with something new and clean, before the new year! =)
Post has been editedRVmaster - 11/23/18, 07:54
Click to expand...
Click to collapse
link to their servers
It worth a try
Credits @RVMaster redirected from FirstEver Rom and FirstEver P20Pro XDA thread
The description in the quote refers to already realised ubr rom.
The kangvip rom is chinese with full of bloatware, but those can be uninstalled via AppGallery (without root), or Frozed/Uninstalled via TitaniumBackup (with root).

flash random Chinese ROM.. what could possibly go wrong

pablo_max said:
flash random Chinese ROM.. what could possibly go wrong
Click to expand...
Click to collapse
Sorry to hear that..
Chinese firmwares in these days are far away better than global firmwares.
Just they have their bloatware apps, that can be uninstalled.
KangVip, Hrt Team, Hi-To are the most renowned developers between them.
So for the moment I could say that their roms are the best Stock Roms with customizations like K-Settings and others.
Again, I don"t speak about custom roms, just Stock Roms with modifications.
Here an example video Huawei P20 Pro KangVip - its a bit older, android 8 rom, but take a look. (At 2:08 are the K-Settings)

tamaskurti said:
Chinese firmwares in these days are far away better than global firmwares.
Click to expand...
Click to collapse
Hmm no disrespect intended, but considering how complete and utter crap Huawei FWs are for their non Nexus devices, as well as many of the other Chinese manufacturers non-sense Android skins, I would say that Chinese firmwares are among the worst on the planet.
This really seems to be an "Asian" thing though. The market in Korean and China are vastly different than in the "West". People like cute little bubbly things and lots of bings and bongs. So while the guys over there may expect and indeed love those types of skins, more than not, people here hate it.
BTW... I see almost no difference at all between stock EMUI and that link you sent.
The entire issue with these phones IS EMUI. It removes are breaks MANY of the best features and usability items in Android. It doesn't matter how you mod it, EMUI will always be crap. And yes... I do own and greatly dislike this phone because of EMUI. But.. 1st world problems and all that

pablo_max said:
Hmm no disrespect intended, but considering how complete and utter crap Huawei FWs are for their non Nexus devices, as well as many of the other Chinese manufacturers non-sense Android skins, I would say that Chinese firmwares are among the worst on the planet.
This really seems to be an "Asian" thing though. The market in Korean and China are vastly different than in the "West". People like cute little bubbly things and lots of bings and bongs. So while the guys over there may expect and indeed love those types of skins, more than not, people here hate it.
BTW... I see almost no difference at all between stock EMUI and that link you sent.
The entire issue with these phones IS EMUI. It removes are breaks MANY of the best features and usability items in Android. It doesn't matter how you mod it, EMUI will always be crap. And yes... I do own and greatly dislike this phone because of EMUI. But.. 1st world problems and all that
Click to expand...
Click to collapse
I understand.

---------- Post added at 01:24 PM ---------- Previous post was at 01:12 PM ----------
[/COLOR]
tamaskurti said:
Yes, unfortunately.
Hovewer, @bowlandspoon and @other members of 4pda (sorry but the credits go there) have make it universally available.
This means, that it will work practically with ANY region.
Click to expand...
Click to collapse
Please HuaweiClub mod apk which commantable with any region...

What TWRP are they referring to ? Have you intalled it? Does it offer decryption if you don't allow PIN / Password? on PIE? I think this is probably the best thing that this process could offer.
IF it does then you could maybe share the TWRP as a "This is not my work" but here you go thread.
We sorely need it.

[SOLVED] MTCE GS 3.07 settings entries missing, clock does not work properly

My device info:
Build number: rk3368-userdebug 9 PQ2A.190205.003 eng.hct2.20190411.192110 test-keys
Kernel version: 4.4.167
MCU version: MTCE_GS_V3.07_3
In settings menu I don't see lot of std android settings (probably hidden for normal user).
I would like to enable split screen (it is disabled by default - 7 inch screen), but I can not enter developer options.
Standard android way with tapping build number is not working.
I also tried apps (e.g. "developer options) but it does not work - it shows "First enabled developer options".
I also tried rooting (simple way) with code (*#htc#root#) in factory settings, and with kingoroot. It does not work.
Do I need use adb for that?
Additionally clock is not working properly. After vehicle shutdown signal - radio is falling a sleep. After wakeup it looks like time freeze.
If I activate GPS time adjust it makes clock late 30 minutes.
If I activate internet time update it makes clock late 1h - probably because of winter / summer time switch, but I don't see that setting (also hidden).
Any help would be pleasent

I would try to change to stock rom.
But Im not sure if that would be even possible if I do not enable developer options first and next usb debug to access adb and flash mode.
Maybe it could be done by MCU update file? somehow make it to change system configuration?

SZAMAN92 said:
I would try to change to stock rom.
But Im not sure if that would be even possible if I do not enable developer options first and next usb debug to access adb and flash mode.
Maybe it could be done by MCU update file? somehow make it to change system configuration?
Click to expand...
Click to collapse
for what vehicle is that HU ?
i have same for opel, and have problems with stering wheel buttons, when i press next or back button it react like i press it 2 or 3 times :/
do you know how to enter recovery in that unit? maybe flash other MCU file ?

It is my device
https://xtrons.com/renault-megane-iii-fluence-android-9-0-pa79mg3rip
For me wheel buttons work well.
However try to check factory settings
Settings > Factory settings > enter code (126 in my case) > Keys
I have there option to change CAN bus to proper vehicle model.
Unfortunetaly I don't have experience with flashing such devices. Until now I was flashing only smartphones.
There were lot of tutorials how to do that. For Android auto HU I dont know even how to start.
For smartphone you could enter recovery by adb, but first you need unlock USB debugging. If you have access to developer options you could do that - that is not my cas.. sadly.
EDIT:
I found solution for time issue
https://forum.xda-developers.com/showpost.php?p=72946736&postcount=4
EDIT2:
Better solution
1. Get root
https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740
2. Use that app
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=pl
EDIT3:
1. Malaysk ROM!!!
Clock work without any problem, I have split screen on my 7 inch device

Enable Hidden Dark Mode for pocophone f1 Miui10

For those of you who cannot wait until miui 11 - here is a easy trick to activate dark mode
How to enable dark mode
Connect your device to your PC , open command prompt in the same directory where ADB binary is stored
Enable Dark Mode: adb shell settings put secure ui_night_mode 2 Disable Dark Mode: adb shell settings put secure ui_night_mode 1
Reboot your phone to get the system-wide dark mode
*before doing these change your theme to classic version
*enable usb debugging security settings as well - once you activated dark mode you can turn it off.
im using global rom with locked bootloader
10.3.5.0
source:
http://c.mi.com/thread-2274658-1-0.html

Or just use eu roms and that option is built in.

As far as I understand, we have to enter these lines everytime if we want to switch from dark to white vice versa? I can't see any toggle after I enabled the dark mode. I even tried the (auto) mode and it is not changing.

Works great! MIUI 10 Beta 9.6.27, locked bootloader.
Thank you very much!!

mkozal said:
As far as I understand, we have to enter these lines everytime if we want to switch from dark to white vice versa? I can't see any toggle after I enabled the dark mode. I even tried the (auto) mode and it is not changing.
Click to expand...
Click to collapse
Yes you are right
There will be no toggle
They hide this toggle in poco phone but dark mode is still supported
For my case I don't change between modes
It will happen only once

Pavamarea said:
Works great! MIUI 10 Beta 9.6.27, locked bootloader.
Thank you very much!!
Click to expand...
Click to collapse
I am happy that it worked ???

Worked on Pocophone F1
Worked on Pocophone F1 (MIUI Global 10.3.7)
You are the BEST....I had this issue where I couldn't change to system mode (after plugin in the android car it changed to dark mode and won't come back to the default)....
I've tried a lot of stuff to change it back to default and nothing worked...
Now it worked thanks to you!!!
Regards,
Vinicius

that's what I'm getting even after setting the theme to classic mode.

Nfury00701 said:
that's what I'm getting even after setting the theme to classic mode.
Click to expand...
Click to collapse
You must activate developer options (security) for it to work.
I got the same issue that you before enable that option.
Regards,

vmantovani said:
You must activate developer options (security) for it to work.
I got the same issue that you before enable that option.
Regards,
Click to expand...
Click to collapse
the developer option is ON and it still showing this

There's another option below the developer options, Developer Options (Security Settings). You have to enable that. MIUI will ask if you want to enable it, just wait for 5 seconds and tap yes, and you're good to go.