Related
Could someone help me restore 4.4.2 stock firmware?
MY BOOT LOADER IS LOCKED
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
ImAustin366624 said:
Could someone help me restore 4.4.2 stock firmware?
When I turn on my phone I get this:
version downgraded for boot
failed to validate boot image
Fastboot reason: fall-through from normal boot mode
Click to expand...
Click to collapse
Flash the 4.4.4 image.
pfufle said:
Flash the 4.4.4 image.
Click to expand...
Click to collapse
My moto g never received the 4.4.4 update so do you think it will still work? Where could I find the 4.4.4 firmware?
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
It's downloading now, will report back when i'm done Thanks for helping!
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I will have to do this later in the day, my crappy satellite internet is acting up right now
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
ianxblog said:
I had this problem and sadly, after trying countless times with different firmwares the only solution I could find is to unlock the bootloader.
Then it stops giving you an error when you try to flash boot.img.
Your mileage may vary, but that is a potential fix, so keep that in mind.
Click to expand...
Click to collapse
The only way to unlock the bootloader with AIO moto g's is to use Jcases sunshine app and you have to be in the operating system for that
pfufle said:
It will work irrespective of whether you received the update or not.
Firmware image: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143
Guide to Flash: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My parents use the same exact phone as me on the same carrier, could I dump the firmware from their phones and then flash it onto mine?
You can take a system image via a nandroid backup and the flash it on your device
hello everybody
my english is not so good, i try to describe and hope you understand what i mean.
ok let´s go
i updated my moto g 2013 (with open bootloader but without root) from original stock 4.4.4. manually to 5.0.2 - Not OTA. i did it with fastboot.
i don´t like 5.0.2 because the phone has to many bugs and it won´t be better. bad 3g and sometimes i don´t have any signal, play store services are shut down very often, can´t open playstore because my account is not available and yesterday all my apps from homescreen were gone......and so on.....
now i want to have 4.4.4 back again and i hope you can help me.
what i have is the original stock 4.4.4 (XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml)!
in this post, there are only BR, FR, MX, GB Firmware http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
1. what about my firmware, does it works too with this method?
so, here are so many posts about downgrade/restore..... just give me a link or post a description here or something else with an easy guide please.
more questions i have
2. which is the right description, tools, downgrade for my phone? the link above?
2. i read that after downgrade to 4.4.4 the phone has a kind of line or light on the display, is that right and why the phone get this?
3. what about this here? has it something to do with this display bug or for what is this file http://forum.xda-developers.com/showpost.php?p=54103676&postcount=2
what i have to do with this file? important for downgrade?
4. is it possible to downgrade bootloader too and how?
i know here are many posts about this and don´t be angry to me that i start a new one. a friend recommend this forum and said, here are a lot of good and helpful people.
so thank you so much
I hate lollipop!!
xodbx said:
hello everybody
my english is not so good, i try to describe and hope you understand what i mean.
ok let´s go
i updated my moto g 2013 (with open bootloader but without root) from original stock 4.4.4. manually to 5.0.2 - Not OTA. i did it with fastboot.
i don´t like 5.0.2 because the phone has to many bugs and it won´t be better. bad 3g and sometimes i don´t have any signal, play store services are shut down very often, can´t open playstore because my account is not available and yesterday all my apps from homescreen were gone......and so on.....
now i want to have 4.4.4 back again and i hope you can help me.
what i have is the original stock 4.4.4 (XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml)!
in this post, there are only BR, FR, MX, GB Firmware http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
1. what about my firmware, does it works too with this method?
so, here are so many posts about downgrade/restore..... just give me a link or post a description here or something else with an easy guide please.
more questions i have
2. which is the right description, tools, downgrade for my phone? the link above?
2. i read that after downgrade to 4.4.4 the phone has a kind of line or light on the display, is that right and why the phone get this?
3. what about this here? has it something to do with this display bug or for what is this file http://forum.xda-developers.com/showpost.php?p=54103676&postcount=2
what i have to do with this file? important for downgrade?
4. is it possible to downgrade bootloader too and how?
i know here are many posts about this and don´t be angry to me that i start a new one. a friend recommend this forum and said, here are a lot of good and helpful people.
so thank you so much
Click to expand...
Click to collapse
Did u find a way to revert back to kit Kat?
hey
no, sorry
i´m waiting for the answers
Just flash the 4.4.4 firmware via fastboot, using the following commands:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Use only this commands, absolutely DON'T flash gpt.bin and motoboot.bin, or you'll end bricking your device.
mfastboot download link: https://mega.co.nz/#!xgYkgI6I!E4MkiSwCm1AS4qor5xP8QTNeL-BAFZLrV9JDCIlBImM
I have successfully downgraded from 5.0.2 Retail DE to 4.4.4 Retail DE this way. The line glitch is due to a compatibility issue between kitkat kernel and lollipop bootloader, but it isn't so annoying, you only have to lock and unlock your device only once after every reboot. BTW I think that a hard reset will solve most of the problems you've faced on lollipop, I haven't experienced any of the issues you're talking about.
hello and thanks for your answer
why is there a different way for downgrade between yours and this http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553 ???
whats the different?
and what about the adb drivers. it must be installed first, saw on a video? i don´t need it for downgrade? i have a "minimal adb+fastboot setup.exe"!
what is behind ...... don´t flash gpt.bin and motoboot.bin...?
and i did a hard reset after update to 502, but have still some bugs
sorry for all my questions, i´m a bit careful
The partition layout may be different between KK and LP; therefore, I would recommend flashing gpt.bin.
You won't be able to flash motoboot.bin because your phone probably has the 41.18 bootloader which cannot be downgraded.
When you downgrade to KK, you will see a line running from the top to the bottom of the screen. It looks like it is rippling. Don't worry, this is happening because your are running KK on a LP bootloader. To get rid of the rippling, just lock and unlock the phone using the power button.
If you flash to stock KK and run the OTA update to 5.02, the rippling will go away because you'll be running stock LP on a LP bootloader.
Hello and thanks for answer, but you say its recommend to flash GPT and the other member said DON'T. so two different answers,. What happened if i flash and don't flash???
You can try to install the ROM without flash gpt.bin.
When going from GPE to non-GPE and vice versa, gpt.bin had to be flashed.
Hey audit13
Thanks for answer but i don't understand what you mean. What is gpe ?non gpe? Vice versa? No plan, sorry
Gpe means google play edition and non gpe means non Google play edition
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
As there are many threads about downgrading
So Im very much confused
Can anyone help me with the best way
If yes then it will be needfull to me
xodbx said:
Hey audit13
Thanks for answer but i don't understand what you mean. What is gpe ?non gpe? Vice versa? No plan, sorry
Click to expand...
Click to collapse
GPE = Google Play Edition
Non-GPE = Stock ROM
GPE uses the ext4 file system for data.
Non-GPE uses f2fs for data.
Flashing GPT.bin is recommended, in my experience, when going from GPE to non-GPE and vicer versa.
audit13 said:
GPE = Google Play Edition
Non-GPE = Stock ROM
GPE uses the ext4 file system for data.
Non-GPE uses f2fs for data.
Flashing GPT.bin is recommended, in my experience, when going from GPE to non-GPE and vicer versa.
Click to expand...
Click to collapse
hello and thanks for your answers. sorry, i was sick for a few days and could not write back.
so my moto g has the google play app. is it a gpe? i have the original ....XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml...
have to flash or not gpt.bin?
thanks again
xodbx said:
hello and thanks for your answers. sorry, i was sick for a few days and could not write back.
so my moto g has the google play app. is it a gpe? i have the original ....XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml...
have to flash or not gpt.bin?
thanks again
Click to expand...
Click to collapse
OK guys, i did it without flashing bootloader and GPT and it works. Thanks for Helping me :good:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:
This is a newest MIUI 9 China Beta "s TZ &Modem
Baseband:BO.2.6.c1.2-0818_1948_87b78d2
Link:https://yadi.sk/d/wdmLsruk3MSQJr
Flashable ZIP File
Please Use TWRP
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: DO NOT flash this on official Lineage with Lollipop bootloader, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot which is also pretty useless, since your bootloader is locked
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
PeterMarkoff said:
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: do not flash this on official Lineage, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Click to expand...
Click to collapse
kindly type, fastboot oem device-info on fastboot mode with phone pluged in,hope it didnt lock your bootloader.
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
PeterMarkoff said:
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
Click to expand...
Click to collapse
Have you unlocked your phone officially?
Because i flash this too and had no problem at all.
?
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
PeterMarkoff said:
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
Click to expand...
Click to collapse
YES,This is a Nougat Bootloader,you must unlock bootloader in official tools after you install this file in twrp
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
buktore said:
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
Click to expand...
Click to collapse
****ing ask before do something if you're not so sure about it.
Has anyone noticed any improvement with the new radio?
Hello. Has anyone got a link to the latest firmware available for a MI4C. I'm not after the official ROM, just firmware workable with ROMs. I think the last update I done was through andropax link https://androidfilehost.com/?w=files&flid=155424 is there a way I can also find out which firmware I have installed I forgot.
Is this the latest > https://androidfilehost.com/?fid=890278863836288705
fw_libra_miui_MI4c_V9.5.2.0.NXKCNFA_81f363e363_7.0
& will it run dev ROMs?