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.
Related
I was using androidflasher.zip and I put radio.img in the "radio" box but i also had another .img in the zip folder I downloaded with the radio it was called mdm9k.img so I put that in the radio box and right when I clicked flash BOOM hardbrick.. phone wont respond to anything.. no lights no recovery/bootloader.. NOTHING.. the phone wont even charge or respond to me plugging it in to my computer.. I still have a warranty but REALLY dont feel like going through all that.. any easier methods?
First question why use a program to flash a radio when Hboot is simple, fast, easy, and built in. Wow people surprise me, if something does not make sense don't do it. You are now the proud owner of a fancy paper weight, well fancy looking it does the same thing as a rock.
Sent from my Thunderbolt using XDA App
Use warranty, GL
Sent from my Thunderbolt using XDA App
u didnt answer my question at all..
thanks for wasting precious seconds of my life reading your pathetic post
I did answer it for you, there is nothing you can do I saved you time waiting for an answer just as good as mine. If you don't like it that is life. Do what ever you can to get a new phone and use Hboot with that phone or just don't even root it, you don't seem to know what you r doing.
Sent from my Thunderbolt using XDA App
#1 your a dumbass.. just need to put that out there..
#2 why would a developer spend precious time making a program that was irrelevant and didn't come in handy
#3 thanks for answering my question.
Grnlantern79 said:
First question why use a program to flash a radio when Hboot is simple, fast, easy, and built in. Wow people surprise me, if something does not make sense don't do it. You are now the proud owner of a fancy paper weight, well fancy looking it does the same thing as a rock.
Sent from my Thunderbolt using XDA App
Click to expand...
Click to collapse
time to use your warranty
#1 I am sure the developer made a program that worked fine, have I used it no I used one better stock Hboot.
#2 Did you use the program wrong, I am going to say yes since you carelessly put a file in the radio box that you were not even sure went there.
#3 Is my phone working cause I know what I am doing, well I am typing on it now so who is the smarter one of us? I will give you a penny for your paper weight.....final offer.
Sent from my Thunderbolt using XDA App
Oh don't forget to use the thank you button.
Edit: he left and didn't even thank me....did I say anything but the truth?
Sent from my Thunderbolt using XDA App
hmm.. well lets see i downloaded a RADIO from xda and inside the zip file were the two files i flashed under RADIO because that IS what I downloaded.. but yeah Im the stupid one.. i should have put it in some other checkbox that didn't say RADIO.. i should have just put it in the bootloader checkbox or something.
Did you try a battery pull? If you can at least get it to boot into bootloader, you may be able to reflash the radio.
Not sure, because I've never used the app your talking about.
Anyways, good luck.
You broke it, don't drive the prices up for the rest of us by doing a warranty claim! Use your insurance.
Sent from my HTC ThunderBolt using Tapatalk
Never heard of it but it looks like AndroidFlasher uses fastboot to flash radios for several different devices.
So for a brick one of these is probably the case
1) the radio you downloaded was wrong
2) AndroidFlasher doesn't take into account multiple radios for Thunderbolt so the wrong radio was flashed to the wrong location
I talked to the developer he said you are the only one who did this process wrong. So yes you are the dumb one. Go ask him what you did wrong. Please stop trying to make yourself any smarter or someone else's fault.
Sent from my Thunderbolt using XDA App
Hey bro!
First of all, let me clarify for the XDA world, it doesn't seem to me that you are "DUMB". In fact, I don't think we need to even tell people these things. On the opposite side, we all do "ignorant" things at times. Please don't get offended that I say the word, "ignorant"? All ignorance means is that you did or did not do something without knowledge or experience. Ignorance does not claim that you are dumb. The word "dumb" is defined by Webster as, "Lacking the power of speech". Evidently, that is not what you are doing! In fact, you were trying to do the opposite!
Sincerely, I have done many ignorant things in my life. So, I am not sure that you will be able to fix your phone, but I hope and pray that you do get it fixed. Keep your head up and don't be afraid to fail. You are doing more than many people! Those who do not take risks fail because they accomplish little.
Living by Faith in Christ,
Ryon Lee Adcock
there are some few options for saving you from a hard brick. I got my SGS saved from that kind of stuff! What's your device?
Grnlantern79 said:
I talked to the developer he said you are the only one who did this process wrong. So yes you are the dumb one. Go ask him what you did wrong. Please stop trying to make yourself any smarter or someone else's fault.
Sent from my Thunderbolt using XDA App
Click to expand...
Click to collapse
Edit'd.
Dear OP,
Looks like Grnlantern79 did your homework for you!
I took a pretty good chunk of time to compile a beginner's Q&A thread that answers virtually every beginner question. As Einstein said, the difference between stupid and genius is that genius has it's limits (as in, stupid has NO limits). I think I speak for every developer out here when I say it's impossible to predict how "ignorant" a potential user is going to be. There's a very real expectation that guys like you are going to school themselves on some basic things. To not assume that puts a LOT of explanatory work on guys like Grnlantern79, myself, and others, that's simply not needed for the VAST majority of folks out there.
I've been bumping around the Tbolt forums for a while now. I can't recall ever seeing anything describing what you attempted to do. I know you didn't find it in any radio thread here, on Rootzwiki, or teamBAMF.com, which are the only places that have respectable radio listings. Clearly you didn't read my thread either. In fact, you somehow managed to avoid a tremendous wealth of information!
The answer to your question is you're SOL. It's that simple. You did at least two stupid things, probably more, and it can only be accounted for by deliberately avoiding/neglecting knowledge. First, you didn't check the MD5. An MD5 is ONLY valid when it's checked on the root of your SDcard. Second, you had no idea what software you were dealing with; either the radios or this flash utility. Bad radio flashes, even through hboot, will brick your device. They are NOT recoverable. Even if you'd done whatever you were trying to do correctly, your neglect of verifying the file could have bricked it.
So, when you get your new device, I HIGHLY recommend reading my thread and following the directions to the letter. I can promise you that you will not accomplish anything more with what you were (possibly) trying to do than what I've laid out already using well tested and highly reliable means.
And with all due respect, please do some reading around here. Between XDA and Rootzwiki, you will learn almost everything you'll ever need sans the дезинформация.
loonatik78 said:
Dear OP,
Looks like Grnlantern79 did your homework for you!
I took a pretty good chunk of time to compile a beginner's Q&A thread that answers virtually every beginner question. As Einstein said, the difference between stupid and genius is that genius has it's limits (as in, stupid has NO limits). I think I speak for every developer out here when I say it's impossible to predict how "ignorant" a potential user is going to be. There's a very real expectation that guys like you are going to school themselves on some basic things. To not assume that puts a LOT of explanatory work on guys like Grnlantern79, myself, and others, that's simply not needed for the VAST majority of folks out there.
I've been bumping around the Tbolt forums for a while now. I can't recall ever seeing anything describing what you attempted to do. I know you didn't find it in any radio thread here, on Rootzwiki, or teamBAMF.com, which are the only places that have respectable radio listings. Clearly you didn't read my thread either. In fact, you somehow managed to avoid a tremendous wealth of information!
The answer to your question is you're SOL. It's that simple. You did at least two stupid things, probably more, and it can only be accounted for by deliberately avoiding/neglecting knowledge. First, you didn't check the MD5. An MD5 is ONLY valid when it's checked on the root of your SDcard. Second, you had no idea what software you were dealing with; either the radios or this flash utility. Bad radio flashes, even through hboot, will brick your device. They are NOT recoverable. Even if you'd done whatever you were trying to do correctly, your neglect of verifying the file could have bricked it.
So, when you get your new device, I HIGHLY recommend reading my thread and following the directions to the letter. I can promise you that you will not accomplish anything more with what you were (possibly) trying to do than what I've laid out already using well tested and highly reliable means.
And with all due respect, please do some reading around here. Between XDA and Rootzwiki, you will learn almost everything you'll ever need sans the дезинформация.
Click to expand...
Click to collapse
+1
I said all that but I am a man of short words, for you few on this thread that say I am an ass, to each his own I have went out of my way to help people I don't know but i gave him a direct answer under OP and he fired back at me, after that yes I was an ass but no matter what info you guys give him you can't fix stupid.
Sent from my Thunderbolt using XDA App
I think we're done here.
Being a Member of XDA for a while now I recall in the past on different models that XDA use to create sub-forums for Carrier Variants. I.E. Verizon, Sprint, GSM based. This was helpful for the noobs and Rom creators in making sure that Noobs didn't flash the incorrect Rom or Recovery.
Looking at the HTC One Max forums there occasionally is this confusion as members will post a general variant specific issues and a novice not knowing the difference would unintentionally use it thinking it applied to their device. Some Devs don't identify there Roms or indicate a variant which contributes to the issue.
I think it would be very beneficial for development on this device to have Variant based sub forums. Additionally having variant based sub-forums will help identify Underdeveloped devices.
Just my 2 cents.
DeadPhoenix said:
Some Devs don't identify there Roms or indicate a variant which contributes to the issue.
Click to expand...
Click to collapse
I'm sure when we get way more than 3 threads in original and 3 in development they will look at dividing the Max forum. Until then we need anyone that posts anything to ensure they identify what model it will work on. I believe most of the development done for us thus far does not identify which model it works for because it works across all (in one form or another).
To be honest most if not all of the issues people have had thus far is because they are not searching and reading to understand something before they do it. I guarantee a dev or someone with knowledge will try to help the best they can. BUT no one wants to help someone that doesn't try to help themselves by understanding what they are doing first.
If anyone notices that some development is device specific and it is not labeled as such then ping the dev and ask that they identify it appropriately. And if anyone feels strongly enough that something is not labeled or mislabeled that could end up causing issues with someone's device then AFTER ASKING THE OP to update feel free to contact one of our mods to correct or close the thread until it is adjusted. Many hands make light work...
i can see both points here
oneandroidnut said:
i can see both points here
Click to expand...
Click to collapse
I can see the point as well. But it will be a while before the forums are divided if at all. I said "until then" because we all need to work together now to police the threads to make sure things are made clear if they are not.
Jiggity Janx said:
I can see the point as well. But it will be a while before the forums are divided if at all. I said "until then" because we all need to work together now to police the threads to make sure things are made clear if they are not.
Click to expand...
Click to collapse
yeah i know what you mean. we clearly need more roms and development before anything gets split up
oneandroidnut said:
yeah i know what you mean. we clearly need more roms and development before anything gets split up
Click to expand...
Click to collapse
I know coming from the Motorola Droid HD forums that the impact of not separating them is lots of "Learning Experiences". I am quite learned in the rooting/bootlocker experience and even I was confused by the variants in that forum. I got it sorted out but it took longer then is should have.
I am in the process of learning java and android development and I plan on properly labeling my threads and apps. Oh and Blender for Custom Boot Animations. I have a Plan for A Doctor Who based Animation.
Plus I like tidiness and organization. Makes things more efficient.
How do I tell which version of the One Max I have?
It's one of the 32 gig versions, it's gsm and works on United states ATT. baseband version is 4T,27.3218.14_10.33C.1718.01L Software number says 3.15.1540.1 I think it might be the Hong Kong or British one, but it's been quite confusing trying to figure out which is which. I bought it off Amazon, so I know there's a chance that the software has been "improved' a bit.
Thanks for any help-I did try to search on it, but wasn't finding anything with useful info for me, or possibly I just don't know where to look. It's been some few years since I had an HTC..I bought the original G1 on opening day
Any help, or even just a point in the right direction would be most appreciated. I'd like to get this sucker rooted and get rid of the crapware as soon as possible
{
"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.
{
"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"
}
★ Official Guide, FAQ & Discussion for the ZTE Zmax from METROPCS and TMOBILE ★
Previous thread can be found here
CASES
Eagle Cell
E-Time
EBAY 1
EBAY 2
SCREEN PROTECTORS
EZGaurdz
XTreme Guard
REVIEWS
CNET
Phonearena
GSM Arena
AndroidAuthority
BENCHMARKS
AnTuTu V5.1:
Please read everything, carefully, before posting a question.
FAQ
(Other common questions/answers may be added to this list by posting them in the thread.)
Can I root this phone? / Is there a root for this phone?
NO. Not one of the multitude of root options currently work for this phone. We have exhausted every single option. None exists. The very best minds on XDA worked on it but were unable to make the root stick. (It is a read/write issue) There are no plans to continue development of root by existing XDA devs. At this time, No **ACTUAL** dev is working on this phone. Only novices and those new to root are working on it.
Can I post a link to a root for another phone I found?
NO. It's likely one of the many found below. (see: Untrustworthy sites/links)
Has anyone tried [INSERT THING HERE], yet?
YES. We have been at this for months. We know all the methods, already, and have exhausted them. Anything more would require a brand new method no one has tried or posted about, yet. You can share something that has not been offered before in the old thread or is not one of the Untrustworthy sites listed in the bottom of this post.
Is there a custom ROM/TWRP/ETC?
NO. Until root is achieved, this is an impossibility. If you want the Lollipop feel, why not try Nova Launcher. It has material design built in!
unlocking is the same as rooting, right?
NO. Unlocking is for network access (like using Verizon on a TMOBILE phone). It in no way means you have root.
Is it true TMO/METRO/ZTE is releasing root for this device?
NO. There is zero confirmation of this even being a remote possibility. Only speculation after a single email from an unknown sales rep. Please do not keep this rumor alive. It is the #1 reason the devs stopped working on this phone. #2 was negative attitudes/disrespect.
I just installed/used a file browser and I can get into /system. Is this important?
:
NO. That doesn't help root or show that you have root. Think of it like this: You can use Windows Explorer to view your System32 folder, but you can not manually alter its contents. Being able to see something doesn't mean it is editable/writeable.
How do I turn off connection/touch/etc vibration?
Go to settings> sound> alerts and notifications (Toward the bottom) Uncheck the box associated with the item you want to disable.
Can I...? should I...? Do I...? Is this...? Will you...?
99.9% of your questions have existed and been answered in these amazing forums for YEARS. Please use the search feature built into XDA to find the answer to your common questions.
WILL THIS ROOT WORK?
(If it is in this list, it has been tried multiple times with the same result: FAILURE)
framaroot: NO
TowelRoot: NO
Kingo: NO
shuame / Root Genius: NO
Baidu: NO
Root Ninja: NO
shuaji.360: NO
Tacoroot: NO
Nachoroot: NO
burritos: NO *ONLY FOR KINDLE FIRE
Pie: NO
stump: NO
chainfire: NO
Qualcomm exploit: NO
purpledrake: NO
Iroot/vroot: NO
Srsroot: NO
DC-Unlocker: NO Huawai devices only
zergRush: NO
RootMaster: NO
g2root: NO
zdsrooter: NO
cydia impactor: NO
sunshine: NO
Methods for other phones: NO *Never do this. You can brick your phone. Also, the architecture is almost always going to be different.
Untrustworthy sites/links
(Do not, under any circumstances, post any sites that relate to or contain the following words. They are fake, scams or clickbait. They may even contain viruses. BEWARE.)
upgrade-lollipop
unlockr
how-to-root
downloadsafe
root-android
unlock-bootloader
** reserved **
ATTRIBUTIONS
Material Design Icons used in this thread:
dribbble
iconshock
USEFUL LINKS
Original thread started by @Planterz
ZTE Zmax on Reddit
...
IMPORTANT
Please make sure all posts are on-topic, respectful, succinct, educated, researched, reviewed and have correct (or at least adequate) spelling and punctuation. Thank you!
Also, PLEASE RESPECT ALL DEVS AND THEIR HARD WORK. This is not the place to beg, brag or post messages like "Boy, I'd really like to have root". We all want root, but hounding the devs to do it is not a good motivator. Patience & respect are.
The original discussion thread was closed at my (the OP) request, since I do not own the device, nor do I have any interest in maintaining a database of FAQs or guides or accessories. Thus, a new thread was created by someone who willing and able to keep any and all pertinent information on the first page of discussion, rather than scattered and buried amongst dozens of pages and a couple thousand posts.
@therealduckie It's all yours now.:good:
Add purpledrake to the WILL NOT ROOT zmax list before it's asked.
A fresh start! A great idea @therealduckie and @Planterz :good:
If you need anything, I'm an "@Darth" away!
Lightfeather said:
How on earth can a thread reach the epic proportions of this one, yet the ZTE zmax hasn't been offered its own forum?
Click to expand...
Click to collapse
Because nothing has been achieved yet deserving of its own forum. Forums are granted to devices when there is so much going on with them that there's too many individual threads scattered about the place that it behooves the people that organize XDA to contain them all in one place.
For example, one of my phones, the Samsung Galaxy Light. This phone has a "how do I root" thread, a discussion/development thread (with accompanying Q&A Bot thread), a couple different modified stock ROM threads, a TWRP development thread, and a CyangemMod porting thread (and accompanying Q&A thread). That's like 9 different threads, give or take, plus several more asking specific questions. All scattered throughout the place, but it apparently it's not enough yet to warrant its own subforum. There are many other devices in the same boat.
At this point, all the ZMAX has is discussion. No root, no recovery, no ROMs. Everything there is to talk about with this device is easily contained within a single thread. Turning OP control over to someone willing to maintain it is something I should have thought up a while ago.
Realize also that new forums need moderators to monitor and micromanage them. So if you ask "well, why not just make a new forum?", that's a big reason why not. The forum software can handle it. It'd reduce confusion and clutter. But someone has to herd the cats.
Iroot/vroot no go.
Sent from my Nexus 6 using XDA Free mobile app
Srsroot/kingroot no go.
Sent from my Nexus 6 using XDA Free mobile app
Nachoroot... No go
I think this is somewhat on topic (if not please delete) but I was just able to pair my dualshock 4 controller with the ZMAX. I played a little GTA 3 but with considerable lag. I'm trying different ideas for how to be able to map the buttons so getting in a car isn't L1..anyway, this was amazing to me because I thought you had to root the phone for the DS4 to work. If it's ok I'll post more when I have something else to say on this.
Thanks!
Sent from my Z970 using XDA Free mobile app
Everyone including @Darth there is literally no development at all happening here so what is all the STAY ON TOPIC talk about? I don't understand it. Really I could see if someone was actually doing anything toward achieving root then, ya know, we need to stay on topic. But this is a GENERAL THREAD so what , if any, is the topic. This is, at best, a thread that a few people are trying every one click root in the world.
I'm sorry if I'm hurting anyone's pride or sense of accomplishment or always being negative, but honestly there is no topic here. It's about the Zmax and 99% of the people here have no idea what root truly is or how it even works, let alone have a chance in achieving it themselves for this device. Myself included! I'm just against getting my hopes up or anyone else's for something that is nowhere close to being completed, or started, for that matter! I mean isn't it better to be realistic or is everyone here really that optimistic. I'm all for getting root but we need knowledge to achieve this and without ZTE or a mobile securities expert, cough cough @jcase, then we are just passing the time here, surrounded by friends, at best!
So, in saying all of this, I ask all the people that say, "Stay on topic!" Why can't this thread, be a hangout/ fun/ noob friendly/ awesome freaking place to come and talk to friends and people, that have the same phone, interests, and love for Android.
Also, I ask you,(the OP, @Darth, and etc.) in the kindest, awesomest, only way I know how, to not turn this place into an, "It's in the OP!"/ impatient/ rude response giving everytime/ awkward/ no sense of humor having/ no fun having/ dull/ dead/ boring/ thread!? Because to me that's the vibe I'm getting from this place already! But maybe it's just me, I just don't get why everyone is so uptight and mad about nothing! If development does occur ask people to sit back and watch and listen. But just because you make a thread OP organized with a FAQ table and a few rude sentences doesn't turn this into a Development thread with actual progress. I want my ZMAX rooted as much as the next man really I do we just need more than us to do it. We need to find another DEV like jcase that's willing to help! Even if for a fee AND WE actually treat him or her like a dignified human BEING THIS TIME. I truly believe that is our only hope!
I've been around XDA-Developers for 5+ yrs, yet only been a member a few and I've seen my fair share of awesome threads and I think this could be one!
Live Long and Prosper! \\//
It doesnt take an "expert" (i hate ppl calling me that), it just takes someone dedicated. I have no education in computer science, well i didnt when i started.
johnb380 said:
Everyone including @Darth there is literally no development at all happening here so what is all the STAY ON TOPIC talk about? I don't understand it. Really I could see if someone was actually doing anything toward achieving root then, ya know, we need to stay on topic. But this is a GENERAL THREAD so what , if any, is the topic. This is, at best, a thread that a few people are trying every one click root in the world.
I'm sorry if I'm hurting anyone's pride or sense of accomplishment or always being negative, but honestly there is no topic here. It's about the Zmax and 99% of the people here have no idea what root truly is or how it even works, let alone have a chance in achieving it themselves for this device. Myself included! I'm just against getting my hopes up or anyone else's for something that is nowhere close to being completed, or started, for that matter! I mean isn't it better to be realistic or is everyone here really that optimistic. I'm all for getting root but we need knowledge to achieve this and without ZTE or a mobile securities expert, cough cough @jcase, then we are just passing the time here, surrounded by friends, at best!
So, in saying all of this, I ask all the people that say, "Stay on topic!" Why can't this thread, be a hangout/ fun/ noob friendly/ awesome freaking place to come and talk to friends and people, that have the same phone, interests, and love for Android.
Also, I ask you,(the OP, @Darth, and etc.) in the kindest, awesomest, only way I know how, to not turn this place into an, "It's in the OP!"/ impatient/ rude response giving everytime/ awkward/ no sense of humor having/ no fun having/ dull/ dead/ boring/ thread!? Because to me that's the vibe I'm getting from this place already! But maybe it's just me, I just don't get why everyone is so uptight and mad about nothing! If development does occur ask people to sit back and watch and listen. But just because you make a thread OP organized with a FAQ table and a few rude sentences doesn't turn this into a Development thread with actual progress. I want my ZMAX rooted as much as the next man really I do we just need more than us to do it. We need to find another DEV like jcase that's willing to help! Even if for a fee AND WE actually treat him or her like a dignified human BEING THIS TIME. I truly believe that is our only hope!
I've been around XDA-Developers for 5+ yrs, yet only been a member a few and I've seen my fair share of awesome threads and I think this could be one!
Live Long and Prosper! \\//
Click to expand...
Click to collapse
@jcase I don't suppose you could point me in the right direction when it comes to starting android development? I've got a rudimentary knowledge of Linux, Java, and C but I really don't know where to start learning when it comes to android development. I'm willing to be dedicated, I'm just not sure where to start.
jcase said:
It doesnt take an "expert" (i hate ppl calling me that), it just takes someone dedicated. I have no education in computer science, well i didnt when i started.
Click to expand...
Click to collapse
Sorry friend but can WE as in this thread and community start over with you! Can we be friend again. Don't forsake us for a few bad apples @jcase ! As you have seen and can tell we don't know what we are doing here honestly. Is there anyway you could point us in the right direction. Or maybe get us started somehow. I or maybe We don't want spoonfed or maybe we need spoonfed even if we don't want to say it. But anyways if we don't know where to start how can we finish is all I'm saying!
We need your help and I'm willing to do whatever to help in the endeavour! We do have quite a bounty amount built up $400+ pledged. I don't know if that's enough for you to be interested but I know money would help anyone!
So what I'm asking is for any help friend!
Hope your health is improving. Your life is more important then this phone. So when you're well and rested and ready we are all here waiting with baited breath.
See ya when you are up to it.
jcase said:
It doesnt take an "expert" (i hate ppl calling me that), it just takes someone dedicated. I have no education in computer science, well i didnt when i started.
Click to expand...
Click to collapse
Clayjn said:
Hope your health is improving. Your life is more important then this phone. So when you're well and rested and ready we are all here waiting with baited breath.
See ya when you are up to it.
Click to expand...
Click to collapse
Ditto!
Clayjn said:
Hope your health is improving. Your life is more important then this phone. So when you're well and rested and ready we are all here waiting with baited breath.
See ya when you are up to it.
Click to expand...
Click to collapse
Thanks, my wife just lost her former roommate yesterday to lung infections as well, same first name as me, really freaky.
jcase said:
Thanks, my wife just lost her former roommate yesterday to lung infections as well, same first name as me, really freaky.
Click to expand...
Click to collapse
Our condolences go out to you and your wife. I think I can speak for a lot of the people here when I say that your health and well-being are more important than what this thread is trying to accomplish.
Glad you're getting better!
Hi guys, I installed the 35b and the latest azadi rom following all the instructions and i dont have movile data at all, calls are normal, on screen notifications the message: "SIM card is not from Verizon Wireless", I really like this ROM so i´m very sad, i´m in Colombia in Movistar service, thanks for any help,
You might change the title of the thread to include the carrier you're using since it's possible only people who use this phone on that carrier would know what specifically to do to make the phone work with the carrier, if possible.
Did the phone previously work with this carrier on another ROM you had flashed or on completely stock?
roirraW "edor" ehT said:
You might change the title of the thread to include the carrier you're using since it's possible only people who use this phone on that carrier would know what specifically to do to make the phone work with the carrier, if possible.
Did the phone previously work with this carrier on another ROM you had flashed or on completely stock?
Click to expand...
Click to collapse
Thanks for the suggestion!!,, yesterday I have changed the APN config and everything works FINE!! thanks
Blackcamel said:
Thanks for the suggestion!!,, yesterday I have changed the APN config and everything works FINE!!
Click to expand...
Click to collapse
Awesome! Glad it was the easy.
What happened to the Azadi rom thread....my bookmark says thread not found.
speedingcheetah said:
What happened to the Azadi rom thread....my bookmark says thread not found.
Click to expand...
Click to collapse
Looks like the thread has been deleted.
AngryManMLS said:
Looks like the thread has been deleted.
Click to expand...
Click to collapse
Yeah, anybody know what happened? I was getting ready to install Azadi .... now the thread is MIA. I've only heard good things about the ROM. I hope this is just a fluke that an Admin can correct.
speedingcheetah said:
What happened to the Azadi rom thread....my bookmark says thread not found.
Click to expand...
Click to collapse
AngryManMLS said:
Looks like the thread has been deleted.
Click to expand...
Click to collapse
Specter597 said:
Yeah, anybody know what happened? I was getting ready to install Azadi .... now the thread is MIA. I've only heard good things about the ROM. I hope this is just a fluke that an Admin can correct.
Click to expand...
Click to collapse
She posted in the CM13 thread that she sometimes hates XDA and something like that all Android users are stupid:
{
"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"
}
Maybe it's related to that.
I don't fault her to be honest. I see the attitude not just here on XDA but in real life with certain people showing little to no respect at all towards others who have put long hard hours working away from family/friends/etc only to be treated like crap and "ooohhhh why doesn't this have this feature like other thing has you need to have that feature."
I'dont get it...it was the best MM rom for that phone. Of course u are gonna get many folks asking for this feature or to do this and that...there are so few roms and this is the most popular. Its a given when u post your stuff to a site like this.
Its like whining about youtube comments....deal with it, get used to it. Ignore it. Real idiots is ones who throw a tantrum, or give a giant middle finger and fume their way off a site blaming others.... BUt they can choose to delete their stuff if they want to, still a **** move. So she switches to an iphone and no longer wants to dev Android...ok....so update the rom thread to say discontinued, and lock it. Simple. But nooooo....to bad. Least I had the files saved.
Even more sickening is that people 'thanked' that snotty reply by bschmidy.
daagar said:
Even more sickening is that people 'thanked' that snotty reply by bschmidy.
Click to expand...
Click to collapse
Exactly.
roirraW "edor" ehT said:
She posted in the CM13 thread that she sometimes hates XDA and something like that all Android users are stupid:
Maybe it's related to that.
Click to expand...
Click to collapse
Drama?
Bummer.
Off topic: (by necessity) roirraW "edor" ehT what ROM are you using?
what will be a stable, clean and stock based ROM for our beloved vs985
Specter597 said:
Drama?
Bummer.
Off topic: (by necessity) roirraW "edor" ehT what ROM are you using?
Click to expand...
Click to collapse
Blackcamel said:
what will be a stable, clean and stock based ROM for our beloved vs985
Click to expand...
Click to collapse
I use @xdabbeb 's stock rooted 47A firmware with maximum debloating. Debloat zips [UNSTRIKE]and link to @joshua70448 's nice online custom debloat zip generator[/UNSTRIKE] (was down but it's up right now) in the third post of that thread, or in my signature below. I use Nova Prime launcher along with G3TweaksBox, Flast Style Bar Indicators and Greenify Xposed modules (the last one with aggressive doze), and a few others.
While I do want to give Fulmics a try if they ever resolve the reported US 4G issues on the vs985, the 47A rom seems to be working out great. My only "issue" at the moment is that it seems to suck down battery a LOT more (when active) than it did on KitKat - standby is fine.
AngryManMLS said:
Exactly.
Click to expand...
Click to collapse
Ugh, it's amazing how one or two bad apples spoil it for everyone... Azadi was an awesome ROM.
Does anyone happen to have an archived copy of the last build? (2129 I believe, came out a day or two before the thread was deleted) -- I was waiting for it, got sucked up in real life things, then it was gone.
Okay, I can't keep my mouth shut anymore.
Out of the blue, RoxanaSchram posted in the CM13 a rant that I, for one, didn't even understand what she was referring to. This was only the most recent time she had expressed a desire to leave XDA and to go back to iPhone. My impression of her post is that she was rude and disrespectful. Hate XDA? Can't wait to go back to iPhone? What was keeping her? If she did hate XDA and couldn't wait to leave, why was she posting on XDA about it at all, and why in the CM13 thread?
Even before the other person's response to her first post, I thought something similar. "Well, see you!"
It was RoxanaSchram who chose to leave XDA. She was already on her way out - she said so. Noone pushed her. RoxanaSchram is the only one who's responsible for deleting her ROM thread. If you want to blame someone, blame the person who did it - her! Noone else made her do it. Noone else made her delete (or hide) her G3 files from Android File Host.
But somehow you people manage to blame anyone but the only person who's responsible for these things. Roxana. Sure, a few of us have remarked to her initial offending post in like kind. If anything, I felt that responses to her have been fairly restrained. If she doesn't have respect for XDA or it's users (need I remind you her claim about Android users being idiots?), then she should've just gone somewhere else and not posted off topic in the CM13 thread about it.
I keep waiting for users to stop mentioning the whole thing. Somehow, once a day or so, someone manages to make sure the issue is still alive, and here I am doing the same thing so now I'm guilty of it. I'm just tired of Roxana not being held accountable for her actions and the blame being put on others.
Good day.
Buzzy42 said:
Ugh, it's amazing how one or two bad apples spoil it for everyone... Azadi was an awesome ROM.
Does anyone happen to have an archived copy of the last build? (2129 I believe, came out a day or two before the thread was deleted) -- I was waiting for it, got sucked up in real life things, then it was gone.
Click to expand...
Click to collapse
I may know someone to contact for your question above....(uhhhh me) However, I'm not sure what the XDA rules are about reposting and/or distributing something like that. I certainly enjoy being here in the forum and want to follow the necessary guidelines. So if a moderator wants to clarify on want is acceptable, I would be glad to share Buzzy.
Actually, since the files still exist on AFH in public domain I assume it's fine
Base https://www.androidfilehost.com/?fid=24459283995306526
Update https://www.androidfilehost.com/?fid=24545070682210923
Stock Dialer/MMS https://www.androidfilehost.com/?fid=24438995911974996
OK Google https://www.androidfilehost.com/?fid=24421527759890576
VVM standalone https://www.androidfilehost.com/?fid=24421527759888643
47A Live Wallpaper https://www.androidfilehost.com/?fid=24459283995307802
---------- Post added at 07:25 PM ---------- Previous post was at 07:19 PM ----------
I take no credit for this ROM, just re-posting links that were already created by Roxana Schram. This ROM was designed by RoxanaSchram....
Without quoting anyone in case there's an issue, I'll just say thanks for the posts, and I apologize for my part in keeping this going. I just assumed (I know, I know) there had been a blowup in the support thread as there had been occasionally before. Sounds like there must be a bit more to it, though, so I'll just be quiet in my uninformed state.
But thanks b00ster!