android partitions - Galaxy Note II, Galaxy S III Developer Discussion

wanting to know if it's possible ( obviously maybe not the right thread ) ive thought about doing this and obviously it's going to be "advance" but since androids basically computers with linux instead of windows is there anyway that i can delete all the partitions and "re install" the boot.img the system.img etc to the respect blocks and allow for downgrade through advance means? if so im willing to take on the task ( this was my brother's old s3 and it's cracked and i don't care if i destroy it so ) im willing to take one for the dev team and personally destroy my data and even the phone if it comes to it i don't care about bounties i honestly don't i just care about getting our phones back to being OUR'S not some locked down piece of plastic so if there's anyway to do so please let me know and send me links etc and if need be please explain if it would take jtag im hoping not due to well not having one lol but please if there are any devs that are willing to help me out i would appreciate it ( for links advice etc ) like i said IDC if i destroy this phone i truly don't ( i about threw it against my wall just cause i was so pissed off that it's locked down ) but if there is anyway of literally deleting ALL partitions and manually installing the OS i would appreciate it and yes i am familiar with android and linux and computers in general but as i stated im willing to take one for the team

i've made a tutorial long ago for modifying i9300 partitions, here: http://forum.xda-developers.com/galaxy-s3/development/mod-usable-space-smaller-custom-roms-t1873734
I've never had or have seen any other s3 variants, so be wary - the method might not work.

Related

[Q] Checked and didn;t see anything like this

Can someone with good experiance, possible write up a 'doc', or start a thread on what n00bs can or maybe should do with various things once they for instance root them etc.? (In this instance for the gt-p5113 specifically, if you would.) sure it will be opinion, etc. but for instance I just rooted my samsung galaxy tab 2 10.1 gt-p5113 (by the excellent docs here btw, I think they worked flawlessly.) But I just do not know what to do next.....it is freshly rooted.
and by next I do not mean things to use and do WITH it....I know somewhat some of the things I want to do there, but for instance making a backup...probably a good idea, but I do not really know the best way to go about it....or installing super user...it was mentioned, but I have no clue really how, or if they were talking about another device or needing to or not. or installing a firewall or some other type of protection. I don;t know...I guess I am expecting someone to do some thinking for me, and maybe that isn;t always the best thing to do, but it'd sure help me thats for sure, because I'm sorta weary at this point and not yet comfortable messing with it, sorta and could use some verification/validation of thinking with less of the fear of bricking my tech. I literally just rooted it like 5 minutes ago.
RS-232D said:
Can someone with good experiance, possible write up a 'doc', or start a thread on what n00bs can or maybe should do with various things once they for instance root them etc.? (In this instance for the gt-p5113 specifically, if you would.) sure it will be opinion, etc. but for instance I just rooted my samsung galaxy tab 2 10.1 gt-p5113 (by the excellent docs here btw, I think they worked flawlessly.) But I just do not know what to do next.....it is freshly rooted.
and by next I do not mean things to use and do WITH it....I know somewhat some of the things I want to do there, but for instance making a backup...probably a good idea, but I do not really know the best way to go about it....or installing super user...it was mentioned, but I have no clue really how, or if they were talking about another device or needing to or not. or installing a firewall or some other type of protection. I don;t know...I guess I am expecting someone to do some thinking for me, and maybe that isn;t always the best thing to do, but it'd sure help me thats for sure, because I'm sorta weary at this point and not yet comfortable messing with it, sorta and could use some verification/validation of thinking with less of the fear of bricking my tech. I literally just rooted it like 5 minutes ago.
Click to expand...
Click to collapse
Did the root method install a custom recovery?
RS-232D said:
I literally just rooted it like 5 minutes ago.
Click to expand...
Click to collapse
It will take a little more than 5 minutes to do your research.
My experience over the years has taught me that doing your own research is far more rewarding than having someone else do it for you and hand everything to you on a plate.
You can take it at your own pace, and you will get a far more rewarding experience of your tech if you put the effort in. Not only will you learn more, but you will discover other things as you search for the answers. This is truly mind expanding stuff, but it requires effort.
And that's the point of Android I find - if you don't want to make the effort and you want someone to do everything for you then buy a product from Apple. They are the masters at making things easy...as long as you are prepared to do things their way, and not expect too much from your device.
Android is flexible and configurable, but that means thinking, exploring and discovering things yourself.
If you're not comfortable then don't do anything. Read, read and read some more until you get comfortable - then act. That is the safest way to avoid problems as well as rewarding you with knowledge and understanding.
Good luck in your quest.
acefsw said:
Did the root method install a custom recovery?
Click to expand...
Click to collapse
Uhm.....uhm......I am not thinking so.....I used a method which used Odin....I started in I think recovery mode, by holding power and volume up, then switched to volume down, and selected a recovery file that I had put on my Sdram card, it did it's thing, and now I notice I have super user capability. I then installed supersu and quickboot . And that is where I am at. Pretty much.
Mr.Anderson....ya.....I hear you, and have run with the rtfm crowd enough to grasp the concept..... but perhaps that is why the other guy after joining Iin 2012, has a thank you meter of 16 and you have one of 6 after joining 4 years ago? I am not trying to really skip the 10 billion posts of reading time exactly, or learning on my own. What I am trying to do is avoid problems I might from more experianced people who wish to share, after looking and not finding a specific post that I am sure is up to date, thag answers the issue. Frankly, I'd like for there to be a sticky on it specifically for this model. I''ll write one myself and submit it once I know enough to do it probably......but I promise, if you do not wish to help me, I won't think any less of you, or blame you. I am sure you have gained all your knowledge and earned it on your own, or if not, on this subject specifically, it wasn't any help from me, so neither you nor anyone else owe me anything.
RS-232D said:
Uhm.....uhm......I am not thinking so.....I used a method which used Odin....I started in I think recovery mode, by holding power and volume up, then switched to volume down, and selected a recovery file that I had put on my Sdram card, it did it's thing, and now I notice I have super user capability. I then installed supersu and quickboot . And that is where I am at. Pretty much.
Mr.Anderson....ya.....I hear you, and have run with the rtfm crowd enough to grasp the concept..... but perhaps that is why the other guy after joining Iin 2012, has a thank you meter of 16 and you have one of 6 after joining 4 years ago? I am not trying to really skip the 10 billion posts of reading time exactly, or learning on my own. What I am trying to do is avoid problems I might from more experianced people who wish to share, after looking and not finding a specific post that I am sure is up to date, thag answers the issue. Frankly, I'd like for there to be a sticky on it specifically for this model. I''ll write one myself and submit it once I know enough to do it probably......but I promise, if you do not wish to help me, I won't think any less of you, or blame you. I am sure you have gained all your knowledge and earned it on your own, or if not, on this subject specifically, it wasn't any help from me, so neither you nor anyone else owe me anything.
Click to expand...
Click to collapse
Ok, go in to recovery mode volume up+power and see what it loads, if it is cwm, then you can select backup, I backup to my extsd because it takes up a lot of space on internal sd, then reboot. If not, then search for install cwm on the forum. I can explain later, but am on vacation visiting the parents, so I can't guarantee how timely my response will be.

Let's make a rom! :) (question)

Starting a new thread here.
YES I A NEWBIE!!!
(when it comes to Android at least).
That said. Nobody has to point it out. I know where I stand and I don't know much about Android. I know quite much about Unix/Linux so that's
a start. I know some electronics. I own a Note 3 that I think is mostly the same and want to try to take it parts from there.
It's not about stealing, "kanging", code. Please see it as a journey of fun. Of learning. Making something!
Newbie or not. I think we could be a fun bunch. Since we all want to learn!
I see more want the same. So why don't we pool? Why not make a "Hello I9506!"-Rom?
It's something I want to learn. Today I don't know something. Tomorrow I will. But just the satisfaction of doing something is worth it.
So if someone is interested. Message me. Hell. All the devs where newbies once.
Some are very helpful and some are jerks. We have the whole spectrum here and met both sides. But I don't care if a "elite-dev" snorts at me.
I want to produce something. From there on? Who knows?
A quick question:
Do we have some bloatware-list we can use or it the same? Still would need it thank you
I got some strange behavior of it yesterday (yes, I rooted it and tripped Knox, knowingly). It says it doesn't have space.
Folderspace says otherwise but saw that the /system was 89% and that feels just like it needs a real good cleanup.
I need to do the same with my Note 3. There I think there are scripts, but not for this. Is it the same TouchWiz as on the '05?
I contacted the "head developer" (I think, the one that made the first post) from FoxHound Rom since they
1) Makes a really nice rom
2) Have a release it on Note 3
So I asked for some help, hints. I'm sure he answers when he sees it.
What I like is the AOSP-feel of it. I'm like all the time running, between them. Flash, flash, flash. Ok dual boot now, but not the same!
Was same on my HTC until Venom released Viper for One X. The rom of roms! Venom Team. They are damn skilled.
So you find your "fav-rom". Me I like Foxhound just because it connects the two worlds. It's aiming for the best of the both worlds. Innovative.
Granted TouchWiz as a base is stable. They have a whole stab of people working on it.
It's fun to play around with both Probam or Pac-man (as it's built on) but it has drawbacks.
I can't use my Flipcase, and on the Note the pen and then we have some bugs on it. As all the rest.
Nothing that I can't complain about, since then I should take my butt and fix them or report them at least.
Please. Report. Never complain of bugs, because they happen. It's their hobby project ffs!
I really hate people that start to "demand" or are very unfriendly in their bug reporting.
It goes the other way around as well. Sauerkraut-devs with snotty answers.
Having worked with several closed and open source projects bug-reports are good, ideas for change. You can voice.
Sometimes strongly, about a new direction you don't like but you can NEVER demand, complain. Want something that badly? Ok. Pay me.
Over the years I've been on the net (like since 1991) I've seen this circle over and over.
The circle of Open source development
1) Enormous enthusiasm. The start! The first little halting buggy rom. So proud. Full of energy.
2) Taking in own and others ideas and develop, develop, develop - this is the happy times
3) The bugs start to be complicated as the code complicates so they are not that "fun" as to implement new stuff - and here starts the spiral
4) Here it's a combo that can go two ways or together
a) Constant nagging, demanding users without positive feed back makes them think that the users are just ungrateful. Because they are.
The coding is done on spare time. You can't "demand" someone from an Open source project. You can ask, propose.
In some you can expect it holds high standards and you can sometimes question if the decision in some part is wise and made a good and sound argument.
Give an alternative. But never demand and the final decision is up to the project.
b) The coders starts to seem themselves as the best on the earth and starts to see the users as something unavoidable.
This is a big error because then they should stop releasing version and just have their own. So they stop listen to ideas, and feel that the users
are ungrateful ****heads that should just follow the path and be happy that they get some app at all.
That is the negative spiral.
The frustration and the worst scenario, a rouge programmer, that go it's own way in the project. That makes a schism. Quarrels
Either the code is then forked (parted) or the whole structure starts to fall apart in who is the leader, owner, and never-ending discussions
because everybody knows BEST. Here the users are totally ignored since the internal conflicts takes over the whole project.
5) The coders gets tired of all this. Have bugs they don't care to fix and if someone files a report or do a suggestion they get a "Do it yourself" back.
6) Abandoned code or a restructure, a new way of working and uniting, some people leave, some new joins.
Healing and a fresh start or the project dies, often with the last version full of bugs that people still use because it's still what they want.
If there is luck, an new bunch of coders take that code and start from 1
I've seen this so many times and it's always the same.
In commercial projects you try to identify when the coder comes to this frustration point, because then it's time to move him/her to something else.
Because a disgruntled and unhappy person is never good, in anything. So it goes both ways.
So how to avoid it?
Basics. Planning. Setting goals. Having a real bugtracking system. Making clear that suggestions are suggestions and have a civil tone from both ways.
And then talk, yell, have big arguments inside the group, but make a real case for it. Like having your own space, where you give proposals.
But in the end. ALWAYS RESPECT.
A round table is not a bad thing, but there has to be respect and it has to be someone that has the final word that you have enough respect
for and trust that he/she decide what he/she think is the best and accept it. Else it's a chicken-yard. Never ending back and forth.
If you can't live with it because YOUR proposal was not granted either leave in a good way or make a fork. Or be a good player and not a crybaby.
A proposal should be in the form of What, Why, Time, Benefit (and if you are mature enough - potential problems and implications).
And then have a discussion about it. Advocate your case. Have a chat in the group.
There is nothing to say that a program can't have two different versions. Sometimes an experimental branch just to test things.
Time can tell which is the best. Be humble and respectful. Have heated discussions, as I have in a current project, challenge something.
That way, you see if it holds. It's the basis of research as way.
Postulate something. Try to prove it. Find someone to disprove it. Have an argument. See if it holds else start over. Boring? Yepp.
Does it give results? Oh yes. This is how mature people work.
Especially when it comes to medicine (that is my field now). Proving something is not easy. And think of those who sit for 20 years with a problem,
try 200 ways that fails, but don't give up. Persistence towards a goal. I met a professor. She has been working with HIV for something like 20 years.
She told me how many times they thought they where close. How it looked so nice. How it looked "THIS IS THE KEY" to see that it held for that part of the virus,
but not for the other 18 mutations and that it doesn't do any real benefits compared to the disadvantages. Finding a "hook" as they thought a few years back.
That was the most promising. Because a specific "hook" in something means that you can do something that grabs it. But it failed.
Or the people working on Malaria that kills so many. It's a complicated parasite and we have been so close, so close, but not yet.
The really big big thing. Documentation. I know, this is sooo damn boring, but to write out what you are doing in this block of code
(if obvious, just one line), If more complicated, explain.
Don't over complicate.
Don't insert numbers that you forget lie *1024 or +2, use a label for that. Document!
Try to write as general code as possible. KISS! (Keep it simple, stupid).
There is this case that we always get. It's about a coder in a project. He has this subroutine. He has been writing it to "perfection". Rewriting it.
Over and over. The machine went for years. Then it called that function and it crashed. Oh the irony,
In Sweden we call code that is in total disarray for spaghetti-code, because YOU know it, can navigate, but for someone new, it's hard or impossible.
Modularize as much as possible! Can't stress this enough.
That way, even if it take a bit extra time you have "boxes" that are taking in stuff and spitting out stuff.
Example.
We need a database to store things. We chose X. We work with X and then the X is not ideal, we need to make compromises in the code.
Mend it to work with X. But we come to a point where we want and need Y. But since the code is so intertwinned with X it's a hell to change it to Y.
Making an "interface", where you define clearly, the function of the database simplified (creations etc), boils down to this:
Search for something, read that something, write (change/add/delete) that something. That is it.
So yes, you write a few more lines, but today, we don't need to count how many clock-cycles the penalty it get (as I did way back).
We have damn fast things. When Java came it was like syrup. So zzzlooooowww. People just scratched their heads.
The only thing was that it worked over platforms. Today we have computers that can run it just fine. Fluid. Our phones for instance.
Same with C++. And yes, you can still make it zzzzloooow. So it's good to have some books (I have ebooks) on functions.
Don't reinvent stuff.
A sort function is mathematical. It will not change. When I started my masters we had this "little" book called "Introductions to algorithms".
It's like 3000 pages! Written in "pseudo code" 20 years ago but still holds. I can teach why we should not use this and why we should use that.
But I have not coded since 1997 or so and so much has changed!
But an Android is a Linux in the bottom. I've worked as a Unix specialist for many years before I changed path. So I know my way around there.
I DO need to update myself. I'm honest. I can spend time in clusters. Sometimes I have personal matters that hinders me. Like most people.
But first and foremost. It has to be FUN. This is our spare time. We do this for free. It SHOULD be fun.
Writing not fun is something you get paid for. Get a specification. Do this and that.
We still need that and it can be an obstacle but it still should be a goal to want to do this.
Persistence. Ask for help. Get a no? Ask another. We all have to start from square one. That is the beauty of this in a way.
So I'm asking if someone wants to make a group and do a ROM? I want to try. We seem to be an enthusiastic bunch here right now. Let's pool!
Let's make our "Hello Worlld! I9506 rom!
So if anybody else, newbie or not, feel it would be fun, message me. Cause I will try anyway and I would love some company.
I've had "some" project leading experience, and I still sit as a bit "advisor/pain in the but".
I don't code but most probably need to start again. But I do voice advice/concern from time to time. I try to propose some solution based on experience.
Call it "meta-coding", but it can be just as important to know how to move code fast then to be able to write the lines.
"Paradigms" don't change. If you look at a language, Java, C etc. You can boil it don't to rules. And the rules are basically the same.
The syntax, how you write it, is different. Some special solutions that is unique for just one language is there.
It's a pain to work with strings of text in C but easy peasy in Perl for instance.
And if we find someone that can give us hints help. That would be kind of them. We can ask. The worst response we can get is a "no", right?
As you see I'm known to write long. "Walls of text" is something I first got a bit mad at, now I find it funny. Sure, I "chat" in a written form.
But I'm full of ideas and enthusiasm here.
I have no plans to enforce me as some "boss". We are a team. Later on, someone will lead. We are a bunch of enthusiasts.
Right now. Baby steps. At least this is how I look at things. You might look at it otherwise.
Nothing stops us from exchanging ideas, even if we don't work on the same thing? I think that is the spirit. Helping each other.
This is not an competition. I don't care if 5 people uses the rom or not. It's not about that. The next one will be cooler. But competition?
Isn't that a bit childish? People have different tastes. I like the AOSP. If my flipcase etc worked I would move from TouchWiz since I even don't use it.
My subproject that takes precedence
KNOX. I will not give up on Knox. That is my main goal right now.
It affects me personally. If we don't stop it. Stop wasting time how to circumvent the bootloader. That is irrelevant.
If not stopped NOW. We will have an S5 with a chipped version of it. Then it's too late.
I see, in some despair, people whining in the threads, but no action. Why don't 20 people start to reg at user-forums and start to spread this?
I have MY theory. You can have that. I think it's for spying. Because I can't any other reason. My employee would give me a phone.
It has no place in our phones. But whining in a thread in a special forum like XDA, where there are people who are wizards when it comes to
developing and people that want to custom their hardware doesn't do it.
We need to spread it to the forums where the "normal" users sit. That probably never noticed it's even there. The ones that ask how to change
the different levels of volume, for calls and system. The user-base. Make them understand in simple terms. Telling them that this place, where the
best people frequent, doesn't really know what it does, because Knox is more then a bootloader that you want to circumvent not to trip that "flag".
That is the only place where we can reach the masses. Make people think. NSA. Snowden. Reading my mails? Recoring my calls?
I don't know. Do you? But it's possible. Who am I to know if my provider feeds my government with data. We already feed them with positiondata.
Make people aware. Make this crowd DO SOMETHING...
[/I]
When you turn on Skype it tries to make a tunnel through in a very sneaky way to "somewhere". I see it each time I turn it on since I tap my ethernet.
My webcam is on a switch. When I Skype I turn it on. Else it's off. And aimed at the wall, if I would happen to forget to turn it off.
So they can make happy pictures. So did Hitler. I just don't buy their bull**** of security for individuals that they added a few days ago.
if I don't want to use a firewall and a viruskiller on my PC. That is my choice. If I look at the downloaded movie Intel won't blow up my CPU.
But here, if this e-fuse is true. That is a deliberate active action. Then they are destroying my property. That is not acceptable.
But to make the "whiners" do something. Damn. That takes energy.
Ok, I stop here. If someone IS interested in experimenting together, message me. I think it can be a fun journey
All the best,
Absolon (yes I got my real nick back!)
:good: Nice explanaition of your opinion and you plan!!!
Never Seen such one!!
.........Few things about me...
1. I AM A NEWBIE TOO IN ANDROID AND LINUX!!
2. I want learn more about LINUX and ANDROID
3. Everything that i know about LINUX and ANDROID i learned here from Instructions of some people( cant remember all nicks - but BIG THANKS to THEM!!! ) that are posted on XDA Forums or Googled it!! And that is not much since i can not even compile a CWM from CM source - after 2 weeks of investigation and always getting error - - i understand its not easy to do that with my less experiance!!!
4. I have a wife and 2 kids around me - so thats top priority 1 for me!
5. I do things in Android when i got time for that - thats mostly on weekends in the evening or night when wife and kids are in bed!!
6. My english is not the best!!
7. Yes of course i am interested in experimenting and learning with other interested people!!!!
8. If you can live with that 7 points before this point - you can call me a member of the ROM "Hello I9506!"
Click to expand...
Click to collapse
Cheers ​
absolon said:
Starting a new thread here.
YES I A NEWBIE!!!
(when it comes to Android at least).
.....
.....
......
.......
Ok, I stop here. If someone IS interested in experimenting together, message me. I think it can be a fun journey
All the best,
Absolon (yes I got my real nick back!)
Click to expand...
Click to collapse
xenix96 said:
:good: Nice explanaition of your opinion and you plan!!!
Never Seen such one!!
.........Few things about me...
1. I AM A NEWBIE TOO IN ANDROID AND LINUX!!
2. I want learn more about LINUX and ANDROID
3. Everything that i know about LINUX and ANDROID i learned here from Instructions of some people( cant remember all nicks - but BIG THANKS to THEM!!! ) that are posted on XDA Forums or Googled it!! And that is not much since i can not even compile a CWM from CM source - after 2 weeks of investigation and always getting error - - i understand its not easy to do that with my less experiance!!!
4. I have a wife and 2 kids around me - so thats top priority 1 for me!
5. I do things in Android when i got time for that - thats mostly on weekends in the evening or night when wife and kids are in bed!!
6. My english is not the best!!
7. Yes of course i am interested in experimenting and learning with other interested people!!!!
Cheers ​
Click to expand...
Click to collapse
DEAL!
ALL programming books starts with how to write a "Hello World!" program. That's why I thought of the name
So "Hello I9506"?
/Absie
Looks interesting, i have only build a buggy CM rom for S3 but never released it, can i join ya .
Sent from my GT-I9505 using Tapatalk
absolon said:
DEAL!
ALL programming books starts with how to write a "Hello World!" program. That's why I thought of the name
So "Hello I9506"?
/Absie
Click to expand...
Click to collapse
Yes "Hello I9506" sounds nice and the Rom Name got also a background by this way why we call it so.
cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
Hey man, i agree with your point. I'd like to help even if I own a I9505. That shouldn't be a problem though! Count me in as a developer! :good:
My I9506 is ready for testing!
A lot of being a good developer is mindset and enthusiasm. I'm sure you'll do great!
Sent from my GT-I9505 using xda app-developers app
I hope the ROM also includes support for the E330S variant....
GO young Dev's !!
@Absie
Hi, my mate.
If u need help/some knowledge in decompiling/compiling of apks and framework jar files and building yr own ROM, PM me.
I have done my ROM projects in the S2 forums and some mods in I9505.
But I'm not a C++/java programmer freak.
I didn't have time to study in this field .
Just a tiny bit of xmls, themings and smali codes here and there that I can help u.
I'm sure u can make a good ROM in this forum.
U need more "real" devs to help u in making yr own ROM.
Cheers.
You are not alone on this. if you can do a clean system dump of 4.3 for me when it released I will take on some projects for you folks
Absolon said:
She told me how many times they thought they where close. How it looked so nice. How it looked "THIS IS THE KEY" to see that it held for that part of the virus,
but not for the other 18 mutations and that it doesn't do any real benefits compared to the disadvantages. Finding a "hook" as they thought a few years back.
That was the most promising. Because a specific "hook" in something means that you can do something that grabs it. But it failed.
Or the people working on Malaria that kills so many. It's a complicated parasite and we have been so close, so close, but not yet.
Click to expand...
Click to collapse
Yup, that about sums up the majority of time I spend troubleshooting, with the answer often being something very simple that I overlooked in the beginning.
As for de-bloating, once you get familiar with what's what it can usually be done pretty quickly.
The first thing to always do is make nandroid of everything and save it your desktop just in case. Having a zip with the stock ROM handy can also save you a lot of time if you need to replace just one app.
There are four main places you have to remember when doing this:
/system/app - primary location for system apps
/data/data - where the app's data is stored
/data/app - where upgraded copies of the apps are saved
and the dalvik-cache (usually /data/dalvik-cache or /cache/dalvik-cache)
If you're using an odexed ROM you'll want to get both the .apk and .odex files at the same time. Many apps will also have two or three widget providers, etc., be sure to get all that stuff. Just keep a list of everything you've removed.
Facebook is usually the first thing I nix as it often uses ~50MB, is redundant when it's going to install itself from the market anyway, and always has way to much access to your personal information as a system app. Twitter, flickr and any other apps like that, which you don't need or want as a system app, can all go too. Some devices also ship with keyboards for every language ever created, you can get rid of any that don't apply to you.
Once you've cleaned out the easy ones take your list and open up Settings -> Apps. The apks may be gone from /system, but all their data and updates are still taking up space. So to finish removing them look under the "All" tab and when you see one hit wipe cache, wipe data & uninstall.
Now just return to the recovery so you can wipe your dalvik-cache and create another nandroid. If you want to clean even more this will give you a good checkpoint to revert back to if needed.
xHausx said:
Yup, that about sums up the majority of time I spend troubleshooting, with the answer often being something very simple that I overlooked in the beginning.
As for de-bloating, once you get familiar with what's what it can usually be done pretty quickly.
The first thing to always do is make nandroid of everything and save it your desktop just in case. Having a zip with the stock ROM handy can also save you a lot of time if you need to replace just one app.
There are four main places you have to remember when doing this:
/system/app - primary location for system apps
/data/data - where the app's data is stored
/data/app - where upgraded copies of the apps are saved
and the dalvik-cache (usually /data/dalvik-cache or /cache/dalvik-cache)
If you're using an odexed ROM you'll want to get both the .apk and .odex files at the same time. Many apps will also have two or three widget providers, etc., be sure to get all that stuff. Just keep a list of everything you've removed.
Facebook is usually the first thing I nix as it often uses ~50MB, is redundant when it's going to install itself from the market anyway, and always has way to much access to your personal information as a system app. Twitter, flickr and any other apps like that, which you don't need or want as a system app, can all go too. Some devices also ship with keyboards for every language ever created, you can get rid of any that don't apply to you.
Once you've cleaned out the easy ones take your list and open up Settings -> Apps. The apks may be gone from /system, but all their data and updates are still taking up space. So to finish removing them look under the "All" tab and when you see one hit wipe cache, wipe data & uninstall.
Now just return to the recovery so you can wipe your dalvik-cache and create another nandroid. If you want to clean even more this will give you a good checkpoint to revert back to if needed.
Click to expand...
Click to collapse
Thank you!
Right now, all we have is the original rom, that is "normal" so I gess it's "dexed". I have no clue how to make it odexed, since what I understood it makes
the whole rom smaller?
The thing that worries me is the bootloader, since we only have the one with Knox in it and I don't know how other bootloaders work or are compatible.
But that means that we are locked into SELinux, right? So until having a "Knox-free" bootloader we can't do **** when it comes to customizing roms?
Because we can't add our own kernel or is there some code that Samsung have, because I found out that Samsung had a code-repo (wow), but
not for this phone yet.
I tripped the Knox-flag when I rooted it. Found no other way really. And I don't know if this is Knox-related or something else. I noticed this on the i9505
as well. I have space but when I try to install things it says that it's out of space and can't install it. The "funny" thing is if I push the install from the webpage
of Play it installs just fine so it's seems to be something preventing it?
I don't recall if I had it before or after Knox since I tripped Knox unknowingly on my other phone before we even found out what it was.
So I need to clean it out. Yes, /system is 76% full with the original. Since all I have done so far is just rooted the phone.
If someone has an I9505, can you do
1) df -k
The partitions (not counting the sd.) on I9506 are:
The root partition (/)
/efs
/firmware-modem
/data
/persist
/system
I'm too tired to write out a good coomand, but best is to use "find" and with some -printf options and then start to hunt.
Then we can compare the phones. The special parameters for SELinux are the next step. But this is a start to see how
The SELinux special parameters part is also something that I want to see, but I want to start with this.
Btw. On my Note 3 I got an "update" of the SELinux rules. Anyone else? (Will ask in the Knox-tread as well).
That is not rooted but totally plain vanilla and I didn't even noticed that there was an update function but got "update 16".
See my post: From Knox-thread
I read and read this night, and to just condense it since I write too long anway and I'm tired. Since the bootloader
is loading an SELinux, that won't boot if it's not compared with an unique X.509 cert in every phone and see if the
loader checksums we really get an virtual environment. That is the "wrong" feel I've had I think. And I think that we need
to sit down and test some things to verify this theory. Get some programs that can do some deep probing of the hardware.
If I'm right, and they have made a VM out of the phone we should probably notice it somehow, because it's easy. I looked,
SEAndroid that NSA created is a VM with Xen.
That means that the SELinux can just run in the background with it's processes that it will never show to you and you think
you have a rooted and Knox-free phone when you never have it since the bootloader loags a SELinux and makes a sandbox.
If's perfect. Unique id on each phone. Your signature on the papers with the serial numbers which identify you as the owner.
So perfect that I could cry if I was an engineer at Samsung...
/Abs
Please make a custom ROM that works for the SHV-E330S as well
THank you very much!
sheesha_straw said:
Please make a custom ROM that works for the SHV-E330S as well
THank you very much!
Click to expand...
Click to collapse
We need to start with baby steps so a skeleton for the I9506 is the first prio.
SHV-E330S I head that before. What IS that? Can you give me details? Is that some version of the I9506?
If it is then you are most welcome to help out!
/Abs
Absolon said:
We need to start with baby steps so a skeleton for the I9506 is the first prio.
SHV-E330S I head that before. What IS that? Can you give me details? Is that some version of the I9506?
If it is then you are most welcome to help out!
/Abs
Click to expand...
Click to collapse
I think it's the Korean SK Telecom version of the i9506
It has the same LTE-A support & Snapdragon 800 processor and everything
GSMarena description of the phone
Also known as Samsung Galaxy S4 with LTE+
Available as Samsung SHV-E330S Galaxy S4 LTE-A for SK Telecom.
Inventory
First,
I need to know if it's ok that I take the Project leader role here a bit? I have sat down and identified the things we need to even start and I have some pretty good idea.
But I can only be a Project leader if you let me. If I'm allowed to spread out the work. Else we can close this. I can't do this alone. It's too much work.
But I think that the work WE can do is the base that will benefit all rom-makes. Because this is the starting point that anyone that want to make a
rom has to start from.
The difference is that I want this to be here. In the open, and not at some closed webpage. I want all to benefit from what we do.
Either we do this openly or not at all.
And so you know. There will be a bit of work. I have my Unix knowledge and I run several Linux/BSD machines at home. I did a small calculation.
I have now been playing/then having it for getting bread on the table with Unix for 23 years.
I don't know everything. Far from. Even though I been working with it that long, the part I did as a consultant was within a certain part and I never learnt
other. Simply because I was hired for knowing just that part really well.
The problem with Unix (and why I use Unix is that everything is basically Unix, even though it called differently. It would be called Unix today if it didn't
happen to be a patent fight over the NAME. The one that held the patent of the name Unix wanted money for people to use it (it might have been SCO,
they tried to get money for anything they could. Really despise that company).
So instead of paying the companies invented their own names, Sun went for SunOS and then Solaris, Hp (HP-UX), IBM (AIX) etc.
So it's hard to say that Linux is not a Unix because it's not a Unix Unix (that doesn't exist anymore) but when I say Unix I mean the whole spectrum
of very very closely related OS to it, ok? So I will sometimes say Linux and can say Unix, but I mean basically the same.
The thing with Unix is that the learning curve is steep. You install it and have a black screen with a ">". It's a bit more easy now with Ubuntu (that I hate),
but it's better for you, that never worked with it to have something to "point and click". When it comes to the real work you will have to open up a
terminal anyway and TYPE command. See it a bit as a DOS-windows in your Windows.
There is two distinct flavors though. The one is BSD and the other is the Linux, bla bla. Those two are a fork that happened long ago and you tend
to feel like a newbie again, once you sit in from of a FreeBSD after being a homie on Linux because everything is different.
There is a standard basically on how to start up things. There is now a new thing that comes more and more that should be less conservative then
what has been the case the last 20 years but that is another thing. The Linux that Android is based on has a normal "init.d"-structure and that is
where the different scripts are that start up, in an order you decide, different parts of the system, or do what ever really. They are just scripts and
could write "Hello I9506!" on the screen if you would like that.
Did you all see the post I made about the i9506?
PLEASE ALL. I need to verify this so it's not some duckup from my part but I will do a odin today to be sure
Take a look at what I wrote: http://forum.xda-developers.com/showpost.php?p=48320189&postcount=1402
Anyone here that tripped Knox? Anyone got any strange things?
We need to know this before making any attempt at all.
I don't cry wolf here. This is true. No bulltitting. I KNOW I had this.
If you look my sig, you might think I know has build a Faraday's cage around me and have a folio-hat while looking through a magnifying glass at my
monitor at a Youtube-video showing taped in a tv that was recorded by a CC-camera from a TV in the 80-ies about the (pick one):
Moon landings
Kennedy
Roswell
9/11
Ilumatnii/NWO
And I wish I where. But the phone is erratic and I really think it's tampered. Did someone get a notice with rule-updates? I didn't get it to this one
but I got it to Note 3.
-------------------------------
So in case that you let me lead the project here in the start and be able to have work that I can "assign", or I rather want to list work and have volunteers for it.
Then I can say "Ok, test that then" etc. And we have a dialog that is open and never that someone feels forced over it, ok?
We need a BASE. Something to start from and we need to see what we have so this is the inventory part. What we have, where we start.
The first step
And I need someone that can do some deep probing for me of the hardware. We need to start comparing.
Can all do a *#1234# and post it?
I have:
AP: I9506XXUAMI3
CP: I9506XXUAMHD
CSC: I9506NEEAMI1
I noticed it only works on the original "Phone app".
This is what I think we need as a base to start with.
I9505
As close stock rom as possible. Now I saw that Hotfile was closed down (did a post about it) so I hope we get
Base
I9505 - Plain vanilla rom. As close we can get
I9506 - Depends here what you have. Here I would ask if someone has an unrooted and a rooted version.
Note 3 - I have an unrooted version. Anyone has a rooted? Knox tripped? I tried to root it with that Universal thing that doesn't trip know but it hangs.
This are the things we need to start with at least. Make nandroid-backups on them. When you have them I'll prepare a space for them on my g-drive
where you can upload them and then I can start to compare them.
Also, anyone with a Knox-tripped I9506. Please PM me. I got really strange behavior and I don't know if it's Knox or something else.
The ones with Note 3, did you get an "SELinux rules upgrade #16" a few days back? I didn't see that was an option to turn them off.
As I wrote in my other thread. My I9506 started to behave real strange. REALLY strange. There are a whole bunch of programs missing.
The are gone. I have 3 icons on them in launcher but they are just not there. So what gives?
Is this only me or is this something that we all get when we trip the Knox?
After I did a clean with the CleanMaster and removed the Knox apps, I can't get into settings, so I need to try a nandroid restore or in worst case
try to install a odin-version and reroot it. Or maybe play with it unrooted for a while.
This is serious things is this Knox-flag tripped something. I talked with my provider today about this.
So an inventory! What do we have for hardware to test on?
Things to investigate - Here I start list things that any of you can do. As I said. I can't do all and I have so much IRL that I shouldn't be here at all...
Hardware
We know it's closer to Note 3 then to 05. When I look at specs it seems like the same phone.
But I need a rooted Note3 to get the app that list ALL hardware, sensors etc, to compare it. An unrooted Note 3 will not get that access.
My theoryI is that a BL from Note 3 will probably work but one from 05 will not.
But that need to be verified. And I need to see that Odin can reflash if we do something that hangs the phone. This is the risk I will take.
What is on it?
Here I could start to compare. But I need backups of the phones!
If you happen to have any personal password for your wifi, I can give my word that I will overlook it.
Besides, what do I need it for? Not like I would come home to you and hack your Wifi
So here is a list of things:
There is no source released on their webpage about the i9506 yet.
We don't have any "pre-knox" BL for this one.
Can someone check the Note 3 forum if there is some pre-knox. Did a 4.2.2 even existed or was it a 4.3 from the start?
And then backups of the partitions for comparison.
That is the first steps to even start to move this.
/Paul
Absolon said:
First,
I need to know if it's ok that I take the Project leader role here a bit? I have sat down and identified the things we need to even start and I have some pretty good idea.
But I can only be a Project leader if you let me. If I'm allowed to spread out the work. Else we can close this. I can't do this alone. It's too much work.
But I think that the work WE can do is the base that will benefit all rom-makes. Because this is the starting point that anyone that want to make a
rom has to start from.
The difference is that I want this to be here. In the open, and not at some closed webpage. I want all to benefit from what we do.
Either we do this openly or not at all.
And so you know. There will be a bit of work. I have my Unix knowledge and I run several Linux/BSD machines at home. I did a small calculation.
I have now been playing/then having it for getting bread on the table with Unix for 23 years.
I don't know everything. Far from. Even though I been working with it that long, the part I did as a consultant was within a certain part and I never learnt
other. Simply because I was hired for knowing just that part really well.
The problem with Unix (and why I use Unix is that everything is basically Unix, even though it called differently. It would be called Unix today if it didn't
happen to be a patent fight over the NAME. The one that held the patent of the name Unix wanted money for people to use it (it might have been SCO,
they tried to get money for anything they could. Really despise that company).
So instead of paying the companies invented their own names, Sun went for SunOS and then Solaris, Hp (HP-UX), IBM (AIX) etc.
So it's hard to say that Linux is not a Unix because it's not a Unix Unix (that doesn't exist anymore) but when I say Unix I mean the whole spectrum
of very very closely related OS to it, ok? So I will sometimes say Linux and can say Unix, but I mean basically the same.
The thing with Unix is that the learning curve is steep. You install it and have a black screen with a ">". It's a bit more easy now with Ubuntu (that I hate),
but it's better for you, that never worked with it to have something to "point and click". When it comes to the real work you will have to open up a
terminal anyway and TYPE command. See it a bit as a DOS-windows in your Windows.
There is two distinct flavors though. The one is BSD and the other is the Linux, bla bla. Those two are a fork that happened long ago and you tend
to feel like a newbie again, once you sit in from of a FreeBSD after being a homie on Linux because everything is different.
There is a standard basically on how to start up things. There is now a new thing that comes more and more that should be less conservative then
what has been the case the last 20 years but that is another thing. The Linux that Android is based on has a normal "init.d"-structure and that is
where the different scripts are that start up, in an order you decide, different parts of the system, or do what ever really. They are just scripts and
could write "Hello I9506!" on the screen if you would like that.
Did you all see the post I made about the i9506?
PLEASE ALL. I need to verify this so it's not some duckup from my part but I will do a odin today to be sure
Take a look at what I wrote: http://forum.xda-developers.com/showpost.php?p=48320189&postcount=1402
Anyone here that tripped Knox? Anyone got any strange things?
We need to know this before making any attempt at all.
I don't cry wolf here. This is true. No bulltitting. I KNOW I had this.
If you look my sig, you might think I know has build a Faraday's cage around me and have a folio-hat while looking through a magnifying glass at my
monitor at a Youtube-video showing taped in a tv that was recorded by a CC-camera from a TV in the 80-ies about the (pick one):
Moon landings
Kennedy
Roswell
9/11
Ilumatnii/NWO
And I wish I where. But the phone is erratic and I really think it's tampered. Did someone get a notice with rule-updates? I didn't get it to this one
but I got it to Note 3.
-------------------------------
So in case that you let me lead the project here in the start and be able to have work that I can "assign", or I rather want to list work and have volunteers for it.
Then I can say "Ok, test that then" etc. And we have a dialog that is open and never that someone feels forced over it, ok?
We need a BASE. Something to start from and we need to see what we have so this is the inventory part. What we have, where we start.
The first step
And I need someone that can do some deep probing for me of the hardware. We need to start comparing.
Can all do a *#1234# and post it?
I have:
AP: I9506XXUAMI3
CP: I9506XXUAMHD
CSC: I9506NEEAMI1
I noticed it only works on the original "Phone app".
This is what I think we need as a base to start with.
I9505
As close stock rom as possible. Now I saw that Hotfile was closed down (did a post about it) so I hope we get
Base
I9505 - Plain vanilla rom. As close we can get
I9506 - Depends here what you have. Here I would ask if someone has an unrooted and a rooted version.
Note 3 - I have an unrooted version. Anyone has a rooted? Knox tripped? I tried to root it with that Universal thing that doesn't trip know but it hangs.
This are the things we need to start with at least. Make nandroid-backups on them. When you have them I'll prepare a space for them on my g-drive
where you can upload them and then I can start to compare them.
Also, anyone with a Knox-tripped I9506. Please PM me. I got really strange behavior and I don't know if it's Knox or something else.
The ones with Note 3, did you get an "SELinux rules upgrade #16" a few days back? I didn't see that was an option to turn them off.
As I wrote in my other thread. My I9506 started to behave real strange. REALLY strange. There are a whole bunch of programs missing.
The are gone. I have 3 icons on them in launcher but they are just not there. So what gives?
Is this only me or is this something that we all get when we trip the Knox?
After I did a clean with the CleanMaster and removed the Knox apps, I can't get into settings, so I need to try a nandroid restore or in worst case
try to install a odin-version and reroot it. Or maybe play with it unrooted for a while.
This is serious things is this Knox-flag tripped something. I talked with my provider today about this.
So an inventory! What do we have for hardware to test on?
Things to investigate - Here I start list things that any of you can do. As I said. I can't do all and I have so much IRL that I shouldn't be here at all...
Hardware
We know it's closer to Note 3 then to 05. When I look at specs it seems like the same phone.
But I need a rooted Note3 to get the app that list ALL hardware, sensors etc, to compare it. An unrooted Note 3 will not get that access.
My theoryI is that a BL from Note 3 will probably work but one from 05 will not.
But that need to be verified. And I need to see that Odin can reflash if we do something that hangs the phone. This is the risk I will take.
What is on it?
Here I could start to compare. But I need backups of the phones!
If you happen to have any personal password for your wifi, I can give my word that I will overlook it.
Besides, what do I need it for? Not like I would come home to you and hack your Wifi
So here is a list of things:
There is no source released on their webpage about the i9506 yet.
We don't have any "pre-knox" BL for this one.
Can someone check the Note 3 forum if there is some pre-knox. Did a 4.2.2 even existed or was it a 4.3 from the start?
And then backups of the partitions for comparison.
That is the first steps to even start to move this.
/Paul
Click to expand...
Click to collapse
Main:
AP: I9506XXUAMHE
CP: I9506XXUAMHD
CSC: I9506VF6AMH4
It's GOOD!!!
Ap : E330sksuamg5
cp : E330sksuamg4
csc : E330ssktamg4

android partitions

wanting to know if it's possible ( obviously maybe not the right thread ) ive thought about doing this and obviously it's going to be "advance" but since androids basically computers with linux instead of windows is there anyway that i can delete all the partitions and "re install" the boot.img the system.img etc to the respect blocks and allow for downgrade through advance means? if so im willing to take on the task ( this was my brother's old s3 and it's cracked and i don't care if i destroy it so ) im willing to take one for the dev team and personally destroy my data and even the phone if it comes to it i don't care about bounties i honestly don't i just care about getting our phones back to being OUR'S not some locked down piece of plastic so if there's anyway to do so please let me know and send me links etc and if need be please explain if it would take jtag im hoping not due to well not having one lol but please if there are any devs that are willing to help me out i would appreciate it ( for links advice etc ) like i said IDC if i destroy this phone i truly don't ( i about threw it against my wall just cause i was so pissed off that it's locked down ) but if there is anyway of literally deleting ALL partitions and manually installing the OS i would appreciate it and yes i am familiar with android and linux and computers in general but as i stated im willing to take one for the team

[Q] s-off 3g issue

Hi,
I just bought a one s and read through the forums for root, s-off and so on.
Compared to my EVO 3D and Sensation, s-off seems to be less painfull since there are some convenient exploits around that don't need any hardware actions (as the wire trick or soft brick the device).
But I got a little bit concerned about some posts claiming that after s-off the 3g connectivity got lost,
though reading the threads of the latest/greatest custom roms, there's nothing mentioned.
There's one dedicated thread in dev section, but I found no clear statement on how this is to fix.
Some state, that simply changing rom helps to get 3g back.
Some say it's a radio thing.
One member described a method where memory block is manipulated, but this also didn't work for all.
Till now I s-offed each htc phone I owned immediately, but now I'm getting doubts.
I'd appreciate any feedback on this from you experienced ville users out there.
To save you money, time and grief DONT DO IT.
Surely me and most everyone else is thankful that these guys spend time developing and tinkering but I screwed 2 One S,
that is when those disclaimers kick in, and I also looked, not exhaustively, for a skilled JTAG tech/user, the guy I sent it to
said he couldn't figure it out.
Maybe someone here can; most people that JTAG said that doing it to that phone is hard because it has to be taken apart.
Honestly, S-Off would make sense if its a new device to come in the market, as you have noticed, most ROMs and apps just
disappeared and the latest radio put together by someone in here is a 1.35.XX.XX. Since ROMs are limited, and most developers
dont even bother with this device just leave it alone. If flashing the radios is what you want, try the Aroma radio installer for Sense,
if I remember correctly, I think I flashed a radio while running SlimROM and the radio did not reset after reboot.
P.S. If you decide to do it, before hand, find a JTAG tech that has experience with it and can fix this problem, and post it here, please.
I'm still holding on to it in case I find such a person.
sns00 said:
To save you money, time and grief DONT DO IT.
Surely me and most everyone else is thankful that these guys spend time developing and tinkering but I screwed 2 One S,
that is when those disclaimers kick in, and I also looked, not exhaustively, for a skilled JTAG tech/user, the guy I sent it to
said he couldn't figure it out.
Maybe someone here can; most people that JTAG said that doing it to that phone is hard because it has to be taken apart.
Honestly, S-Off would make sense if its a new device to come in the market, as you have noticed, most ROMs and apps just
disappeared and the latest radio put together by someone in here is a 1.35.XX.XX. Since ROMs are limited, and most developers
dont even bother with this device just leave it alone. If flashing the radios is what you want, try the Aroma radio installer for Sense,
if I remember correctly, I think I flashed a radio while running SlimROM and the radio did not reset after reboot.
P.S. If you decide to do it, before hand, find a JTAG tech that has experience with it and can fix this problem, and post it here, please.
I'm still holding on to it in case I find such a person.
Click to expand...
Click to collapse
OP is four month old ...
I never screwed up ANY HTC phone, because they are pretty nice to handle. If the phone fits the prerequisites S-OFF is easy to gain. That users screw their phones by wrong handling is not the dev's fault
Well, good for you:victory:. Since you know so much, why not show everyone else how to properly handle the device?
Did not mentioned methods/names, so I think I did not offended anyone. If software/hardware did not break, there wouldn't
be a disclaimer on the device and on the software.
That the post is 4 months old is irrelevant, we are not the only ones with One S. Next time provide a solution along with criticism.
If this post offended anyone in any way shape or form, complain to a moderator so my post can be erased.
LS.xD said:
OP is four month old ...
I never screwed up ANY HTC phone, because they are pretty nice to handle. If the phone fits the prerequisites S-OFF is easy to gain. That users screw their phones by wrong handling is not the dev's fault
Click to expand...
Click to collapse
sns00 said:
Well, good for you:victory:. Since you know so much, why not show everyone else how to properly handle the device?
Did not mentioned methods/names, so I think I did not offended anyone. If software/hardware did not break, there wouldn't
be a disclaimer on the device and on the software.
That the post is 4 months old is irrelevant, we are not the only ones with One S. Next time provide a solution along with criticism.
If this post offended anyone in any way shape or form, complain to a moderator so my post can be erased.
Click to expand...
Click to collapse
I'm fine with your post I try to help in any case I can. Since today I "bricked" one Samsung phone by following a incorrect guide from another forum, cost me 40$ to repair the bootloader. But that can happen and its totally okay for me and I won't stop modding phones just because of it. For most users S-OFF works without any problem and grant a lot of benefits. So just because you screwed up two One S you can't tell other members to don't set their phone S-OFF as it will probably brick...
Dude, they will do whatever they want with their devices, regardless of what you , me or anyone say.
And the same way you can speak your piece, I can speak my piece, so do not tell me that I can't say this or that. If you don't like what others have to say, there's a number of things you could do instead of reading what I type.
Just sharing an experience that things can go wrong, as it just happened to you. S-Off'ing a phone is something I wouldn't pontificate to a regular user, because if things don't work out I'm not going to pay for a replacement or repair costs. That mod is a "at your own risk" as most other mods are. Do you realize we are a minority, a big chunk of the world don't even install themes on their devices, millions of locked bootloaders, billions of S-On devices and I had nothing to do with it; what are you going to do about that?
S-On works for me, so far, with my M8 GPe, I don't earn a living working with phones or anything related to it, I don't even know how to make a simple app, so what I post is not the gospel, as I assumed it is implied.
"For MOST users S-OFF works..." I rest my case.
LS.xD said:
I'm fine with your post I try to help in any case I can. Since today I "bricked" one Samsung phone by following a incorrect guide from another forum, cost me 40$ to repair the bootloader. But that can happen and its totally okay for me and I won't stop modding phones just because of it. For most users S-OFF works without any problem and grant a lot of benefits. So just because you screwed up two One S you can't tell other members to don't set their phone S-OFF as it will probably brick...
Click to expand...
Click to collapse
sns00 said:
"For MOST users S-OFF works..."
Click to expand...
Click to collapse
Most off the poeple, who set their HTC One S and other HTC devices S-OFF, still enjoy a working phone after this modification.
Better?
I just got one question left.
After you broke one HTC One S, why you did you risk doing (probably the same thing) again?

What are the chances of BRICKING your phone via rooting?

Hi. I've been wanting to root my phone for a while now, but since as I am still a kid, I asked my parents if I could. They didn't like the idea of bricking. I tried to explain how low the risks are to them, but no.
I'm pretty sure that hearing professional's opinions on it would atleast help to change their mind.
You may be thinking, since im only a kid, that I dont know all this types of stuff? Well, I spend most of my time on the computer and I generally am really good with them.
I know a good of C++, but thats beside the topic.
(I would be using kingroot's one click since I have a nexus 5)
Thank you, and best regards,
R3pix.
R3pix said:
Hi. I've been wanting to root my phone for a while now, but since as I am still a kid, I asked my parents if I could. They didn't like the idea of bricking. I tried to explain how low the risks are to them, but no.
I'm pretty sure that hearing professional's opinions on it would atleast help to change their mind.
You may be thinking, since im only a kid, that I dont know all this types of stuff? Well, I spend most of my time on the computer and I generally am really good with them.
I know a good of C++, but thats beside the topic.
(I would be using kingroot's one click since I have a nexus 5)
Thank you, and best regards,
R3pix.
Click to expand...
Click to collapse
I'm going to have to give you a thumbs down on rooting.
If you need king root to root a nexus, you don't know what your doing and shouldn't root.
bweN diorD said:
I'm going to have to give you a thumbs down on rooting.
If you need king root to root a nexus, you don't know what your doing and shouldn't root.
Click to expand...
Click to collapse
I know how to root without KR, but it seems like the easiest way.. (I meant since it supports it)
R3pix said:
I know how to root without KR, but it seems like the easiest way.. (I meant since it supports it)
Click to expand...
Click to collapse
i can root any nexus the right way in under 5 minutes. how is that difficult? and better to use the trash root that king gives you?
no one is going to support your petition to be allowed to root, when your using king on a nexus.
dont believe me? go post exactly what you posted here in the n5 forum. they will flame you mercilessly, i guarantee it.
im being nice about the situation, trust me lol
It's pretty damn hard to actually brick a Nexus. Permanently, anyway. In fact, I'm not sure it's even possible. With TWRP recover you can just restore from a back-up if you screw something up, and as long as you can boot into download mode, you can always just reflash the factory firmwares from a PC.
However, I think the method you'd use is less important than the question of why you want or think you need to root in the first place. If it's to learn about Android, programming, app making, etc for a future career (or even just a hobby) then I think it's a great idea. But not on your Nexus 5, if that's your only phone. Even if you screw something up, but not permanently, you still don't want to be without your phone for however long it takes to fix it.
I don't know how much money might be at your disposal (or your parents), but my suggestion would be to look on Swappa or eBay for something cheap to play around and learn with. Like a Nexus 4 or Galaxy S3. Both can be had for under $100 if you don't mind a little wear and tear. Heck, there's a brand new 16GB Nexus 4 listed right now for $123. If you can afford just a bit more, a second Nexus 5 for ~$150 would be an even better device to learn on, since it has official Marshmallow 6.0. Heck, a Nexus 7 tablet would be learning device, with its bigger screen.
You've already shown commendable responsibility in asking your parents and not just going ahead behind their backs, so I'll say this to you: If you want to convince your parents to let you try, or better yet, get the second device to experiment with, explain to them that a smartphone isn't a phone anymore. It's a computer that fits in your pocket that you can make calls with. And a Nexus is like a home-built PC that doesn't require restore disks and impossible-to-find drivers to fix if you happen to screw something up. And frankly, screwing up and learning how to fix your mistakes and not make others is all part of the knowledge process. Trust me, we've all done it.
But, if you want to root just to get free gems and gold and screenshot Snapchat pictures without the other party knowing, then that's an entirely different thing. And I'm not your parents.
Reasons for bricking a device.
Which are the major reasons which results into a useless bricked device?? I frequently use xposed modules and my device is mtk 6592 chipset one.
Please throw some light on my querry. Thanks
SKDesignsuccw said:
Which are the major reasons which results into a useless bricked device?? I frequently use xposed modules and my device is mtk 6592 chipset one.
Please throw some light on my querry. Thanks
Click to expand...
Click to collapse
the #1 way to brick your device from rooting, or any other mod is user error.

Categories

Resources