Related
I would firstly like to apologise in advance to all the members in here that are gurus. (I get paranoid when it comes to things that I describe bellow)
So I have just bought and received my mi4c, but as I am sure a great deal of people in this forum, I am experiencing certain things I do not like. What am I referring to you may ask? Primarily the massive amount of Chinese bloatware + unstable google services.
I have done a bit of my homework but I got stuck and came here. So here is the list of things that I am trying to do:
Install international rom (http://xiaomi.eu/community/threads/5-10-8.28692/) for gapps and removal of bloat
root
custom recovery (twrp)
So here is the challenge.. I do not know in what order to do them. I also found this thread here (http://forum.xda-developers.com/mi-4c/development/flash-twrp-using-flashify-app-pc-dev-rom-t3230355) which is basically root + recovery but it asks you to use a developer rom, wouldn't that be pointless if I am going to flash the international one?
Can someone please point me in the correct direction
Thanks in advance.
The rom from xiaomi.eu has to be flashed with TWRP - so you have two choices:
1. boot or flash TWRP via fastboot and after that flash the Rom from Xiaomi.eu
or if you do not want to mess with drivers and computer and fastboot:
2. use the built in updater app to change to the chinese/english stock developer! rom found here (dev version has root built in) - after that flash TWRP via an app like flashify (play store) - flash Xiaomi.eu within TWRP
i chose the 1. Variant and did only BOOT TWRP (fastboot boot .....) and did not permanently flash it at this time - so i could make a nandroid backup of the complete stock ROM - including the stock recovery first ! If you go this way too - do a backup of the ESF partition too because this one contains your IMEI and MAC Adress infos - can help to have this backup in the hand if something fails. If you have an OTG cable you can directly backup to an external USB Stick (must be FAT32 formatted !). I found this was the best solution for me before permanently flashing any other ROM.
Be aware that if you boot TWRP (temporarily or permanent flashed version) the touch sometimes simply does not work (in a few cases the power button did not work too). Solution: wait two or three minutes until the touch begins to work.... i used the TWRP (DEV Variant of the recovery) found here. Because the touch begins to work a little faster (sometimes it works instant).
since the last 2 weeks i stick with the sMIUI ROM (its a "slimmed" Xiaomi.eu ROM) you can cook your individual slimmed variant here. And you can read a little about it here.
Hope this helps you....
Andiii said:
The rom from xiaomi.eu has to be flashed with TWRP - so you have two choices:
1. boot or flash TWRP via fastboot and after that flash the Rom from Xiaomi.eu
or if you do not want to mess with drivers and computer and fastboot:
2. use the built in updater app to change to the chinese/english stock developer! rom found here (dev version has root built in) - after that flash TWRP via an app like flashify (play store) - flash Xiaomi.eu within TWRP
i chose the 1. Variant and did only BOOT TWRP (fastboot boot .....) and did not permanently flash it at this time - so i could make a nandroid backup of the complete stock ROM - including the stock recovery first ! If you go this way too - do a backup of the ESF partition too because this one contains your IMEI and MAC Adress infos - can help to have this backup in the hand if something fails. If you have an OTG cable you can directly backup to an external USB Stick (must be FAT32 formatted !). I found this was the best solution for me before permanently flashing any other ROM.
Be aware that if you boot TWRP (temporarily or permanent flashed version) the touch sometimes simply does not work (in a few cases the power button did not work too). Solution: wait two or three minutes until the touch begins to work.... i used the TWRP (DEV Variant of the recovery) found here. Because the touch begins to work a little faster (sometimes it works instant).
since the last 2 weeks i stick with the sMIUI ROM (its a "slimmed" Xiaomi.eu ROM) you can cook your individual slimmed variant here. And you can read a little about it here.
Hope this helps you....
Click to expand...
Click to collapse
Thank you for your response just 1 thing I do not understand, is there a difference between the developer rom and the international 1 I mentioned? and when you say I can flash it using the the updater app to flash the dev rom (it sounds easier to me + safer) do you know how to do this? (is it this : "You can also use Mi PC Suite to flash the ROM "?)
YES the Rom you posted is a "Custom Rom" and is not officially (Xiaomi). Thats why the website says:
Unofficial International MIUI / Xiaomi Phone Support
the original (official) Xiaomi Rom - Stable and Developer - for Mi4c is only available in Chinese and english language and is translated by the community Xiaomi.eu and optimized (removed chinese apps that wouldn't work for you anyway)
How to install stock android 6.0 on Mi 4c?
I am getting an Mi4c, straight from China, but don't want the heavy MIUI lagging the performance. I would like to intstall the stock android. How can I do it? Also :-
1. Will the edge tap and other features work outside of MIUI?
2. Will Google play services be installed alongwith the stock android ROM?
I'm newbie to the rooting scene......please be little comprehensive in explanation :angel:
Cheers!!
drevankar said:
I am getting an Mi4c, straight from China, but don't want the heavy MIUI lagging the performance. I would like to intstall the stock android. How can I do it? Also :-
1. Will the edge tap and other features work outside of MIUI?
2. Will Google play services be installed alongwith the stock android ROM?
I'm newbie to the rooting scene......please be little comprehensive in explanation :angel:
Cheers!!
Click to expand...
Click to collapse
As far as i know there's no announcement for android marshmallow update for the Mi4c yet. Neither for Miui nor for CyanogenMod (CM).
... I guess CM is what you meant with "stock android".
There's just an unofficial build for CM and I guess as long it's not official there won't be edge tap support for the device.
And you have to flash google apps by yourself.
The reseller ROM they ship with 77.00.44 is total trash. I chose to keep the Chinese dev ROM as there are several Mi apps I like to use in conjunction with Gapps. It is playing very nice with my battery now.
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
shatheone said:
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
Click to expand...
Click to collapse
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
timba123 said:
Did you figure it out
Click to expand...
Click to collapse
yea
wait that wasn't a question for me...lol
TWRP is not required in order to root the MaxWest Nitro 5P. In fact, you could not root it using TWRP even if you wanted to. This device ships with Android 9 Pie Go Edition and is fully Project Treble supported. Also, like many devices of its kind with a System-as-Root (SAR) configuration, this phone has no boot-ramdisk. The only workaround to attain root is to patch the ramdisk in the recovery image and flash the patched image to /recovery versus the typical /boot partition. This effectively enables Magisk to hijack the recovery partition. Thus, the tricky part. In order for root to be properly installed, the phone must manually be booted to recovery mode during each and every reboot. However, it won't actually boot into recovery mode due to Magisk hijacking the /recovery partition. It will boot into the Android OS with Magisk systemless root installed. If you choose to boot the phone normal, it will still boot into Android, but without Magisk installed. This is rather unorthodox and inconvenient but it remains the only solution for these devices with no boot-ramdisk. For more info on Magisk running in recovery, see the official GitHub documentation here: https://topjohnwu.github.io/Magisk/install.html
TWRP is not compatible with this type of install and will cause a bricked device. Simply unlock the bootloader, patch the stock recovery image with Magisk, and flash the patched image to the recovery partition via fastboot. Boot to recovery mode during the next and every subsequent reboot. I am presently drafting a rooting guide on this device and I will post my link here when finished, for anybody needing instructions.
The OP of this thread originally requested info on root for purposes of possibly installing a custom ROM. Indeed, there are a few Treble GSI ROMs compatible with the Nitro 5P (ARM, A-Only). However, you do not need to have a rooted OS in order to install GSI custom ROMs, but only an unlocked bootloader. I will compile some resources for compatible GSI Treble ROMs and list this info in my rooting guide coming soon. TWRP isn't needed for GSI installation. Everything can be done in AP Fastboot Mode. I am not certain if MaxWest Telecom has released the kernel source code for the Nitro 5P. I will research this. This code will be required for the compiling of custom ROMs such as LineageOS & Pixel Experience. It is likewise needed for TWRP to be built from source.
No problem. I'm certainly not saying that TWRP cannot be booted or even installed on the Nitro 5P. I'm only stating that under no circumstances can the Nitro 5P (in its stock configuration, at least) be rooted using TWRP. The only root solution -- due to the boot image being devoid of a ramdisk -- is the method I outlined above. Now, if someone compiled a custom boot image with integrated ramdisk, this would certainly change matters. Out of curiosity, have you tried flashing TWRP to the /recovery partition using fastboot flash recovery twrp.img? Or, in the alternative, you can replace the stock recovery image with TWRP by decompiling the .pac firmware package, repack the .pac archive, and flash TWRP using the Spreadtrum Flash Tool. I'm just curious as to whether anybody has tried that.
timba123 said:
I finally got a decent laptop. Windows 10. I'd love to root this nitro 5p. IDC if it's superuser or magisk root. I could take or leave twrp.
Click to expand...
Click to collapse
Magisk is the only supported root solution for this devices
Installation
The Magic Mask for Android
topjohnwu.github.io
Scroll down until you reach the installation heading titled "Magisk in Recovery." Follow those steps and you will attain root on your Nitro 5p. In a nutshell, you will be patching a stock recovery image versus a stock boot image. Magisk will be able to hijack the /recovery partition and enable systemless root on the Android OS.
hellofriendlymanveriosns said:
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
Click to expand...
Click to collapse
Why would you want somebody to PM you in order to get help? This is a custom Android development community. Provide your input openly on the thread so it can benefit all others who need help as well.
hellofriendlymanveriosns said:
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
Click to expand...
Click to collapse
Keep in mind that you rarely ever need to be rooted in order to install a custom ROM. However, you will need a custom recovery and the custom ROM itself. To the best of my knowledge, no custom ROMs have been ported to, or compiled for, the Maxwest Nitro 5p. However, the Nitro 5p is Project Treble supported, meaning you can boot and install a Generic System Image (GSI). There are a nunber of custom GSI ROMs available here on XDA, which have been build by various developers. This is a link to several GSI ROMs built from some of the more popular custom ROMs, i.e. HavocOS, LineageOS, ArrowOS, PixelExperience and others. These are available both with and without GApps, in both 32-bit and 64-bit architectures.
[SUMMARY][PIE GSI] BEST PIE-GSI ROMS to TRY (to this moment)
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in...
forum.xda-developers.com
Also, this is the official Project Treble forum here on XDA. This includes numerous GSI ROMs in various versions, instructional guides, device-specific resources and a ton of general info on Project Treble.
Project Treble
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
forum.xda-developers.com
shatheone said:
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
Click to expand...
Click to collapse
I've tried unlocking the bootloader with no success.
For members having difficulties unlocking the Nitro 5P bootloader, you need to use the Token Identifier method typical to Unisoc (Spreadtrum) devices. There is a comprehensive YouTube guide on the process.
You will need a modified fastboot tools build, A Linux PC (or Windows PC running Ubuntu Live), and ADB Debugging/OEM Unlocking enabled in Developer Options. Links for the files you will need can be found here https://forum.hovatek.com/thread-32287.html
To the best of my knowledge, this is the only viable method for unlocking the bootloader on the Nitro 5p.
timba123 said:
I had trouble originally but a fellow xda member ma
I had trouble but someone here made a token for me. I'm bl unlocked for sure. I'm going to try to magisk root this weekend. The specs are poor on this device (nitro 5p) but is gsi/treble compatible . So I plan on trying that but in the end I'll prob just debloat stock to be as vanilla as I can and also add custom audio.
Click to expand...
Click to collapse
Viper4Android FX with the NEON audio drivers works quite nice on the 5p. A good debloating and some build.prop tweaks to optimize RAM efficiency and responsiveness made a big difference for me. You can also add a line to build.prop to disable the boot animation during boot up, which speeds up boot time considerably. Use Kernel Adiutor-Mod (APK available here on XDA) to enable Touch Boost under CPU settings and change the CPU Governor to Performance. Set I/O scheduler parameters to a 512 KB read-ahead on internal storage, using the noop scheduler preset. Set SELinux to permissive mode as well and use the Low Memory Killer (LMK) preset of Very Aggressive. In the ZRAM options, ensure Swappiness is set to 100.
Keep in mind that when rooting, you will need to install Magisk to run in recovery versus the typical boot.img patching.
I installed LineageOS 18.1 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply
there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
I am still trying to fully wrap my head around Android moving to Slot partitions. I am reading as much as I can and feel I have a better understanding of it but have tried to flash lineageOS with microg but ended up with a bricked device maybe due to not doing the proper steps to switch to the active slot? My question is if I have TWRP installed and currently on OOS 11, can I just flash the zip file for lineage OS or so I need to do something additional? The TWRP script states you have to boot into Recovery to switch active slots and flash additional items. I know if I flash lineage I will end up with their Recovery as well which I obviously dont want. Can I flash the TWRP installer after flashing lineageOS zip or no? Please help confirm or deny what needs to be done given my current setup.
Thank you all in advance for any help/experiences you can share about this.
Hi! Are there any pro’s out there that can help out with some issues, we are having with 3 phones.
It would be greatly appreciated. I believe we are not the only ones.
How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?
All 3 phones manufactured in 2022.
The Bootloader is unlocked for all 3. USB Debugging is turned on.
- Moxee m2160 MH-T6000 only boots to Fastboot & Recovery. I have tried to restore but it will not restore.
- Vortex V22 has a GSI Pixel Experience Plus 13 ROM installed and is unable to go back to factory ROM image.
- ANS ACK2326 is on a stock Android 12 ROM and hasn’t been modified but has a build number kirk2_v1 2.0_BTM-ST.
Is it possible to get a Generic BOOT.IMG to modify for root?
Are there other ROMS like GSI’s with a BOOT.IMG that could work to try to get root?
Are there other ways to get root without a BOOT.IMG?
Is there a way to parse the entire phone to compile a BOOT.IMG?
The manufacturers were contacted. No system firmware ROM is available online that we could find after searching. We don’t have any experience searching china websites or know where to begin. If someone knows where we could find the stock ROM's on a China website that would be a great help!
Are we SOL? Are phones that don’t publish stock firmware that secure that if you need a BOOT.img from stock firmware to get to access the entire encrypted rom, you are out of luck?
Or, would we need a Jtag hardware reader?
Thank you in advance for your time and help which is greatly appreciated!
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
V0latyle said:
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
Click to expand...
Click to collapse
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
defcondoc said:
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Click to expand...
Click to collapse
No, but it is the most popular and arguably the best
defcondoc said:
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
Click to expand...
Click to collapse
No, because again you need root to run adbd as root. I could be wrong...
defcondoc said:
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
Click to expand...
Click to collapse
I am not a developer so I have no idea but I imagine you'd need the original kernel source, yes.
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
kelvinchinedu said:
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
Click to expand...
Click to collapse
I actually had or was going to ask this if there is a way to access firmware from the hardware level. Somehow the post never got posted or deleted.
Anyway, with MTK Client & QFIL, how complicated is it to extract the firmware from a device? Will it work with all devices, or will I run into issues with newer devices? I will do some researching on these and see what I can find. Thank you!
alecxs said:
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
Click to expand...
Click to collapse
Interesting. Where can I get a rooted GSI? I tried to searching but couldn't find anything. Is there a special way to search for one. I would be willing to try this. I had a boot loop on one and a unofficial unrooted PixelExp13 GSi fixed it.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you! I'm assuming these are all GSI builds from LOS 16-20? Am I also correct in saying the difference in the bgN, bvN, bvS, files? b = a/b system, g = gapps installed, v = vanilla - no gapps installed. N = No Root? S = Root?
To get a GSI that is already rooted, I must install the file with S in the filename?
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
defcondoc said:
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
Click to expand...
Click to collapse
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
omb714.1980 said:
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
Click to expand...
Click to collapse
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
defcondoc said:
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
Click to expand...
Click to collapse
I'm having the same issue with the ANS your not alone.
omb714.1980 said:
I'm having the same issue with the ANS your not alone.
Click to expand...
Click to collapse
I appreciate you letting me know. Good to know I'm not the only one.
Did anyone ever figure out how to unlock the bootloader yet?
ronnieshane1 said:
Did anyone ever figure out how to unlock the bootloader yet?
Click to expand...
Click to collapse
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
defcondoc said:
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
Click to expand...
Click to collapse
I know right! I cant find hardly anything on the ACK2326 at all! I wish they would go ahead and make it public already.