Hi fellow HTC One M7 users,
After initialling upgrade my M7 to Marshmallow I have loved and embraced the features but felt like Lollipop would be more stable. I have searched all over the forum but could not find concise instructions as to exactly how to downgrade from Android 6.0 --> Android 5.x safely (Change from ART to Dalvik)? If anyone can help towards this, it would be greatly appreciated!
Nothing much needed. Just wipe your system, data and cache in the recovery and flash any Lollipop ROM you want, then you're good.
Siphoné said:
Nothing much needed. Just wipe your system, data and cache in the recovery and flash any Lollipop ROM you want, then you're good.
Click to expand...
Click to collapse
Don't you have to downgrade the either the firmware or the radio? i forget.
Because Lollipop uses Dalvik runtime and Marshmallow uses ART.
Hi. After instalation Android 6.0 and downgrade to Android 5.0 my phone is does not define mobile operator "SIM Card error". IMEI is not lost. But but everything works fine when installing Android 6.0 ([ROM][MM][6.0.1][18-08] CyanogenMod 13.0 - UNOFFICIAL BUILDS for M7 [cam fixed] or [ROM][6.0.1] Slim6 [m7])
I restored a backup my Stoke firmware but nothing has changed. The phone is not define mobile operator. Please help in solving this problem.
HTC M7 (Ukraine)
Hboot 1.61 (Unlocked/s-on)
Radio 4T.35.3218.16
Ok, problem is solved. I used RUU and everything works fine.
purezalbert said:
Don't you have to downgrade the either the firmware or the radio? i forget.
Because Lollipop uses Dalvik runtime and Marshmallow uses ART.
Click to expand...
Click to collapse
No, the radio and the firmware aren't related to the system.
Also, dalvik and ART are part of the system you're using, they're not "inside" your device. They're bundled with the system image (so, the ROMs) you are using.
IIRC no official Android 6.0 was released for the M7, as such, even if we flash 7.x (if it ever comes out) we'll still be using Android 5.x radio and firmwares...
Related
Hi,
I've installed ARHD 8.0, and am absoloutely loving it so far, it is running like a treat, a particularly beastly one mind you! . My only problem is, since I flashed 7.4, which was my first ever Custom ROM, I haven't been able to get NFC. I clean flashed 8.0, hoping that would resolve the issue, but unfortunately I still have no NFC capability on my phone. I have enabled it in the settings, and I have also checked in my list of apps in order to see my Tags, but unfortunately that seems to have been wiped from the phone also, with no hope of getting it back.
I am on an International HTC One, which was previously locked to EE, on an ORANG001 CID, unlocked bootloader and have installed the ARHD 8.0, and flashed the same kernel in the boot.img file of the .zip for ARHD 8.0.
If anyone could help, it would be greatly appreciated, I would have asked about this in the ARHD thread but unfortunately I don't have enough posts and this same post didn't get much love in the Q&A thread .
Many thanks,
Omar
My NFC just works fine with ARHD 8.0.
I think you should ask in the ARHD thread itself.
Have you done a full wipe (data/system/cache/davlik cache) before installing it?
joshoon said:
My NFC just works fine with ARHD 8.0.
I think you should ask in the ARHD thread itself.
Have you done a full wipe (data/system/cache/davlik cache) before installing it?
Click to expand...
Click to collapse
Hi,
Yeah, I attempted to put this in the ARHD thread, but unfortunately I don't have enough posts to make any contribution in that thread atm.
Yeah, I did a full backup aswell of my 7.4, and also a full system reset of the davlik cache, cache, data, before I installed 8.0...
I am totally at a loss as to why my NFC has just gone, its not a urgent matter but I would like to try and get it back as it is undoubtedly going to be an important feature as contactless payment becomes more prominent.
Hey guys. I just flashed CyanogenMod 11 on my phone yesterday. And it was my first time trying a custom rom.
Aside from a few bugs, I'm really enjoying KitKat on this device.
Now my question, I've read that when you have to flash an update (let's say 12, or something) you don't have to wipe cache/data (factory reset). I don't really understand all this, but my main concern is will I loose my data/apps when I flash a CyanogenMod update?
Thanks!!!
hleotangco said:
Hey guys. I just flashed CyanogenMod 11 on my phone yesterday. And it was my first time trying a custom rom.
Aside from a few bugs, I'm really enjoying KitKat on this device.
Now my question, I've read that when you have to flash an update (let's say 12, or something) you don't have to wipe cache/data (factory reset). I don't really understand all this, but my main concern is will I loose my data/apps when I flash a CyanogenMod update?
Thanks!!!
Click to expand...
Click to collapse
If you want update your current CM11 version then you only need to flash it via recovery without any wipe. After install the update via recovery and after reboot to system then do your phone automatically optimize your apps while it booting
Unless you specifically select 'wipe data/factory reset', your data and apps won't be removed. Your apps also weren't removed when you installed an official Samsung update, so CyanogenMod won't do that either.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.4
Android version 6.0.1 bootloader and radio files updated January 7, 2016
Hello all.
I created a few flashable ZIP files which will install the radio and bootloader images from Android 5.0.x, 5.1.x or 6.0.x depending on your choice.
To install the Android 6.0.1 radio (M8974A-2.0.50.2.28) and bootloader (HHZ12k), flash the following ZIP in recovery:
The file is N5_AndroidM_6.0.x-MMB29S_Radio+Bootloader.zip, MD5 9fef18abade89f85fe13b37320b740bd, size 22.7MB.
You can download it here: https://www.androidfilehost.com/?fid=24352994023708028
---
To install the Android 5.1.1 radio (M8974A-2.0.50.2.26) and bootloader (HHZ12h), flash the following ZIP in recovery:
The file is N5_AndroidL_5.1.x-LMY48M_Radio+Bootloader.zip, MD5 c90de28bf48e9461a13c6617c9d792ce, size 22.7MB.
You can download it here: https://www.androidfilehost.com/?fid=24052804347812405
---
To install the latest Android 5.0.x radio (M8974A-2.0.50.2.22) and bootloader (HHZ12d), flash this ZIP in recovery:
The file is N5_AndroidL_5.0.x-LRX22C_Radio+Bootloader.zip, MD5 4c9861bfe068d232340e961aa7726767, size 22.6MB.
You can download it here: https://www.androidfilehost.com/?fid=24052804347812506
Hope this helps!
Thanks
Separate radio frm the zip
Thanks for this.
I already have the updated radio. Could you please split the zip in two, with the updated bootloader separate from the radio.
FunDionysus said:
Thanks for this.
I already have the updated radio. Could you please split the zip in two, with the updated bootloader separate from the radio.
Click to expand...
Click to collapse
I suppose I can, though it doesn't change anything to flash the same radio version on top of itself, so you could just flash the whole thing to update the bootloader. The only reason there would be to split it up would be if you wanted to keep a different radio version than the one in the zip.
Are these updated files? Google factory images are at LRX21O but I've seen threads here that have LRX21V in the name, suggesting there's an update of some kind but I'm unable to find any info regarding this with my searches lol.
I'm just trying to update my wife's nexus 5 with factory files (no custom ROM's) as she just wants her phone to work and not have any instability unlike what I do with my phone haha.
She's had it say no network sometimes, I wonder if Google released this update to the radio to address a bug? Or where did you get these files from? Just wondering
ek69 said:
Are these updated files? Google factory images are at LRX21O but I've seen threads here that have LRX21V in the name, suggesting there's an update of some kind but I'm unable to find any info regarding this with my searches lol.
I'm just trying to update my wife's nexus 5 with factory files (no custom ROM's) as she just wants her phone to work and not have any instability unlike what I do with my phone haha.
She's had it say no network sometimes, I wonder if Google released this update to the radio to address a bug? Or where did you get these files from? Just wondering
Click to expand...
Click to collapse
The bootloader and radio has been the same through all the revisions of Lollipop.
Wakamatsu said:
The bootloader and radio has been the same through all the revisions of Lollipop.
Click to expand...
Click to collapse
So these files are from the Google factory images then?
Do you have a link to get the latest revision of lollipop? I wonder if LRX21O isn't the latest anymore lol
ek69 said:
So these files are from the Google factory images then?
Do you have a link to get the latest revision of lollipop? I wonder if LRX21O isn't the latest anymore lol
Click to expand...
Click to collapse
Yes, these are from the Google factory images. Specifically, the factory images for the Nexus 5. You can see all of the released Nexus factory images here. As you can see, LRX21O is still the latest version released for the Nexus 5. It seems as though other devices have had images released with "higher" letters, for instance LRX21V is the build number for the latest Nexus Player factory image. My guess is that Google makes device-specific changes to Android and then updates only those devices that would benefit, though I have nothing to back that up.
In any case, the radio and bootloader have been the same versions throughout all builds of Android 5.0 for the Nexus 5 so far, and the latest of those builds is LRX21O. This ZIP does contain the latest and greatest that we have officially available at the moment. I'll do my best to keep it updated should that ever change.
iammuze said:
YIn any case, the radio and bootloader have been the same versions throughout all builds of Android 5.0 for the Nexus 5 so far, and the latest of those builds is LRX21O. This ZIP does contain the latest and greatest that we have officially available at the moment. I'll do my best to keep it updated should that ever change.
Click to expand...
Click to collapse
Thanks for this info. When I installed the bigxie stock Lollipop flashable ROM, the OP included a link to the updated radio. But the bootloader was not updated to the latest.
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
So if the latest bootloader is available as a separate flashable zip that would be best. However I've yet to find a link for such.
No problem!
FunDionysus said:
So if the latest bootloader is available as a separate flashable zip that would be best. However I've yet to find a link for such.
Click to expand...
Click to collapse
Well like i said a couple posts above there's no harm in flashing the same version radio on top of itself, so even if all you want is to update the bootloader (and as long as ths radio in the ZIP is the same version you want to keep), this will work just fine.
Maybe a stupid question but I prefer to be on the safe side.... If I flash this file on my device (Nexus 5 of course) actually rooted with custom KK rom and TWRP. Will this wipe the data in the SD card (flashing a new bootloader) or is it safe ?
Thanks
pierrep56 said:
Maybe a stupid question but I prefer to be on the safe side.... If I flash this file on my device (Nexus 5 of course) actually rooted with custom KK rom and TWRP. Will this wipe the data in the SD card (flashing a new bootloader) or is it safe ?
Thanks
Click to expand...
Click to collapse
Nope! No wiping, perfectly safe.
Thx for all your help and clarifying things
I was just wondering why some threads in the nexus 5 section were referencing LRX21V in the titles cuz like u said LRX21O is the latest out by Google for nexus 5
Simply and easy to upgrade the bootloader. Thanks!
Thanks ! :good:
If we flashed the lollipop factory image I assume we have the latest bootloader?
Thank you for this file! I was already running the latest radio but I needed the boot loader update!
Why does everyone care about latest bootloader update so much?
Just wondering
Sent From Bacon
ek69 said:
Why does everyone care about latest bootloader update so much?
Click to expand...
Click to collapse
For myself just wanting to learn the diff.
Can locate no documentation or changelog.
The Android 5.0 LRX21O - Stock/Flashable ROM I installed did not install the updated bootloader, which I believe came out for the Lollipop Preview back in October,
Just to make sure I don't have to fix anything after I do this process.
If I flashed Cataclysm ROM for Android 5.0, I need to install this correct?
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.
cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.
cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.
[Important] Read this before FLASHING/Updating to Stock PIE 9 {SPRINT,TMO AT&T ETC}
Mates! for newbies specially Sprint,TMO and Atn&t users I know you are sad to hear that you won't get stock Pie update and you have been watching threads here on XDA showing how to flash captured Stock Pie of Verizon/Brazil variant on your Sprint ,at&t TMO variants this very important to know that DO NOT UPDATE/FLASH 9.0 Pie update of Verizon/Brazil variants. Otherwise you will loose your IMEI, Baseband N, modem. AND definitely NO WIFI and there is turning back
That update only works for Verizon/brazil variant devices which are getting updates by Motorola it's not for sprint at&t tmo etc THIS ONLY WORKS FOR VARIANTS WHICH ARE ANNOUNCED BY MOTO.
Reasons: when you flash stock pie your Oreo modem is replaced with Pie modem which doesn't matches to your variant which results in loosing of imei,base band and wifi.
Even if you try to flash back oreo with a clean flash you may be able to use your stock oreo but due to pie modem you won't be able to downgrade to your oreo modem and in result your imei baseband will still be gone with pie and there is no solution haven't been found yet.
Please if you really want to use pie there are other custom roms like Dirty Unicorns, CR Droid,Havoc and Lineage OS use them till the developers found an solution for this problem. Thank you!
just don't flash modem,see no problems.sprint - pie
Can at&t ariants flash it?
As it is locked...
Dreamerok said:
just don't flash modem,see no problems.sprint - pie
Click to expand...
Click to collapse
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
KOAO said:
Considering that I've tried to flash the Verizon Pie Image on my Z2 force, and nearly made it useless, how did you do yours? Flashing the Indian Variant?
Click to expand...
Click to collapse
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
found this
Found this forum:
bbs.ixmoe.com/t/topic/22171
Could be a solution to unbrick ?
Dreamerok said:
yeap
indian via fastboot without mode etc guide on the forum. or manual flash via fastboot each file.
Click to expand...
Click to collapse
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated ??
gokart2 said:
So.....you flashed everything but the modem files and everything works for Sprint? I'd assume you didn't flash the bootloader?
Basically want to know which files you flashed and what issues you've seen if any. Much appreciated
Click to expand...
Click to collapse
work fine for me. some bugs with wifi (quick connect disconect sometimes)
battery better. twrp * magisk + gpay ) gcam last works perfect. motocamera & motoprojector ? moto verve buds work
Just came to me....there might be a way to revert back firmware. Way back in 3vo 3d days there was a Boost mobile update that had a newer Android version then what the Sprint people got. So many of us flashed it and had problems. And couldn't revert back.
The best kernel dev I've seen to date (name cannot be given due to settlement between him an xda) found he could hex edit the previous bootloaders version number to be post the Boost version, which then allowed it to flash. And we could then revert back to the Sprint firmware/ROM. I don't know how Moto checks or limits firmware flashing, but just an idea?
I have same problem but i had Lineage OS Backup and flashed it. Now I have normal Lineage OS on Partition B and Lineage OS with Problem on Partition A. (Official Rom only uses A partition, Lineage OS supports A/B partition update). I don't know if there is any way to copy B partition IMEI and Baseband on Partition A.
Moto z2 force sprint
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
can you update what have you done?
Zuhaib King said:
I have also same issue no wifi or network n also no imei if i install lineage os will it resolves imei issue
Click to expand...
Click to collapse
I have the same problem. Can I fix it somehow?