Hey everyone,
I've just bought a 5x (a KIW-L24) expecting to be able to install Lineage. I have had issues trying to do this, and the error I'm getting indicates that I need to update to stock Marshmallow before I can do this.
I can install the C567B130 ROM (United States,Channel-Others) firmware successfully, but there's no Marshmallow patch or version. Both of the other stock ROMs (C567D003 and C567B140) cause a bootloop if I attempt to install them.
Does anyone know whether there are hardware variants that may account for the issues I'm facing? Failing that, can anyone recommend an alternative ROM that I can upgrade to from an Android 5.1 stock ROM?
Thanks!
Related
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
xN1ghtShadoWx said:
Hello everyone,
I have recently purchased this phone from my (much) younger brother, who is requires it for school next year. I got it for only £25 used, which was a bargain in my opinion.
My plans are to upgrade it directly to Cyanogenmod 12.1 Lollipop, as I use the same ROM on my other two devices (Nexus 7 2k13, Moto G)
However, I have just found out about the "superbrick" bug which affects our devices. I ran Chainfires app, and it said that my emmc chip and firmware were known to cause issues. The phone is currently still on android version 4.0.3 (ics), so am I right in saying that the superbrick bug is present on this phone currently?
Therefore, what is the best way that I can safely upgrade the phone to Cyanogenmod 12.1, without experiencing this bug? In addition, does CM 12 have the "fix" for superbrick, so that it will not happen again in the future?
Finally, I have read a bit about system partitioning. I would quite like to not have to do this, so can I just Flash CM 12 with the MINI GApps, and not run into any issues?
Thanks a lot for the support, and I look forward to receiving and answer
Click to expand...
Click to collapse
First thing I would do is upgrade to jellybean stock. The kernel you have(4.0.3) is vulnerable to the superbrick bug, and rooting the phone from 4.1.2 is easier/safer. Once you do this, you almost never need to worry about this bug again, as the newer kernels are safe. From there use philz kernel to root the phone. Just follow the steps in that thread and match the kernel to the rom. Have a good read, but particularly the 2nd and 3rd posts. Then you need a "kitkat compatible" recovery to flash cm12. You can use the newer philz recovery from HERE. Just flash it then reboot straight back to recovery. Then flash cm12 and gapps etc as normal
Bootloader
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
xN1ghtShadoWx said:
Hi, I have recovery installed fine, but inside the CM 12 rom zip, I see a boot.img. If I brick my phone whilst installing the rom, can I still unbrick with the offical 4.1.2 firmware via odin?
Thanks!
Click to expand...
Click to collapse
Don't worry about that. That is just the kernel(not bootloader if thats what you thought). Yes it is fine to flash stock firmware if you need.
Hi there folks. I got my Huawei Honor 7 phone for two months ago and I'm loving it, currently rooted it and everything except being unable to install Xposed on it, which I'll get to soon.
Now, the main problem is that I'm unable to update my phone in any way, not via the Updater app nor Local update, so I'm kinda stuck. (Wanting to download the YODA ROM 6.0 B250 to install Xposed with)
Is there some problem with it being the Chinese model? I currently have B173 installed and I assume I can't download an European update.app and upgrade it or? Do I need to debrand it? How?
Need some serious help, everything is confusing at the moment.
EDIT: Fixed with downgrading, suddenly got to upgrade via the OTA then!
Like many others, I'm completely frustrated with random restart issues after the June security update for Marshmallow (6.0.1) on my N915P.
I would rather not downgrade to Lollipop, as several posts have suggested.
Can anyone recommend an easy-to-install Nougat ROM, or at least a more-stable Marshmallow ROM?
retiredguy1945 said:
Like many others, I'm completely frustrated with random restart issues after the June security update for Marshmallow (6.0.1) on my N915P.
I would rather not downgrade to Lollipop, as several posts have suggested.
Can anyone recommend an easy-to-install Nougat ROM, or at least a more-stable Marshmallow ROM?
Click to expand...
Click to collapse
I'd have to recommend the ROM I use currently on my Canadian Note Edge. Which is the Resurrection Remix ROM made by micky387 which is also android Nougat (7.1.2)
https://forum.xda-developers.com/showthread.php?t=3509295
And Since the ROM doesn't natively support the N915P you would need to flash micky387's TWRP version that will let you flash the ROM in the first place.
https://www.androidfilehost.com/?fid=529152257862722140
Flashing the TWRP and then the ROM should make the Rom install just fine. My phone isn't supported but I made it work
Sent from my SM-N915F using Tapatalk
Thanks for the suggestion. Anyone know of a N915P (Sprint) version?
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
I think since the stock rom is 8.0 it might brick your device... Not sure though.
snsone said:
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Vcek said:
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Click to expand...
Click to collapse
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
snsone said:
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
Click to expand...
Click to collapse
I would recommend OTA through the device but it's not reversible (once you flash it you can't downgrade because of bootloader upgrade)
Flashing reteu over retus should be fine as long as you are doing it manually and are aware which partitions you are flashing and which you are omitting. I don't recommend this because sometimes it can break certain things like wifi or data signal (especially if you are on stock rom) and doing OTA later through the device can cause errors
Tldr;
If you want to stay on stock rom, flash back to stock then update everything through rom
If you need root or play around with custom ROMs then don't flash anything just reinstall a stock-like custom ROM
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712 this is the guide i've used to update to oreo (which is RETUS and my device is RETEU), then installed RRO. My guess is I have to install all oreo partitions again (I installed all as stated in that guide) and let it do its OTAs. I had no problems with IMEI and signal on RRO.
Hi all,
I recently purchased a Poco F1 and am planning a trajectory for flashing a custom ROM and kernel when the limit expires on unlocking. However, I'm having issues following what is the latest firmware, or MIUI version, or Android release for the unit. Let me explain:
This unit came with a MIUI 9 version that promptly got a two-step OTA to MIUI Global 10 10.0.6.0(OEJMIFH). It is running Android Oreo (8.1.0).
However, discussion in custom ROM threads as late as this week refer to MIUI 10 8.13.x builds and betas being the most recent firmware, and advise to use these firmwares that are based on Android Pie as the base for flashing custom ROMs based on Pie. Despite the older MIUI version number, the Android version is newer.
In addition, there are complaints around the touch performance of this device when using 8.12.x or earlier firmwares that I am not experiencing with this 10.0.6.0 firmware, and I don't want to introduce issues in the process of preparing this unit for a custom ROM.
Basically, I'm not sure what my trajectory should be if I wish to use a MIUI beta ROM, or if I wish to flash something like LineageOS while retaining or updating the touchscreen firmware appropriately. Can I simply unlock the bootloader, flash TWRP, then flash a custom ROM as I have done in the past on other devices? Can I update the touch firmware separately?
Any help would be much appreciated, thanks.
Crayphish said:
Hi all,
I recently purchased a Poco F1 and am planning a trajectory for flashing a custom ROM and kernel when the limit expires on unlocking. However, I'm having issues following what is the latest firmware, or MIUI version, or Android release for the unit. Let me explain:
This unit came with a MIUI 9 version that promptly got a two-step OTA to MIUI Global 10 10.0.6.0(OEJMIFH). It is running Android Oreo (8.1.0).
However, discussion in custom ROM threads as late as this week refer to MIUI 10 8.13.x builds and betas being the most recent firmware, and advise to use these firmwares that are based on Android Pie as the base for flashing custom ROMs based on Pie. Despite the older MIUI version number, the Android version is newer.
In addition, there are complaints around the touch performance of this device when using 8.12.x or earlier firmwares that I am not experiencing with this 10.0.6.0 firmware, and I don't want to introduce issues in the process of preparing this unit for a custom ROM.
Basically, I'm not sure what my trajectory should be if I wish to use a MIUI beta ROM, or if I wish to flash something like LineageOS while retaining or updating the touchscreen firmware appropriately. Can I simply unlock the bootloader, flash TWRP, then flash a custom ROM as I have done in the past on other devices? Can I update the touch firmware separately?
Any help would be much appreciated, thanks.
Click to expand...
Click to collapse
If you flash a custom ROM over what you have (Oreo), you will retain the existing firmware & modem. If it is compatible with the ROM flashed, you will not have any issues.
It is possible to flash firmware & modem alone at any time if it is available separately.