Related
Hello,
I have purchased a Mi4c and it has what I am told is a ROM that has had malware/spyware placed on it. It is listed as version 77.00.44.00.
I have downloaded the latest Stable Chinese version of MiUi 7 from the mi site.
If I flash my 4c with this ROM from the PC Manager app will it erase everything and leave me with a clean phone?
I am confused as I read elsewhere that I would need the Fastboot version of the ROM to do that. I have been trying to download it but it is too slow and keeps freezing. Even with the putting of the "o" at the beginning of the link trick.
The phone came with a few apps installed on it I am concerned about:
kkbrowser - DCShare - Clean Master - Search - Magic Photo
I have disabled them but I really want to flash the device and get rid of everything but Stock MiUi 7.
Please, any help would be appreciated.
mishuno said:
Hello,
....
Click to expand...
Click to collapse
Please don't cross post. I've answered your question in the other thread.
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.
Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..
lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.
Ladies and Gentlemen,
It is my pleasure to present the latest stock Oreo 8.1 (Beta) ROM for Xiaomi Mi A1. Up till now, only a handful of testers were able to use the stock beta 8.1
But now, everyone has the opportunity to use it on their device.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I would not be responsible if anything happens to your device. Your warranty will be void after flashing the ROM. You need to go back to stock stable ROM with a locked bootloader for Warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and unzip it.
2. You will see a folder with name as tissot_images_V9.6.2.0.ODHMIFE_8.1
3. Keep it on C drive
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.2.0.ODHMIFE_8.1 and click on "Flash". Make sure you are doing it in a proper way.
10. Wait until you see a "Flash Done" message on the screen. It may take around 5-10 minutes. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with June security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. A lot of newbees have problem at first, especially when flashing rom on MiFlash tool. That's because of selecting and flashing the rom file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
I have been using the ROM for two days and I am yet to find any bugs except ctsProfile shows as false and Google Play Store shows Uncertified.
*For better battery life, you can try Void kernel (Choose the stock version).
ROM Download Link:
https://www.androidfilehost.com/?fid=818222786056041186
Credit:
Xiaomi, 4PDA, @topjohnwu for Magisk, @flex1911 for Void kernel, @CosmicDan & @mohancm for their work on TWRP.
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.
MiFlash Tool
Screenshots will be added shortly.
Screenshots
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
exodius48 said:
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
Click to expand...
Click to collapse
I can confirm battery drain with this rom.
Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
Did xiaomi give you the permission to share it on xda?
muruu said:
Did xiaomi give you the permission to share it on xda?
Click to expand...
Click to collapse
No, this is leaked beta. He just reshare from displax @ 4pda.ru
after sucessfully flashing using miflash it stucks on andriodone
N1ck474 said:
This update is leaked from weeks, why complaining here and now?
We're getting delayed updates cause Xiaomi is far away from Quick updates (MIUI or Stock, still Xiaomi).
Click to expand...
Click to collapse
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
joeniz said:
when unlock bootloader cause erase all information like may update?
Click to expand...
Click to collapse
Why would they remove a security feature they just recently added?
joeniz said:
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
Click to expand...
Click to collapse
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
dback31 said:
Why would they remove a security feature they just recently added?
Click to expand...
Click to collapse
Cause i found no phone that u can't root !!
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
Rowdyy Ronnie said:
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Click to expand...
Click to collapse
What about messenger fb in any rom i use i get animation lag in messenger when message appear things like that and if someone send me message while i using phone the phone animation lag .... Only in fb messenger i found this problem i hate this app .... Anybody have that issue because iam going mad .
Rowdyy Ronnie said:
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
Click to expand...
Click to collapse
If you just share a rom build by someone else, this is the wrong section of the forum to post it.
Too, you say (in op) you have permission from xiaomi to post it here in xda. This sounds unusual. Do you have any proof for this claim?
Thread cleaned.
Thread moved to the guides section where shared ROMs belong. The redirect from development section will expire in 24 hours.
:good:
Rowdyy Ronnie said:
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
hahahah oh wow
the best joke i ever seen
seriously
copyright to leaked build? hahaha i can't stop
Closed beta ROM, so no point in "allowing" you to share it. They could open beta and do it themselves.
I call fake news on that
You share a rom from another forum. Okay. It was already been shared in XDA by the original poster in 4pda.
I call this reposting in the same forum.
You state that the ROM isn't yours and you "share" it with other people on XDA. And then you say reposting is stealing? Didn't you repost it as well? For you is not stealing but for others is?
Conclusion: Are you that desperate for attention?
Is this the official beta rom?
Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
Click to expand...
Click to collapse
How did you manage to get permission from Xiaomi? Have some proofs?
Xiaomi released July security patch a couple of days back. However, as always, a lot of people didn't receive it yet. But the wait is over. Now everyone can update their device to the latest security patch.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I can not be held responsible if anything happens to your device. Your warranty will be void after unlocking the bootloader. You need to lock the bootloader for any warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and extract it.
2. You will see a folder with name as tissot_images_V9.6.4.0.ODHMIFE_20180712.0000.00_8.0_735823083f
3. Double click on the folder and open it. You will see another folder with name as tissot_images_V9.6.4.0.ODHMIFE_8.0
3. Copy the folder into the C drive. Remember, you need to copy tissot_images_V9.6.4.0.ODHMIFE_8.0 and not the main folder.
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.4.0.ODHMIFE_8.0 and click on "Flash". Make sure you are doing it in a proper way.
10. It may take around 10-15 minutes (for me it took around 11 minutes) to get the process completed. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with July security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. All newbies have a problem at first, especially when flashing ROM on MiFlash tool. That's because of selecting and flashing the ROM file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
LED notification stays still when a notification comes in. It doesn't blink.
ROM Download Link:
https://www.androidfilehost.com/?fid=5862345805528051162
Credit:
Xiaomi
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.
Occupied
Reerved
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
barrack1 said:
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
Click to expand...
Click to collapse
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
In his defense. This link is AFH, while still not wonderful, it is usually SOOOO much faster than the damn MIUI links. (at least in my experience)
berezker said:
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
Click to expand...
Click to collapse
Listen, this is the second time I am telling you not to be personal. If you don't like something, report it to the mods. XDA is not your personal property. So, you don't get to judge people here. I checked all the post for July OTA and then I posted it here. The particular post you are talking about, I checked it prior to creatingmine. He didn't have the ROM uploaded when I created my post. It's not my fault that he uploaded the July fastboot ROM without checking mine. I have already asked the mod to check both his and my post to see who uploaded the July fastboot ROM.
barrack1 said:
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
Click to expand...
Click to collapse
Are you sure that post has the July fastboot ROM? I checked his post prior to creating one. He didn't have the ROM uploaded. If you see both my and his post, you can see who edited the post later. It was he who posted the July fastboot ROM later. I have already asked the mod to check both his and mine post to see who uploded the post first. Till then, you may wanna stop being sarcastic.
berezker said:
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
Click to expand...
Click to collapse
And talking about attention and thanks, I am not going to be rich by getting a few thanks. You might have joined XDA for thanks, but I don't find any pleasure or point of getting thanks and attention on a software development community. You should think first before attacking someone. You might have forgotten about the "Report" option, but I didn't.
jareddlikewhoaa said:
In his defense. This link is AFH, while still not wonderful, it is usually SOOOO much faster than the damn MIUI links. (at least in my experience)
Click to expand...
Click to collapse
I checked all XDA post prior to posting mine. XDA gives you an option to check all similar posts while you are creating your post. I went to each post and checked if anyone had uploaded the July security patch.
https://forum.xda-developers.com/mi...-ota-links-t3718542/post74828108#post74828108 (I checked his post at first and when I created my post, he didn't have July fastboot ROM uploaded).
https://forum.xda-developers.com/mi-a1/how-to/download-opr1-170623-026-9-5-4-february-t3758090 (This guy gave a headline of July fastboot ROM. But I didn't find V9.6.4.0.ODHMIFE anywhere on his post)
Now, it's not my fault if someone uploaded the July fastboot ROM after I posted it here. I don't know why some people act violently (not you) towards others.
Rowdyy Ronnie said:
Disclaimer:
Your warranty will be void after unlocking the bootloader. You need to lock the bootloader for any warranty.
Click to expand...
Click to collapse
I dont think thats the case with xiaomi.
Thanks for uploading fastboot image.
.:Addicted:. said:
I dont think thats the case with xiaomi.
Thanks for uploading fastboot image.
Click to expand...
Click to collapse
Well, the warranty remains intact only if you use a miui based handset. But since Mi A1 runs on pure AOSP, Xiaomi doesn't provide any warranty after unlocking bootloader (confirmed with Xiaomi customer service).
Rowdyy Ronnie said:
Well, the warranty remains intact only if you use a miui based handset. But since Mi A1 runs on pure AOSP, Xiaomi doesn't provide any warranty after unlocking bootloader (confirmed with Xiaomi customer service).
Click to expand...
Click to collapse
ahh ok. good to know that
i am already rooted on custom rom but i want to flash stock 8.1, do i use mifalsh tool? and does it wipe all the internal data? or use the userdata (like apps etc)
faddys123 said:
i am already rooted on custom rom but i want to flash stock 8.1, do i use mifalsh tool? and does it wipe all the internal data? or use the userdata (like apps etc)
Click to expand...
Click to collapse
Hi, yes you need the MiFlash tool as this is a fastboot ROM. And it is not necessary (but suggested) to wipe the internal storage. You can select your desired option on the MiFlash tool. If you want to keep your apps and data, you can select "Save user data" on MiFlash tool and flash the ROM.
we only need one thread about stock roms. Let's make it easier on everyone and keep all the info in the same thread.
https://forum.xda-developers.com/mi-a1/how-to/mi-a1-monthly-updates-t3750419
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542/
Hello all,
I am in need of some help please.
I have 18.1220.2109.126 installed presently. I have the EU version/WW version of this phone.
I want to upgrade to the latest firmware but I have an unlocked boot loader and root.
Can someone please provide me with the links for the firmware and an upgrade path from this firmware if i cant go direct?
Thanks
Valen.
as I've wrote a couple times before....
you could've just googled how to manually ota update asus phones. they works more less the same:
1. download the update pkg to the phone.
2. move it to the root of the storage (i.e. the first page you open when you tap internal storage in fm.
3. charge your device to at least 60% and up.
4. reboot the phone.
5. after a while it should give a popup saying update found, tap on it and start local ota.
some notes:
if you want to keep magisk then DONT reboot after ota finished. go to magisk manager and select install to inactive slot. then you can reboot.
This only works for updates not downgrade. if you flashed 31.xxxxx (A12) then you cant go back to 18.xxxx (A11), it won't give you the prompt.
Click to expand...
Click to collapse
yurishouse said:
as I've wrote a couple times before....
Click to expand...
Click to collapse
I am having some trouble navigating this thread. its a mess of stuff.... Other phones have sectioned areas for exactly what i need.
THank you for replying to me. I have begun doing this and am updating as we speak. Sorry i made you repeat yourself.
np
Hi,
It would be awesome if getting to one build.prop from pro
And is Armoury Crate version in pro 5.50.0.49_220124 ? 124MB ?
In: system / priv-app / ROGGameCenter
Plz
Thank you
good afternoon i also have this version 18.1220.2109.126 is there a latest version other than this? because i have an warning saying my installed firmware does not match the device origin