Related
Greetings ,
Im new to this phone so i need some help with an issue if possible, i unlocked bootloader,installed cwm, and then flashed Google play Edition for HTC one ,afterwards i wiped data and cache and then restored stock rom ,current version 4.2.2 more info photo #2. A new update for the software came up and i chose to download.When i tried to install it the phone goes to recovery mode and some info appears on the screen (photo) ,when i restart my phone there is a message saying update was corrupted and then he tries to download/install again.Can some1 explain me what i have to do in order to update my device properly?
degothia said:
Greetings ,
Im new to this phone so i need some help with an issue if possible, i unlocked bootloader,installed cwm, and then flashed Google play Edition for HTC one ,afterwards i wiped data and cache and then restored stock rom ,current version 4.2.2 more info photo #2. A new update for the software came up and i chose to download.When i tried to install it the phone goes to recovery mode and some info appears on the screen (photo) ,when i restart my phone there is a message saying update was corrupted and then he tries to download/install again.Can some1 explain me what i have to do in order to update my device properly?
Click to expand...
Click to collapse
I don think you can install an OTA from a custom recovery. You need the stock recovery
dgtiii said:
I don think you can install an OTA from a custom recovery. You need the stock recovery
Click to expand...
Click to collapse
Other than that is this rom European?
degothia said:
Other than that is this rom European?
Click to expand...
Click to collapse
Well, your 2nd screenshot says HTC Europe 2.24.401 release, so I assume so
dgtiii said:
Well, your 2nd screenshot says HTC Europe 2.24.401 release, so I assume so
Click to expand...
Click to collapse
Yes you are right i think, but one thing u dont understand , this rom is the stock rom which i restore after a little test with the Google Edition rom , why in my original rom shows something that i can not update?How is that possible?Because i bought it 2nd hand , is possible the last owner could flash another rom , not exactly original stock rom ?
degothia said:
Yes you are right i think, but one thing u dont understand , this rom is the stock rom which i restore after a little test with the Google Edition rom , why in my original rom shows something that i can not update?How is that possible?Because i bought it 2nd hand , is possible the last owner could flash another rom , not exactly original stock rom ?
Click to expand...
Click to collapse
The OTA update needs 3 things in order to be successful
1) Stock ROM
2) Stock Recovery
3) APPS that are lost during unlocking the bootloader
you currently have the stock ROM, so you should also flash the stock recovery and the missing apps.
I have included both links for you. First, unzip the apps file and copy the APK's to your phone and install all of them, then go into fasboot and flash the stock recovery and then you can do the OTA update. And if you dont know how to flash the recovery you can find it somewhere around here on the forums!
Here is the link for the missing apps https://docs.google.com/file/d/0BzXWB5B2uUs7R2hjQnN3NFFNNVk/edit
This is the link for the recovery http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
RTIT said:
The OTA update needs 3 things in order to be successful
1) Stock ROM
2) Stock Recovery
3) APPS that are lost during unlocking the bootloader
you currently have the stock ROM, so you should also flash the stock recovery and the missing apps.
I have included both links for you. First, unzip the apps file and copy the APK's to your phone and install all of them, then go into fasboot and flash the stock recovery and then you can do the OTA update. And if you dont know how to flash the recovery you can find it somewhere around here on the forums!
Here is the link for the missing apps https://docs.google.com/file/d/0BzXWB5B2uUs7R2hjQnN3NFFNNVk/edit
This is the link for the recovery http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
I need the phone to be rooted for one application called Root Call Blocker , i think is the only app that works properly with sense 5 (not notification or sound or even light screen ,when there is incoming call-please tell me if i am mistaken-) so i need to stay rooted, with the above actions will i be rooted afterwards?
degothia said:
I need the phone to be rooted for one application called Root Call Blocker , i think is the only app that works properly with sense 5 (not notification or sound or even light screen ,when there is incoming call-please tell me if i am mistaken-) so i need to stay rooted, with the above actions will i be rooted afterwards?
Click to expand...
Click to collapse
Yes if you are currently rooted, you will still be rooted afterwards and after the update finishes you can reflash TWRP or CWM and everything will be back to where you are now!
I actually didn't try any call blocking apps, maybe ill try this one!
RTIT said:
The OTA update needs 3 things in order to be successful
1) Stock ROM
2) Stock Recovery
3) APPS that are lost during unlocking the bootloader
you currently have the stock ROM, so you should also flash the stock recovery and the missing apps.
I have included both links for you. First, unzip the apps file and copy the APK's to your phone and install all of them, then go into fasboot and flash the stock recovery and then you can do the OTA update. And if you dont know how to flash the recovery you can find it somewhere around here on the forums!
Here is the link for the missing apps https://docs.google.com/file/d/0BzXWB5B2uUs7R2hjQnN3NFFNNVk/edit
This is the link for the recovery http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
By installing the recovery i lost everything in the phone, is that correct?
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
You downloaded the wrong modem file. You need the one for the I8190L, but you flashed one for the I8190.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.2
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
jstath1972 said:
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
Click to expand...
Click to collapse
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
KoolKid98189 said:
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
Click to expand...
Click to collapse
its not going to be that easy for me... i've had this phone for almost 2yrs already
tys0n said:
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
no recovery at all... it bootloops if i power on normally
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
chan1628 said:
its not going to be that easy for me... i've had this phone for almost 2yrs already
no recovery at all... it bootloops if i power on normally
Click to expand...
Click to collapse
It was a tough decision for me, it was either stick to a ****ty BlackBerry or get a free replacement and sacrifice the data. Some of it should be synced to your Google account
tys0n said:
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
Click to expand...
Click to collapse
ok, i will give all this a try and hope for the best
thanks everyone for the quick responses :good:
You could also try to reflash just recovery thru Odin and see if it works.
Sent through time and space from my s3mini/CM11
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
You are in Canada but the L version is for the Latin America countries. So the firmware must be from one of that countries. Which one i can't tell you. You should ask your seller.
[problem solved]
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
chan1628 said:
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
Click to expand...
Click to collapse
Good sleep tonight, my friend ! :good:
Hello everyone, I have sultanxda cm13 ROM on my oneplus 3t and i have a problem. When i try to flash a ROM( lineage 7.1.2, oxygenos and hydrogenos) twrp give me error 7. On other devices i can flash all type of rom from example 6.0.1>7.1.2 or 7.1.2>6.0.1 so, what can i do to flash a nougat ROM? Thanks.
You will have to clean data between ROM change as they're incompatible. You really should newer dirty flash between different ROMs, that's a certain way to get yourself troubles. Also, make sure you have the correct Radio firmware for the ROM you flash (usually the latest unless you of course flash an older oudated ROM).
And... Try an updated twrp.
Kollachi said:
And... Try an updated twrp.
Click to expand...
Click to collapse
Thanks. However i have the 3.1.1.0 twrp and i clean flash every time. Do you recommend me the blue spark twrp?
pitrus- said:
You will have to clean data between ROM change as they're incompatible. You really should newer dirty flash between different ROMs, that's a certain way to get yourself troubles. Also, make sure you have the correct Radio firmware for the ROM you flash (usually the latest unless you of course flash an older oudated ROM).
Click to expand...
Click to collapse
I clean flash every time. Also, what is the correct radio firmware?
Either OnePlus3T_4.1.6-(10-6-17)-FIRMWARE-flashable.zip or the latest Beta modem firmware found in this forum.
Ivanprince99 said:
Thanks. However i have the 3.1.1.0 twrp and i clean flash every time. Do you recommend me the blue spark twrp?
Click to expand...
Click to collapse
Don't know the difference between them. An old twrp can cause this error but I think it's because u haven't the right firmware installed right now.
OK Thanks a lot.
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK https://www.youtube.com/watch?v=KBsWNrKNZzA
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
yeah, you are missing a step.
you have to format data partition.
check my guide on how to install roms: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, may I suggest EU/masik instead of stock, its a lot better
in #3 you can see that in the video data is also formated: https://youtu.be/KBsWNrKNZzA?t=190
of course i did this too....was also not working.
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
motorh3ad said:
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
Click to expand...
Click to collapse
Don't flash vendor, theirs no need, eu.miui has everything in the one zip file. Just to clarify have you formatted in twrp? The option where it requires you to type 'yes'? Everything gets wiped from your photos and apps all to the rom itself. Then just flash eu.miui and reboot. Works everytime for me without fail.
no i never formatted in TWRP wipe, only used the factory reset and swiped to wipe.
just did a format and flashed xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM _v11-10.zip
ITS BOOTING!!
first please let me thank you very much for this help, i was already quite desperate about nothing working except LINEAGE.
fingerprint in MIUI rom is working great, unbelievable!
can you please explain me why this FORMAT in WIPE is needed and what its used for? i was not aware and i can not find it in any of the howtos..
haha, glad it's working. Knew the problem was that you didn't format.
however since you posted on xda, I just assumed you knew format data is not the same as wiping data.
(literally, the most common beginners mistake for this phone)
it's cause of the encryption keys, when moving from MIUI to AOSP (and vice-versa) a format data partition is required.
I stated this in How To Change My ROM? I wanna Try them all!
section in the first post.
under there, FOR MIUI ROMS (since that is what you were trying to do)
you missed the 7th bullet point. (you can also text me on telegram)
(also, in the same guide, I inform people to flash their vendor first -4th bullet point- then in the 5th bullet point you wipe it.)
(this is cause often miui customs and some people are usually on a vendor that isnt there's. you have to be on your region vendor, then wipe it, then allow the miui custom's vendor to take over, else you will face fingerprint problems)
This is just another point most just don't follow.
Umm, if my guide needed anything to be included, or like... needed to be more easy to read and follow... I can edit that if you like.
(use can text me on telegram as well)
edit: just read the xiaomi.eu one, I'll edit it to make it more informative
motorh3ad said:
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
Click to expand...
Click to collapse
You're not installing stock ROMs. You are installing custom ROMs based on stock.
If you want to return to true stock grab a fastboot ROM from here and flash it with the Mi Flash Tool. After fully extracting the ROM delete the flash_all_lock.bat file before flashing. That way you cannot accidentally lock the bootloader.
Then choose the 'clean all' option in the Mi Flash Tool before you hit the flash button.
thank you.
my mistake, i didnt write clear. i just wanted to test a miui rom to see how the fingerprint is working there. im happy now with the custom rom based on stock.
but i also went for this solution you mentioned and noticed that on the https://www.xiaomiflash.com/ site only older xiaomi devices are mentioned as beeing compatible.
looks like this is not the point, so im happy to have this option too.
Does anyone know of a stock miui rom for the Spes that has been debloated of ads and other crap and optimised? Don't mind whether it is a recovery rom or needs to be flashed with fastboot (or miflash).
I'm currently on v13 Android 11 the global version, quite happy to remain on that.
Can someone provide a link to the rom?
Thanks.
Look here: https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Microsheepcl said:
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Click to expand...
Click to collapse
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
maritimesbob said:
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
Click to expand...
Click to collapse
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
I downloaded the miui.eu rom which is debloated and allegedly more optimised. I went back A11 the same as I had before I unlocked my bootloader. I flashed the fastboot version and used the bat script inside the zip to flash it.
Alex Zander-kun said:
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
Click to expand...
Click to collapse
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Microsheepcl said:
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Click to expand...
Click to collapse
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Alex Zander-kun said:
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Click to expand...
Click to collapse
Always that I need as a base a stock ROM flashed, I "simply" use the fastboot commands that are inside the ROM, I open my ADB/fastboot CMD/terminal, and drag and drop the flash_all.bat file while in Windows or the flash_all.sh file while on Linux. This method allows to me, to can follow the process while the scripts are running, and search for issues (if there are some)
As per the TWRP flashing the stock ROM, it worked fine too. You just need to flash the ROM, then boot to recovery once, you'll find the stock one, then format data from it, then you are ready, either to go straight to system, or if you prefer have TWRP (or any custom recovery), go to fastboot and follow the method to boot to, and then flash it permanently to the ramdisk.