{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
Edit your device's build.prop file to say that the device/model is a Sprint Galaxy S5. For galaxy S5 if follow the pattern of KLTETMO, KLTEATT (AT&T), KLTEAIO (Cricket),etc. I'm not sure that the string is for Sprint, but it should be easy enough to find using the search.
neatojones said:
Edit your device's build.prop file to say that the device/model is a Sprint Galaxy S5. For galaxy S5 if follow the pattern of KLTETMO, KLTEATT (AT&T), KLTEAIO (Cricket),etc. I'm not sure that the string is for Sprint, but it should be easy enough to find using the search.
Click to expand...
Click to collapse
I've looked around but couldn't find anything :crying:
The string for sprint is KLTESPR.
Sent from my SM-G900A using XDA Free mobile app
neatojones said:
Edit your device's build.prop file to say that the device/model is a Sprint Galaxy S5. For galaxy S5 if follow the pattern of KLTETMO, KLTEATT (AT&T), KLTEAIO (Cricket),etc. I'm not sure that the string is for Sprint, but it should be easy enough to find using the search.
Click to expand...
Click to collapse
I discourage changing system files like this for simply an icon change. I believe there is an xposed mod floating around to change the icons. Otherwise, simply renaming the image files inside the framework-res.apk
Sent from my SM-G900T using Tapatalk
elesbb said:
I discourage changing system files like this for simply an icon change. I believe there is an xposed mod floating around to change the icons. Otherwise, simply renaming the image files inside the framework-res.apk
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
While I understand that concern, there shouldn't be much risk in changing the one line. The process I described is the method used by the manufacturer themselves and is therefore, likely the most "pure" way of making the change. If it doesn't result in the desired effects it can always be changed back. Arguably safer and easier than using a "hack" such setting up and trying to use xposed in this case. While possibly the safest if someone knows what they are doing, most less experience users would be unable to rename files in an apk. Further, this is also changing a "system file". While it doesn't necessary make it right, there are several other threads with the same recommendation as mine. But, as an important notice to anyone reading this: Any system modification has potential for serious and unexpected consequences.. That includes all of those mentioned above.
neatojones said:
While I understand that concern, there shouldn't be much risk in changing the one line. The process I described is the method used by the manufacturer themselves and is therefore, likely the most "pure" way of making the change. If it doesn't result in the desired effects it can always be changed back. Arguably safer and easier than using a "hack" such setting up and trying to use xposed in this case. While possibly the safest if someone knows what they are doing, most less experience users would be unable to rename files in an apk. Further, this is also changing a "system file". While it doesn't necessary make it right, there are several other threads with the same recommendation as mine. But, as an important notice to anyone reading this: Any system modification has potential for serious and unexpected consequences.. That includes all of those mentioned above.
Click to expand...
Click to collapse
Actually, the manufacturer doesn't, the carrier does. There are MANY bad things that can happen when changing the "type" of device you are using. Firstly, the most scary one: Using any app/script/code that relies on the system property (which is what build.prop values define) such as ROM Manager (For installing ROMs and recovery) as well as Mobile Odin can and most likely WILL result in a brick. You have a T-Mobile device, you are now telling apps that heavily rely on what device they are running on to properly do the work they need to, are now thinking they are on a Sprint device. Guess what, its gonna run code that is designed for a Sprint device. This means anything dealing with the radio will get effed up because Sprint is a CDMA phone NOT a GSM phone, partition details could be different and I believe they are now on the S5, recovery images are WAY different for each phone, so flashing the wrong recovery will definitely get you into a pickle. All I'm saying is that changing what the phone thinks it is not a safe method for simply changing a lousy icon. There is more margin for error and causing damage down the road then good you are getting out of it. Yes other threads have mentioned to change the build.prop, I'm not saying its wrong, I'm just saying its unsafe and has a higher potential for future errors, I already read a thread where a guy bricked because they used Mobile Odin Pro to flash a tar file and it bricked their device because they changed the build.prop device name (they recovered because the bootloader was intact but they surely weren't tech savy and had a hard time getting back to it).
The BEST method, would be xposed, why? Because someone else has done the heavy lifting for you. They took the time to analyze the code and make the appropriate changes and if it doesn't work you simply reboot and press the power button ten (i think) times and boom xposed is disabled. Its the most foolproof modding solution for anyone (including power users as myself) why do you thinks its become so popular? lol.
I'm not trying to talk down on you or anything, I'm just trying to help you understand the implications and full extent of what is going on in such a simple line change in a system file. Because, the statement you made "Any system modification has potential for serious and unexpected consequences" this is only true when you have no idea what it is you are doing
In addition, if someone doesn't know how to make the simple png file name changes inside the framework-res.apk, they merely need to ask or Google it (which the latter should be done first). Why? Because this is a site to learn and learning something can help in the future with a similar mod for whoever the person was that asked about it.
I am sorry if I came off sounding harsh or condescending, I just hate to see someone brick their device because they wanted a simple icon change
elesbb said:
Actually, the manufacturer doesn't, the carrier does. There are MANY bad things that can happen when changing the "type" of device you are using. Firstly, the most scary one: Using any app/script/code that relies on the system property (which is what build.prop values define) such as ROM Manager (For installing ROMs and recovery) as well as Mobile Odin can and most likely WILL result in a brick. You have a T-Mobile device, you are now telling apps that heavily rely on what device they are running on to properly do the work they need to, are now thinking they are on a Sprint device. Guess what, its gonna run code that is designed for a Sprint device. This means anything dealing with the radio will get effed up because Sprint is a CDMA phone NOT a GSM phone, partition details could be different and I believe they are now on the S5, recovery images are WAY different for each phone, so flashing the wrong recovery will definitely get you into a pickle. All I'm saying is that changing what the phone thinks it is not a safe method for simply changing a lousy icon. There is more margin for error and causing damage down the road then good you are getting out of it. Yes other threads have mentioned to change the build.prop, I'm not saying its wrong, I'm just saying its unsafe and has a higher potential for future errors, I already read a thread where a guy bricked because they used Mobile Odin Pro to flash a tar file and it bricked their device because they changed the build.prop device name (they recovered because the bootloader was intact but they surely weren't tech savy and had a hard time getting back to it).
The BEST method, would be xposed, why? Because someone else has done the heavy lifting for you. They took the time to analyze the code and make the appropriate changes and if it doesn't work you simply reboot and press the power button ten (i think) times and boom xposed is disabled. Its the most foolproof modding solution for anyone (including power users as myself) why do you thinks its become so popular? lol.
I'm not trying to talk down on you or anything, I'm just trying to help you understand the implications and full extent of what is going on in such a simple line change in a system file. Because, the statement you made "Any system modification has potential for serious and unexpected consequences" this is only true when you have no idea what it is you are doing
In addition, if someone doesn't know how to make the simple png file name changes inside the framework-res.apk, they merely need to ask or Google it (which the latter should be done first). Why? Because this is a site to learn and learning something can help in the future with a similar mod for whoever the person was that asked about it.
I am sorry if I came off sounding harsh or condescending, I just hate to see someone brick their device because they wanted a simple icon change
Click to expand...
Click to collapse
I disagree with you regardless (IE: You mean to say that the carrier built their icons into some other carriers ROM? Doubt it...It was the manufacturer.) But, thanks for enlightening me on your opinions. Neither of us want the user to break their device. Since we're giving out advice: I would caution any reader not to assume any user here has limited knowledge of android based on their post count or vice versa.
neatojones said:
I disagree with you regardless (IE: You mean to say that the carrier built their icons into some other carriers ROM? Doubt it...It was the manufacturer.) But, thanks for enlightening me on your opinions. Neither of us want the user to break their device. Since we're giving out advice: I would caution any reader not to assume any user here has limited knowledge of android based on their post count or vice versa.
Click to expand...
Click to collapse
The carrier determines the build.prop value. But i always assume every user has a limited knowledge of anything when they are personally requesting how to do something. Any other user would have used the tools provided to them(Google xda search, etc) because this topic has definitely been covered before.
elesbb said:
The carrier determines the build.prop value.
Click to expand...
Click to collapse
I can see you really want to be right about this. I'm discontinuing to follow this thread. I don't think either of us is adding anything useful at this point (certainly not myself anyway).
AND this is why I have a low post count on XDA. Carry on with the topic at hand.
Edit - To the OP (Or any other curious readers): I just tested this mod by making the recommendations I suggested. It DID NOT change how the product is identified in download mode or for ODIN. It may be possible to change how the device is identified in download mode, but this is not (and was not intended to be) a method to do so. However, this does not mean it is not possible through some other method or that the method could not cause problems with your device in some other fashion.
neatojones said:
I can see you really want to be right about this. I'm discontinuing to follow this thread. I don't think either of us is adding anything useful at this point (certainly not myself anyway).
AND this is why I have a low post count on XDA. Carry on with the topic at hand.
Edit - To the OP (Or any other curious readers): I just tested this mod by making the recommendations I suggested. It DID NOT change how the product is identified in download mode or for ODIN. It may be possible to change how the device is identified in download mode, but this is not (and was not intended to be) a method to do so. However, this does not mean it is not possible through some other method or that the method could not cause problems with your device in some other fashion.
Click to expand...
Click to collapse
I never once said download mode did I? It's called mobile Odin pro. It's an app genius. I don't mind being wrong when I am. You're telling a guy to do a mod that could potentially brick his device. You're right that the mod will work to get what the OP wants. But it's not the best. That's all I've ever been saying. I'm giving the OP safer more practical ways to get what they want. I'm giving them options. That's all I've been doing. Lol
Sent from my SM-G900T using Tapatalk
I've changed 2 values in my build.prop file so I have the Verizon symbols on my T-Mobile S5, and it has not led to any issues whatsoever. These are the 2 lines I've modified:
ro.product.device=kltevzw
ro.product.name=kltevzw
No issues whatsoever.... Running any Touchwiz Rom anyway
neatojones said:
I can see you really want to be right about this. I'm discontinuing to follow this thread. I don't think either of us is adding anything useful at this point (certainly not myself anyway).
AND this is why I have a low post count on XDA. Carry on with the topic at hand.
Edit - To the OP (Or any other curious readers): I just tested this mod by making the recommendations I suggested. It DID NOT change how the product is identified in download mode or for ODIN. It may be possible to change how the device is identified in download mode, but this is not (and was not intended to be) a method to do so. However, this does not mean it is not possible through some other method or that the method could not cause problems with your device in some other fashion.
Click to expand...
Click to collapse
Apparently, I needed to be more direct: I tested my device in download mode and with Odin after doing the mod I mentioned. It was found to be safe.
On the other hand: Other software apps or procedures may not be safe. Such apps/procedures include burning your device with a torch, dropping it from a plane, or using Mobile odin pro*. As such I would avoid these things.
*Another user has tested Mobile Odin Pro and found it to be unsafe. It was not retested for the puposes of this thread. The other two haven't been formally tested, YET.**
Let's keep moving forward. Or by all means we can both keep making fools of ourselves.
**Any tests will be at discretion of device owner and no damages shall be levied against XDA or this user.
i always changed to AT&T icon and never has any problem.
neatojones said:
I can see you really want to be right about this. I'm discontinuing to follow this thread. I don't think either of us is adding anything useful at this point (certainly not myself anyway).
AND this is why I have a low post count on XDA. Carry on with the topic at hand.
Edit - To the OP (Or any other curious readers): I just tested this mod by making the recommendations I suggested. It DID NOT change how the product is identified in download mode or for ODIN. It may be possible to change how the device is identified in download mode, but this is not (and was not intended to be) a method to do so. However, this does not mean it is not possible through some other method or that the method could not cause problems with your device in some other fashion.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s5/themes-apps/missing-link-aroma-powered-theme-t2867014
You will find what you are looking for in this installer.
Related
Warning!!! Assuming you can find QPST and get it running, don't play around unless you know what you are doing. It is extremely likely you will brick your phone.
In the midst of my poking around I discovered you can enable the phone's diag mode with:
In rom:
Code:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
In recovery:
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
I haven't been able to find any driver downloads that work with it, but I did get Window 7 64 bit working:
In fastboot:
Code:
fastboot oem enableqxdm
1. Open Windows device manager
2. Double click on HTC DIAG (or HTC 9k DIAG for LTE, I haven't tried that one yet though)
3. Update Driver
4. Browse My computer for software
5. Let me pick from a list of device drivers on my computer
6. Ports (COM and LPT)
7. HTC Corporation
8. HTC Diagnostic Interface
So far I have only done this from inside my booted rom. I still need to test from recovery.
This is a screen shot of some of what is available in QPST EFS explorer:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a small sample of what is available in QPST RF NV Manager:
Very interesting.
Maybe this will lead to something more
Until you release something useful that corresponds to this or are trying to create a think tank for a specific problem, this probably belongs in the general section along with the photos.
con247 said:
Until you release something useful that corresponds to this or are trying to create a think tank for a specific problem, this probably belongs in the general section along with the photos.
Click to expand...
Click to collapse
"If you are posting something that others may use regarding development such as a new ROM, kernel, guide, mod, recovery, or tool, it will be posted there. "
All of my threads have directly pertained to this statement. The android development folder is where this info has generally been posted for other phones, so it seemed reasonable to do so for the Rezound as well.
If mods want to move it I don't care. I was just posting in the place that most closely fit the rules.
Cant you enter this mode with some code on the dialer? I know with sprint phones you can.
fix-this! said:
Cant you enter this mode with some code on the dialer? I know with sprint phones you can.
Click to expand...
Click to collapse
I would assume so, although I don't know the code. The benefit of this method is that it is easily scriptable, and you can use it from recovery (although the path is slightly different).
The only benefits to this diag mode is manually changing the PRL, or if you wanted to provision the phone to another cdma network, Other then that no real development use/need.
bouchedag said:
The only benefits to this diag mode is manually changing the PRL, or if you wanted to provision the phone to another cdma network, Other then that no real development use/need.
Click to expand...
Click to collapse
Man... what is it with people in this forum.
jefffeely said:
Man... what is it with people in this forum.
Click to expand...
Click to collapse
The fact you keep posting worthless information in our development forum.
Sent from my ADR6425LVW using XDA
nosympathy said:
The fact you keep posting worthless information in our development forum.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
I am sorry that you are the opinion that it is worthless. However, it does have merit and I am glad I posted it for the people that it helped out. Whatever you think, being able to access diagnostic modes for devices is essential to development. All the other people who have posted the same information in the other HTC phone dev forums seem to agree with me. Since It took me quite a while to get some of this working on the rezound due to it not being in this forum, I thought it might be useful to someone else. I personally like sharing information I have learned. The path to enable this diagnostic mode is not the same as any other phone I came across. This leads me to believe that it is useful information.
Just tell us what we can do with it. Then it isn't worthless. That is seriously the only difference. If there is something that can be done with it, by all means, post it. I know you don't want to help me so I won't be expecting anything.
con247 said:
Just tell us what we can do with it. Then it isn't worthless. That is seriously the only difference. If there is something that can be done with it, by all means, post it. I know you don't want to help me so I won't be expecting anything.
Click to expand...
Click to collapse
I honestly assumed that all the all knowing people in this forum would already know why one would want to be able to access our phone with QPST. I've only been doing HTC dev for a couple days and I already figured it out.
Off the top of my head:
Back up NV ram without being in recovery
Full access to EFS
Access to change all NV variables
Radio troubleshooting
Radio transmit power
A real world example would be the ability to trouble shoot the SMS problems associated with using the Rezound on non-Verizon networks.
I wasn't even looking for any of this. All I wanted to do was turn on the serial output over USB, but I came across this information and I thought someone else would find it useful. As I've said before, people thought it was useful for other phones. How was I to know that it would be received as such here.
I know that a lot of you already know this stuff. The problem is that since it was assumed we wouldn't have S-OFF no one has posted it for our phone. That means that the people who are doing dev work more complicated than changing font size in a ROM have had to look elsewhere for information. I haven't posted a single thing in this dev forum that wasn't posted in another HTC phone's dev forum. I also haven't posted anything that was already clearly answered in a post in the rezound forums. I personally think that everything I have posted is relevent to dev work. Other forums have used blurry-cam shots for developing S-OFF. It was reasonable to think that clear highres shots might be useful for something. People are still locking and unlocking their bootloaders. It was reasonable to think that having super CID so that you wouldn't have to lock the bootloaders before flashing an RUU would be useful to some. Personally, I like being able to have my hboot not say "locked". If nothing else, how is that any different from people who like a different splash screen for their phone? I can guarantee I've spent more time in hboot than anyone here has spent looking at their splash screen. Aside from that, I actually have come across some very minuscule things that superCID brings that I can't articulate right now. I'm way too pissed off to get that technical. Maybe it is worthless, but with the work I'm doing it would be stupid to not consider it. Until I posted here I had no clue people would think it was worthless and there wasn't anything in any of our forums to suggest otherwise.
I could go on, but I'll change direction a bit. I'm working on getting 100% pure AOSP working with a current 3.3 kernel and a new customized hboot. I already have the kernel compiled and semi-working and would be in the same place with AOSP but google made changes to their build process in the last month and I ended up with a corrupted build tree. I haven't wanted to say anything because a. I don't want to get people excited if it ended up not working or I decide something else is more interesting, and b. because I want to have something that is past the pre-alpha stage before I say anything.
EVERYTHING I have posted is useful information for the DEV work I am doing. I just wasted 5+ hours dealing with the fact I thought someone else might like the info and having to deal with the snooty people that ruin XDA for the people like me who are doing this kind of work for the pure thrill of the fact that it is borderline impossible. I personally think AOSP is flawed at its core and is ultimately a waste of time, but I don't care because it is still something fun to work on and I'd like to think that I can ultimately make a tiny difference towards fixing the issues I see with it. Discussions like this just make me want to delete my account and just keep the info to myself.
Well if you would have posted that to begin with we wouldn't be having this problem.
con247 said:
Well if you would have posted that to begin with we wouldn't be having this problem.
Click to expand...
Click to collapse
I assumed that all knowing people like you already knew it. I admit it is completely my bad for not going deeper into it. Aside from the fact that I thought I was doing the right thing part of the reason I posted in the dev forums is because I didn't want people who haven't at least read the dev forums messing around with this stuff since there is a pretty much 100% chance of ruining your phone if you don't know what you are doing (and probably not much lower of a chance even if you do. I'm honestly kind of surprised I haven't bricked my phone yet).
best thread ever.
jayochs said:
best thread ever.
Click to expand...
Click to collapse
I think you'd like the other one better.
jefffeely said:
I assumed that all knowing people like you already knew it. I admit it is completely my bad for not going deeper into it. Aside from the fact that I thought I was doing the right thing part of the reason I posted in the dev forums is because I didn't want people who haven't at least read the dev forums messing around with this stuff since there is a pretty much 100% chance of ruining your phone if you don't know what you are doing (and probably not much lower of a chance even if you do. I'm honestly kind of surprised I haven't bricked my phone yet).
Click to expand...
Click to collapse
Since you mentioned it. Might be a good idea to put a big red disclaimer at the top stating that if you don't know what you are doing you will brick your phone.
Concerning aosp are you close to just booting? Or have you been working on ril too?
Sent from my ADR6425LVW using XDA
jefffeely said:
I think you'd like the other one better.
Click to expand...
Click to collapse
oh i love both of them equally.
nosympathy said:
Since you mentioned it. Might be a good idea to put a big red disclaimer at the top stating that if you don't know what you are doing you will brick your phone.
Concerning aosp are you close to just booting? Or have you been working on ril too?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Good point, will do so. Don't know why I didn't think of it.
Unfortunately I lost all my work with AOSP. I only just now got the source re-synced. Hopefully it won't take me too long to get back up and going though. I'm going to start from scratch this time instead of building off of someone else's work so when I have errors they will be mine and I won't have to look all over the place trying to figure out what is going on. I did just get done with a basic generic build though so at least that is working.
jayochs said:
oh i love both of them equally.
Click to expand...
Click to collapse
Glad to please.
The best part is that my thanks meter has been going up lol.
Hi Everyone,
I just got my Galaxy S2 back, model number GT-19100M. I had sent it in to get it unlocked, the sim and the carrier unlock. I assume that this would be rooted to have accomplished this?
They had an issue unlocking the carrier and had to reflash the phone to gingerbread before they were able to unlock the carrier. So I got it baack and the version is 4.0.3 now.
So I did some googling about how to tell if it was rooted. Now, from my understanding that to flash the phone with a rom it would have to be rooted. So I came across about using Root Checker, So i installed it and it said it wasnt rooted, I then installed ConnectBot and the thread (not from here) said that if a prompt came up with a # then it meant it was rooted, and if it came up with a $ at the prompt then it wasnt rooted. Low and behold it showed a $.
So all in all how do I tell if it was rooted? It cost me 50$ and well over a week and a half to get it back. So were the two applications correct and if not what is the right way to tell if it was rooted or is there something I should notice on the phone?
Thanks for any and all help on this situation.
BlindSession said:
Hi Everyone,
I just got my Galaxy S2 back, model number GT-19100M. I had sent it in to get it unlocked, the sim and the carrier unlock. I assume that this would be rooted to have accomplished this?
They had an issue unlocking the carrier and had to reflash the phone to gingerbread before they were able to unlock the carrier. So I got it baack and the version is 4.0.3 now.
So I did some googling about how to tell if it was rooted. Now, from my understanding that to flash the phone with a rom it would have to be rooted. So I came across about using Root Checker, So i installed it and it said it wasnt rooted, I then installed ConnectBot and the thread (not from here) said that if a prompt came up with a # then it meant it was rooted, and if it came up with a $ at the prompt then it wasnt rooted. Low and behold it showed a $.
So all in all how do I tell if it was rooted? It cost me 50$ and well over a week and a half to get it back. So were the two applications correct and if not what is the right way to tell if it was rooted or is there something I should notice on the phone?
Thanks for any and all help on this situation.
Click to expand...
Click to collapse
1) u can check ur kernel and see.
2) also u can check for an app SuperSU or Superuser's presence in app drawer, if present ur phone is rooted else no.
3) u can install some apps like root explorer/browser etc and see, since they wrk only with root prievilage
Sun90 said:
1) u can check ur kernel and see.
2) also u can check for an app SuperSU or Superuser's presence in app drawer, if present ur phone is rooted else no.
3) u can install some apps like root explorer/browser etc and see, since they wrk only with root prievilage
Click to expand...
Click to collapse
Hi thanks for the reply,
I downloaded and ran SuperSu and got this pop up "There is no SU binary installed, and SuperSU cannot install it. This is a problem!". So then I downloaded Root Browser Lite, i opened it up and got a list of folders. So now I'm confused, I have SuperSU saying that there is a problem, and with Root Browser Lite it runs and gives me a list of folders.
My kernel version is as follows: 3.0.15-I9100MUGLD3-CL377577 [email protected] #3
From my understanding and please correct me if i am wrong, but to do both unlocks (sim and carrier) that it needs to be rooted?
Before I handed the phone over to the computer store to unlock it, I had asked if it would be rooted and they said yes, but i didnt copy all the stuff in the about phone, but I was supplied with my unlock code to use when i pop a different sim in it.
Also, when I looked at the messages when i got it back that there was a text from rogers and the carrier that i was using was Virgin, so it looks as though it was properly unlocked.
I dont have anyone near me at the moment with a different carrier sim card (My girlfriend uses Telus, I suppose I could pop hers in but she might throw a fit and think that I could screw her iphone up lol)
So what would be my next plan of action?
Thanks for your reply
BlindSession said:
Hi thanks for the reply,
I downloaded and ran SuperSu and got this pop up "There is no SU binary installed, and SuperSU cannot install it. This is a problem!". So then I downloaded Root Browser Lite, i opened it up and got a list of folders. So now I'm confused, I have SuperSU saying that there is a problem, and with Root Browser Lite it runs and gives me a list of folders.
My kernel version is as follows: 3.0.15-I9100MUGLD3-CL377577 [email protected] #3
From my understanding and please correct me if i am wrong, but to do both unlocks (sim and carrier) that it needs to be rooted?
Before I handed the phone over to the computer store to unlock it, I had asked if it would be rooted and they said yes, but i didnt copy all the stuff in the about phone, but I was supplied with my unlock code to use when i pop a different sim in it.
Also, when I looked at the messages when i got it back that there was a text from rogers and the carrier that i was using was Virgin, so it looks as though it was properly unlocked.
I dont have anyone near me at the moment with a different carrier sim card (My girlfriend uses Telus, I suppose I could pop hers in but she might throw a fit and think that I could screw her iphone up lol)
So what would be my next plan of action?
Thanks for your reply
Click to expand...
Click to collapse
well by seeing ur kernel it seems that its a stock kernel hence ur phone is not rooted.
may be after unlocking ur phone they might have flashed the stock kernel back to unroot ur phone i suppose
Sun90 said:
well by seeing ur kernel it seems that its a stock kernel hence ur phone is not rooted.
may be after unlocking ur phone they might have flashed the stock kernel back to unroot ur phone i suppose
Click to expand...
Click to collapse
After thinking for a moment, this does look like the kernel that was previously on it, I had played around with it before hand and I remember some things and the kernel looks familiar..
Well I believe you are correct that they reflashed it with the stock rom...Why they would do that is beyond me lol.
So I guess I am going to start rooting this on my own, would you please direct me to rooting this model? I know I can search this forum but I have done that before and noticed different ways of doing it. I just want to make sure that i do this properly using the proper thread and if i can do this properly then Im going to start on the path to rooting my S3 , So i guess my s2 is my practice
I do appreciate your replies and help with my situation
BlindSession said:
After thinking for a moment, this does look like the kernel that was previously on it, I had played around with it before hand and I remember some things and the kernel looks familiar..
Well I believe you are correct that they reflashed it with the stock rom...Why they would do that is beyond me lol.
So I guess I am going to start rooting this on my own, would you please direct me to rooting this model? I know I can search this forum but I have done that before and noticed different ways of doing it. I just want to make sure that i do this properly using the proper thread and if i can do this properly then Im going to start on the path to rooting my S3 , So i guess my s2 is my practice
I do appreciate your replies and help with my situation
Click to expand...
Click to collapse
the link below would be the simple on to start with rooting for u
http://forum.xda-developers.com/showthread.php?t=1746794
read the OP completely to understand the procedure and then proceed
good luck
Sun90 said:
the link below would be the simple on to start with rooting for u
http://forum.xda-developers.com/showthread.php?t=1746794
read the OP completely to understand the procedure and then proceed
good luck
Click to expand...
Click to collapse
Thanks alot for your help I'll let you know how it goes I will be calling the computer store tomorrow that i used to question them on why they would do that after saying that it would be rooted lol
BlindSession said:
Thanks alot for your help I'll let you know how it goes I will be calling the computer store tomorrow that i used to question them on why they would do that after saying that it would be rooted lol
Click to expand...
Click to collapse
Wow this looks confusing on where do I start lol
BlindSession said:
Wow this looks confusing on where do I start lol
Click to expand...
Click to collapse
nothing is confusing as long as u read and understand carefully what has been specified in those rooting method threads.
but still i would suggest u simply keep out of this rooting thing, if ur not sure about the same and unable to understand things about rooting properly
Sun90 said:
nothing is confusing as long as u read and understand carefully what has been specified in those rooting method threads.
but still i would suggest u simply keep out of this rooting thing, if ur not sure about the same and unable to understand things about rooting properly
Click to expand...
Click to collapse
I have read the rooting methods, and again reading it slower, I am not sure about this busybox thing, i think where i am getting confused because it doesnt seem to pop out to me saying if its ok to uninstall busybox and if i did would it still be rooted. I really dont some program running in the background to keep it rooted.
I have been writing software for over 5 years and i figured that this would be a walk in the park. Sit me infront of visual studio and i am a wiz with c#/Asp and sql, but with this i feel like complete noob and i am in actuality. Which is irritating me.
The reason behind having the desire to root this phone is because it should have been done when i got it unlocked 2) because with a rooted phone i have more options and control over this phone 3) because i dont know how and for being able to program that i should be able to do this. It seems like a different ball game and in all honesty knowledge is power and what i dont know how so it is a need to know how to do it. regardless if i wreck the phone, trial by fire i suppose. I cant learn if i dont attempt it and make the mistakes. When you learn how to do something and have come across making mistakes you tend to keep the knowledge more and appreciate what is learned.
Sorry, I got on my soap box on trying to justify doing this lol. But I do appreciate what you suggest. But Im going to try it and hopefully bring me out of my noob status lol.
i will keep you posted
Its not rocket science and what a load of rubbish about doing things wrong and wrecking your phone in order to learn.
What you do is read about other clowns wrecking their phones and dont do what they done-so you learn without any risk.
Just get rooted for now so you can use them fancy apps to get more control over you phone.Read about brickbug and look at some of the rom threads and also learn about cwm and odin.
Sent from my GT-I9100 using xda premium
theunderling said:
Its not rocket science and what a load of rubbish about doing things wrong and wrecking your phone in order to learn.
What you do is read about other clowns wrecking their phones and dont do what they done-so you learn without any risk.
Just get rooted for now so you can use them fancy apps to get more control over you phone.Read about brickbug and look at some of the rom threads and also learn about cwm and odin.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Forgive me for using the wrong words, I did not say to do things wrong and wreaking my phone. I should have phrased that differently, IF i do it wrong and wreck it somehow then it is a lessoned learned.I'm in no way out to wreck my phone, thats ridiculous. I have made many mistakes during programming that I have learned and remembered what not to do, some people learn the hard way to retain what they did wrong and not to repeat it. Not everyone learns the same way.
I completely understand about reading how others wreck their phone so i can learn without risk, and to read up on odin and brickbug, which is blatantly obvious.
As for fancy apps, you are kidding right? you think i want to root my phone to use fancy apps? I think not. i'm not some kid that likes shiney new things and to be the one to say "look what i got". That comment was utter disrespect. Maybe instead of trying to make me look like a dumbass you could be a little more helpful and not be so blantantly obvious on what i should do, which i already have started doing until i had to reply this.
Is this how you treat everyone that is starting to learn something new? You make obvious statements, mock by saying what isnt rocket science? I highly doubt that when you started doing this that you werent some dumbass in the beginning.
I appreciate the person who was replying to my questions and pointing me in the right direction, he was helpful. You were just being a ****. you know on forums dealing with c#/asp.net I dont act like you do to questions or statements that i feel are silly, especially to people just starting out. You must have been treated the way you treated me when you first started out, how many times did you feel like a dumbass from people that knew what they were talking about? probably still to this day in one way or another you are treated like an idiot. So instead of acting the way you were and still are treated, try acting decent and helpful and not counter-active.
I hope that there isn't more people acting like you did towards me to other people, if so then this isnt a place to learn.
Thanks for the praise.....
I ask myself every day....is rooting really that difficult?.Is this xda or facebook?.Whats with "life stories" included in posts?.Have all them guys that created stickies/guides wasted their time cos noobs/donks like you dont read them?.
And guys like Sun90 are helpful and intelligent....theyve helped me out before.
Sent from my GT-I9100 using xda premium
BlindSession said:
Forgive me for using the wrong words, I did not say to do things wrong and wreaking my phone. I should have phrased that differently, IF i do it wrong and wreck it somehow then it is a lessoned learned.I'm in no way out to wreck my phone, thats ridiculous. I have made many mistakes during programming that I have learned and remembered what not to do, some people learn the hard way to retain what they did wrong and not to repeat it. Not everyone learns the same way.
I completely understand about reading how others wreck their phone so i can learn without risk, and to read up on odin and brickbug, which is blatantly obvious.
As for fancy apps, you are kidding right? you think i want to root my phone to use fancy apps? I think not. i'm not some kid that likes shiney new things and to be the one to say "look what i got". That comment was utter disrespect. Maybe instead of trying to make me look like a dumbass you could be a little more helpful and not be so blantantly obvious on what i should do, which i already have started doing until i had to reply this.
Is this how you treat everyone that is starting to learn something new? You make obvious statements, mock by saying what isnt rocket science? I highly doubt that when you started doing this that you werent some dumbass in the beginning.
I appreciate the person who was replying to my questions and pointing me in the right direction, he was helpful. You were just being a ****. you know on forums dealing with c#/asp.net I dont act like you do to questions or statements that i feel are silly, especially to people just starting out. You must have been treated the way you treated me when you first started out, how many times did you feel like a dumbass from people that knew what they were talking about? probably still to this day in one way or another you are treated like an idiot. So instead of acting the way you were and still are treated, try acting decent and helpful and not counter-active.
I hope that there isn't more people acting like you did towards me to other people, if so then this isnt a place to learn.
Click to expand...
Click to collapse
hey buddy chill for now , in XDA u will face all sort of people, which is quite common ma8.
as for as ur 'Busybox' thing is concern, this is what it means.
BusyBox is a software application that provides many standard Unix tools, much like the larger (but more capable) GNU Core Utilities. BusyBox is designed to be a small executable for use with the Linux kernel, which makes it ideal for use with embedded devices. It has been self-dubbed "The Swiss Army Knife of Embedded Linux".
it will provide u all necessary things to have access to root of ur phone, while SuperSU or Superuser grants necessary permissions to all those apps which need 'Root Access' to perform efficiently.
if u remove busybox then u will loose root access to ur phone for sure.
hope the above things ar clear for u for now
Sun90 said:
hey buddy chill for now , in XDA u will face all sort of people, which is quite common ma8.
as for as ur 'Busybox' thing is concern, this is what it means.
BusyBox is a software application that provides many standard Unix tools, much like the larger (but more capable) GNU Core Utilities. BusyBox is designed to be a small executable for use with the Linux kernel, which makes it ideal for use with embedded devices. It has been self-dubbed "The Swiss Army Knife of Embedded Linux".
it will provide u all necessary things to have access to root of ur phone, while SuperSU or Superuser grants necessary permissions to all those apps which need 'Root Access' to perform efficiently.
if u remove busybox then u will loose root access to ur phone for sure.
hope the above things ar clear for u for now
Click to expand...
Click to collapse
Hi Sun90,
You are absolutely right when it comes to types of people that I wil come across in this forum or any other forum for that matter, I just didnt expect someone to start flaming right off the bat.
Thank you for the explaination on 'BusyBox', I understand what you are saying. My concern was that I didnt want to have to rely on something that had to be constantly running on my phone to ensure that it stays rooted. I gather from what you said about buysbox that its just tools, and not something that constantly runs. The swiss army metaphor, makes sense.
I have searched through these forums and somethings that may be obvious and cut and dry to people that have done this, isnt always the case to everyone else. I get left with many questions after reading threads. I have read many threads here and throughout online on rooting. Some guides are easy, they tell you how but never the 'why'.
I have heard alot about odin, and I have read things where i plug my phone in and run a 'runme.bat' that does it all but explain why.
Today I'm going to be reading deeper on Odin and Clockworkmod and trying to find the correct secure and unsecure kernel. I hope to run across more people like you that actually are here to help and not wanting to show how much they know by being condescending to make themselves feel better about themselves.
In the end, for me, its not enough to do it but to know the whys behind it. Thank you for your patience and the help.
BlindSession said:
Hi Sun90,
You are absolutely right when it comes to types of people that I wil come across in this forum or any other forum for that matter, I just didnt expect someone to start flaming right off the bat.
Thank you for the explaination on 'BusyBox', I understand what you are saying. My concern was that I didnt want to have to rely on something that had to be constantly running on my phone to ensure that it stays rooted. I gather from what you said about buysbox that its just tools, and not something that constantly runs. The swiss army metaphor, makes sense.
I have searched through these forums and somethings that may be obvious and cut and dry to people that have done this, isnt always the case to everyone else. I get left with many questions after reading threads. I have read many threads here and throughout online on rooting. Some guides are easy, they tell you how but never the 'why'.
I have heard alot about odin, and I have read things where i plug my phone in and run a 'runme.bat' that does it all but explain why.
Today I'm going to be reading deeper on Odin and Clockworkmod and trying to find the correct secure and unsecure kernel. I hope to run across more people like you that actually are here to help and not wanting to show how much they know by being condescending to make themselves feel better about themselves.
In the end, for me, its not enough to do it but to know the whys behind it. Thank you for your patience and the help.
Click to expand...
Click to collapse
:laugh: u should not misundertand people's comments here in the first place ma8, but do take it positively, since everybody in XDA is willing to Help one another for sure, But some times the helping way which really Confuses the matter for sure
since i assume ur a man who is more hungry for indepth knowledge of things u come accross,which is really good in its own way, I wish u success for ur journey seeking the same here on XDA
Good Luck:good:
Sun90 said:
:laugh: u should not misundertand people's comments here in the first place ma8, but do take it positively, since everybody in XDA is willing to Help one another for sure, But some times the helping way which really Confuses the matter for sure
since i assume ur a man who is more hungry for indepth knowledge of things u come accross,which is really good in its own way, I wish u success for ur journey seeking the same here on XDA
Good Luck:good:
Click to expand...
Click to collapse
Well I just downloaded CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip, and Odin3-ver3.5 and am about to follow Chainfire's thread with its step by step guide, i found his guide to be pretty insightful. Another thing I got confused on was the difference between I1900, I1900M and I found out that the only difference between the 2 was nothing. One question though, after i root the phone and if i ever do a factory reset on it does it stay rooted or do I have to do the process over, likewise with busy box.
I did copy down what version my phone is running if something goes wrong...
I'll post back soon with either success or failure.
BlindSession said:
Well I just downloaded CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip, and Odin3-ver3.5 and am about to follow Chainfire's thread with its step by step guide, i found his guide to be pretty insightful. Another thing I got confused on was the difference between I1900, I1900M and I found out that the only difference between the 2 was nothing. One question though, after i root the phone and if i ever do a factory reset on it does it stay rooted or do I have to do the process over, likewise with busy box.
I did copy down what version my phone is running if something goes wrong...
I'll post back soon with either success or failure.
Click to expand...
Click to collapse
You won't lose root if you factory reset. Only way to unroot is to flash stock firmware again.
Sent from my GT-I9100 using Tapatalk 2
Thanks Spiralzz
So right now i followed the instructions, i have odin running. I have the phone itself in usb debugging... but it looks like odin froze up..its at SetupConnection and hasnt continued. Could i be wrong and it takes time? Its been in this state for about 5 minutes now.
Sent from my SGH-I747M using xda app-developers app
Ok well, i wasnt successful. Odin came back with a fail. It came back 3 times failing.
Sent from my SGH-I747M using xda app-developers app
Q&A for [ROOT] Easiest Way To Root Your LG G3 [Stump APK]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Re-root with IOROOT after reset (STUMP, IOROOT, BUMP, TRWP)
Not a question, just a thanks.
Rooted with STUMP initially just fine. Then had to factory reset due to a malfunctioning app.
Stump does not (yet) support re-root after reset unless you flash back to stock.
Thanks for all the helpful posts in several threads. I Rooted using IOROOT, using ADB no problem. http://forum.xda-developers.com/showthread.php?t=2776198
Now running BUMP TRWP recovery too. http://forum.xda-developers.com/ver...pment/bump-unlock-lg-g3-twrp-verizon-t2900590
BUT, since i'm somewhat of a n00b, i used Flashify from the Google Play store to flash the image. Worked flawlessly. http://www.droidforums.net/threads/...ock-and-install-recovery-on-any-lg-g3.275056/
(in flashify, pick 'choose file' and navigate to the .IMG file)
Thanks!!
New to this - hopefully this is the right thread
I am the noobest noob around when it comes to android based phones (hoping to climb the mountain of knowledge to start developing during this winter if I have the time!).
The first thing I want to say is a clear "thank you" to those of you who are sharing knowledge - all searches "root my G3" led here to this site and it appears that there are some very talented people here - I am here to learn, experiment and share... Right now I am very much in the learning mode with regards to these topics.
So...I just got this LG G3 (Verizon)/VS985. I've had it for 3 days and I am really not a fan of all this bloatware they put on it. I just want it off.
Apparently, removing all these Amazon, football, etc. apps can only be done by rooting the phone.
Now here are the questions:
1. There seem to be many ways now (at least 3, maybe 4) to root these phones. Which is the best? Does it matter?
1(a). Someone mentioned that "they" (not sure if its verizon or LG) might discover the "exploit" that (I assumed) was used to root their phones and then change it - would this affect any phones that have been rooted previously or just phones that would be rooted using that specific exploit?
2. Assuming I am able to successfully root this phone, at that time can I remove the apps I do not want on the phone with the current apps or do I need new apps to accomplish this?
3. Will most play store apps work properly on rooted phones?
4. I do not understand nearly any technical jargon with these unit as of yet. I see people are maybe changing the bios (?) of the unit and software of the unit? Is this correct? If so, where does one obtain different bios or software?
5. This may sound petty, but I dislike the circular shape of "folders" when you combine apps together on this phone - and I wondered - is there a way to change this style to a traditional rectangular file folder or make other cosmetic changes to this phone so it is completely customized? For example, what if I want a small element that shows the weather using the national weather service website instead of what was built in? Do I have to figure out how to produce that or are there already such things out there?
6. I continually note the warnings that are stated when websites give links to root phones - are the risks overplayed or are there really some issues with this (other than "voiding the warranty")?
7. Once I root my phone, can I remove the bloatware and then go on using the phone and useful apps essentially as it was previously?
8. This is a bit off topic, but assuming I have some basic computing and electronic skills, is it possible to learn enough about the foundations of how these units work at the code level and produce an "app" that does specific tasks of which current apps do not within a few months perhaps?
8(a). Any recommendations of literature or other learning tools out there to support this quest?
That's it for now - again thanks very much for those who are sharing knowledge and workarounds on this forum!
Forested said:
I am the noobest noob around when it comes to android based phones (hoping to climb the mountain of knowledge to start developing during this winter if I have the time!).
The first thing I want to say is a clear "thank you" to those of you who are sharing knowledge - all searches "root my G3" led here to this site and it appears that there are some very talented people here - I am here to learn, experiment and share... Right now I am very much in the learning mode with regards to these topics.
So...I just got this LG G3 (Verizon)/VS985. I've had it for 3 days and I am really not a fan of all this bloatware they put on it. I just want it off.
Apparently, removing all these Amazon, football, etc. apps can only be done by rooting the phone.
Now here are the questions:
1. There seem to be many ways now (at least 3, maybe 4) to root these phones. Which is the best? Does it matter?
1(a). Someone mentioned that "they" (not sure if its verizon or LG) might discover the "exploit" that (I assumed) was used to root their phones and then change it - would this affect any phones that have been rooted previously or just phones that would be rooted using that specific exploit?
2. Assuming I am able to successfully root this phone, at that time can I remove the apps I do not want on the phone with the current apps or do I need new apps to accomplish this?
3. Will most play store apps work properly on rooted phones?
4. I do not understand nearly any technical jargon with these unit as of yet. I see people are maybe changing the bios (?) of the unit and software of the unit? Is this correct? If so, where does one obtain different bios or software?
5. This may sound petty, but I dislike the circular shape of "folders" when you combine apps together on this phone - and I wondered - is there a way to change this style to a traditional rectangular file folder or make other cosmetic changes to this phone so it is completely customized? For example, what if I want a small element that shows the weather using the national weather service website instead of what was built in? Do I have to figure out how to produce that or are there already such things out there?
6. I continually note the warnings that are stated when websites give links to root phones - are the risks overplayed or are there really some issues with this (other than "voiding the warranty")?
7. Once I root my phone, can I remove the bloatware and then go on using the phone and useful apps essentially as it was previously?
8. This is a bit off topic, but assuming I have some basic computing and electronic skills, is it possible to learn enough about the foundations of how these units work at the code level and produce an "app" that does specific tasks of which current apps do not within a few months perhaps?
8(a). Any recommendations of literature or other learning tools out there to support this quest?
That's it for now - again thanks very much for those who are sharing knowledge and workarounds on this forum!
Click to expand...
Click to collapse
You're in the same ballpark as me! I just bought my Lg G3 from Verizon yesterday as well, however I'm going to wait a little while to root it. I'm running Nova Launcher and just made all of those apps hidden. But let me answer some of your questions from my past root experience!
1. As for ROMS, I would stick to the Verizon section for now, but that's just me. You can try the other 'variants,' but that's up to you if you want to get your feet wet over there. It won't ruin your phone, just some of the things won't work (probably, I don't know). Looks like Jasmine is your best bet so far, and there's another one MIUI that is pretty popular, but that's your selection as of right now and people seem to be enjoying them the best!
2. Absolutely . If you can't delete them manually, you can download Titanium Backup (what I use) to delete those horrible Verizon apps and Amazon, etc. Now, these will be deleted from your phone for good until you unroot your phone and reflash the official, orginal firmware provided here on xda.
3. All Play Store apps should work. Well...MOST should work. I've been rooting for over 2 years and I've never had an app say, "nope! too bad, so sad." So you should be good Download away.
4. These are new concepts for me too...I would just do some homework. Like every flasher out there would say, "Read read read! Oh. And READ BEFORE ROOTING!"
5. I would assume this is just based on the Launcher that you're using. You can use the stock software which is pretty nice, actually, but I prefer Nova launcher in my personal liking. There's also GEL that is pretty and fluent. In the settings of these apps, you can (usually) change the folder icons.
6. If you have a warrenty, yes, it's "Voided," unless you unroot . Make sure you read up on that, but there is nothing wrong with it. I've had Verizon reps actually tell me that what I did was a good thing, haha. But if you plan on returning the phone, make sure you unroot it and discard of any "suspicions!" Again, just do your reading about root/unroot and you should be solid. :good:
7. Yes.
8. Just read the general LG g3 forums of rooting, unrooting, bumping (this is new), and read what others are saying about the ROM to see what kind of issues there may or may not be with it. And have fun! Also, once you get the hang of rooting, it will be easy as pie. If it's something new, there's a ton of information out there already with our phone where you can fix it! There's a unbrick solution on here, too, just not sure where in the threads.
Side note - If you have any questions or problems, it's just a simple question in the Questions thread and you have a few thousand people here ready to help you! HAPPY FLASHING!
stump root
I have rooted my lg g3 d855 eur e10 few days ago. Now my play-store keeps saying that i don't have working network connections with 3g and wifi. I factory reseted it today and now i can't log in to my google play account. It says " Can't establish a reliable connection to server. This could be temporary problem or your android device may not be provisisioned for data services".
LG G3
I have a LG G3,Verizon version,and whenever I hit the grind button it will say "Device is patched,sorry!" How do I fix this?
KaesoGallusLaevinus said:
I have a LG G3,Verizon version,and whenever I hit the grind button it will say "Device is patched,sorry!" How do I fix this?
Click to expand...
Click to collapse
What build are you on? 10b 11c? Did you take any otas
I just got my LG g3, from Verizon since it's new it's automatically updated to 12b is there a way to root, unlocked and install recovery and everything. I just came to LG from my s3 which was locked out (thanks knox) so I'm out of the flashing loop so any and all help is appreciated
N3RO2403 said:
I just got my LG g3, from Verizon since it's new it's automatically updated to 12b is there a way to root, unlocked and install recovery and everything. I just came to LG from my s3 which was locked out (thanks knox) so I'm out of the flashing loop so any and all help is appreciated
Click to expand...
Click to collapse
Downgrade to 10B.
http://forum.xda-developers.com/showthread.php?t=2928140
Use Stump root.
http://forum.xda-developers.com/showthread.php?t=2928140
Find the TWRP thread in Development or Original Development, I forget which.
Sent from my VK810 4G
Just thought I'd offer a free service to obtain root using Sam's method. I do not speak any other language than English not to discriminate however I can translate using google translate just be sure to use propper spelling. Seen a lot of people having trouble. With respect to Sampwnd users may feel free to contact me, however, it's on a time consented basis adherent to my schedule. Contact me at a time and I will put it in my calendar and contact you, I do read all messages. New members will get priority as I feel a great learning experience could push someone new into the scene.
Requirements:
Windows OS or Virtualbox Windows
Mac OSX Lion or higher
New User (Admin Privileges)
No personal information
No incriminating devices
Good intentions for obtaining root.
Click thanks after you've been taken care of.
Yes please
Please help me with this
Sassygreen said:
Please help me with this
Click to expand...
Click to collapse
pm contact details on the best way to instant message or get in contact
hey i was wondering if you possibly give us some insight to your methods, here in this thread? Possibly some steps, apps, youtube links? Would love to help spread the knowledge!
Well it really just vary's from the type of phone you have, Getting the MSL without root is a pain, however once rooted, you are than able to control anything in the phone i.e what's locked and unlocked. Know and understand that the letters ending after the base model numbers determine a big factor, such as G955UF is a unlocked world version of the 7 plus, it doesn't use the USA version of snap dragon. When the port was created and or root process it it was built off a certan type of model, few adjustments may be needed, i suggest checking out Android Studios, it comes with android dev packaging to help you kick start.
Download:
Sampwnd all neccesary files from the thread D
Download both odins
and download ADB and fast boot.
I will say this, with odin once you put the 4 files in, you need to boot into download moad, once you see the blue screen pop up then plug in your phone and if your mac you type ADB if your windows its ./ADB youll know if it connected or not.
It's pretty simple, I just think alot of people get stuck, so I am willing to hel.
ReqNet said:
Well it really just vary's from the type of phone you have, Getting the MSL without root is a pain, however once rooted, you are than able to control anything in the phone i.e what's locked and unlocked. Know and understand that the letters ending after the base model numbers determine a big factor, such as G955UF is a unlocked world version of the 7 plus, it doesn't use the USA version of snap dragon. When the port was created and or root process it it was built off a certan type of model, few adjustments may be needed, i suggest checking out Android Studios, it comes with android dev packaging to help you kick start.
Download:
Sampwnd all neccesary files from the thread D
Download both odins
and download ADB and fast boot.
I will say this, with odin once you put the 4 files in, you need to boot into download moad, once you see the blue screen pop up then plug in your phone and if your mac you type ADB if your windows its ./ADB youll know if it connected or not.
It's pretty simple, I just think alot of people get stuck, so I am willing to hel.
Click to expand...
Click to collapse
And stuck i definitely am. I now have root so what would be your next step in unlocking? Can you suggest a protocol or website or tools that are used?
I understand its easy to buy an unlock but i would really love to learn this process.
cabg.kepr said:
And stuck i definitely am. I now have root so what would be your next step in unlocking? Can you suggest a protocol or website or tools that are used?
I understand its easy to buy an unlock but i would really love to learn this process.
Click to expand...
Click to collapse
Firstly, congratulations on root.
Give "MSL Code Finder" a search within the play store, root only apps are generally a good area to search within, I couldn't throw a name on one, as my time with development on the G955U is pretty much over, i'm on to some other brands to provide more attention to. However should you need any further assistance, i can use teamviewer to connect and help you out.
ReqNet said:
Just thought I'd offer a free service to obtain root using Sam's method. I do not speak any other language than English not to discriminate however I can translate using google translate just be sure to use propper spelling. Seen a lot of people having trouble. With respect to Sampwnd users may feel free to contact me, however, it's on a time consented basis adherent to my schedule. Contact me at a time and I will put it in my calendar and contact you, I do read all messages. New members will get priority as I feel a great learning experience could push someone new into the scene.
Requirements:
Windows OS or Virtualbox Windows
Mac OSX Lion or higher
New User (Admin Privileges)
No personal information
No incriminating devices
Good intentions for obtaining root.
Click thanks after you've been taken care of.
Click to expand...
Click to collapse
I am interested in rooting my first Android phone after switching from an iPhone for almost ten years, aside from a Note 3 that I had for a few months. I have the S8+ and am pretty technically inclined, although I had a Note 3, I bricked it during my learning experience. I just don't trust myself to do it correctly at this point, I absolutely need to be able to use the app "Amazon Flex" and I am told there is way to hide the root, even though they use a certain method but I am understanding have been told that there are other options available for me to hide the root from this app. If you are willing to help me, I am willing to learn. I appreciate your time and look forward your response. I have the SM-G955U
Noah
nbraunstein said:
I am interested in rooting my first Android phone after switching from an iPhone for almost ten years, aside from a Note 3 that I had for a few months. I have the S8+ and am pretty technically inclined, although I had a Note 3, I bricked it during my learning experience. I just don't trust myself to do it correctly at this point, I absolutely need to be able to use the app "Amazon Flex" and I am told there is way to hide the root, even though they use a certain method but I am understanding have been told that there are other options available for me to hide the root from this app. If you are willing to help me, I am willing to learn. I appreciate your time and look forward your response. I have the SM-G955U
Noah
Click to expand...
Click to collapse
I also have that smg955u. Is that Sprint network you're on
Hey watch out for this guy, everyone. He lives in my hometown and he's really shady. He'll hop on TeamViewer and rummage through your devices and networks.
He sold me a phone with an unpaid balance and told me he could unlock it quickly through TeamViewer. After 3 days (about 12 total hours spent) spent, I eventually told him no thanks. He got very offended and started acting weird.. Even told me he had hacked my network through my television? Haha, anyway, be careful with this guy.
PS. Just in case he's moved to a different name, he uses a strange syntax in his sentences.. There's just something off about it. Its how I was able to recognize him on here.
PPS. I have his name and location if anyone else has been burnt by this guy.
If you have evidence of wrongdoing, then click report and mod staff will look into it. Otherwise, do not make public accusations.
Please note, all things flashed or used on xda are done so at your own risk. If users are being charged, scammed, or devices harmed, then please gather concrete evidence and use the report post system or contact a moderator or administrator directly.
Thanks!
The Merovingian
Senior Moderator
I have no idea what he is talking about nor have I even spoke to him on here. Requesting a removal, and moved to a different section should he want to escalate. This is or was a free service that i DO in my free time to help people.
The Merovingian said:
If you have evidence of wrongdoing, then click report and mod staff will look into it. Otherwise, do not make public accusations.
Please note, all things flashed or used on xda are done so at your own risk. If users are being charged, scammed, or devices harmed, then please gather concrete evidence and use the report post system or contact a moderator or administrator directly.
Thanks!
The Merovingian
Senior Moderator
Click to expand...
Click to collapse
ReqNet said:
I have no idea what he is talking about nor have I even spoke to him on here. Requesting a removal, and moved to a different section should he want to escalate. This is or was a free service that i DO in my free time to help people.
Click to expand...
Click to collapse
requesting a closure of this thread due to recent allegations.
Thread closed by OP request.
Hi everyone.
So I've been with this question in my mind for some time now... Are they really unbrickable? I have a ZTE Blade L3 on which flashed infinite times ROMs on it. Some completely bricked it - it couldn't even charge. It has a MT6582M processor on it. It was COMPLETELY bricked. And I always got it to work again. Never bricked it for good - and I did many stupid things on it, many experiments. And after a bit, SP Flash Tool would always flash stuff back to it even by flashing wrong ROMs on it.
I also believe I flashed a wrong ROM to a friend's Elephone P8000 B which has a MT6753 processor on it. I thought I had bricked it (this is why I think I flashed a wrong ROM on it) - but SP Flash Tool got back working after a few tries. I did what I wanted with the phone and it didn't brick.
So my thought is that ANY device with a MediaTek chipset with a ROM and a scatter file available and an always unlocked bootloader (preferably - as my Blade L3 had, I believe - since I never heard of this until weeks ago), might be unbrickable. I, supposedly, can do whatever I want on it and I'll always be able to unbrick it.
Is this true what I just wrote? If it is, then I'll try to never leave MediaTek powered devices.
Note: A thread confirmed this thought I had for some time until I found this thread, but it only says it about MT65xx devices, not all the others: https://forum.xda-developers.com/showthread.php?t=1943442 --> "Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE".
Note 2: Also....... After now reading back a bit of the thread, I found out I did exactly ALL the opposite they recommend there in caps and the phone always unbricked....... XD. So I'm a bit confused with all the careful people are about MediaTek powered devices when I was not careful (stupidly, I know), though it always worked. I have the phone since 2015 and stopped using it last year, but I believe I did the opposite of those things, even though I'm not completely sure. And again, never permanently bricked.
Thank you for any informations!
I'm not going to lie to you, your probably not going to get any other replies to the book you wrote above... I will answer your question however. There is not a single mobile device out there that cannot be unbricked as long as the issues that occurred to cause said brick remains at the software level. It don't matter what brand or carrier it is. If it is a software related issue then it can be fixed as long as you have the knowledge and tools required to do so. As for your experimentation using root, I have done many experiments myself and there are many many things you can do using root that will permanently brick your device. Sounds to me like you got lucky. Simple as that. I'll end this by saying, please do not post your entire relationship with your favorite phone in a single thread like you did. Nothing personal but many probably did not stay long enough to finish what you wrote. You have a valid question. However the rest was just unnecessary and to many, a waste of their time. Hope I helped.
Hi. I didn't even remember about this anymore. This last year I was told I write too much unnecessary things - just like you did. I've been trying to correct that and I believe I improved (no idea if much or not). When you said "the book you wrote" I got embarassed in advance because I knew what was going next, and when I scrolled up I got scared and even more embarassed and it's still increasing as I think more about it . Christ, how did I even post that. I'm very sorry........ I guess we learn as time goes by.... (hopefully haha). Hopefully now it's good enough. If it's still bad, I'll be happy to receive the advice, as I am with the one you gave. Thank you. For everything you said, actually.
Spoiler: Not needed, just curiosity of why I wrote it so big
EDIT: Just a small explanation of the why I wrote the text so big, which was I'd prefer to give all the informations right at the start so people can know exactly what was done and say things according to that. Instead of assuming I did things I might not have done and answer something that might not be correct in my case. But then I write a book and that's beyond stupid. So I've been trying to correct that. That's the wrong point of the view and I think I still need a bit more time, but hopefully I'm getting there - maybe I should start posting on Reddit hahaha. Posting things is not that old for me. Started a few years ago (21 years old - a bit late for my age, I guess, but I didn't go on Internet that much before).
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Tofor said:
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Click to expand...
Click to collapse
Ah no problem at all. Gotta be corrected in some way . That happens with me when I see an enormous stupidity made by me which I did not realize at the time - and this one is 5 months old, which puts it worse haha.
That shall work so I won't forget of not doing this again in the far future xD. Before, some people would tell me about and I'd notice it was a wall of text (like once a person told me). And I appreciate all those who warned me about it. Sooner or later I'll get to a decent amount of text, depending on the forum. I think I didn't know what a paragraph was, as a start xD (though, what you saw there was already an update....). It's still a big post, I think, but hopefully it's readable now. If it's not, I'll cut more of it.
But yes, you did answer the question. Thank you. But to complement it, if you remember, at least, what experiments with root can completely brick a phone? (So I know I won't try them, as a start, but it's also a curiosity.)
Well a good example of some things not to do is changing the system files to allow the device to operate at a level it was not designed to operate at. For example. Messing with the kernel to make the processor run at a higher speed, same goes for the RAM. This will cause it to overheat and will basically fry the system board. Also if you are not sure what you are changing then dont change them. Nothing like accidently changing the EFI settings to where it no longer knows where the internal storage addresses are and does not know it has any type of storage to boot to. However a lot of the efi should be copywrite protected where even a root user cannot modify them but trust me... its possible and may still be repairable but only by the manufacturer who has that level of access and definitely not worth what it would cost. Keep an eye on any files you modify for a copywrite at the top of the file. Changing copywrite files will most likely get you in a whole lot of trouble. If you end up having a web adress listed in the build.prop on every android device you own that brings you to the developers terms and conditions then stop messing with system files. This is more or less a warning telling you that you are breaking the terms and conditions. I would libe to continue but then i would be contridicting myself on my comment about very large messages in the forums. If you would like to know anything else please feel free to PM me and lets put an end to this thread lol.
Guys, speaking of devices with MT chipset, I have a Hannspad HSG1341 that was running Android 5.1 and wanted to root the pad using some tutorial I saw with magisk by installing the APK on this device which creates a modified boot.img. Then using SP Flash Tool I tried to reinstall the stock firmware by replacing the boo.img created by magisk and now the pad would not power on, I have tried searching for means to restore this pad but nothing. Even SP flash tool is now displaying s_ft_enable_dram failed (4032). So please off anyone has any idea how to resolve or is the pad dead for good. The chipset is MT8163. Let me know if you need more info to help out
thanks