So...it's been about 6 months now since first tried to gather the in for I needed in order to get my device back to date.
.When I first got te device...it did an ODA, and I ODINed a root in and installed TWRP.
So I'm essentially on build --info posted below via screenshot-- and am trying to install the New Iron ROM. I've received messages from people whobsaid that I need to flash the boot loader before I can go from stock 5.0.2 to the latest IronROM/Ironkernel.....and I've seen messages that I then purpose of flashing a boot loader for people trying to get on a particular ROM, is so that "they ***can get*** the 5.0.2 boot loader-- if you're on 5.02....you can install 5.0.2 Roms freely...as long as you have the 5.02 boot loader (which you must have because you're running 5.0.2.) The reason this boot loader mess is such a big deal is because some people want to install custom LOLLIPOP ROMs, when they have only Evey installed Kit Kat ROMs. So the first time you flash a lollipop FROM you have to flash the botloader....but once you do that you can flash everything from lollipop and up (because the new lollipopband marshmallow builds use the stock code from lollipop at the moment).
I'm a competitive hearthstone player ad access to a computer and Odin is far away right now.....so if I could do this all through tarp.....or just unfreeze the update app, let it update, and reroot, if possible.....and then I could just flash what I wanted...but I'm notbsure whose right. Most of Tue devices I've handled all my rom flashing through TWRP, with no care I the world for what baseband I had. It was never an issue.
I've posted a screenshot of the build I'm on below (am using a custom kernel for sound boost)....
Would like to install this --
http://ift.tt/1xOMEud
So....I'm on a 5.02 FROM. A stock one. Is it a different build than the one that FROM is based on? It looks like it. But should have the right boot loader! Right? In this case... I can just wipe/flash with tarp! No odin /boot loader futzing about needed. And I can use the other some too right? The CM or Pad Man ones? Because they're using the 5.02 code from Samsung for our device to get those build working?
/facepalm.. .
Or.....if every time a new from based on a new 5.0.2 build comes out, I have to odin a new boot loader so that I can now install roms made from a different base...even though what really mattersnis that I have a 5.02 boot loader already....
I though that the version number was what mattered. IF 6.0 came out tomorrow and everyone started making roms based upon the stock 6.0 code, id have to get the same version number boot loader as they had in the source material.
Conflicting messages >.<
I'm on a Completely stock, rooted 5.02 ROM. U1BOCC
The from I want to install appears to be 5.02 based on BOJJ.
What do I do now?
.When I first got te device...it did an ODA, and I ODINed a root in and installed TWRP.
So I'm essentially on build --info posted below via screenshot-- and am trying to install the New Iron ROM. I've received messages from people whobsaid that I need to flash the boot loader before I can go from stock 5.0.2 to the latest IronROM/Ironkernel.....and I've seen messages that I then purpose of flashing a boot loader for people trying to get on a particular ROM, is so that "they ***can get*** the 5.0.2 boot loader-- if you're on 5.02....you can install 5.0.2 Roms freely...as long as you have the 5.02 boot loader (which you must have because you're running 5.0.2.) The reason this boot loader mess is such a big deal is because some people want to install custom LOLLIPOP ROMs, when they have only Evey installed Kit Kat ROMs. So the first time you flash a lollipop FROM you have to flash the botloader....but once you do that you can flash everything from lollipop and up (because the new lollipopband marshmallow builds use the stock code from lollipop at the moment).
I'm a competitive hearthstone player ad access to a computer and Odin is far away right now.....so if I could do this all through tarp.....or just unfreeze the update app, let it update, and reroot, if possible.....and then I could just flash what I wanted...but I'm notbsure whose right. Most of Tue devices I've handled all my rom flashing through TWRP, with no care I the world for what baseband I had. It was never an issue.
I've posted a screenshot of the build I'm on below (am using a custom kernel for sound boost)....
Would like to install this --
http://ift.tt/1xOMEud
So....I'm on a 5.02 FROM. A stock one. Is it a different build than the one that FROM is based on? It looks like it. But should have the right boot loader! Right? In this case... I can just wipe/flash with tarp! No odin /boot loader futzing about needed. And I can use the other some too right? The CM or Pad Man ones? Because they're using the 5.02 code from Samsung for our device to get those build working?
/facepalm.. .
Or.....if every time a new from based on a new 5.0.2 build comes out, I have to odin a new boot loader so that I can now install roms made from a different base...even though what really mattersnis that I have a 5.02 boot loader already....
I though that the version number was what mattered. IF 6.0 came out tomorrow and everyone started making roms based upon the stock 6.0 code, id have to get the same version number boot loader as they had in the source material.
Conflicting messages >.<
I'm on a Completely stock, rooted 5.02 ROM. U1BOCC
The from I want to install appears to be 5.02 based on BOJJ.
What do I do now?
from xda-developers http://ift.tt/1XRgwgW
via IFTTT
No comments:
Post a Comment