Search This Blog

Tuesday 30 January 2018

Xiaomi Mi A1, Kernel Source Officially Released!


Hei Xiaomi Mi A1 Users,

Xiaomi officially releases Kernel Source for its Android One series smartphone, the Mi A1 which was launched September 5, 2017.

With the newly release kernel, developers can further develop and have better control to the ROM thereby making the most of it.


Released Kernel Source:



Installing TWRP 3.2.1-0 on Mi A1 Oreo Version


Hei Mi A1 fans,


What's cooking with your Android One device? This the second volume for my "ifelixit" series. What do say we install TWRP for our beloved device to flash mods or custom ROMs, to discover and get more customization of your choice. Let's have some fun here for the upcoming Lunar New Year holiday season. 



TWRP 3.2.1-0 is out now for Mi A1
What's new in 3.2.1-1:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Alright, how do we go about doing it. For a quick understanding, as we all know Mi A1 comes with an A/B partition and how it's different. A/B devices have duplicates of many partitions on the device. An A/B device has 2x system partitions, 2x boot partitions, 2x vendor partitions, 2x modem / firmware partitions, etc. Only one slot is in use at a time. During early boot, the first stages of the bootloader read some small amount of data called the BCB or Bootloader Control Block and decide whether to boot the A partitions or the B partitions. When an OTA update is available, the data from the active slot is copied from the inactive slot and patched / updated. For example, if you're currently on slot A, your device would download the update and copy the existing system partition from slot A and patch / update it with the new updates into slot B. Once the copying and updating is complete, the BCB is updated and the device reboots using slot B. Next time an update is available, the system partition in slot B is copied to slot A and updated, the BCB gets updated, and we reboot to slot A.

Since all known A/B devices do not have a separate recovery partition, you will eventually have to flash TWRP to the boot partition. We then use fastboot boot to temporarily boot TWRP without flashing TWRP and afterwards, flash TWRP zip to both slots.


Requirements:

Essentials:
  • 1. Updated to Oreo Android Version
  • 2. Bootloader Unlocked
  • 3. USB DATA cable (the one that came with your device)
  • 4. Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
  • 4. Enable USB Debugging - Goto Developer options > USB Debugging - Enable (If you have not activated Developer options, then Goto Settings > About phone > tap Build number 3 times > You are now a developer)
  • 5. Enable OEM unlocking - Goto Developer options > OEM unlocking - Enable
  • 6. Battery is charged at least 50%.

Method:
  • Switch Off your Mi A1.
  • Connect your USB cable to the PC/Laptop.
  • Goto the location where you copied the "Working folder".
  • Within the folder press the Shift+Right click your mouse, and select "Open command window here"
  • Enter the following command to enter fastboot mode, as follows:-
    1. adb reboot bootloader
    Copy the Code
  • Or else you can alternatively, Press Power & Volume Down simultanously, to enter Fastboot Mode.
  • Enter the following command to "Unlock your bootloader" if it has not been unlocked, as follows:-
    1. fastboot oem unlock
    Copy the Code
    1. fastboot boot oreo_3.2.2_recovery.img
    Copy the Code

11. It will then boot into TWRP 3.2.1-0, then "Swipe to Allow Modifications", in the TWRP Main menu, choose and tap, Install, goto the Download folder when you have copied from your Working folder on your PC/Laptop earlier, and select twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip and "Swipe to confirm Flash". 

12. Once TWRP is flashed, tap Back twice or Home button to return to the TWRP Main Menu, choose and Tap "Reboot", it will bring you to the Reboot menu, you should be on Current Slot:B, if so, tap Slot B to proceed. 


13. Then, tap back button twice or the Home button to return to the TWRP Main menu, then tap Reboot button, choose and tap Bootloader button, then tap Do Not Install button, it will then go into fastboot mode. 


14. Next, on your PC/Lappie type fastboot boot oreo_3.2.2_recovery.img, that will boot into TWRP 3.2.1-0, then select twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip and "Swipe to confirm Flash", once it flashed, continue and tap Reboot System button, then Swipe to instal TWRP App.


15. It will then reboot to system as shown above. Now you have successfully installed TWRP 3.2.1-0 on your Mi A1.



Credit: TWRPDees_TroyMohanCm


DISCLAIMER: DO ON YOUR OWN RISK. Flashing can potentially bricked or bootloop your device.
"Solving with simplicity"


Image credit: Google

Wish Those Celebrating A Happy Prosperous Lunar New Year!

Friday 26 January 2018

Will RCS Messaging be Embraced Over SMS in the Future? Share Your Thoughts Here!



Hei Mi Fans & MIUI-ers,

What have we here? I went thru the Bug reports and bump into an irrelevant report regarding the trending SMS messaging appearing in the battery usage. So I thought it a good topic to discuss about this week and why it showed up on your phone.

Whether we’re receiving a boarding pass for a flight or chatting with friends and family, SMS (better known as text messaging) is a universal way for us to stay connected. But despite its ubiquity, SMS hasn’t evolved to take advantage of all the features that smartphones enable today. Google believe it’s important to innovate in messaging standards, so they have been working with the mobile industry on an initiative to upgrade SMS through a universal standard called RCS (Rich Communications Services), bringing more enhanced features to the standard messaging experience on mobile devices.



So what is RCS exactly?
Short for Rich Communication Services (alternatively known as Advanced Messaging), RCS is a next-generation SMS messaging protocol. It allows users to take advantage of a number of features that were previously exclusive to over-the-top messaging apps like WhatsApp and iMessage.

For instance, when messaging a friend or family member, RCS users will see typing indicators and read receipts (it’s possible to turn both these features off in the Android Messages preferences menu). RCS also enables proper group chat, as well as allows users to send high-resolution images and videos.

Moreover, unlike SMS messages, RCS are messages are sent via the user’s data connection or a nearby Wi-Fi link.

Upgrading the default messaging experience for Android.
Google want to make sure that Android users can access all the features that RCS messaging offers, like group chat, high-res photo sharing, read receipts, and more.


So they are working with mobile device manufacturers to make Android Messages the default messaging app for Android devices. Mobile device brands LG, Motorola, Sony, HTC, ZTE, Micromax, HMD Global - Home of Nokia Phones, Archos, BQ, Cherry Mobile, Condor, Fly, General Mobile, Lanix, LeEco, Lava, Kyocera, MyPhone, QMobile, Symphony and Wiko, along with Pixel and Android One devices, will preload Android Messages as the default messaging app on their devices. With these partners, they are upgrading the messaging experience for Android users worldwide and ensuring a consistent and familiar experience for users. We’ll continue to add more partners over time.

Improving business messaging with RCS.
Currently millions of businesses, service providers, and brands use SMS to communicate with their customers, whether they’re sending a bank fraud alert or package delivery notification. But while SMS provides a universal way for consumers to connect with businesses, the messages are limited to just plain text. RCS will upgrade today’s business messaging experience by enabling brands to send more useful and interactive messages.


For example, a message from your airline reminding you to check in for a flight can now take advantage of rich media and interactivity to provide a full check-in experience, complete with boarding pass, visual flight updates, and terminal maps on demand, all directly within the messaging experience.


Businesses can also have a branded messaging experience with information about the business and the ability to share content like images, video clips and gifs.


The future of RCS
“Even though RCS would appear to be a good fit for cell providers, it’s a big variable,” he said. “Companies like Google are making a push and drawing more attention to it, but a lot of carriers are wary of partnering with a third party. RCS is a new revenue opportunity for carriers, and the truth is that if they don’t do something, apps like WeChat, Facebook Messenger, and Line will get deeper and deeper entrenched.”

What do you think, "Will RCS messaging be embraced over SMS in the future?"

Wednesday 24 January 2018

Rooting your Mi A1 for Oreo Android Version



Greeting Mi A1 fans...

What's new and how is going for the 2018? Wishing everyone a great year ahead and this is my first article for 2018. What is rooting? Rooting is the process of allowing the user to attain privileged control (known as root access) over various Android subsystems.

Good news is Mi A1 is getting an Android 8.0 upgrade, on the other hand most users will find the previous method of installing TWRP is no longer working on Android 8.0 ROM. No worries, for those still insisting on Rooting their devices, here is the old-school method of getting Root Permission, while stay tuned for installing TWRP on my next series.

Let's get going. Read this Guide a couple of times and get a grasp of it, and if you still feel doubtful or find it too difficult, its just not meant for you, as this is meant for an advanced user to fully comprehend the rational of the method.

Requirements:
  • Download Minimal ADB and Fastboot v1.4.2 and install it on your PC/Laptop, preferably on C\:Drive and choose system-wide installation. 
  • Download Magisk Manager v5.5.5 and moved it to your "Download" root directory on your phone for easy access. Install the APK and click Settings when the popped-up balloon appears, and click "OK" to Enable the Unknown sources, and press back to the "Download" folder and click Magisk Manager and click Install.
  • A boot.img from your current ROM Build folder, and moved it to your "Download" root directory on your phone for easy access.
Essentials:
  • Updated to Oreo Android Version
  • Bootloader Unlocked
  • USB DATA cable (the one that came with your device)
  • Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
  • Enable USB Debugging - Goto Developer options > USB Debugging - Enable (If you have not activated Developer options, then Goto Settings > About phone > tap Build number 3 times > You are now a developer)
  • Enable OEM unlocking - Goto Developer options > OEM unlocking - Enable
  • Battery is charged at least 50%.


Methods:
  1. Launch Magisk Manager app.
  2. Then tap "Install" choose Install, then choose "Patch Boot Image File"
  3. It will then create the Patched Boot Image in the Magisk Manager folder and copy it to your PC/Laptop.
  4. Switch Off your Mi A1.
  5. Connect your USB cable to the PC/Laptop.
  6. Goto the location where you copied the "Patched Boot Image".
  7. Within the folder press the Shift+Right click your mouse, and select "Open command window here"
  8. Enter the following commands to enter fastboot mode, as follows:-
  9. adb reboot bootloader
  10. Or you can alternatively, Press Power & Volume Down to enter Fastboot Mode.
  11. To check that your device is connected and detected, enter the following command:-
  12. fastboot devices
  13.  Enter the following command of your current partition:-
  14. fastboot getvar current-slot 
  15. Check the active slot and enter the following command accordingly as "a" or "b":-
  16. fastboot flash boot_a patched_boot.img
    Or
    fastboot flash boot_b patched_boot.img
  17. Then to reboot, type the following:-
  18. fastboot reboot
  19. Your device will boot-up in a few minute, then re-install the Magisk Manager apk again and you will attain the Root permission with the patched boot image.
  20. Enjoy, now your device is rooted.

DISCLAIMER: DO ON YOUR OWN RISK. Flashing can potentially bricked or bootloop your device.

"Solving with simplicity"

RedWolf TWRP, Root Support Incremental OTA - Redmi 3S/X

Hei Redmi 3S/Prime/3X fans, What have we here today? After fiddling around with your Redmi 3S and getting comfortable with it, you ...