Database Develop

Xiaomi Mi5 Prime .RAW and FAKE ROM removing

Hello, I own Xiaomi Mi5 Prime, is it possible to make it capture images in .RAW format, if yes, whats the way? Thanks!

pi4a7a said:
Hello, I own Xiaomi Mi5 Prime, is it possible to make it capture images in .RAW format, if yes, whats the way? Thanks!
Click to expand...
Click to collapse
Try some 3rd part app like Footej Camera (should be free to check if RAW is available) or other camera apps like (manual camera, proshot etc.) to see if it has RAW support.
RAW option is available in Footej Camera in My Mi5 prime with RR rom. The last MIUI version (Xiaomi.eu version) that I checked also passed the manual camera compatibility test which should mean that rom will support RAW too and have camera2 api enabled. Newer Global rom probably have camera2 api enabled too.
LineageOS also have camera2 api and RAW support (most probably).

JRC1995 said:
Try some 3rd part app like Footej Camera (should be free to check if RAW is available) or other camera apps like (manual camera, proshot etc.) to see if it has RAW support.
RAW option is available in Footej Camera in My Mi5 prime with RR rom. The last MIUI version (Xiaomi.eu version) that I checked also passed the manual camera compatibility test which should mean that rom will support RAW too and have camera2 api enabled. Newer Global rom probably have camera2 api enabled too.
LineageOS also have camera2 api and RAW support (most probably).
Click to expand...
Click to collapse
Im using MIUI Global 7.2.8.0.0(MAACNBD) | Stable ROM
My Mi5P doesn't pass the Manual camera compatibility test... aaannnd there is no option in Footej Camera for raw just the quality of the JPEG.
Which MIUI rom should I flash for RAW support?
Also I want to ask about the updater app, looks like it can't connect with network its version 3.0.0 is there update or something ?
Thanks.

pi4a7a said:
Im using MIUI Global 7.2.8.0.0(MAACNBD) | Stable ROM
My Mi5P doesn't pass the Manual camera compatibility test... aaannnd there is no option in Footej Camera for raw just the quality of the JPEG.
Which MIUI rom should I flash for RAW support?
Also I want to ask about the updater app, looks like it can't connect with network its version 3.0.0 is there update or something ?
Thanks.
Click to expand...
Click to collapse
Firstly you seem to be having a very old global rom. So you may need to update it.
If you click the the dots in footej camera you will get options like grid, white balance, single photo etc in the viewfinder.
If you click the single photo option you will get options for HDR, RAW, Burst mode.....
But I doubt you will get RAW support without the camera 2 api enabled (if it is enabled footej camera should also 'show' shutter speed and ISO in viewfinder by default.
But other than the camera thing, I have another major concern for your rom.
I am not sure, but I suspect that you have a 'fake ROM' or 'vendor ROM'.
"h t t p: //xiaomit ips.com/guide/how-to-spot-fake-miui-rom-on-your-phone/" (can't post links yet. Remove quotes and spaces to use the link)
You have more than 4 digits for the version apparently.
It is advisable to get rid of the fake rom as soon as possible....generally they are full of bugs..and may even have adwares and malwares with worse performace. And yes having a fake rom is probably the reason why you have no OTA yet....(not a network problem but a rom problem). Do your research and if you can confirm you are having a fake rom getting rid of it should be your first priority.
I was lucky to have a official global rom from the start, so I can't advise you on how to get rid of it from my own experience.
However I had this link bookmarked as I was expecting I will recieve a fake rom:
"h t t p : //en. miui .com/thread-309122-1-1.html" (can't post links yet. Remove quotes and spaces to use the link)
It seems to list some possible ways to remove the fake rom from least risky to most risky method. Most risky method should still be fine if you are flashing the proper rom, I guess.
EDL is often the recommended method for totally getting rid of it...but after a certain version Xiaomi blocked EDL or something.
Assuming your bootloader is locked, you can request for Mi unlock by explaining your situation and then fastboot flash your rom with the latest global beta (or stable) or you may be able to put twrp and flash Xiaomi.eu version of the rom (which is a bloatfree translated chinese version of miui....which is quite stable..)

JRC1995 said:
Firstly you seem to be having a very old global rom. So you may need to update it.
If you click the the dots in footej camera you will get options like grid, white balance, single photo etc in the viewfinder.
If you click the single photo option you will get options for HDR, RAW, Burst mode.....
But I doubt you will get RAW support without the camera 2 api enabled (if it is enabled footej camera should also 'show' shutter speed and ISO in viewfinder by default.
But other than the camera thing, I have another major concern for your rom.
I am not sure, but I suspect that you have a 'fake ROM' or 'vendor ROM'.
"h t t p: //xiaomit ips.com/guide/how-to-spot-fake-miui-rom-on-your-phone/" (can't post links yet. Remove quotes and spaces to use the link)
You have more than 4 digits for the version apparently.
It is advisable to get rid of the fake rom as soon as possible....generally they are full of bugs..and may even have adwares and malwares with worse performace. And yes having a fake rom is probably the reason why you have no OTA yet....(not a network problem but a rom problem). Do your research and if you can confirm you are having a fake rom getting rid of it should be your first priority.
I was lucky to have a official global rom from the start, so I can't advise you on how to get rid of it from my own experience.
However I had this link bookmarked as I was expecting I will recieve a fake rom:
"h t t p : //en. miui .com/thread-309122-1-1.html" (can't post links yet. Remove quotes and spaces to use the link)
It seems to list some possible ways to remove the fake rom from least risky to most risky method. Most risky method should still be fine if you are flashing the proper rom, I guess.
EDL is often the recommended method for totally getting rid of it...but after a certain version Xiaomi blocked EDL or something.
Assuming your bootloader is locked, you can request for Mi unlock by explaining your situation and then fastboot flash your rom with the latest global beta (or stable) or you may be able to put twrp and flash Xiaomi.eu version of the rom (which is a bloatfree translated chinese version of miui....which is quite stable..)
Click to expand...
Click to collapse
Whoa.. I didn't know that.. looks like mine is fake....
They say "Please note that the new MIUI versions (7.3.X.X and above) today already blocking this method (EDL), but if you have the old version you can use it."
Mine is 7.2 so I guess it's not locked right ?
Can you provide me the best step by step tutorial how to completely remove that fake stuff and install a brand new global stable MIUI rom ?
EDL
Thanks

pi4a7a said:
Whoa.. I didn't know that.. looks like mine is fake....
Can you provide me a step by step tutorial how to completely remove that fake stuff and install a brand new global stable MIUI rom ?
Thanks
Click to expand...
Click to collapse
Follow the 2nd link : "http://en.miui.com/thread-309122-1-1.html"
They have done a good job arranging the possible options along with links to other threads and tutorials necessary for this process.
Sorry, I am not too experienced myself regarding removal of a fake rom. I can help you with specific things like how to unlock bootloader or stuffs but totally getting rid of fake rom can be a complex process and many options and method may be needed to be tried.
First just try to do the simplest possible thing:
0) Backup all data if you need to. Pics, contacts stuffs....
1) Go to miui forum and download the latest China Dev Recovery rom. (It should have english language as an option but no
gapps). ("http://en.miui.com/download-299.html#435") (you may also try the Global beta\stable roms)
2) Rename the downloaded rom to "update.zip" and put it in your phone.
3) Open updater app. Go to menu (three dots or something...) ->choose update package -> then choose the update.zip.
4) The app should try to verify the package and update to it.
5) If update is successfully done check about and see if the version number looks real.
If you happen to have successful then you have removed the fake rom. At this stage you may already have RAW support and more. But if you used the China Dev Rom, you may want to use the Global rom or custom roms for which you have to unlock bootloader. If you have somehow successfully updated to the official global beta\stable rom and don't want to root or try custom rom then no need to do anything.
Note you may first try the above steps using the latest global dev\stable rom and then if it fails, next try to us china dev\stable rom. I think there is a higher chance for china dev\stable rom to work successfully because fake roms are usually based on the china rom.
To unlock bootloader.
1) Make sure you have an MI account at miui forum...and also you must sign in with the same account in your phone. Your account and device should be connected. ALso make sure your MI\MIUI account has proper details like Name, Phone Number etc.
(Also it's better if you keep your name free of spaces).
2) Unlock developer mode. Search google on how to unlock developer settings in miui if you need to.
3) Go to developer settings (probably it will appear inside additional settings)> enable usb debugging and other usb related settings)
4) Enable "allow OEM bootloader unlock" (may not be exactly written like that, currently not in miui so I can't mention the option in exact terms) if the option is there.
5) I think in developer settings there was an option to check lock status of phone....and inside the option there is a button to associate the phone with mi account..do it. (may not be necessary, but just to be safe).
6) Then apply for unlock permission here: http://en.miui.com/unlock/
Note: Your name should be without spaces while filling up.
If you encounter warnings in chinese , use google translate or something. I was warned in chinese about my image verfiication
captcha error.
There you have to explain why you need to unlock bootloader. Clearly explain your need regarding why (it may be because you are still stuck in fake rom and you want to remove it or if you are already in official china rom you can explain that you want to shift to global rom).
7) Wait for the msg. They (Xiaomi) should message to your phone (the no. which is registered to your mi account) regarding if they have accepted your request and granted you unlock permission. After that they will provide the link to download the unlock tool and a code.
8) Connect your phone to computer after entering fastboot mode (power off your phone then hold volumn down+power button until you see the fastboot screen). Then just use the mi unlock tool that you will recieve and follow the instructions to unlock the phone. (for more details you may google on how to use mi unlock tool to unlock bootloader or something).
Once you have unlocked bootloader:
You can have several options. You may shift to global dev rom (download the fastboot rom for your device and use the mi flashing tool. "http://en.miui.com/a-234.html". Google for more details)
NOTE: Be careful following this steps. I won't be responsible if your device is bricked. I may have overlooked certain things so consider my instructions merely as a summary. Do check the links for details. Also even if the miui thread about unlocking bootloader suggest one to use china dev rom for unlocking, I have unlocked my bootloader from global beta rom and global stable rom may work too.
You may install twrp and then flash Xiaomi.eu (China versions of MIUI made bloatfree with more languages and necessary gapps like google play store and services) or you can try custom roms like Resurrection Remix, Lineage OS etc. All of them should have camera 2 api support, at least.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
pi4a7a said:
Whoa.. I didn't know that.. looks like mine is fake....
They say "Please note that the new MIUI versions (7.3.X.X and above) today already blocking this method (EDL), but if you have the old version you can use it."
Mine is 7.2 so I guess it's not locked right ?
Can you provide me the best step by step tutorial how to completely remove that fake stuff and install a brand new global stable MIUI rom ?
EDL
Thanks
Click to expand...
Click to collapse
Apparently yes, you might be able to attempt EDL. However, I have no experience in that regards. You have to google it.

JRC1995 said:
Follow the 2nd link : "http://en.miui.com/thread-309122-1-1.html"
They have done a good job arranging the possible options along with links to other threads and tutorials necessary for this process.
Sorry, I am not too experienced myself regarding removal of a fake rom. I can help you with specific things like how to unlock bootloader or stuffs but totally getting rid of fake rom can be a complex process and many options and method may be needed to be tried.
First just try to do the simplest possible thing:
0) Backup all data if you need to. Pics, contacts stuffs....
1) Go to miui forum and download the latest China Dev Recovery rom. (It should have english language as an option but no
gapps). ("http://en.miui.com/download-299.html#435") (you may also try the Global beta\stable roms)
2) Rename the downloaded rom to "update.zip" and put it in your phone.
3) Open updater app. Go to menu (three dots or something...) ->choose update package -> then choose the update.zip.
4) The app should try to verify the package and update to it.
5) If update is successfully done check about and see if the version number looks real.
If you happen to have successful then you have removed the fake rom. At this stage you may already have RAW support and more. But if you used the China Dev Rom, you may want to use the Global rom or custom roms for which you have to unlock bootloader. If you have somehow successfully updated to the official global beta\stable rom and don't want to root or try custom rom then no need to do anything.
Note you may first try the above steps using the latest global dev\stable rom and then if it fails, next try to us china dev\stable rom. I think there is a higher chance for china dev\stable rom to work successfully because fake roms are usually based on the china rom.
To unlock bootloader.
1) Make sure you have an MI account at miui forum...and also you must sign in with the same account in your phone. Your account and device should be connected. ALso make sure your MI\MIUI account has proper details like Name, Phone Number etc.
(Also it's better if you keep your name free of spaces).
2) Unlock developer mode. Search google on how to unlock developer settings in miui if you need to.
3) Go to developer settings (probably it will appear inside additional settings)> enable usb debugging and other usb related settings)
4) Enable "allow OEM bootloader unlock" (may not be exactly written like that, currently not in miui so I can't mention the option in exact terms) if the option is there.
5) I think in developer settings there was an option to check lock status of phone....and inside the option there is a button to associate the phone with mi account..do it. (may not be necessary, but just to be safe).
6) Then apply for unlock permission here: http://en.miui.com/unlock/
Note: Your name should be without spaces while filling up.
If you encounter warnings in chinese , use google translate or something. I was warned in chinese about my image verfiication
captcha error.
There you have to explain why you need to unlock bootloader. Clearly explain your need regarding why (it may be because you are still stuck in fake rom and you want to remove it or if you are already in official china rom you can explain that you want to shift to global rom).
7) Wait for the msg. They (Xiaomi) should message to your phone (the no. which is registered to your mi account) regarding if they have accepted your request and granted you unlock permission. After that they will provide the link to download the unlock tool and a code.
8) Connect your phone to computer after entering fastboot mode (power off your phone then hold volumn down+power button until you see the fastboot screen). Then just use the mi unlock tool that you will recieve and follow the instructions to unlock the phone. (for more details you may google on how to use mi unlock tool to unlock bootloader or something).
Once you have unlocked bootloader:
You can have several options. You may shift to global dev rom (download the fastboot rom for your device and use the mi flashing tool. "http://en.miui.com/a-234.html". Google for more details)
NOTE: Be careful following this steps. I won't be responsible if your device is bricked. I may have overlooked certain things so consider my instructions merely as a summary. Do check the links for details. Also even if the miui thread about unlocking bootloader suggest one to use china dev rom for unlocking, I have unlocked my bootloader from global beta rom and global stable rom may work too.
You may install twrp and then flash Xiaomi.eu (China versions of MIUI made bloatfree with more languages and necessary gapps like google play store and services) or you can try custom roms like Resurrection Remix, Lineage OS etc. All of them should have camera 2 api support, at least.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
Apparently yes, you might be able to attempt EDL. However, I have no experience in that regards. You have to google it.
Click to expand...
Click to collapse
I downloaded Version: V8.1.4.0.MAAMIDI (MIUI8) Global Stable ROM from their site
Did as you said with the Updater app, now all I see is black screen with white circle spinning from about 5 minutes.
In case this method bricks my device what should I do?
Edit: It's booting now..
Edit2: Nothing really happened, just drained my battery with 4%. Everything is still the same...

What exactly did happen?
IIRC the updater app first verify the package and then tries to update.
Was the verification successful?
Did it directly went to the black screen in one go?
Also you may wait for at least 10-20 minutes.
I am not really experienced in this method...I only suggested as it was written in the link.
I don't think it's exactly bricked, the white circle means something is going on......if the updater successfully updated first boot should take some time.
In case of brick., I am not sure what to do with a locked bootloader. You will probably be able to still go to fastboot (holding volume down + power button)....but not exactly sure what after that. May be you will need an engineering cable. May be make a thread here or search google regard what to do when mi 5 bricked with locked bootloader.
Here's a thread where an user bricked his phone while bootloader is locked: http://en.miui.com/thread-474717-1-1.html
Hopefully the solution given in the reply should work: http://en.miui.com/thread-298885-1-1.html

JRC1995 said:
What exactly did happen?
IIRC the updater app first verify the package and then tries to update.
Was the verification successful?
Did it directly went to the black screen in one go?
Also you may wait for at least 10-20 minutes.
I am not really experienced in this method...I only suggested as it was written in the link.
I don't think it's exactly bricked, the white circle means something is going on......if the updater successfully updated first boot should take some time.
Click to expand...
Click to collapse
The Updater verificated the package and then it ask me am I sure, etc. and I agreed then the circle for 10 min. then restarted, and nothing changed...

pi4a7a said:
Edit: It's booting now..
Edit2: Nothing really happened, just drained my battery with 4%. Everything is still the same...
Click to expand...
Click to collapse
So still the vendor rom?
I guess you can try china dev recovery rom next.
Or other methods. May be start by unlocking bootloader (may have to wait 3-10 days to get permission and in the end they may even deny permission for some reason) or you may take the risk and try EDL searching google for guide.

JRC1995 said:
So still the vendor rom?
I guess you can try china dev recovery rom next.
Or other methods. May be start by unlocking bootloader (may have to wait 3-10 days to get permission and in the end they may even deny permission for some reason) or you may take the risk and try EDL searching google for guide.
Click to expand...
Click to collapse
Yup...
I will try the China rom but wasn't this rom without Google Play store and Google Services, how can I get them without unlocking bootloader?
If this fails I will try Option Two... Or I will try it directly

pi4a7a said:
Yup...
I will try the China rom but wasn't this rom without Google Play store and Google Services, how can I get them without unlocking bootloader?
If this fails I will try Option Two... Or I will try it directly
Click to expand...
Click to collapse
Here's a relevant thread (check the whole discussion, and decide how you wanna do it): https://forum.xda-developers.com/mi-5/themes/play-store-mi5-chinese-dev-miui-8-rom-t3578236
Apparently this is usually the suggested way to install gapps in china rom: http://en.miui.com/thread-299317-1-1.html

JRC1995 said:
Here's a relevant thread (check the whole discussion, and decide how you wanna do it): https://forum.xda-developers.com/mi-5/themes/play-store-mi5-chinese-dev-miui-8-rom-t3578236
Apparently this is usually the suggested way to install gapps in china rom: http://en.miui.com/thread-299317-1-1.html
Click to expand...
Click to collapse
Tried China ROM but it couldnt be verified by the Updater...
The Mi tool for PC shows the picture from the first post from this thread http://en.miui.com/thread-309629-1-1.html
I really don't want to unlock the bootloader what should I do..

pi4a7a said:
Tried China ROM but it couldnt be verified by the Updater...
The Mi tool for PC shows the picture from the first post from this thread http://en.miui.com/thread-309629-1-1.html
I really don't want to unlock the bootloader what should I do..
Click to expand...
Click to collapse
For chinese characters you can try google translate phone app to get the gist of what is going on.
Also the thread is quite old, I wonder if the same thing can be done using the English version of MI PC Suite or not. You can try that if the language barrier poses a problem. But I am not sure if there are any reason for which english version shouldn't be used or not.
Even if you unlock bootloader it can be relocked again while flashing the global fastboot rom using mi flash tool if you choose the clean all and lock (or something like that) option.

JRC1995 said:
For chinese characters you can try google translate phone app to get the gist of what is going on.
Also the thread is quite old, I wonder if the same thing can be done using the English version of MI PC Suite or not. You can try that if the language barrier poses a problem. But I am not sure if there are any reason for which english version shouldn't be used or not.
Even if you unlock bootloader it can be relocked again while flashing the global fastboot rom using mi flash tool if you choose the clean all and lock (or something like that) option.
Click to expand...
Click to collapse
I just don't want to go through the unlocking process and requesting and stuff...
I give up...

UPDATE!
I just coudn't sleep all night because of that...
So I followed so many guides and nothing worked, then I discovered this one - http://en.miui.com/thread-293457-1-1.html
Everything went fine, now my phone is going through first boot up so im waiting, Ill update is with more details when I got results.
EDIT: The device got bricked... I went through the procces again and this time the PC Suite (English version) found a newer ROM and installed it, it said procces failed or something like that, the device turned on and it was with the new 8.2 china rom, all information was on the phone, everything is good now, Thanks for all the help
Suggesting all to you guys with Fake Mi rom, remove it!

pi4a7a said:
UPDATE!
I just coudn't sleep all night because of that...
So I followed so many guides and nothing worked, then I discovered this one - http://en.miui.com/thread-293457-1-1.html
Everything went fine, now my phone is going through first boot up so im waiting, Ill update is with more details when I got results.
EDIT: The device got bricked... I went through the procces again and this time the PC Suite (English version) found a newer ROM and installed it, it said procces failed or something like that, the device turned on and it was with the new 8.2 china rom, all information was on the phone, everything is good now, Thanks for all the help
Suggesting all to you guys with Fake Mi rom, remove it!
Click to expand...
Click to collapse
I don't know what happened, but it's all's well when the end is well, I guess.
It sounds like you went through a messy processes, some bugs may appear as a result....if you experience strange graphical bugs or something you might consider full wipe flashing but if there is no major bugs (though there are some bugs that are part of the rom which won't be gone no matter how clean the flash is), things should be alright now if you are on the official version.
I am not sure if camera2 api is enabled by default in 8.2 stable china rom (which is what I am guessing you have now?) but hopefully it is enabled. In miui 8 camera 2 can still be enabled by editing build props even if it is not enabled by default but that will need root which will need bootloader unlocking beforehand......but hopefully latest stable version is enabled by default.
So it seems you are stuck on the china rom...but if you can make gapps work with it, it might not be so bad. I also hear that china roms are more supported and has less bug (3rd party widgets didin't work well in latest global dev but work for me in latest xiaomi.eu based on china rom) and many users said that china rom has better audio output (in headphone or something)...but that may be fixed in latest global rom....well my point is that there can be some pros in staying in china rom too.

JRC1995 said:
I don't know what happened, but it's all's well when the end is well, I guess.
It sounds like you went through a messy processes, some bugs may appear as a result....if you experience strange graphical bugs or something you might consider full wipe flashing but if there is no major bugs (though there are some bugs that are part of the rom which won't be gone no matter how clean the flash is), things should be alright now if you are on the official version.
I am not sure if camera2 api is enabled by default in 8.2 stable china rom (which is what I am guessing you have now?) but hopefully it is enabled. In miui 8 camera 2 can still be enabled by editing build props even if it is not enabled by default but that will need root which will need bootloader unlocking beforehand......but hopefully latest stable version is enabled by default.
So it seems you are stuck on the china rom...but if you can make gapps work with it, it might not be so bad. I also hear that china roms are more supported and has less bug (3rd party widgets didin't work well in latest global dev but work for me in latest xiaomi.eu based on china rom) and many users said that china rom has better audio output (in headphone or something)...but that may be fixed in latest global rom....well my point is that there can be some pros in staying in china rom too.
Click to expand...
Click to collapse
There are no bugs at all. Raw is not supported...
Now I want to swap to Global stable rom, is that posssible ? This is top priority now.
If not, How can I get google play working on this china 8.2 stable?

pi4a7a said:
There are no bugs at all. Raw is not supported...
Now I want to swap to Global stable rom, is that posssible ? This is top priority now.
If not, How can I get google play working on this china 8.2 stable?
Click to expand...
Click to collapse
So it didn't pass the manual camera compatibility test? (Note, RAW is not available in stock camera, it can only be used in some 3rd party camera if camera 2 api is enabled which can be checked using manual camera compatibility test)
I guess, then they implemented this feature in the dev versions. You can probably update to china dev by downloading the latest china dev ota rom and updating it with the updater app after renaming it to update.zip. Or they will probably implement it in the later stable versions which they will release.
Switching to global rom without unlocking bootloader? Now that process is not as straightforward.
Here's a thread about it: http://en.miui.com/thread-299790-1-1.html
But it talks about making\buying an engineering cable.....unlocking bootloader is much less hassle imo and in future all these rom switicng things will be lot easier.......
For installing google apps in china rom, you need google installer or something, I guess. Installing gapps should be the simplest thing that you can try at the moment, I guess. You have to use google installer or something.
http://www.technobuzz.net/install-google-apps-xiaomi-miui-china-rom/
https://xiaomininja.com/2016/09/16/the-complete-guide-to-installing-google-apps-gaaps-on-miui-8/
I gave some links earlier too...I really haven't tried any of these things, google can be your friends in this regards.

JRC1995 said:
So it didn't pass the manual camera compatibility test? (Note, RAW is not available in stock camera, it can only be used in some 3rd party camera if camera 2 api is enabled which can be checked using manual camera compatibility test)
I guess, then they implemented this feature in the dev versions. You can probably update to china dev by downloading the latest china dev ota rom and updating it with the updater app after renaming it to update.zip. Or they will probably implement it in the later stable versions which they will release.
Switching to global rom without unlocking bootloader? Now that process is not as straightforward.
Here's a thread about it: http://en.miui.com/thread-299790-1-1.html
But it talks about making\buying an engineering cable.....unlocking bootloader is much less hassle imo and in future all these rom switicng things will be lot easier.......
For installing google apps in china rom, you need google installer or something, I guess. Installing gapps should be the simplest thing that you can try at the moment, I guess. You have to use google installer or something.
http://www.technobuzz.net/install-google-apps-xiaomi-miui-china-rom/
https://xiaomininja.com/2016/09/16/the-complete-guide-to-installing-google-apps-gaaps-on-miui-8/
I gave some links earlier too...I really haven't tried any of these things, google can be your friends in this regards.
Click to expand...
Click to collapse
So if I unlock my bootloader it will be easy to change to Global Stable right?
I will reques unlock code.
Can you share the process for UB please?
And how to lock it later if its not ok to stay with unlocked..

Searching V405EBW owners for TWRP/ROM tests

Hello everyone
Some might know me from the V30... Also got my hands on a V40 now (which I will also give my best to develop for).
I'm currently searching for people who are capable AND willing to test different things.
With that I mean:
- You know how to take logs (logcat, dmesg)
- You know how to recover from a soft brick (either how to get into TWRP for example, or in really bad cases fastboot or flashing a kdz)
- You know how to follow orders
I currently have a (somewhat decendly) working TWRP build (cant decrypt stock encryption atm).
GSIs are a complicated thing, because of not only vbmeta but also because of our 8.1 vendor (Pie GSIs work, if you remove some sepolicies from their system, Oreo GSIs dont have that issue)
What I would need more people to test for:
- stock decryption
- trying out different ways when something (doesnt) boot (e.g. need to flash magisk for xy to not crash to fastboot)
and so on
After everything is somewhat stable (I had to reflash a kdz today, as somehow nothing, no twrp in either slot, or restored stock rom didnt wanna render anything anymore, even though usb/adb worked just fine)
Also working on LOS for this device btw (but thats far more work in progress)
If you wanna be part of this upbringing, reply here, and I'll message you via PM the details.
PS: Having Telegram would be very beneficial.

I volunteer for this. Happy to see you step up for our forgotten device.

How did you reflash the KDZ?

I`m also interested in testing.

onslaught86 said:
How did you reflash the KDZ?
Click to expand...
Click to collapse
In my case i used LG Bridge, at first it complained that MTP wasnt running, but after clicking a few times ok it was fine with that lol
but i read in another thread that a lgup_cmd is able to flash kdzs to the v40

I think I can participate in the test, I have a V405US ROOT phone。
Please forgive me for my bad English. :）

In +1

Hi, how you rooted LG V40?

Any movement on this?

Evilmonstertruck said:
Any movement on this?
Click to expand...
Click to collapse
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.

SGCMarkus said:
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
Click to expand...
Click to collapse
Any update is a good update. I appreciate all the work your doing. I know it's not easy. Thanks again

I can test out twrp and or ROM! Best regards.

[Q] A Proper Guide for Rom Flashing Our Mi8? Avoiding EDL and Bricking Device

Greetings Folks
For starters I just got Mi8 and am planning to go for Havoc or Pixel Experience there is a Pixel Port too I'll have to try which is best close to stock but with gestures features and full fledged Gcam support
Back to Questions
I have seen many threads where newer folks are victim of their devices getting bricked and paying for fix?
Why isnt there a proper guide thread to avoid these obstacles and spread awareness out ?
I know there are certain partitions you need to backup too e.g efs in case of lost IMEI there was a thread Its hell I have been through it with a Samsung Device,There was a guy who messed up his phone sensor files?
But most of all EDL and Devices getting brick so lets address the elephant in the room
Now My Phone is on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
Rom threads say 9.3
take havoc for example
Help Appreciated thanks

@techyrock
Here is a guide : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Part 1 ( The OP is general info ) Below the first couple of comments have detailed steps for AOSP.
Be extremely careful, unfortunately this community doesn't have a lot of highly active professionals.
So definitely double check any advice that you are given, or that you find. With that being said there are definitely several members that are mature, knowledgeable, friendly and overall fantastic.
If you need help, feel free to ask me anytime, I haven't had a lot of time to use XDA recently. But if I am around, I am always willing to help. At the moment I am going to sleep, but go ahead and read my thread, and I have made some lengthy post that may be helpful as well. You can find those posts by reading my post history. Enjoy.
As long as your account is bound to your device, unbricking is pretty easy with these phones. If you want to avoid a brick, avoid brand new builds, test software etc. Some of the recent issues actually stemmed from the 7.11 china developer rom which had a major issue.
if you want to use Miui with zero ads, and every single feature, then Mi-Globe is pretty great, and solid on a week to week basis.
As far as AOSP, I feel that in my experience that Syberia is practically always highly stable, but it's a little plain compared to some other roms. I also liked Pixel 3, Bootleggers ( Newer version) and Havoc. ( I used Havoc in the beginning of July and loved it, that build is fantastic)
I haven't tried a lot of AOSP roms on this phone yet. So that is all I have

Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.

The War Profiteer said:
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
Click to expand...
Click to collapse
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers

Erpe7 said:
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Click to expand...
Click to collapse
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.

First of all thanks guys for replies wasn't expecting this response
My device is Global Mi8 bootloader is locked for now I still have some hours left I'll be able to unlock it by 26th
miflash_unlock prompted to bind my account from developer option for unlocking,I did so it will be bound to my account and ill be unlocking it for first time I believe i bought it used but previous owner seemed to have know info about ROMs though
I have been using Pixel 2XL twice followed by Nokia 8 so I am much more inclined towards AOSP stock experience the two feature I would love to have from MIUI are the
1)MIUI gestures
2)MIUI Dual Apps (I am aware of Play store alternatives but clash of clans doesnt work as good on them as on dual apps )
I know gestures are on Havoc
guess you guys have been playing around with your mi8 kindly guide me to right directrion what ROMs you guys prefer and why ?
how would you prefer to flash a ROM do I need to back up any partitions ? if so which app should use for it ,Ill surely back up everything via TWRP for sure
also the encryption thingy should I sign out my google account before bootloader unlock and other stuff?
and since I am on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
is it safe to flash havoc ?

tsongming said:
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
Click to expand...
Click to collapse
Thank you for this precious advices ;(
I'll note that!
Sent from my Redmi Note 5 Pro using XDA Labs

Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk

ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
There's a primary bootloader that we consumer know of and there's Qualcomm's Emergency Download Mode bootloader (EDL) , since Mi8 has ARB(Anti Rollback) downgrading the phone gets it bricked to EDL mode requiring EDL authentication to my understanding thats why edl is a thing(since its just emergency bootloader for oems to work with) I have not experienced it personally so I don't know whether it bricks that way or not but ARB and EDL authentication are a thing with Mi8 from what I have read in different threads
Sent from my MI 8 using Tapatalk

ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
EDL is Qualcomm recovery mode, it's the mode that you must be in to restore a hard bricked phone.
As long as you are careful you should never need to worry about EDL. Basically, you place the phone into a mode that the computer is able to recognise port 9008, once that is down you can use 1 of 4 techniques to restore your phone. Unbricking Xiaomi's is actually very easy to do, as long as the device is bound to your account.
The big issue is that unscrupulous Chinese vendors, used their own account to unlock bootloaders of Mi8's and other Xiaomi devices, then installed the Global Miui ROM and then sold the phone as new to unsuspecting western customers and at a lower price than western outlets such as Amazon. These vendors marketed the phones as Ïnternational versions" when they were actually Chinese devices and not the Global version that the customer thought they bought.
When these customer's used programs such as MiFlash to upgrade their phone's their bootloaders were locked and the are unable to log into their Mi Account to restore the phone. Remember the vendors unlocked the phone, so these Mi8's were bound to the vendor and not the final customer. This is the Primary reason why Xiaomi makes us wait to unlock the bootloader. Finally, ARB is potential issue, but it hasn't been implemented yet on Global devices.
So do your research before flashing anything and you should be safe.

How not to Brick Mi 8

Dear all experienced folks,
Can uou please tell me the point which i should avoid to Bricking My MI 8?

Just follow the guides step by step, but verify before comments

Dont flash experimental roms.
Dont flash roms made by rom automation program. Such as Mokee.
Don't flash roms from people who don't own the same device, and therefore cannot test it themselves.
Don't get impatient and restart the phone if a rom is taking longer than expected to install.
Don't bother installing GSI roms, they don't work well anyway.
Dont flash roms from other devices.
Don't feel obliged to flash every single update that is released. Especially when your device is already highly stable, wait to hear feedback from others.
prior to flashing AOSP roms.
Make a FULL TWRP backup of your stock installation. Keep this backup on your desktop and worst case you have a fast path to restoring your phone.
Do your homework and take notes, if you mess and brick your device, in the end , it's your fault.
Finally just because is bricked doesn't necessarily mean that the phone is unrecoverable. I have hard bricked my Mi8 about 3 times this year and fixed it everytime.
If you do, brick your phone

* So basically i can flash Global Stock [V11.0.6.0.PEAMIXM] via TWRP without bricking my phone?
* I have heard it bricks our phone if we downgrade [Flash anything below V11.0.6.0], right?
Frankly speaking i dont see any need of downgrading stock to a previous version...!
tsongming said:
Finally just because is bricked doesn't necessarily mean that the phone is unrecoverable. I have hard bricked my Mi8 about 3 times this year and fixed it everytime.
If you do, brick your phone
Click to expand...
Click to collapse
* And may i ask what was the way?

F3AR said:
* So basically i can flash Global Stock [V11.0.6.0.PEAMIXM] via TWRP without bricking my phone?
* I have heard it bricks our phone if we downgrade [Flash anything below V11.0.6.0], right?
Frankly speaking i dont see any need of downgrading stock to a previous version...!
* And may i ask what was the way?
Click to expand...
Click to collapse
Hmmmmm. Mi 8 have no arb set (source xiaomi.eu) always do clean install(format data) while switching rom. It works for me and doesn't break my device.

JonathanFreeze said:
Hmmmmm. Mi 8 have no arb set (source xiaomi.eu) always do clean install(format data) while switching rom. It works for me and doesn't break my device.
Click to expand...
Click to collapse
Formatting Data means Cleaning of Internal Storage... Which is {Quite} problematic
Aren't there any solutions. Like, In my Redmi Note 4 I formatted my Data partition with F2FS file system. That helped me not to wipe my internal storage while switching back and forth with Android 8 and 9.

tsongming said:
Dont flash experimental roms.
Dont flash roms made by rom automation program. Such as Mokee.
Don't flash roms from people who don't own the same device, and therefore cannot test it themselves.
Don't get impatient and restart the phone if a rom is taking longer than expected to install.
Don't bother installing GSI roms, they don't work well anyway.
Dont flash roms from other devices.
Don't feel obliged to flash every single update that is released. Especially when your device is already highly stable, wait to hear feedback from others.
prior to flashing AOSP roms.
Make a FULL TWRP backup of your stock installation. Keep this backup on your desktop and worst case you have a fast path to restoring your phone.
Do your homework and take notes, if you mess and brick your device, in the end , it's your fault.
Finally just because is bricked doesn't necessarily mean that the phone is unrecoverable. I have hard bricked my Mi8 about 3 times this year and fixed it everytime.
If you do, brick your phone
Click to expand...
Click to collapse
Don't know why, but TWRP backup/recovery stopped working on my device some time ago, like 4 months perhaps. I manage to make a backup (default options and partitions) and get a bootloop when try to recover. Used 3 diffferent twrp intotal none of them worked properly. So I ended up recovering using migrate. Not sure why twrp so temperamental though.

So do i need to Clean my Internal Storage (Data) before using Xiaomi.eu?
Currently using HavocOS 3.0 [Android 10], Willing to Flash Xiaomi.eu Miui 11 [Android 10]
Currently using recovery: TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN-wzsx150

F3AR said:
So do i need to Clean my Internal Storage (Data) before using Xiaomi.eu?
Currently using HavocOS 3.0 [Android 10], Willing to Flash Xiaomi.eu Miui 11 [Android 10]
Currently using recovery: TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN-wzsx150
Click to expand...
Click to collapse
If you are not encrypted your data may persist, just be sure to back your files up just in case.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
pabloeldiablo said:
Don't know why, but TWRP backup/recovery stopped working on my device some time ago, like 4 months perhaps. I manage to make a backup (default options and partitions) and get a bootloop when try to recover. Used 3 diffferent twrp intotal none of them worked properly. So I ended up recovering using migrate. Not sure why twrp so temperamental though.
Click to expand...
Click to collapse
Before creating backups, I find that it works best by not using encryption and removing passwords prior to the full backup.Otherwise, you would need to flash the boot image that you were using previously.

tsongming said:
If you are not encrypted your data may persist, just be sure to back your files up just in case.
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
Before creating backups, I find that it works best by not using encryption and removing passwords prior to the full backup.Otherwise, you would need to flash the boot image that you were using previously.
Click to expand...
Click to collapse
I don't have Encryption and I find it best using OrangeFox, the Chinese recovery gives me error 7 while orangefox can flash seamlessly
I have successfully flashed Xiaomi.eu and got back into LineageOS again.
*Each time i downgrade, i format my Data partition to avoid any problem.

F3AR said:
I don't have Encryption and I find it best using OrangeFox, the Chinese recovery gives me error 7 while orangefox can flash seamlessly
I have successfully flashed Xiaomi.eu and got back into LineageOS again.
*Each time i downgrade, i format my Data partition to avoid any problem.
Click to expand...
Click to collapse
Absolutely use what works for you, if you have no issues then I certainly don't blame you for sticking with it.
Personally I prefer the L.R Team version. ( For the long run, months of use, it is absolutely fail safe,)
Edit: For the record, Orange failed on me twice, and became encrypted and unavailable, I could not access recovery or fastboot. But finally resolved using edl.
L.R. Team may require a full clean start and it definitely has some limitations.
Specifically for users whose primary language is not Chinese or English. Also Orange Fox, is definitely much nicer looking and I love its customization options.
But in the long run, and I am sure that the people who have used both extensively would agree the LR Team while not pretty, is extremely stable, and that is what really matter when choosing a recovery.
Plus it is not a blind build, LR Team only build for devices they have on hand.

tsongming said:
Edit: For the record, Orange failed on me twice, and became encrypted and unavailable, I could not access recovery or fastboot. But finally resolved using edl.
Click to expand...
Click to collapse
Have you flashed your Mi 8 in EDL mode? Any special work is needed to flash in edl?

alone_in_dark said:
Have you flashed your Mi 8 in EDL mode? Any special work is needed to flash in edl?
Click to expand...
Click to collapse
I have written about this on various threads...extensively.
I don't have time write now to explain all the steps, also i you ever find yourself in this situation I can attempt fixing it , for a fee. Basically avoid using EDL at all cost, unless you are involuntarily stuck in EDL and have no choice.
My phone was hard bricked and it took a full day to fix. ( mostly because it was the first hard brick with my mi8) The issue with people needing special account privileges is due to those people not having proper credentials. They did not unlock the bootloader themselves,and they don't have a MiCloud account linked to their devices serial number.
However, if the phone is bound to a known account , that is you have the correct credentials then the solution is not terribly difficult. Even if the bootloader is locked: if the phone is bound to your account there is usually no issue with recovering the phone. When the phone is hard bricked, port 9008 is still accessible and the phone can usually be repaired using QPST, MiFlash, or Flashall.bat methods.
If you do not have the credentials then that is a whole different matter:
In that case, you must have the phone restored by an authorized service center. As far as I know, those types of 3rd party repair centers, with EDL privileges are no longer available in western countries.

[TWRP] A8M Ported Moto One 5G Ace TWRP (An Experimental Work In Progress)

Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.

Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.

useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.

Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?

Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!

useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.

Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.

useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.

useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!

@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.

Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..

Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.

PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.

Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.

https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.

fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.

Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.

useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work

Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.

useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.