Related
Hello I'm a newb!
I'm sorry, but this is the unfortunate state I find myself in.
When I first found this site, what I was expecting to find was a ICS for my phone. I could not have guessed what I would learn here. I had no idea I had a counter in my phone to worry about when installing open sourced roms? Next after much more reading I am to learn the source code Google releases is not complete, and uses binary drivers? Now I am to learn about CIQ, and my phone is spying on me? Wow!
Before I say anything else I want to express my thanks to this community. This has been such a resource I had no idea that it would be when I started. Thank you!
Now on to my question that after learning about all of that I don't seem to have a clear answer to. What I wanted when I first considered getting an Android phone, was to build from source, and run my own rom. I still want this, even more so since I learned about CIQ.
1. Due to the counter on my phone
2. I am to understand multiple images that make the phone work (boot, firmware, system)
3. The binary drivers.
Is this at all a reasonable goal?
Are there more flash images that I haven't read about yet?
Would having a direct from Google rom even be desirable?
I own a stock SGH-I777, I have done nothing to it yet.
Lastly about this site:
Is there anything you think I should read about on the forums?
Any language I should know, as in what does hellraiser imply/mean?
Any Android experience you think might benefit a could be developer?
Counter can be reset and avoided all together.
Sorry I don't know much about AOSP building, but your better off starting with compiling CM and learn from there unless you are really experienced in coding.
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source. Ty for reminding me.
NEME5I5 said:
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source.
Click to expand...
Click to collapse
AT&T Galaxy S2 SGH-I777 has never had CIQ.
LiLChris06 said:
AT&T Galaxy S2 SGH-I777 has never had CIQ.
Click to expand...
Click to collapse
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
NEME5I5 said:
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
Click to expand...
Click to collapse
No it was just some phones, I think the skyrocket had it at some point.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Ok, so I rooted my first cell phone. It would seem heimdall latest has a bug that will brick your phone. (I'm on Mac OS Lion) I used the 1.3.1 instead, and it worked fine.
I saw many more sites, and this was quite easy. The way they showed it was very complex. Since I'm new at this should I wait to try out a ICS rom till after Samsung releases their source code, and the devs have had a chance to get it stable? How complete is the open source version of ICS? There was a note on the fsf.org page that linked me over here that some of the parts were still binary. Is it still true?
I think long term I want to get away from the official releases.
Well, you came this far, might as well flash an ICS rom now. If the leaks are any indication of status, the Samsung release will be pretty stable but the included kernel is problematic because it can cause hardbricking. Besides, you want to get away from stock, and all of the big roms released thus far are pretty darn stable; I don't know anything about binary parts or any of the coding, but plenty of people have no problem running CM or AOKP. Even the Samsung-based roms all look AOSP-like nowadays because they use Apex or Nova (not many devs like Touchwiz anymore). So take your pick, they're all good roms and most look like AOSP to some extent, with a few (mainly CM and AOKP) striving for pure AOSP.
Make sure to read and follow this guide carefully for flashing stuff, and have fun!
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Prother, by no mean to offense you, but seriously, if you don't know those fundamental technical terms, I strongly suggest you to hold off what you about to do and spend more time reading.
Let me go off and do a search the post for you, where you can get used to those terms.
Hang tight, prother.
Pirateghost said:
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
So I will. To be honest I don't see the connection between the new jargon, and development I learn in school. There is definately much to learn here. I was expecting this to be like Zaurus development from back when I was active, it's very clear to me that this is a very different beast.
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
votinh said:
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
Click to expand...
Click to collapse
Thank you friend. I may not have my own rom at the end of summer, but I should be on my way to understanding what would be needed for one.
Well the terms I wanted are not present on that list, most of that I was familiar with. To be honest, some of it I have not seen before as well. What is hellraiser, and some of the other xda developed jargon? I do have a tab open to that part of the forums, I just hadn't made it over there yet. I started on the forums for my device, then Android OS, and lastly general. Is there any other place I should pay special attention to that would help me?
Phalanx7621 said:
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok? I'm not sure I understand, is there something you don't like about the aokp rom that doesn't work very well?
I want off of the carrier provided images based on personal conviction. Google's development practices smack of cathedral, as do all of the 3rd party companies. In a sense they are abusing the spirit of free software by using a signed kernel to impede (if not actually prevent) our right to modify hardware we own. Any normal user of the software provided by the community (bazaar) can only help the cause.
I plan to share what I personally learn with close friends who live in my area. The more people we liberate, the better for everyone else. I simply applaud the work done here.
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
karate104 said:
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
Click to expand...
Click to collapse
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
From a relative noob:
Follow the directions in the " [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!! " thread. Then pick a rom you want to try and follow the CWM directions ... after that , find a ROM you like. If you don't want to void your warranty, wait for your carrier to provide the closest thing to what you want ... but, I'm happy with my flashed ICS ROM.
NEME5I5 said:
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
Click to expand...
Click to collapse
Just like everyone else has said. Read read read. Search for answers for your questions before you ask on forums. U will be fine as long as u can read and follow simple directions. Good luck to u. If u haven't flashed a rom yet I would recommend aokp. Awesome rom.
Sent from my SGH-I777 using XDA
Hi.
I've been a lurker on XDA for a while. This weekend I ordered a Galaxy Note to replace my Atrix 2, and I started going through the process of combing through the posts here to figure out how to root, flash roms, what roms to flash, etc. In the process I started learning a bunch of new terms that I'd never encountered before (ODIN specifically, but also "Fast Dormancy," APN, a few others). There's a lot of information here and it's a little dizzying.
Which brings me to the setup for my question(s). I am a technical writer, and have been for 19 years. I'm a pretty good one, and I have a knack for putting together pretty solid documentation. I thought it might be useful if I took a lot of these documents and put them together into an actual document, sort of an unofficial Galaxy Note manual for the i717, and turned it into a PDF that someone could download and use as a reference.
My questions are:
1. Is there any actual need or desire from the community for this? I figure a lot of you are probably more used to crawling through the forums for information than I am, so perhaps this is something that wouldn't provide much benefit.
2. Is there any legal concern for it? This is a little trickier. Essentially I'd be providing documentation that included how to root a phone, and as far as I know there's no reason it would be illegal (just, you know, warranty-voiding). I'm a little fuzzier on documenting ODIN, since it's apparently Samsung-provided software...
3. If I created this, where should I put it? I'd be tempted just to link to my own site, but I notice the common thing to do here is to post it on a cloud/file hosting account. Is there a specific reason I shouldn't put it up on my site, other than the bandwidth hit if it turned out to be ridiculously popular?
Anyway, those are my questions. Just trying to get feel for whether it would be worth the time to take on this project...
I have a Nook Tablet 8gig that I rooted about 10 months ago with no problems. I have had no complaints so I have not mucked around with it, but now I am wondering about updating a bit. The issue is that I want to be able to use an external keryboard dock with my NT, and I read that it was only possible with CM7 (not sure if that means CM7 and above). I rooted the NT using the great instructions and files recommended in the developers thread, but to be honest I have no idea what my nook is rooted with- it works well so I have not messed with it.
I am essentially looking for instructions on how to re-root my NT after I re-set it to factory, or how to alter my current root to run CM7. My screen is half wonked, and I may take it back since I got the extended warrenty, especially if I have to re-root it for this anyway.
Also...what is CM7? Is that an Android version?
As a side note: Can anyone confirm that you can use an external keyboard with CM7 or above?
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
systems6 said:
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Click to expand...
Click to collapse
Ultimately what I want to do is run an external keyboard, and the information I have is that they will run on CM7. I will probably (assuming my warranty will cover this) be getting this one fixed to replaced soon, so I will need to re-root when I get it back, but for now I don't see the need to re-root if I don't have to.
What does it mean to "flash" cm7?
drworm73 said:
What does it mean to "flash" cm7?
Click to expand...
Click to collapse
If your nook is broken already, why bother doing anything to it? Just get it fixed then address the things you want to address. And while you are waiting for the replacement see the next line.
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z".
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
SlowCobra96 said:
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z"
Click to expand...
Click to collapse
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
Click to expand...
Click to collapse
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
drworm73 said:
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
Click to expand...
Click to collapse
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
SlowCobra96 said:
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
Click to expand...
Click to collapse
Thank, I just took it back to Best Buy and they replaced it with an HD. I thought about an HD+, but I use my nook for reading more than anything (lots of comics, some novels), and the 9" is much less comfortable for that. Now I need to root this bad boy, and I don't have to monkey around with roms other than rooting because the HD already has support for an external keyboard.
This can be closed, as far as I am concerned. Thanks.
I've read countless forums on the rooting and roms and kernels and I have the most basic grasp of what each do. It seems that every time I read an article or forum post at some point something is mentioned that is over my head or that I don't fully grasp. I would love to not brick my phone. I need someone to explain my options and what I can do like I'm 5. What is Odex or Deodex? HOW do I find roms and kernels that work for my phone. What is clockworkmod and ADB? And what can I do to make sure I don't completely brick my phone.
I currently have an AT&T S4 that I rooted with Casual. Through casual it also loaded TWRP. I made a backup of everything it would let me check. I need to get a kernel onto this phone that will allow me to run Call Recorder "http://forum.xda-developers.com/showthread.php?t=1441643"
I am required to have a call recording feature on my cell phone or I'm tied to a landline for work. I had a Galaxy S2 Skyrocket that this program worked perfectly on.
I would like to for the most part keep the phone looking stock. Although I'm not sure what features I could add by going with a different rom.
I'm sorry for the noob questions.
There is a 1% chance of your device bricking if you follow all the correct root steps. Clockworkmod is like twrp. It is a custom recovery to let you put custom Roms on. ADB is the android device bridge. It let's you control your android from Ubuntu command prompt. Hope this helped
Sent from my SCH-I545 using xda app-developers app
No offense meant, I honestly can't suggest you Root or ROM your phone if you can't follow the root procedure without getting confused. If you don't understand the basics how are you going to take care of issues that will inevitably come up? Desperately asking for help when your phone is looping isn't a good answer.
ADB
Odex and Deodex
ATT galaxy s4 forums, kernels are under Original Development
TWRP and CWM are just different types of recoveries. I don't like CWM because the wipe options aren't all in one menu which is bothersome. But both work well. I suggest TWRP to all my friends to limit the amount of "my phone won't boot" phone calls I get.
And the only way to ensure you don't mess up your phone is by not messing with it at all.
Mebct76 said:
I've read countless forums on the rooting and roms and kernels and I have the most basic grasp of what each do. It seems that every time I read an article or forum post at some point something is mentioned that is over my head or that I don't fully grasp. I would love to not brick my phone. I need someone to explain my options and what I can do like I'm 5. What is Odex or Deodex? HOW do I find roms and kernels that work for my phone. What is clockworkmod and ADB? And what can I do to make sure I don't completely brick my phone.
I currently have an AT&T S4 that I rooted with Casual. Through casual it also loaded TWRP. I made a backup of everything it would let me check. I need to get a kernel onto this phone that will allow me to run Call Recorder "http://forum.xda-developers.com/showthread.php?t=1441643"
I am required to have a call recording feature on my cell phone or I'm tied to a landline for work. I had a Galaxy S2 Skyrocket that this program worked perfectly on.
I would like to for the most part keep the phone looking stock. Although I'm not sure what features I could add by going with a different rom.
I'm sorry for the noob questions.
Click to expand...
Click to collapse
Every last one of those questions can and would be answered through very few Google searches. Hell, searching this site will return a lot of the same results. There's even an XDA Wiki for such FAQ. And why are you posting in Verizon if you have AT&T and there's and AT&T section for the S4? Just sayin'
Wrong forum
I would also like to suggest you make sure to post in the correct forum for your device to ensure any answers you get are applicable to what you're using. The OP indicates you have an AT&T S4, yet you posted in the Verizon forum. Should you ever have an issue with your device and need further assistance, getting responses specific to the Verizon device versus your actual device could cause further problems for you.
EDIT: Didn't see Delakit's response before posting mine
Delakit said:
Every last one of those questions can and would be answered through very few Google searches. Hell, searching this site will return a lot of the same results. There's even an XDA Wiki for such FAQ. And why are you posting in Verizon if you have AT&T and there's and AT&T section for the S4? Just sayin'
Click to expand...
Click to collapse
Yeah I just noticed it was in the Verizon section. My bad. It appears I wasn't paying close enough attention when I posted that.
Dubbsy said:
No offense meant, I honestly can't suggest you Root or ROM your phone if you can't follow the root procedure without getting confused. If you don't understand the basics how are you going to take care of issues that will inevitably come up? Desperately asking for help when your phone is looping isn't a good answer.
ADB
Odex and Deodex
ATT galaxy s4 forums, kernels are under Original Development
TWRP and CWM are just different types of recoveries. I don't like CWM because the wipe options aren't all in one menu which is bothersome. But both work well. I suggest TWRP to all my friends to limit the amount of "my phone won't boot" phone calls I get.
And the only way to ensure you don't mess up your phone is by not messing with it at all.
Click to expand...
Click to collapse
I can follow the root procedure just fine and have rooted my phone. How can I learn if I just sit back and say "well guess I can't do it". Your right there are going to be the inevitable issues. The only way to ensure that I never learn this stuff is to not mess with it. I'm fully aware of the risks and potential rewards of this. But I'd like to figure it out. It is probably difficult for the senior guys such as yourself to remember what it was like first starting out. You've got multiple devices with multiple influences on the current setup of the phone at stock and because of the multiple hands in the making of each phone you have different rules and procedures for each one. The sprint S4 is different from the AT&T s4 which is different from the T-mobile S4. So following a guide doesn't always help if you don't completely understand the terminology. Can I use a mod kernel on a stock rom? From what i've read, yes but if it is AT&T it must be loki'd, ok What does loki do, why does it need to be loki'd, can I loki any S4 designed kernel, and HOW do i Loki something. I have yet to find something that answers all of those. Would you like to try? Maybe someone has answered them and I just can't find it.
Also, it appears I posted this in the Verizon forum instead of the AT&T forum. It was late and I wasn't paying that close of attention. My apologies.
Icculus760 said:
I would also like to suggest you make sure to post in the correct forum for your device to ensure any answers you get are applicable to what you're using. The OP indicates you have an AT&T S4, yet you posted in the Verizon forum. Should you ever have an issue with your device and need further assistance, getting responses specific to the Verizon device versus your actual device could cause further problems for you.
EDIT: Didn't see Delakit's response before posting mine
Click to expand...
Click to collapse
Thanks...I wasn't paying close enough attention when I posted that.
Mebct76 said:
I can follow the root procedure just fine and have rooted my phone. How can I learn if I just sit back and say "well guess I can't do it". Your right there are going to be the inevitable issues. The only way to ensure that I never learn this stuff is to not mess with it. I'm fully aware of the risks and potential rewards of this. But I'd like to figure it out. It is probably difficult for the senior guys such as yourself to remember what it was like first starting out. You've got multiple devices with multiple influences on the current setup of the phone at stock and because of the multiple hands in the making of each phone you have different rules and procedures for each one. The sprint S4 is different from the AT&T s4 which is different from the T-mobile S4. So following a guide doesn't always help if you don't completely understand the terminology. Can I use a mod kernel on a stock rom? From what i've read, yes but if it is AT&T it must be loki'd, ok What does loki do, why does it need to be loki'd, can I loki any S4 designed kernel, and HOW do i Loki something. I have yet to find something that answers all of those. Would you like to try? Maybe someone has answered them and I just can't find it.
Also, it appears I posted this in the Verizon forum instead of the AT&T forum. It was late and I wasn't paying that close of attention. My apologies.
Click to expand...
Click to collapse
Holy crap, hyper questions. Let me try to tackle them.
I remember what is was like. As weird as it sounds, I've never been hesitant about breaking my phone even when it was my only device. But everyone is different. I have learned the most when I've made my device unusable for a few days. Everyone learns and functions differently though. In Psychology they call it the Theory of Multiple Intelligences. Some people are brilliant but can't visualize anything. Some are brilliant and can't take tests. I could go on and rant about our school's piss poor management of teaching children correctly according to their "intelligences" but I'll just stop there.
GSM is different than the CDMA versions because the radios are looking for entirely different signals. Srint, USC, Metro, and Verizon all being CDMA. Radios are the biggest pain when trying to port IMO.
Loki is an exploit to work around the locked bootloaders of ATT and VZW. There is a thread somewhere on exactly how it works. But there are also loki patches posted and the better recoveries all automatically loki patch boot.img's for you.
Almost every gs4 version has their own versions of each kernel built off of the aboot and boot images of the stock files. For instance ktoonsez has a kernel available for all the carriers and one for touchwiz and one for aosp. If you are running stock you would simply flash his kernel for TW and it would install just fine on the stock ROM without you knowing anything about loki or how it works.
To be honest, I don't know enough about the actual vulnerabilities and exploits to FULLY understand loki. But I don't need to. It works. I plan to learn more about root vulnerabilities later. But I can only work on so much at once.
You can flash other carrier's kernels, but I wouldn't recommend it if there are kernels that suit your need for your carrier. I say this because I did loki the 4.3 kernel designed for the 9505 and got it working on my vzw gs4. BUT things may be broken or not fully working due to the differences in the kernels themselves. If you don't want to tear into things, it's best to just run the one for your phone.
I think I got it all. Maybe not though.
The best way to learn is with a nexus device. You can't brick that thing if you tried, and even if you were trying, you'd have to know what you were doing to brick it.
I mean, as long as you have the money to replace your phone, and don't mind not having an operational phone, dive right in. I've gone a weekend without a phone, stayed up til 2am trying to fix my phone when I had to be at work at 6:30, but I like to tinker with stuff and I'm fine with that.
Sent from my SCH-I545 using Tapatalk 4 Beta
Yeah I've bricked my gnex before and I learned a lot from it. There is almost always a way to fix a bricked phone whether its Odin or somehow flashing a new ROM. And like what was said before there is only a 1% chance you'll actually brick your phone. A lot of people think they are bricked when it is only a soft brick instead.
Sent from my Galaxy Nexus using xda app-developers app
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
BrendonButton said:
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
Click to expand...
Click to collapse
Bump.
Hi there. Welcome to the forums!
Unfortunately, the bad thing about phones that aren't very popular in the grand scheme of things means less people have them = less people making stuff for it. Developers often end up picking phones that are going to have more support from the manufacturer and more people will be able to enjoy the fruits of their labors. This of course, is a general rule, and of course there are exceptions, but your phone doesn't seem to be one of them. Companies like ZTE aren't concerned about putting out the source code for phones like this means that it is hard, to almost impossible, to make a really custom rom work correctly due to driver issues among other things.
So to answer the questions:
1) Sometimes, but very dependent on the models, carriers, and which software updates. General rule of thumb is that if it isn't based off the same chipset, it won't have a chance of working. But there are lots of other things to consider to, like radio versions, bootloader status, partition layout, etc. Long story short, there's no easy answer and there are lots of caveats.
2) + 3) See above.
4) You SHOULD be safe if CWM told you that the nandroid was completed successfully, but just like any other software based things, things happen.
Best way to be safe is to be able to reflash the original firmware for the phone back to it, but not even sure if that's an option for you - which goes back to ZTE not giving a $^!* about these cheap little phones for small prepaid companies. They save money by not doing any extra work like providing firmware, updates, source code, etc.
The only forums I know that mess with these kinds of things are:
http://unleashedprepaids.com/forum-1491.html
Not for your phone specifically, but similar ones:
http://androidarea51.com/zte-phones/
So yea, slim pickings.
es0tericcha0s said:
Helpful Info.
Click to expand...
Click to collapse
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
BrendonButton said:
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
Click to expand...
Click to collapse
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
es0tericcha0s said:
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
Click to expand...
Click to collapse
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
BrendonButton said:
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
Click to expand...
Click to collapse
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
es0tericcha0s said:
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
Click to expand...
Click to collapse
Oh, wow! Thanks! I'm glad you pointed that out before I tried. So, I should be okay as long as I flash that ROM from the Unleashed Prepaid page? Now I am afraid, but curious.
Also, thank you for the theme modules names, I will kindly note them.
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
es0tericcha0s said:
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
Click to expand...
Click to collapse
Thank you.
I'll look into it tonight. I will try and tell about what happens tomorrow-ish.
Cool. Good luck.