[Q] [NOOB] Flash a 4.4.2 custom rom over a 4.3 firmware ok? - Moto G Q&A, Help & Troubleshooting

I had some trouble rooting after I first did a 4.4.2 OTA. So I downgraded to 4.3 and got root and installed TWRP without any trouble.
So from a 4.3 firmware I went to Cyanogenmod (Android 4.4.2). Is that ok ? Or do I need to upgrade radio, boot or other parts that dont come with a custom rom? In other words: is a (rooted) 4.4.2 firmware a precondition for installing alternative 4.4.2 roms?

Well, everything might not work perfectly as many things (though little) changed from 4.3 to 4.4. Yup, most of those things (radio,etc) change, flashing a cm11 rom wont change those and cm will most likely need them. Better to upgrade to 4.4. Also, does ART (new kitkat runtime) need anything new from kernel or anything? I don't see anyone who seems to have tried this and might mostly not work.
Also, What root trouble did you have? Easier to solve that issue than deal with any new issues that might arise from this.

hemanthmahesh said:
Well, everything might not work perfectly as many things (though little) changed from 4.3 to 4.4. Yup, most of those things (radio,etc) change, flashing a cm11 rom wont change those and cm will most likely need them. Better to upgrade to 4.4. Also, does ART (new kitkat runtime) need anything new from kernel or anything? I don't see anyone who seems to have tried this and might mostly not work.
Also, What root trouble did you have? Easier to solve that issue than deal with any new issues that might arise from this.
Click to expand...
Click to collapse
Thanks. I will look into that. The kernel is included in a ROM though wright? So that wont be an issue I guess... But just to be save I'll flash 4.4.2 firmware and start from there. My problem was I actually got root, but flashed custom roms always got stuck in the boot animation. The thread on that is here.

Related

[Q] Horizontal line continuously looping down the screen

After flashing a GPE ROM on a non-GPE device, I get these results: http://webmup.com/naZUn/vid.webm
Basically it is a weird horizontal transparent line that moves down the screen... After flashing the 4.4 GPE ROM got those symptoms -- But even after going into TWRP recovery, the line is still there!
Also, once I decided to revert to stock to try and fix it, there is still this annoying line after booting!! This includes stock ROM, CM, and TWRP ( But once booted, locking and unlocking will fix it temporarily)
I don't think its a hardware problem because the fastboot screen does not face the issue :\
Please can anyone give me some guidance? Im really desparate.
The cause of this phenomenon is the Bootloader (BL) included with Lollipop. Your current BL is 41.18, the KitKat version is 41.13. There is no way to return to the KitKat BL, and I suggest you avoid trying. The issue will disappear when using a Lollipop ROM and Kernel.
right now i'm on GPE 5.0.1 and when ever i flash cm12 over it i get like this screen flickering
and my question is we wont be able to use cm12 over 5.0.1 or what? Please some one explain
The issue is kernel-related and I expect can be resolved with a custom Lollipop Kernel. Current CM12 ROMs need to take into account the new bootloader - then the problem will be fixed.
Thanks for the explanation!
Shouldn't CM 12 already be using a lollipop kernel though? What sort of changes to the kernel are required to fix the issue?
marcoms said:
Thanks for the explanation!
Shouldn't CM 12 already be using a lollipop kernel though? What sort of changes to the kernel are required to fix the issue?
Click to expand...
Click to collapse
Yes, but as you have observed; CM12's current Kernels (or any KitKat Kernel) are not fully compatible with the new Lollipop Bootloader (v41.18). The display problem does not occur with Stock Motorola Lollipop Kernels.
Perhaps @TeamMex can suggest what changes are needed.
lost101 said:
Yes, but as you have observed; CM12's current Kernels (or any KitKat Kernel) are not fully compatible with the new Lollipop Bootloader (v41.18). The display problem does not occur with Stock Motorola Lollipop Kernels.
Perhaps @TeamMex can suggest what changes are needed.
Click to expand...
Click to collapse
well i don't have time to investigate what i need change to make fully compatible with new bootloader.
maybe when motorola release his kernel for lollipop I can check...
for now we need wait.
Can someone experiencing this issue try the following?
Settings > Developer options > Tick "Disable HW overlays"​
Reboot may be necessary.
Unfortunately ive flashed back the gpe rom, but if no one else can do it then I guess I can try at home with CM
Apparently disabling 'HW overlays' makes no difference. I guess the only way to remove this effect is to use a Kernel that is fully compatible with the 41.18 Bootloader included with Stock Lollipop. As suggested above, we have to wait for Motorola to release Lollipop Kernel sources before DEVs can figure out a solution.
lost101 said:
Apparently disabling 'HW overlays' makes no difference. I guess the only way to remove this effect is to use a Kernel that is fully compatible with the 41.18 Bootloader included with Stock Lollipop. As suggested above, we have to wait for Motorola to release Lollipop Kernel sources before DEVs can figure out a solution.
Click to expand...
Click to collapse
Thanks for finding this out lost101 - we can expect a kernel release in early 2015 then
Hi there! First of all thank you guys for all the effort you're putting into this. I've got the same problem with the horizontal line looping down and wanted to ask if anything changed since the last post of december. I don't really like Lollipop, flashed back to 4.4.4 and am stuck with the line issue.
Thanks for any updates!
:good:
is there no update on this issue as of 18/02?
funster_ said:
is there no update on this issue as of 18/02?
Click to expand...
Click to collapse
Nothing will change until custom kernels for stock are available. Maybe then a kernel DEV can find a work around. Motorola have not yet released any kernel sources for Lollipop - which they legally have to.
lost101 said:
Nothing will change until custom kernels for stock are available. Maybe then a kernel DEV can find a work around. Motorola have not yet released any kernel sources for Lollipop - which they legally have to.
Click to expand...
Click to collapse
yeah, that was what i mean.. is there no updates about motorola releasing the source for the kernel anytime soon?
funster_ said:
yeah, that was what i mean.. is there no updates about motorola releasing the source for the kernel anytime soon?
Click to expand...
Click to collapse
After bricking my moto g by "downgrading" from Android 5.0 to 4.3, I recovered it by going to 4.4.2, but got this horizontal line issue. However, it seems to have pretty much cleared itself up. The last time it occurred, I allowed the screen to enter sleep mode, then woke it and the problem had fixed itself.
Just leave it for a while
Hey bro don't worry about a thing. I had the same issue. Just leave your phone for a while and the looping will disappear. From experience.
I got horizontal line on recovery.
I have 41.18 bootloader.
What is the problem?
Im on cm12.1 xt1033.
There is no problem on Rom though, its only on the recovery.
Here is a fix for the issue:
http://forum.xda-developers.com/moto-g/help/solution-to-moto-g-2013-tearing-t3408447

[General] Lollipop Information Thread S4

General Lollipop Information Thread​
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
LastStandingDroid said:
General Lollipop Information Thread​
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
Click to expand...
Click to collapse
Can u port soundcamp to s4 ?
i've flashed cf autoroot and it works perfectly
i did a completly downgrade,also bootloader and no issues
Sent from my GT-I9505 using XDA Free mobile app
i have installed official lollipop 5.0.1. If I root my phone, I will be able to flash official updates from samsung in the future? or I won't because of triggered knox
ViPER4Android
I managed to install Viper as system app but problem is How do I Activate it? In Sound settings there is No Music fx, (although it's installed), so I don't have the option switch Viper on, let only see Adapted Sound and in custom profile doesn't select it either. Am I missing something or is it because this update is so terrible
great info Droid! saw this thread in your signature
Revert from LL 5.0.1 to KK 4.4.2 is possible even if you flashed the Bootloader!
Personaly tested and working like charm!
No IMEI lost, no issues soo far found....
re
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Xain47 said:
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Click to expand...
Click to collapse
yeah..they are the same but i don t know if modems are diferent. i think you should not flash i9506 on E330s

[Q] Trying to flash custom ROMs on Sprint GS5 (SM-G900p) and FAILING

I'm new to the whole rooting and flashing scene. However, I'm good at following instructions, generally pretty good at figuring out how to overcome unexpected problems, and a pretty quick study. I've got the hang of rooting my phone down pat, and I can flash stock ROMs with no trouble. Unfortunately though, I have yet to successfully flash a custom ROM on my Sprint Galaxy S 5 (SM-G900P). First, I thought I'd try for CyanogenMod, but the CM installer says that my device is not supported, and refuses to work for me. I know it can be done without the installer, but I have yet to locate the instructions someplace to do it manually.
After giving up on CM for now, I found Alliance ROM for KitKat 4.4.4, which REALLY intrigues me with its high flexibility. What's more, it's KitKat, which I much prefer over Lolipop. Ever since I switched to Lolipop, my apps have all started crashing frequently, even after being updated, and even TouchWiz itself has started crashing frequently. I also don't like the new drop-down menu or the new Recent Apps display. So, I flashed KitKat 4.4.4 kernal and then tried to flash Alliance ROM, but I just got stuck in a boot loop. I booted back to recovery, flashed the stock 4.4.4 image again, and tried to figure out what to do to get Alliance working. I went through the entire Alliance ROM thread here on xda, and found THIS POST describing a method to get Alliance ROM working on a 4.4.4 kernal without having to flash back to 4.4.2. After following those directions, though, I still wound up in a boot loop. Now, when I did that, I wasn't able to use the de-odexed version, and had to use the odexed one instead. After waiting 2 hours to download both versions, I couldn't get the de-odexed one to flash at all. It gave me an error message about no md5 found, or something like that. Unzipping the zip file would have given me a bunch of disconnected folders, so I just tried to flash it from the zip, but it didn't work. The odexed version, however, had an md5 inside the zip, so I just unzipped and flashed the odexed md5. Still got boot loop, though, after I tried to install Alliance ROM afterward.
So, with all that being said, here's what I'm looking for.
Either:
1.) A reliable way to install Alliance ROM on my Sprint Galaxy S5 (SM-G900P)
2.) A different custom ROM that might be better suited to my needs. This is what I'm looking for:
a.) Rooted
b.) debloated
c.) wifi tether and USB tether
d.) KitKat Drop Down and Recent Apps menus
e.) Some badass-looking themes. I really like the look of the Black Glass themes from Alliance, so either THAT or something that looks equally badass
f.) I would like to be able to overclock
g.) want to see CPU usage
h.) battery percent
i.) want to be able to turn off camera shutter sound. (Maybe this can be handled by just installing a different camera app, idk)
j.) Working private mode
k.) fingerprint scanner functionality would be NICE, but not a must. I really only use it for Private mode.
I'm sure there are probably other things that I'd like to see, but those are the ones I can think of right now. So if anyone can tell me how to get Alliance ROM working, or has a suggestion of another custom ROM that would include those features, and that will work with my Sprint Galaxy S5 (SM-G900P), and where I can find it, I'm all ears.
Thanks!
So, from what I have read here, and I skimmed most of it, is a bootloader issue. You not only need version specific kernel but bootloader as well. You're issue might be that you have a kit-kat bootloader trying to flash lollipop or vice versa. Your best bet is to Odin the Official stock tar of which ever version of custom rom you want to flash, i.e 4.4.2, 4.4.4, 5.0. Then you can reroot and flash the coinciding custom rom. Does that make sense?
metalfan78 said:
So, from what I have read here, and I skimmed most of it, is a bootloader issue. You not only need version specific kernel but bootloader as well. You're issue might be that you have a kit-kat bootloader trying to flash lollipop or vice versa. Your best bet is to Odin the Official stock tar of which ever version of custom rom you want to flash, i.e 4.4.2, 4.4.4, 5.0. Then you can reroot and flash the coinciding custom rom. Does that make sense?
Click to expand...
Click to collapse
Yeah, that makes sense. Where do I find the Official stock tar? Also, if I flash back to 4.4.2, then reroot and flash Alliance for 4.4.2, can I upgrade from there to 4.4.4 without having to flash again? Or do I have to flash stock 4.4.4 followed by flashing Alliance for 4.4.4?
4.4.2 and 4.4.4 are both kit-kat, so you can flash either one. Look in Sprint Galaxy s5 Android development for the tar files
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
http://forum.xda-developers.com/showthread.php?t=2958614
Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_2_7_15
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2787760
[LINK][ROM][ODIN][TAR]SM-G900P NE5 (NE5 Modem/Kernel/ROM - Stock)
4.4.2
missionary7 said:
Yeah, that makes sense. Where do I find the Official stock tar? Also, if I flash back to 4.4.2, then reroot and flash Alliance for 4.4.2, can I upgrade from there to 4.4.4 without having to flash again? Or do I have to flash stock 4.4.4 followed by flashing Alliance for 4.4.4?
Click to expand...
Click to collapse
Go with 4.4.2, 4.4.4 had such small improvements, you wouldnt even notice. I recommend M.O.A.R. ROM it is the mother of all ROMS. Paired up with ktoons kernal, its amazing!!!

Migrating from one M8 to another - sanity check

Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
j006 said:
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
Click to expand...
Click to collapse
firewater sever is taken down, even if you have an old version of it laying around it is useless.. you must pay for sunshine.
but other than that everything looks good.
you have your nandroid backup, on the new m8, s-off using sunshine, then update the firmware from 442 to 444, then flash custom recovery (TWRP is recommended), and then wipe and restore the nandroid and you should be good to go. :good:
(no need to flash supersu as the ROM you have backed up using nandroid is already rooted)
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
j006 said:
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
Click to expand...
Click to collapse
I find many benefits to LP over KK personally.
If you like a stock ROM we have stock based LP ROMs, and firmware.zip you can flash and you are up an running a stock LP ROM within 10 minutes. Sure you need to set things up, but most can be backed up and if you take some screen shots of everything it's pretty easy to get everything set up to your liking.
If you want some customization there are ROMs like mine, that come mostly stock with some benefits like root, busybox, etc, and then offer you a MOD Pack.
See ROM thread here
If you want to customize pretty much every aspect of the ROM you have Venom at your fingertips.
Venom ROM thread
There is the benefit of having all the security updates with the newest firmware.
We also have Marshmallow 6.0 ROMs out already that are rock solid.
A Google Play Edition ROM found here
And a Sense based ROM found here
You can also run some Sense 7 ROMs that are very stable, you can find one in my linked thread posted above, and in the Development area.
I personally would try things out, that's the great benefit of root/s-off/custom recovery/ROMs
You can always make a nandroid backup of your current ROM, and flash the older firmware to get right back where you left off.
Best of luck, enjoy your flashings

Random Freezing

Has anyone since having this phone, plain stock rooted, either KK, LL, or MM had at anytime random freezing? This would include apps or even with the keyboard.. I'm stock rooted LL 5.0 and started having this issue today.. I got the phone with MM, but personally do not like MM, as it seems not much in the way of TW roms.. I only had MM for a short time, before downgrading to LL. So this could be a software issue or hardware not sure.. I might go back to stock rooted MM to see. I also do not have any custom kernel with this, left everything alone and only have TWRP, and SU for root. Thanks.
Well after messing around, I figure it was software.. MM is a complete joke, went back down to LL and installed MOAR 7.1 and so far it's working just fine..

Categories

Resources