Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.
It has been a long time since a last rooted my Nexus 5 device. Therefore and for some other reasons i flashed a new custom rom from screw'd android.
The lastest official image of 30th april. So now Android 7.2.1 is working very well on my phone. But how can i simply root my android phone
now?
(In early times i used Nexus Root Toolkit but for some reasons this doesn't work i think with this custom rom..., or im not able to do it..)
Hopefully someone who has still a good overview can give me a short explanation.
thx.
Flash Magisk v12.0 in recovery, or just flash supersu.
7.2.1 lol
lol 7.1.2 -> no i got root, flashing supersu zip file.
one question i got information that a new OTA update by LEAN screw'd is available.
There stand with root i can directly update, but i can not get information if data / app will be lost?
Do you know how this would/should be handled?
I have a rooted phone with a rom that isn't being supported anymore but it actually works great. I just want to update to oreo so is there a rom I can flash from twrp that is already rooted and ready to go? I saw a video of a how to install oreo 8.1 but it's just music playing with someone showing the menu option and no installation instructions.
The OpenKirin ROMs don't work with TWRP. Moreover, TWRP is risky -- it is much easier to recover a phone using the stock EMUI recovery than with TWRP. It is probably better to eliminate TWRP (which will not eliminate your rooting) by flashing the stock ramdisk), then use Magisk if you want to take advantage of root for installation of unapproved apps. I'm not an expert -- this is what I get from reading threads. Now that I'm running OpenKirin (Carbon), I haven't bothered to install Magisk again as I don't need it, but I appreciate that there are things you can do with it.
prestonmcafee said:
The OpenKirin ROMs don't work with TWRP. Moreover, TWRP is risky -- it is much easier to recover a phone using the stock EMUI recovery than with TWRP. It is probably better to eliminate TWRP (which will not eliminate your rooting) by flashing the stock ramdisk), then use Magisk if you want to take advantage of root for installation of unapproved apps. I'm not an expert -- this is what I get from reading threads. Now that I'm running OpenKirin (Carbon), I haven't bothered to install Magisk again as I don't need it, but I appreciate that there are things you can do with it.
Click to expand...
Click to collapse
Last night I installed Oreo from a custom nougat rom. My wifi tether was working before now it isn't so I'll have to figure that out and maybe re root etc.. Is OpenKirin Oreo?
Yes, OpenKirin is Oreo 8.1.0, with security patches in Carbon 3.1 of July 2018. (The OpenKirin site currently has Carbon 2, which has the June patch, but you can get 3.1 from the telegram support group, which is what I'm running. It will show up on the OpenKirin site sooner or later.)
Can I go from stock 8.0 to OpenKirin? Since it doesn't use twrp I'll have to read how to do it.
Edit: Where do I find OpenKirin Carbon? I didn't see it in the rom section here.
jeffrimerman said:
Can I go from stock 8.0 to OpenKirin? Since it doesn't use twrp I'll have to read how to do it.
Edit: Where do I find OpenKirin Carbon? I didn't see it in the rom section here.
Click to expand...
Click to collapse
https://openkirin.net/download/
There are instructions at the site as well as downloads. The current version of Carbon, 3.1, can currently only be reached by going to the telegram group, but I found no bugs in v2.
I already know how to install the unofficail TWRP firmware for my Pixel 4a but it goes back to the custom roms recovery or stock recovery almost every time even after installing ramdisk. What's going on?
Since you are on Android 10, I don't think there will be anymore OTA updates because I think they are only for android 11 at the moment.
To get TWRP to "stick", you probably need to install a custom kernel that has ramdisk built into it as shown in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
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.