Hi, I have a big doubt about this. Is it possible to install a custom ROM based on Lollipop on a Pure updated to Marshmallow? Do I have to downgrade before doing that?
Thanks in advance.
PD: why not downgrading? because I still like Marshmallow, and I don't want to screw things up
lucianogm said:
Hi, I have a big doubt about this. Is it possible to install a custom ROM based on Lollipop on a Pure updated to Marshmallow? Do I have to downgrade before doing that?
Thanks in advance.
PD: why not downgrading? because I still like Marshmallow, and I don't want to screw things up
Click to expand...
Click to collapse
I've never tried this on this phone. My experience with other phones is that custom roms really don't care what firmware is on the phone. The worst thing I've had happen when flashing an outdated custom rom is it either won't boot at all, or sometimes it boots but won't work with your modem, you can't get data, maybe you can't make calls, and maybe the imei looks blank. Any time that has happened restoring a backup has fixed it for me, so don't panic and try to start restoring efs or injecting imei. Just make sure you have a nandroid backup available, or wipe and flash a known good rom. Everything will go back to normal on an up to date rom. Custom roms are just a boot image and a system, they aren't going to mess with your bootloader or modem; they just might not work with them.
We had working TWRP for clark before Marshmallow rolled out. When Marshmallow rolled out TWRP stopped booting on the Marshmallow bootloader. Hashbang fixed it pretty quick. I kind of suspect that Lollipop roms might fail to boot on the Marshmallow bootloader unless they are up to date enough to have that fix incorporated, but I'm just guessing. I also know from that week or two that some people rolled back to the Lollipop bootloader with no apparent ill affects. Read through late November to early December 2015 in the TWRP thread if you're curious.
This phone isn't particularly picky about flashing modems either. You would probably be ok if you rolled it back too, but I just wouldn't recommend it. You won't be able to downgrade the partition table. Lollipop firmware GPT.bin will fail if you try to fastboot flash a full firmware downgrade, and you'll be left in this weird mixed firmware environment. This phone really isn't very finicky about firmware, but tinkering too much with bootloaders and modems, particularly going backwards, is kind of asking for a brick. People get in all kinds of weird mixed states on clark and usually it just breaks wifi until they get things properly matched up again, not like some Samsung phones where mismatching the bootloader and modem or even just looking at them funny results in a hard brick. I'd just really hate for you to end up being one of the few who hard bricks, though.
---------- Post added at 09:11 AM ---------- Previous post was at 09:04 AM ----------
Oh yeah, almost forgot. That was all for AOSP or CM based roms.
If you try to flash a stock based LP rom on MM firmware it will almost certainly bootloop. If it does manage to boot, wifi probably won't work and maybe some other problems.
jason2678 said:
I've never tried this on this phone. My experience with other phones is that custom roms really don't care what firmware is on the phone. The worst thing I've had happen when flashing an outdated custom rom is it either won't boot at all, or sometimes it boots but won't work with your modem, you can't get data, maybe you can't make calls, and maybe the imei looks blank. Any time that has happened restoring a backup has fixed it for me, so don't panic and try to start restoring efs or injecting imei. Just make sure you have a nandroid backup available, or wipe and flash a known good rom. Everything will go back to normal on an up to date rom. Custom roms are just a boot image and a system, they aren't going to mess with your bootloader or modem; they just might not work with them.
We had working TWRP for clark before Marshmallow rolled out. When Marshmallow rolled out TWRP stopped booting on the Marshmallow bootloader. Hashbang fixed it pretty quick. I kind of suspect that Lollipop roms might fail to boot on the Marshmallow bootloader unless they are up to date enough to have that fix incorporated, but I'm just guessing. I also know from that week or two that some people rolled back to the Lollipop bootloader with no apparent ill affects. Read through late November to early December 2015 in the TWRP thread if you're curious.
This phone isn't particularly picky about flashing modems either. You would probably be ok if you rolled it back too, but I just wouldn't recommend it. You won't be able to downgrade the partition table. Lollipop firmware GPT.bin will fail if you try to fastboot flash a full firmware downgrade, and you'll be left in this weird mixed firmware environment. This phone really isn't very finicky about firmware, but tinkering too much with bootloaders and modems, particularly going backwards, is kind of asking for a brick. People get in all kinds of weird mixed states on clark and usually it just breaks wifi until they get things properly matched up again, not like some Samsung phones where mismatching the bootloader and modem or even just looking at them funny results in a hard brick. I'd just really hate for you to end up being one of the few who hard bricks, though.
---------- Post added at 09:11 AM ---------- Previous post was at 09:04 AM ----------
Oh yeah, almost forgot. That was all for AOSP or CM based roms.
If you try to flash a stock based LP rom on MM firmware it will almost certainly bootloop. If it does manage to boot, wifi probably won't work and maybe some other problems.
Click to expand...
Click to collapse
So there shouldn't be no big issues with an AOSP/CM ROM, right?
lucianogm said:
So there shouldn't be no big issues with an AOSP/CM ROM, right?
Click to expand...
Click to collapse
That's right. It might not work right, but it's nothing you can't recover from easily. Just make sure you have a backup or a zip for a ROM you know is OK handy.
jason2678 said:
That's right. It might not work right, but it's nothing you can't recover from easily. Just make sure you have a backup or a zip for a ROM you know is OK handy.
Click to expand...
Click to collapse
Yeah, that's the good thing. I have lots of zips and an old backup, I think I'm good to go
will update after flashing a rom. Thanks for your help!
The only issue you might run across is connectivity, the radio firmware changed a lot from Lollipop to the first Marshmallow release to current Marshmallow release... It is possible WiFi or Mobile data will not work, but you could either restore back to a working ROM or flash the correct radios from Lollipop ROM.
Be aware, although the Moto X is pretty tolerant of flashing lots of varied stuff, Moto devices in general like to complain when being downgraded, and some E/G series have been semi-bricked doing this depending on what version they started with.
Related
Ready to sell this phone... tried everything I know how to try... Dev Edition Verizon S5, CAN'T UPGRADE from stock NCG. The most I can do it root... any ROM I flash is nonfunctional on Verizon's network with NO SIGNAL. Replaced SIM, flashed modems, etc etc... I think I'm just not sure how to do it with a dev edition... seriously feel like I'm missing a step. Would like to start from scratch. Does anyone have a stock image of a G900V Dev Edition I could work from, since I'm starting to think the one I've been working from is somehow the incorrect version. Thanks!
http://www.sammobile.com/firmwares/
type g900v in search bar
DSA said:
http://www.sammobile.com/firmwares/
type g900v in search bar
Click to expand...
Click to collapse
I would but I'm trying to avoid locking the bootloader, if possible. Didn't intend on having a developer device, but now that I do, I'd like to try to maintain it's use as one. Bought this phone on swappa, seller didn't give any indication that it was a developer device. Now I'm concerned he did something to it prior to selling that is causing me difficulties. I don't think I should be having these network difficulties, but there could very well be something I'm supposed to be doing with the modem that I'm just unaware of. I figure if I can get back to the way this phone was when it was new (when the original seller bought it) I'd at least have a clean slate to work with.
gatorhater73 said:
I would but I'm trying to avoid locking the bootloader, if possible. Didn't intend on having a developer device, but now that I do, I'd like to try to maintain it's use as one. Bought this phone on swappa, seller didn't give any indication that it was a developer device. Now I'm concerned he did something to it prior to selling that is causing me difficulties. I don't think I should be having these network difficulties, but there could very well be something I'm supposed to be doing with the modem that I'm just unaware of. I figure if I can get back to the way this phone was when it was new (when the original seller bought it) I'd at least have a clean slate to work with.
Click to expand...
Click to collapse
Anything usable in here?
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
kprice8 said:
Anything usable in here?
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
Click to expand...
Click to collapse
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
gatorhater73 said:
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
Click to expand...
Click to collapse
It's not like there's a ton of development going on for Dev edition. I'm loving the retail version of the phone just rooted and running some Xposed. Like it so much, I went out and got one for the wife too and I paid full retail for both to keep my old unlimited data plan. Hers I just left out of the box stock. Will be interested to see how Lolipop looks when it drops to her phone. Sure hope we keep root with Lolipop, I use the heck out of my hotspot, to the tune of about 70gb/mo ...
gatorhater73 said:
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
Click to expand...
Click to collapse
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
JOrkin said:
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
Click to expand...
Click to collapse
Had marginal success using this method... Have been able to maintain a 3G signal, but no LTE after first boot. Rather, when I first booted, I had LTE and thought I was good, but since my first reboot, I can only get 3G and nothing I do can get it back so far.
JOrkin said:
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
Click to expand...
Click to collapse
This happened after I flashed the update.tar (with aboot.mbn removed) and I have note gotten LTE back. Is there something I can do with my aboot.bak that I'm missing?
I'm currently on 4.3 with the original bootloader. Is it possible to update to an official touchwiz 4.4 or 5.0 rom and keep the old bootloader?
If no, are there any touchwiz roms modified to work with the old bootloader?
Does CM12 work well with the 4.3 bootloader?
Edit: I have the n9005 (n900x LDU to be exact) version of the Note 3.
You need to post in Q&A section mate but to answer your question no. Bootloaders are compatible with past versions of Android but not future versions. For example: 4.4 Bootloader is compatible witn Android 4.3 but not Android 5.0. Android 5.0 Bootloader is compatible with 4.4 + 4.3 but not Android 6.0 (if it even exists, but as i said, for example) hope this makes sense
P.S welcome to XDA
Are you sure about the backward compatibility? I read in multiple places that people couldn't downgrade to 4.3 because the new bootloader doesn't work with 4.3.
The 5.0 bootloader works fine with 4.3. I've seen and done it myself (I'm a flashaholic).
Do you have the n9005, n900 or some other version of the phone?
I have the N9005 mate.
So these threads are a bunch of baloney?
http://forum.xda-developers.com/galaxy-note-3/help/bootloader-free-n9005-downgrade-4-4-2-t2817775
http://forum.xda-developers.com/showthread.php?t=2613745
Yes....i will post screenshots of me on 4.3 if you like?
I believe you, I'm just surprised as there are lots of threads that claim otherwise. Can you post exact steps of how you upgrade and downgrade? Maybe there's something special about the way you do it as others have obviously had problems with downgrading.
Also, can you respond to my other two questions (CM12 and touchwiz based roms that work with the old bootloader)?
Ideally I'd like not to upgrade my bootloader as this n900x (demo unit) that I have reportedly has major issues on new bootloaders (most probably because no new versions of the modem exist).
errmalt said:
I believe you, I'm just surprised as there are lots of threads that claim otherwise. Can you post exact steps of how you upgrade and downgrade? Maybe there's something special about the way you do it as others have obviously had problems with downgrading.
Click to expand...
Click to collapse
There is no special way of downgrading or upgrading, its just the normal way.
PS: One thing I should have mentioned, if you wipe before upgrading and all that (that's what I do) and wipe via TWRP and then reboot the phone after wiping via TWRP then the bootloader won't upgrade, at least that's what I think, cause that's what happened to me while I was upgrading from KK to LP, the bootloader wasn't updated because I rebooted the phone from TWRP. So to avoid that you need to turn off the phone (if you are in recovery) and then enter download mode by Vol Down and Power, once again, rebooting to download mode from recovery won't upgrade the bootloader, you need to manually do that by powering off the phone and so on.
Trough Odin, not through a custom recovery? What about my other two questions (CM12 and touchwiz based roms that work with the old bootloader).
No idea about CM12, not in that sort of stuffs.
You will flash the ROM via Odin yes, but my previous comment is only valid if you wipe your phone via recovery before upgrading. I always wipe my phone before upgrading (and this was a big platform upgrade from KK to LP), thus thought about mentioning that.
How can you tell which bootloader you have? I wiped everything via TWRP and then used odin to flash a 5.0 rom.
Not sure what bootloader I have though..
That's the thing, I don't know that either! I guess when you enter bootloader there might be a mention of it, or not, not sure really.
I wouldn't have understood that anyway if I didn't have the WiFi password reset problem with LP. A user then pointed out that my bootloader wasn't updated and thus the WiFi problem was happening, and he was right.
errmalt said:
Trough Odin, not through a custom recovery? What about my other two questions (CM12 and touchwiz based roms that work with the old bootloader).
Click to expand...
Click to collapse
Cm12 works with any bootloader
I know it does. How well it works on the 4.3 bootloader was the question.
I just got the Verizon variant of the Galaxy S5 (SM-G900V). I rooted it very easily using odin without tripping knox; that was easy.
I then began looking for ROMs; which for this phone, isn't easy with the locked bootloaders.
I came across a custom ROM, forgot off the top of my head but may go back to retry loading it.
Because these devices have locked bootloaders, any ROM flashed to it will need to have a separate bootloader flashed as well. The aforementioned ROM had one and I understood why, but after I odin flashed the new bootloader, i kept getting a black screen. OK no biggie, factory flash, re-root look for another ROM, except this time, I'm looking for a pre -rooted factory ROM. I came across a lollipop one, 0A8, was hoping for 0G5, but will deal with that later. Of course the ROM had to have, I guess for lack of a better word, a custom bootloader, or index, to tell the phone it's okay to use this software right? So now have lollipop, but have lost TWRP on boot. I'm not sure as to why this has happened, but it's a real pain I want to install and use ROMs on this phone. If I need to downgrade to have TWRP, that's no big deal. So here I am a lollipop stock ROM, rooted wihout TWRP, ugh.
Is there anyone who can help me find a solution to this, it's driving me mad. I just want to have a recovery installed and the klte version won't install. It must be a lollipop thing, but I would love to have cm12.1 when it comes out. And why does this stupid script keep popping up while I'm trying to type this. Just thought I'd share my frustrations or see if there is a way to get TWRP on lollipop?
Thanks in advance.
Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/verizon-galaxy-s5/help
The experts there may be able to help. Good luck.
U cannot load into twrp or safestrap above the n12 kernal.
If you want to access your recovery, you could try loading the n12 kernal via odin. Then use your recovery. Then reflash the right kernal for your rom via Odin to return to loading status.
That's what I hear is possible- you sound like you can rebuild if u get in trouble.
As for CM - we don't have an unlocked bootloader so that's unfortunately killing it at this time. We are stuck on stock rooted TW roms, or slight variations of TW roms.
Sent from my SM-G900V using XDA Free mobile app
So Last night I decided to Flash the 5.1.1 update to my Note 4. I made a full nandroid backup via TWRP
before I updated. Well, I updated successfully, but soon found the method I was planning to use to root had been
withdrawn and could no longer be used.
So I thought I would just run TWRP and restore the back up I made and go back to 5.0.1. Well the restore seemed to work, however now I'm stuck in a
bootloop. I just get the Note Logo and then a reboot. I tried flashing SuperSU via TWRP (as my previous setup was rooted) However
that hasn't helped.
Anyone got any ideas?
did you flash the latest COJ5 build of 5.1.1? if so then there is no way to downgrade as the new bootloader in COJ5 build is locked.
dork997 said:
did you flash the latest COJ5 build of 5.1.1? if so then there is no way to downgrade as the new bootloader in COJ5 build is locked.
Click to expand...
Click to collapse
Yeah, it was that build. Damn.
(Man, That gives me the sh!ts. I searched for the difference between COI1 and COJ5 and could find anything.. Grrrrrr.)
Was the COI1 build locked as well?
EDIT: it appears not.
Suppose flashing the COI1 over the COJ5 will do nothing?
BrikHaus said:
Yeah, it was that build. Damn.
(Man, That gives me the sh!ts. I searched for the difference between COI1 and COJ5 and could find anything.. Grrrrrr.)
Was the COI1 build locked as well?
EDIT: it appears not.
Suppose flashing the COI1 over the COJ5 will do nothing?
Click to expand...
Click to collapse
Well i dont know about COl1...all i know is that once you update to COJ5 there is no way going back to any previous backup or firmware...not even via ODIN as it has locked the bootloader. You are not alone many people have complained about this here in the previous few days but there is no solution for this. Just flash stock COJ5 via Odin and you will be able to get your phone to working.
Yeah I did that this morning. Back on 5.1.1.
Wouldn't mind so much if there was root / xposed.
COI1 is 5.1.1 but apparently not locked Bootloader. So I assume its too late for me. Mine is now locked.
But SO ANGRY! Saw the two updates and tried to Google the difference between the two, and couldn't find anything so went
with COJ5 as that was at the top. Kicking myself for my stupidity, and Cursing Samsung for locking this.
Thanks for your comments. Help has been much appreciated.
I can not flash over recovery when I try to flash the recovery will start again and again, please help
I was able to flash the latest TWRP without any issue, so I'm not sure how to help you..
I guess my biggest concern is whether I will be able to Root on 5.1.1 with this new crap bootloader.
I'm Ok with running Stock.. But Root is a deal breaker for me. Anyone know if this is being worked on?
First of all sorry for my english.
I hope someone can help with this
The thing is that the screen burn issue showed up, so i've seen a guide to remove it (kernel auditor and that..) So i was going for root my device (Nougat)
and i've unlocked my bootloader and installed twrp but the thing is that i didnt installed Elemental Kernel, and ****ed it up installing superSU..
So i decided to install another rom, coming from npj25.93-14 , i've installed Extended AOSP 7.1.2. And everything it's ok but the volume isn't working properly, so i want to install my previous rom npj25.93-14 (Nougat) from the stock xt1622 how can i do it?
Cant find any rom of npj25.93-14 xt1622 , even if i found one, i dont really know the steps to do it properly ( i mean: flashing with twrp, or fastboot.. )
Can someone please make a little "guide"?, i fell so lost right now
Alexmofu said:
First of all sorry for my english.
I hope someone can help with this
The thing is that the screen burn issue showed up, so i've seen a guide to remove it (kernel auditor and that..) So i was going for root my device (Nougat)
and i've unlocked my bootloader and installed twrp but the thing is that i didnt installed Elemental Kernel, and ****ed it up installing superSU..
So i decided to install another rom, coming from npj25.93-14 , i've installed Extended AOSP 7.1.2. And everything it's ok but the volume isn't working properly, so i want to install my previous rom npj25.93-14 (Nougat) from the stock xt1622 how can i do it?
Cant find any rom of npj25.93-14 xt1622 , even if i found one, i dont really know the steps to do it properly ( i mean: flashing with twrp, or fastboot.. )
Can someone please make a little "guide"?, i fell so lost right now
Click to expand...
Click to collapse
If you didn't make a backup then you need to grab the stock MM firmware for your XT1622, flash it via fastboot, and take the OTA.
Maybe if you used a cool little tool called "le Google" along with the forums here on XDA, you wouldn't have these issues. There are so many goddamn guides that it's almost ridiculous.
negusp said:
If you didn't make a backup then you need to grab the stock MM firmware for your XT1622, flash it via fastboot, and take the OTA.
Maybe if you used a cool little tool called "le Google" along with the forums here on XDA, you wouldn't have these issues. There are so many goddamn guides that it's almost ridiculous.
Click to expand...
Click to collapse
I've been searching for a long time, and some people said that i cant get OTA if i downgrade to MM..
Alexmofu said:
I've been searching for a long time, and some people said that i cant get OTA if i downgrade to MM..
Click to expand...
Click to collapse
If you're rooted, then yea, OTAs won't work. If you're not OTAs should work fine- just restore stock MM, take the OTA to N and then root.
Also, you could give RevivorOS a shot- it's based off the latest 14-4 N build and works fine on all G4/G4+ models.
negusp said:
If you're rooted, then yea, OTAs won't work. If you're not OTAs should work fine- just restore stock MM, take the OTA to N and then root.
Also, you could give RevivorOS a shot- it's based off the latest 14-4 N build and works fine on all G4/G4+ models.
Click to expand...
Click to collapse
Thanks!
negusp said:
Maybe if you used a cool little tool called "le Google" along with the forums here on XDA, you wouldn't have these issues. There are so many goddamn guides that it's almost ridiculous.
Click to expand...
Click to collapse
True that! But there are probably 10x as many people (not always noobs), who have made the same or similar mistakes. We all tend to get in a hurry at times and have regrets. Patience is an honorable virtue, both for the student and the teacher. Just sayin'.