Related
keep getting the error assert failed: getprop ("ro.product.device") == " d2tmo" | | getprop (ro.build.product") = = "d2tmo " E: error in/sdcard/cm10.1 etc.... message when trying to flash any, suggestions ?? happens with the cm10 official build and kangs (euroskank) and paranoid android builds and etc... only build I can get to work is the aokp nightlys from the xda site
Edit/solved: did a lil more searching and found the soloution just had to flash the latest cwm from rom manager. Going to leave this up incase anyone else has the problem
I've done everything that it says to do in the install directions, I've read through the troubleshooting, nothing works. I persistently dead end with this:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Dirty RootBox
ROM Version : v2.0
ROM Author : mlaws90
Device : grouper
Start at : Sun Mar 15 12:15:40 1970
==========================
====Dirty RootBox v2.0=====
=======By:mlaws90=========
=========AROMA==========
=======Pie Controls=======
Build Date: Sat Feb 16 13:15:24 CST 2013
>>-Checking Device...
script aborted: assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
Installer Error (Status 7)
End at : Sun Mar 15 12:15:40 1970
I'm downloading this from the link that I found here. I'm trying to upgrade from Root 66 (JB 4.1.1), I've wiped EVERYTHING off my phone (excluding the internal and external user storage) and I still have this issue. For s$&ts and giggles, I tried installing DRB over R66 and still get the same error. It doesn't matter what options I do or don't select, or what kernel I choose. I even bothered to trip the counter and try flashing from ODIN - which left me staring at the GS3 boot logo for an hour before I decided to abandon and restore my back up.
How do I make this work on my SGH-T999?
Is your recovery up to date?
Sent from my SGH-T999 using xda premium
seattlestexan said:
script aborted: assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
assert failed: getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper"
Click to expand...
Click to collapse
Looks like you are trying to flash a rom that isn't for your phone. Looks like it's actually for a tablet. Lucky for you the author put an assert check in before the flash. Because you almost bricked your phone.
Aerowinder said:
Looks like you are trying to flash a rom that isn't for your phone. Looks like it's actually for a tablet. Lucky for you the author put an assert check in before the flash. Because you almost bricked your phone.
Click to expand...
Click to collapse
True.
I don't get it. I see ROM's listed as for the T999, then they either don't work, or they end up being for something else. I was looking for a good JB4.2.2 ROM, and this was listed for the T999.
I just want a good 4.2.2 ROM with plenty of options for personalisation. I'm thinking that's too much to ask for. Codename Android is the closest to what I want, but it doesn't work with the T999 apparently.
Any suggestions?
Here are your choices for 4.2.2: http://forum.xda-developers.com/forumdisplay.php?f=1690
I've been using CM 10-10.1 since it became available.
seattlestexan said:
True.
I don't get it. I see ROM's listed as for the T999, then they either don't work, or they end up being for something else. I was looking for a good JB4.2.2 ROM, and this was listed for the T999.
I just want a good 4.2.2 ROM with plenty of options for personalisation. I'm thinking that's too much to ask for. Codename Android is the closest to what I want, but it doesn't work with the T999 apparently.
Any suggestions?
Click to expand...
Click to collapse
PAC is pretty heavy in the customization field and it is a 4.2.2 ROM.
Sent from my SGH-T999 using Tapatalk 2
I'm very surprised no one has attempted to build ChameleonOS for our phone yet. I've been running it on my n7 and it's fantastic. (It's everything I liked about MIUI without all the stuff I hated. MIUI theme engine built on top of aosp).
Just curious to any devs out there, anyone plan on giving it a try? (I've been thinking of trying to build it myself, but I just don't have the free time I used to.)
mstrk242 said:
I'm very surprised no one has attempted to build ChameleonOS for our phone yet. I've been running it on my n7 and it's fantastic. (It's everything I liked about MIUI without all the stuff I hated. MIUI theme engine built on top of aosp).
Just curious to any devs out there, anyone plan on giving it a try? (I've been thinking of trying to build it myself, but I just don't have the free time I used to.)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2167031
I think this is the same thing. Not my thing I like the CM 10 theme engine
CARBON NIGHTLIES. | KROZ BROWN Theme | Crack Flasher
RonnieRuff said:
http://forum.xda-developers.com/showthread.php?t=2167031
I think this is the same thing. Not my thing I like the CM 10 theme engine
CARBON NIGHTLIES. | KROZ BROWN Theme | Crack Flasher
Click to expand...
Click to collapse
Not to take anything away from Avatar rom (it's a very cool rom) but it's not the same. Well, I haven't really attempted building a device tree on this device yet, I suppose it's time to attempt it myself. (Extremely cool rom, if you haven't read about it, I'd suggest googling it, they have a website.)
mstrk242 said:
Not to take anything away from Avatar rom (it's a very cool rom) but it's not the same. Well, I haven't really attempted building a device tree on this device yet, I suppose it's time to attempt it myself. (Extremely cool rom, if you haven't read about it, I'd suggest googling it, they have a website.)
Click to expand...
Click to collapse
It shows there's an unofficial Note 2 build on their website.
http://forums.chameleonos.org/threads/4-2-2-chameleonos-chaos-unofficialy-offical-4-8.157/
thedrmonkey said:
It shows there's an unofficial Note 2 build on their website.
http://forums.chameleonos.org/threads/4-2-2-chameleonos-chaos-unofficialy-offical-4-8.157/
Click to expand...
Click to collapse
Sadly that's for the verizon version.
I gave it a go and compiled it myself. I got everything working, but the ril. Wifi, all that. But with no radio, it's not very useful as a phone. I'll keep goofing around with it and see if i can figure out what I missed.
Well, I got the tree setup and got it to compile. Anyone interested in it? I won't support it, or update it, but I'll upload the version I built if anyone wants to play around with it.
ill give it a try it seems interesting
Ok, here's ChameloenOS for the t0ltetmo. All I did was compile it, all credit goes to the chameleon os team (and some credit to the cyanogenmod team as well, I borrowed a lot of their device and vendor files, as well as their kernel.)
http://www.4shared.com/zip/sqL7jzEC/cos-07-20130519-UNOFFICIAL-t0l.html
MD5 - 9b85d7e35fa86989b3b2fe5d23024fc3
I have only been testing for a couple hours, but so far everything works. (To add themes, download chameleon or miui themes, and place them in the ChaOS/theme folder on your sdcard.) All cm10 bugs will also apply here as well. Have fun, I'm a big fan of this rom.
Thank you I'm downloading right now. I will flash it in a few after I do some research on plasti-dipping my car lol. You should offer to be a maintainer we need more variety for our phones.
mstrk242 said:
Ok, here's ChameloenOS for the t0ltetmo. All I did was compile it, all credit goes to the chameleon os team (and some credit to the cyanogenmod team as well, I borrowed a lot of their device and vendor files, as well as their kernel.)
http://www.4shared.com/zip/sqL7jzEC/cos-07-20130519-UNOFFICIAL-t0l.html
MD5 - 9b85d7e35fa86989b3b2fe5d23024fc3
I have only been testing for a couple hours, but so far everything works. (To add themes, download chameleon or miui themes, and place them in the ChaOS/theme folder on your sdcard.) All cm10 bugs will also apply here as well. Have fun, I'm a big fan of this rom.
Click to expand...
Click to collapse
Thanks bill
deeznutz1977 said:
Thanks bill
Click to expand...
Click to collapse
Lol, you're welcome. (Caught me off guard for a second, forgot that I use my real name as my login on my laptop, and that would've compiled into the kernel name )
Working great so far. Much appreciated
Sent from my SGH-T889 using xda premium
If only I have skills and knowledge to build roms and kernels
Sent from my SGH-T889 using xda premium
Thank for your efforts. Love this ROM really hope some one who knows helps you maintain it.
Im trying to flash I git the buildprop error. Ive tried to change it but the changes wont stick... strange
Sent from my SGH-I317 using xda app-developers app
philupjfry said:
Im trying to flash I git the buildprop error. Ive tried to change it but the changes wont stick... strange
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I'm assuming you're using cwm, not twrp? This can usually be fixed by doing the following:
In the update zip, navigate to:
META-INF/com/google/android. Edit the file updater-script. Remove the following:
assert(getprop("ro.product.device") == "t0lte" || getprop("ro.build.product") == "t0lte" ||
getprop("ro.product.device") == "t0ltexx" || getprop("ro.build.product") == "t0ltexx" ||
getprop("ro.product.device") == "GT-N7105" || getprop("ro.build.product") == "GT-N7105" ||
getprop("ro.product.device") == "t0ltedv" || getprop("ro.build.product") == "t0ltedv" ||
getprop("ro.product.device") == "GT-N7105T" || getprop("ro.build.product") == "GT-N7105T" ||
getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" ||
getprop("ro.product.device") == "SGH-I317" || getprop("ro.build.product") == "SGH-I317" ||
getprop("ro.product.device") == "t0ltetmo" || getprop("ro.build.product") == "t0ltetmo" ||
getprop("ro.product.device") == "SGH-T889" || getprop("ro.build.product") == "SGH-T889" ||
getprop("ro.product.device") == "t0ltecan" || getprop("ro.build.product") == "t0ltecan" ||
getprop("ro.product.device") == "t0ltevl" || getprop("ro.build.product") == "t0ltevl" ||
getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M");
Save it, and reflash. I've noticed cwm has a lot of problems with the getprop command.
Also, i'm glad you said something, and I took a look at the updater script. There are way too many device's that it'll let flash this, there should only be two listed. I'm going to fix that, and re-upload it. (I'll remove all getprop commands, so it'll flash on cwm as well. However, I hope people who don't have the tmobile version of this won't flash this new update, because I'm essentially removing safety checks.
Give me a few to edit it, and I'll re-up it. (There hasn't been any activity in their github, so there's been no reason to update the build.)
Ok, here's an updated build with the getprop's removed. Hopefully this'll fix the problem with installing under cwm.
http://www.4shared.com/zip/V2lGK6cZ/cos-07-20130519-UNOFFICIAL-t0l.html
MD5 - 2289410e33991038474727ff9eb56091
Let me know if it works for you.
This may be a dumb question bit I can't seen to find the answer. I've seen gee roms and ls970 roms. What's the difference between the two? Why should I choose one over the other?
Sent from my LG-LS970 using Tapatalk
spleef said:
I can try ...k so the ls970 is official cm sources shelnutt2 put together based off the gproj is usable only on the sprint lgog
The geehrc (international lgog) and the geespr (sprint lgog) are based in the mako and put together by xboxfanj... currently x has combined the two sources (geehrc and geespr) into one source (gee) for both making the one zip built with gee flashable on both variants...
The whole cwm twrp issues are the differences n each sources and or ROMs way to build the updater script...
And yes some roms play nicer with cm sources than they do aosp sources and vice cersa.. so saying that cm is well obviously cm based sources where as xboxfanj sources are closer to or are aosp
Hope I'm at least somewhat making sense
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
xboxfanj said:
LS970 ROMs are built from CM's Nexus 4 4.2.2 hybrid with stock 4.1.2.
GEE/SPR/HRC are built from the Nexus 4 4.4.2 source (more up to date and optimized) with only changes for our hardware such as NFC.
geespr is sprint only, geehrc is international only, and gee combines the two so both devices can run the same build. Gee is the future of mako-based ROMs and eventually, there won't be any geespr or geehrc roms. Those are being phased out.
Click to expand...
Click to collapse
Hope this helps...its from the Liquid Smooth thread.
Sent from my Optimus G using xda app-developers app
elvyrorie said:
This may be a dumb question bit I can't seen to find the answer. I've seen gee roms and ls970 roms. What's the difference between the two? Why should I choose one over the other?
Sent from my LG-LS970 using Tapatalk
Click to expand...
Click to collapse
let's see If I can get this right...
Our phone is a bit confusing because the developers couldn't agree on one name.
The official names from the stock ROM build.prop:
Code:
ro.product.model=LG-LS970
ro.product.name=geehrc4g_spr_us
ro.product.device=geehrc4g
Just before Team CodeFire unlocked the many Optimus G variants, the first new name the they came up with for our device was "geebus".
And then many names followed...
Example from CM11 updater script:
Code:
assert(getprop("ro.product.device") == "geebus" || getprop("ro.build.product") == "geebus" ||
getprop("ro.product.device") == "geebusc" || getprop("ro.build.product") == "geebusc" ||
getprop("ro.product.device") == "geehrc" || getprop("ro.build.product") == "geehrc" ||
getprop("ro.product.device") == "geehrc4g" || getprop("ro.build.product") == "geehrc4g" ||
getprop("ro.product.device") == "gee_sp" || getprop("ro.build.product") == "gee_sp" ||
getprop("ro.product.device") == "geehrc_sp" || getprop("ro.build.product") == "geehrc_sp" ||
getprop("ro.product.device") == "geehrc4g_spr_us" || getprop("ro.build.product") == "geehrc4g_spr_us" ||
getprop("ro.product.device") == "ls970" || getprop("ro.build.product") == "ls970" ||
getprop("ro.product.device") == "jeebus" || getprop("ro.build.product") == "jeebus" ||
getprop("ro.product.device") == "jeebusc" || getprop("ro.build.product") == "jeebusc"
The confusion behind "gee" and "ls970" is because there are two main ANDROID bases for us and they are incompatible with each other.
<History>
While Team CodeFire were rolling with the "geebus" name, early attempts to port AOSP and CyanogenMOD to the many Optimus G variants used the Nexus 4 (Mako) ROM & kernel as a base with optimus g stuff mixed in.
Since we were the odd man out with the 13MP camera, our name had to change to be more specific; back to "geehrc4g" and then "geespr".
The "hybrid Mako" base was a little unstable and camera auto-focus was not working for us.
CyanogenMOD requires that everything works to become OFFICIALLY supported.
The "gproj" team working on OFFICIAL CyanogenMOD status for the international variant (e975) used their own device as a base and was the first to become officially supported by several months.
Team CodeFire followed suit and scratched (but not abandoned) the hybrid mako base and used our own device (ls970) as a starting point for the remaining variants.
We also changed name from "geespr" to "ls970" because CyanogenMOD requires you to use your device's model name (or because the code base change, IDK).
While things became rock stable we were still having the camera auto-focus problem (but was not a stopping issue).
ls970 and e970 became officially supported by CyanogenMOD with the "ls970-common" base.
The e975 variant has the same camera as we do and their auto-focus works.
We moved to the "gproj" base while still keeping a few device specific things separated for the other variants (like camera drivers).
Some developers use the CM/gproj base to port ROMs to our device and usually refer to "ls970"
Some developers also used the hybrid Mako base to port ROMs to our device and and usually refer to "geespr" (and now "gee")
The hybrid Mako base (still not abandoned) has become rock stable and has the auto-focus problem fixed.
More recently the hybrid Mako base developers have unified the code for some of the variants and now we are "gee".
</history>
So which is generally the more stable of the two?
Sent from my LG-LS970 using Tapatalk
elvyrorie said:
So which is generally the more stable of the two?
Sent from my LG-LS970 using Tapatalk
Click to expand...
Click to collapse
I've read it depends on your phone lol. Some have better experience with gproj based ROMs others have better experience with Mako based ROMs...
Sent from my Optimus G using xda app-developers app
MikeEx said:
let's see If I can get this right...
Our phone is a bit confusing because the developers couldn't agree on one name.
The official names from the stock ROM build.prop:
Code:
ro.product.model=LG-LS970
ro.product.name=geehrc4g_spr_us
ro.product.device=geehrc4g
Just before Team CodeFire unlocked the many Optimus G variants, the first new name the they came up with for our device was "geebus".
And then many names followed...
Example from CM11 updater script:
Code:
assert(getprop("ro.product.device") == "geebus" || getprop("ro.build.product") == "geebus" ||
getprop("ro.product.device") == "geebusc" || getprop("ro.build.product") == "geebusc" ||
getprop("ro.product.device") == "geehrc" || getprop("ro.build.product") == "geehrc" ||
getprop("ro.product.device") == "geehrc4g" || getprop("ro.build.product") == "geehrc4g" ||
getprop("ro.product.device") == "gee_sp" || getprop("ro.build.product") == "gee_sp" ||
getprop("ro.product.device") == "geehrc_sp" || getprop("ro.build.product") == "geehrc_sp" ||
getprop("ro.product.device") == "geehrc4g_spr_us" || getprop("ro.build.product") == "geehrc4g_spr_us" ||
getprop("ro.product.device") == "ls970" || getprop("ro.build.product") == "ls970" ||
getprop("ro.product.device") == "jeebus" || getprop("ro.build.product") == "jeebus" ||
getprop("ro.product.device") == "jeebusc" || getprop("ro.build.product") == "jeebusc"
The confusion behind "gee" and "ls970" is because there are two main ANDROID bases for us and they are incompatible with each other.
<History>
While Team CodeFire were rolling with the "geebus" name, early attempts to port AOSP and CyanogenMOD to the many Optimus G variants used the Nexus 4 (Mako) ROM & kernel as a base with optimus g stuff mixed in.
Since we were the odd man out with the 13MP camera, our name had to change to be more specific; back to "geehrc4g" and then "geespr".
The "hybrid Mako" base was a little unstable and camera auto-focus was not working for us.
CyanogenMOD requires that everything works to become OFFICIALLY supported.
The "gproj" team working on OFFICIAL CyanogenMOD status for the international variant (e975) used their own device as a base and was the first to become officially supported by several months.
Team CodeFire followed suit and scratched (but not abandoned) the hybrid mako base and used our own device (ls970) as a starting point for the remaining variants.
We also changed name from "geespr" to "ls970" because CyanogenMOD requires you to use your device's model name (or because the code base change, IDK).
While things became rock stable we were still having the camera auto-focus problem (but was not a stopping issue).
ls970 and e970 became officially supported by CyanogenMOD with the "ls970-common" base.
The e975 variant has the same camera as we do and their auto-focus works.
We moved to the "gproj" base while still keeping a few device specific things separated for the other variants (like camera drivers).
Some developers use the CM/gproj base to port ROMs to our device and usually refer to "ls970"
Some developers also used the hybrid Mako base to port ROMs to our device and and usually refer to "geespr" (and now "gee")
The hybrid Mako base (still not abandoned) has become rock stable and has the auto-focus problem fixed.
More recently the hybrid Mako base developers have unified the code for some of the variants and now we are "gee".
</history>
Click to expand...
Click to collapse
Mostly correct, but there's a couple things I'd like to point out. #1: Geebus was not used on ROMs; it was only used by Tyler on the first recoveries. Also, Team Codefire is really only relevant for the recovery and bootloader unlock; Device sources were made primarily by synergy, Shelnutt2, rlasalle15, houst0nn, chadouming, and I. The first ROMs based on the stock kernel were geehrc_sp or geehrc4g_spr_us. Soon after this, the Canadians (chadouming, Houst0nn, and Thracky) found that mako kernels booted and worked fairly well on their phones, but along with dvhexer, they had to change some things for our device, such as NFC. Unfortunately for the US variants, our firmware was too different for this to work. Using Canadian firmware did work, but flashing partitions isn't always the safest. Luckily, LG's JB firmware fixed this issue and allowed us to use mako-based kernels. Everything was going well, until we found that people had EFS issues. Seth made a script that would backup EFS and allow you to restore and also created a workaround telephony framework. After that, the only major issue was autofocus. At this point, there were four device repos: Canada, Sprint, AT&T, and International). Meanwhile, Ricardo at CM created a hybrid of stock and the current mako sources (4.2) for the International variant (e975). A couple months later, Seth rebased to his sources, still 4 device sources, but this time named based on model numbers (e973, e970, e975, and ls970) Around this time, I created TeamPlaceholder, with houst0nn, chadouming, and bbelos to create a kernel and device sources based on the latest Qualcomm CodeAurora jb_2.5 sources. Performance was awesome, however, we never got 13MP camera to work, so none of these builds were widely released, however, this is where I created the names for geeb and geespr, mainly out of laziness because having to type geehrc4g_spr_us every time I wanted to build was a pain. As a team, we were also able to merge the AT&T and Canadian variants by enabling SD support for both, since it doesn't negatively impact anything and is the only difference, is just less general maintenance. and meant we only needed to make 3 builds. Eventually, Google also rebased to jb_2.5 for their 4.3 mako kernel, so we scrapped TPH and worked on that, adding only the necessary hardware specific changes from stock (as opposed to all of LG's stock changes, which GPROJ did). Performance was just as good as TPH, everything worked (except autofocus, which was fixed a few months ago by faust93), all was well. Throughout this time, we have updated to the most recent AOSP, since it is fairly easy because we did not deviate much from it, however, gproj did not rebase to jb_2.5 or the AOSP 4.3 kernel, so they are a bit behind us in terms of optimizations. Google did a much better job on the 4.3 kernel than 4.2, so as such, mako-based ROMs should have a bit better performance and are generally more up to date. KitKat was fairly easy to merge into our sources, so we did so fairly quickly. At this point, Chadouming, houst0nn, and I maintained mako based sources, however, both of them jumped ship, leaving me in charge of most source maintenance. In this time, I became the official Vanir maintainer and have made some kernels. Eventually, I noticed that if the Nexus 5 could run GSM or CDMA on the same sources, we could too, so a month ago, I decided to merge our device and the International variant (geehrc) into one device: gee, using the Nexus 5 sources as reference, meaning that there are only two device sources now on our device: gee and geeb, so all variants can run one of two builds This means that it takes no extra work for someone on AT&T to maintain a ROM for the Canadian variant and vice-versa, same goes for the International and Sprint variants. It has led to great collaboration between the variants and all of you have benefited.
TL;DR: There are two different paths you can take: One closer to stock, but based on an older Nexus 4 4.2 kernel (Gproj) or one with the latest and greatest Nexus 4 4.4.2 sources with only the bare essentials of stock (camera, NFC, etc.)
If you choose stock and Nexus 4 4.2 based, you pick the ls970 ROM.
If you choose Nexus 4 4.4.2 based, you pick the gee ROM.
EDIT: One thing to note: This is the history of the Sprint variant; there are other great devs for the AT&T and International variants, such as arcardinal and dvhexer, but they did not work across all variants, so it's not quite as relevant to us.
@xboxfanj awesome explanation bro!
Sent from my LG-LS970 using xda app-developers app
I saw that Rogers/Bell/Telus released a new carrier update for the SGH-I747M this month. I'd been running CM11, one of the one dailies from earlier in march.
I did a nandroid backup (CWM) then used Odin 3.09 to flash back to the stock ROM.
Stock ROM runs fine and now I'm on baseband/bootloader I747MVLUF0B1, android 4.4.2.
Problem is I can't install any custom ROM's or restore my nandroid backups. ROM or nandroids install OK, but all I get on bootup is the samsung logo for a second then a black screen. Left it all night and nothing.
I've tried several custom ROM's and it's always the same thing. I also tried installing some ROM's with TWRP but no go.
Would anyone know what do I have to do now to get any custom roms to install?
Previous baseband was VLUFNF2
Are you getting an error when installing the custom ROM?
audit13 said:
Are you getting an error when installing the custom ROM?
Click to expand...
Click to collapse
Nah, they go in like buttah....the only thing that concerns me is they seem to install pretty quickly.
No errors at all everything goes like.....wait for it.....clockwork! BOOM! (That's gotta be old in this forum)
This all started because I wanted the most recent bootloader/modem before I jumped to Lollipop.
I'll mention a few other details, in case they're relevant:
- When I first went back to the stock ROM, I forgot to factory reset the phone first. When the phone booted up, I still had all my old apps and data but now running on stock ROM.
- After begging for forgiveness for my ignorance, I then I factory reset the phone from within Android and let it boot. Rebooted into download and installed CWM via Odin. Booted to recovery and installed Supersu 2.46.
- Let phone boot up and check root and everything is working
- Boot into recovery, factory reset, cleared dalvik.
- Then I tried installing Matrixzone's cm-12-20150318-UNOFFICIAL-d2att ROM as my first custom ROM after going back to stock. I now know the way I was going about it was never going to work. I was just changing the build properties from d2att to d2can like the "old days", and I wasn't using TWRP, which I believe is required to get that ROM working as well as a couple of other modem tweaks. On that I would get some error and the ROM would not install.
- I then tried going back to cm11 and that's when all my problems started. I've tried several cm11's, my nandroid's and cyanide-5.0.2-RC-7.5-d2att. I get the same thing on everything except stock ROM.
Phone boots up, displays Sasmung logo for 1 second then goes blank and unresponsive. Can always get into recovery or download or go back to stock but no customs.
While I'd love to get a Lollipop ROM working on this, I'll take anything over Touchwiz.
Even my elderly grandfather, who's never even seen an android device before, told me I had brought great shame to the family by going stock.
Any ideas, anyone?
SuperCoolFool said:
Any ideas, anyone?
Click to expand...
Click to collapse
Could it be as simple as the updater-scripts in the custom roms not taking into account the recent release of the newest bootloader and modem, OB1 .... wait for it .....code named Kenobi?
Check the updater-script on one of the roms you would like to install and see allows your bootloader.
dawgdoc said:
Could it be as simple as the updater-scripts in the custom roms not taking into account the recent release of the newest bootloader and modem, OB1 .... wait for it .....code named Kenobi?
Check the updater-script on one of the roms you would like to install and see allows your bootloader.
Click to expand...
Click to collapse
Thanks for the response, I thought it might be something along those lines, but I had no idea how to find out.
I've looked at the update script for cm-11-20150323-NIGHTLY-d2lte and the last snapshot from december, but I can't see anything that mentions bootloader. Would you happen to know what I'm looking for?
Oh, and BTW, nice one on the OB1...
Were you able to look at the updater scripts? You'll need something like winzip or 7zip to look at the zip file's contents.
The updater script can be opened using a simple text editor. Look for the script in \meta\com\google\android
audit13 said:
Were you able to look at the updater scripts? You'll need something like winzip or 7zip to look at the zip file's contents.
The updater script can be opened using a simple text editor. Look for the script in \meta\com\google\android
Click to expand...
Click to collapse
I looked at the scripts for the most recent d2lte cm11 and also the last snapshot from december.
There's nothing in the script that I can see that mentions bootloader or modem.
I also read up on updater-scripts here:
http://forum.xda-developers.com/showthread.php?t=2377695
But again, nothing I saw mentioned bootloader or modem.
I can upload the contents of one of the scripts if that helps.
Thank you XDA, you're my only hope...
You're right, there is no mention of the bootloader in the ROM's assert lines, only product type and device.
assert(getprop("ro.product.device") == "d2att" ||
getprop("ro.build.product") == "d2att" ||
getprop("ro.product.device") == "d2spr" ||
getprop("ro.build.product") == "d2spr" ||
getprop("ro.product.device") == "d2spi" ||
getprop("ro.build.product") == "d2spi" ||
getprop("ro.product.device") == "d2tfnspr" ||
getprop("ro.build.product") == "d2tfnspr" ||
getprop("ro.product.device") == "d2tmo" ||
getprop("ro.build.product") == "d2tmo" ||
getprop("ro.product.device") == "d2cri" ||
getprop("ro.build.product") == "d2cri" ||
getprop("ro.product.device") == "d2mtr" ||
getprop("ro.build.product") == "d2mtr" ||
getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc" ||
getprop("ro.product.device") == "d2vmu" ||
getprop("ro.build.product") == "d2vmu" ||
getprop("ro.product.device") == "d2vzw" ||
getprop("ro.build.product") == "d2vzw" ||
getprop("ro.product.device") == "d2lte" ||
getprop("ro.build.product") == "d2lte" ||
getprop("ro.product.device") == "d2can" ||
getprop("ro.build.product") == "d2can" ||
abort("This package is for device: d2att,d2spr,d2spi,d2tfnspr,d2tmo,d2cri,d2mtr,d2usc,d2vmu,d2vzw,d2lte,d2can; this device is " + getprop("ro.product.device") + ".");
It looks to me like CM11 just doesn't like the bootloader.
Have you tried flashing CM11 and a custom kernel?
audit13 said:
You're right, there is no mention of the bootloader in the ROM's assert lines, only product type and device.
assert(getprop("ro.product.device") == "d2att" ||
getprop("ro.build.product") == "d2att" ||
getprop("ro.product.device") == "d2spr" ||
getprop("ro.build.product") == "d2spr" ||
getprop("ro.product.device") == "d2spi" ||
getprop("ro.build.product") == "d2spi" ||
getprop("ro.product.device") == "d2tfnspr" ||
getprop("ro.build.product") == "d2tfnspr" ||
getprop("ro.product.device") == "d2tmo" ||
getprop("ro.build.product") == "d2tmo" ||
getprop("ro.product.device") == "d2cri" ||
getprop("ro.build.product") == "d2cri" ||
getprop("ro.product.device") == "d2mtr" ||
getprop("ro.build.product") == "d2mtr" ||
getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc" ||
getprop("ro.product.device") == "d2vmu" ||
getprop("ro.build.product") == "d2vmu" ||
getprop("ro.product.device") == "d2vzw" ||
getprop("ro.build.product") == "d2vzw" ||
getprop("ro.product.device") == "d2lte" ||
getprop("ro.build.product") == "d2lte" ||
getprop("ro.product.device") == "d2can" ||
getprop("ro.build.product") == "d2can" ||
abort("This package is for device: d2att,d2spr,d2spi,d2tfnspr,d2tmo,d2cri,d2mtr,d2usc,d2vmu,d2vzw,d2lte,d2can; this device is " + getprop("ro.product.device") + ".");
It looks to me like CM11 just doesn't like the bootloader.
Have you tried flashing CM11 and a custom kernel?
Click to expand...
Click to collapse
Thx for the reply...
I'm outside my "comfort zone" as it is, my android experience is pretty much limited to using a few CM roms on my Transformer and GS3. I don't know anything about custom kernels unfortunately, but don't mind giving it a try. (I'd need to be pointed in the right direction in terms of how to modify or create.) The most I've ever had to do to get a ROM installed was modify the build properties of a d2att ROM to install on my d2can, before they unified under d2lte.
not sure which kernel @audit13 might have in mind , but i used to use ktoonz kernels on my S3. dont have to modify or create. just flash from recovery just like a ROM. anyway , here's the link if want to give a go. http://forum.xda-developers.com/showthread.php?t=1756776
p.s. OR , may want to wait on audit's recommendations. he's pretty dam wise on what works best.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
not sure which kernel @audit13 might have in mind , but i used to use ktoonz kernels on my S3. dont have to modify or create. just flash from recovery just like a ROM. anyway , here's the link if want to give a go. http://forum.xda-developers.com/showthread.php?t=1756776
p.s. OR , may want to wait on audit's recommendations. he's pretty dam wise on what works best.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Thx for the info...
I did a quick search on custom kernels after @audit13's suggestion and ktoonz is the first one the comes up.
I'll give it a shot in the morning and report back with the results.
May the force be with me...
hope it goes well.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Gentlemen, unfortunately I have to break character because, Great Success!
After a coupla beers and an episode of Homeland, I tried it out LATE last night, but it was a complete total miserable demoralizing soul-shaking utter failure.
Luckily for me, I wasn't hammered enough to be completely useless and I realized the order in which I installed the ROM and kernel was wrong. I need to install the ROM first then the kernel, not the other way around which is what I did the first time. (Makes sense as the ROM contains a kernel as well.)
By this time it's 1:30am and I'm cooked. Rolled out of bed this am, installed ROM then kernel and It's Alive! Restored my last nandroid and all is well in the world.
Thank you very much to @audit13, @dawgdoc and @mrrocketdog for all your help, it's greatly appreciated.
Now in a couple of days, I'm gonna push my luck and try one of the Lollipop roms. My elderly grandfather piped up again and said I'm just asking for trouble.
I told him, I find your lack of faith disturbing...
yahoo. :thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Way to go, glad to hear of your success. :highfive:
Hopefully your elderly grandfather will allow you to attend family gatherings once you are off stock.
Small update in case anyone else has the same issues...
Well, I tried those Android 5.02 roms, matrixzone and Cyanide a couple days ago, and neither would boot up, and I installed ktoonsez kernel with both and I was using TWRP as my recovery. TWRP is supposed to be required to install those roms, but it gives me a problem once in a while where it won't list the contents of my sd card. I prefer cwm just because it always works, never tried philz or any others.
Anyways, I wanted a clean install anyways, so I just tried wiping the phone, installing the lastest nightly cm11 and the ktoonsez kernel but my wifi and cell would never work.
I ended up going back to stock to get wifi and cell back as it wouldn't work on any roms.
Even my nandroids wouldn't work anymore, it was driving me crazy, as I had a call to make and no other way of making it.
At some point after trying all day and getting nowhere, I restored my nandroid and forgot ktoonsez kernel and it booted, which really surprised me as that kernel is what saved got my phone to boot back up in the first place.
Didn't care really, wifi and cell was finally working and after a day of messing around I didn't want to think about it anymore.
Today I wanted to try some of the ktoonsez features (can you tell I'm bored with my S3 yet? Not sure what to get now that Samsung ruined the S6. Leaning towards the Oneplus One, they're not shipping to can but I have friends in US), so I install the kernel, and it breaks my wifi and cell.
I custom restored the boot partition from my nandroid to get rid of ktoonsez and get my wifi and cell back.
I never thought in the midst of all this set of troubles ktoonsez would be the issue when it just finished saving my butt.
I'll do some poking around over in that forum and see if anyone had similar issues. I'd still like to try it out as it has some cool features. FYI, I'm trying the AOSP version of the kernel.
As it stands, I'm running the latest cm11 nightly installed via CWM recovery, over my nandroid, without ktoonsez. Not sure why I can't install ktoonsez anymore. I'll do the clean install some other day.
Haven't given up on Android 5 yet, I want Android Auto!!! Can't WAIT to slam that into my dashboard!
thanks for the update. i'm sure it will help someone.
"all i can really do , is stay out of my own way and let the will of heaven be done"
ktoonsez kernel
I think I may have a lead on the ktoonsez kernel issue.
He has two makes of the kernel for the SGS3. One is for AOSP/CM based ROMs. The other is for TouchWiz based ROMs. The kernels are not interchangeable, you must use the correct one for the ROM you are on. So if it worked for a CM variant it will not work when you go back to TouchWiz.