Related
ok about to root and rom. will verizon know if i call them for service questions? what i mean is, i suppose for a tech support call they can do over-the-phone diagnostics. right? if i call for tech support are they able to determine i am rooted and rommed through their diagnostics?
would i need to return to stock prior to making a tech support call to verizon?
thanks
there are honestly very few reps that know anything about the phones they sell
I'm not sure why you'd call Verizon for diagnostics on a device that's not running their software anymore. I'd think talking to the dev would make more sense. I suppose the could tell, but care? Probably not. I told the manager where I got mine that I intended to root it as soon as I got home shd that my old Incredible was already rooted. His only question was how much better the battery life gets.
They will try to help you for sure but they may no be able to since you do not have stock. They can not look up your phone info on their end but they may ask you for info like software or info about the phone from about phone that could give it away. Honestly you're probably better off posting your issue on this forum and having XDA help.
They wouldn't be too helpful not because you rooted but because you have a different piece of software on your phone.
It'd be like calling Microsoft because your copy of Ubuntu is acting up.
>_> big red is all knowing >_> they will find you.. they will GET YOU! >_>
I don't think they can see what software you are using, but I do believe they may be able to see your radio version.
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
littleguevara said:
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone can google "My Verizon.apk Thunderbolt", download it, and put it on their phones. Even non rooted fellas. So no, this should not throw up any red flags other than you are using a modded application.
U r legally allowed to root so dont worry about it
Sent from my ADR6400L using Tapatalk
I did this a week ago, my TB lost 3G completely at the house and 4G only works in PHX. It just happens the wife's D1 had no 3G so I called and we went through some settings on the phone and they checked the IMEI number etc. Found out the following day after talking to several Verizon people that the issue was the SIM card on the phone so I took it in and they replaced it and that fixed it.
I was rooted when I called, I went back to stock before taking it in and replacing the SIM card. They knew nothing at all.
It would be wise to just find help elsewhere. I find that online support is better than verizons anyways
I am an AT&T tech rep, so I can only speak for here. Bu universally most of us, despite carrier, that know what they are doing will answer the same from what I've found.
When someone walks into the device support center with an obviously rooted I won't exchange it for them. I will help them, find answers, and tell them how to fix it. I will also explain any known problems, or past problems, I know about with various roms. But I won't exchange the phone. And it's not to be mean. But often times when a person does come in with a rooted phone the issue they are experiencing is with the radio they flashed or the rom they are using. I see this a lot with the Inspire as is.
If I deem it to be an actual hardware issue and I can very the rom is not the issue then I will tell them how to take the phone back to stock so I can exchange it. For the Inspire I keep a handy sd card with the stock image there that I can flash it back right away.
If I know a phone has been rooted and the person brings it back to me with it flashed back to stock, I will exchange it without a problem. The phone is still under warranty and the warranty does explain in most products that not current software alterations exist (Ie: rooting, clockwork mod, unlock boot loader). If it's back to stock then warranty guidelines are meet.
Now with that being said, I have physical access to the device. Over the phone, the only way they would really be able to know is if they asked the software version, baseband version, kernel version, etc... and knew what they were off hand. Things like that. They can't magically peer into your phone over the air to see what's going on with it. That's the reason for their little script techs over the phone have to run through.
Ultimately, the advice mentioned above about asking the dev or the rom thread is the best you'll get. Most times this is your best place to look after a custom rom has been flashed. If a problem is deemed hardware and not software and you have to have it exchanged, flash back to stock and take it in. No tech rep will care if it was flashed back to stock (unless they are having a really miserable day and can prove it's rooted. but that's few and far between and not specific to any company).
For anyone searching this problem, the easiest solution (all thanks to Fallen4u) is to purchase ($4), download, and install Camera 360 Ultimate (Pro version no longer available on Market, afaik). This will basically replace your broken camera software (where it just sits on "please wait" - until the cows come home after jumping over the moon) with working software that brings camera back to life. This solution does not require resetting phone which does NOT guarrantee camera software will work with the Froyo 2.2 (I think it's called Froyo, anyway. I know it's the 2.2 update). So, if you have lots of software, don't want to mess with flashing this that or whatever, just save yourself the time and trouble and download the above mentioned software. Problem fixed. It also gives you many more fun possibilities from what my lady friend showed me this evening.
If the camera firmware update failed, the best thing to do is follow adrynalyne's thread to rewrite the firmware instead of purchasing an app.
AlgorithmX said:
Try this before rolling back.
http://forum.xda-developers.com/showthread.php?t=951636
Click to expand...
Click to collapse
Like this suggestion which you seemed to ignore completely.
Sent from my ADR6350 using XDA App
times_infinity said:
If the camera firmware update failed, the best thing to do is follow adrynalyne's thread to rewrite the firmware instead of purchasing an app.
Like this suggestion which you seemed to ignore completely.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
I didn't ignore it, I let her know about it, and she said no. Other than that, 1) It wasn't my phone to mess with and I have no familiarity whatsoever with Android phones. Like I said in my original post, the issue belonged to a lady friend. And, 2), like most people, she's not comfortable with doing anything of the nature described unless she fully understood it first and that it was a verifiable fix. 3), What may appear simple and easy to you, may not appear simple and easy to her. Or, me. One mistake and who knows? Poof goes your phone? So, 4), for the many people like her, where Verizon's 2.2 update broke their camera (and there are many!) simply downloading different software may seem the best/only solution for them. They should at least know it is an alternative. And finally, 5), I hoped for a fix that someone who actually had this problem found and offered. My impression was that the poster, who you say I ignored, did not have that problem himself. As such, I had no way of knowing or verifying that "fix" worked and wasn't a case where the "cure is worse than the disease."
The Reason i ask is either it is or i am the unluckiest person ever with a S2 lol
So far got the phone at xmas wasn't happy with the screen colours sent it off they said the main chip was faulty and had been replaced and a software upgrade etc...
Got it back and flashed a custom rom, well a few and noticed that i then had an issue where if someone called i had to put loudspeaker on in order to hear the other person...
Put phone back to stock and sent it off again...
Phone came back last week picked up monday used for a day all seemed fine, flashed a custom rom got another problem with the phone this time i have to put the loudspeaker on to hear other people they can hear me fine...
So its back to stock and back to vodafone tomorrow...
So can custom roms/kernels cause physical issue's with phones, never had an issue with my HTC Desire HD but i'm beginning to wonder if i should leave my next S2 stock, or have i just been unlucky ???
Would also add when going back to stock the screen colours seem much better than custom roms but the sounds issue's remain...
One word NO!
What rom are you flashing?
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
wakers said:
Checkrom, wickedrom, illusion Xt, not sure which if any has caused any issues could be I'm just unlucky
Definatly noticed issues with screen colours too which now in I'm back on stock have been sorted
Its all a bit weird
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Um, actually, yes.
You run the (slight) risk of bricking your phone every single time you flash something to it. If you're the type of person who's paranoid about these things & can't handle the idea of possibly not getting warranty service if things go wrong, you shouldn't be messing with your phone in the first place.
Anyone who has an expectation (as opposed to a "hope") of warranty service after they stuff around with the phone is an idiot.
The SG2 is a hard phone to brick. Follow the general guidelines and you should be fine. I can't imagine flashing a rom can break this phone. Worst that can happen is you brick it. Either it works or it doesn't.
Yeah Im fully aware that you risk bricking the phone
I've been flashing roms to HTC,s for years always trouble free
I always read and full wipe between flashes
Sounds like I've been unlucky then 3rd time phone is going back and since Xmas 1day without a fault not a great introduction to Samsung for me...
Sent from my GT-I9100 using xda premium
In all my time reading SGS1 and 2 the only ones who have bricked their phone are the idiots (1) who refuse to read instructions . Even then 90% of them have been able to recover .
the SGS2 quota of 1 is getting higher day by day for some reason .
jje
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
wakers said:
Yeah 3 physical faults though in a month which is what got me thinking maybe installing the custom roms is causing an issue, but if others are installing with no issue's i've obviously just been unlucky
Hopefully this time i get it back its sorted...
Click to expand...
Click to collapse
~Don't accept a repair... DEMAND A NEW PHONE
Samsung doesnt change phones, only repairs.
GeorgeCm said:
Samsung doesnt change phones, only repairs.
Click to expand...
Click to collapse
Who said Samsung??? I meant Vodafone, and they do give new phones
About a stock I don't know, and on aosp try it
http://forum.xda-developers.com/showthread.php?t=1385862
Suarez7 said:
Trust me if that was the case damaging my phone by flashing a rom then my phone would of been damaged goods by the first month i had it
Anyway just be careful how you flash a rom and it is always advised to do a full wipe before installing one
Click to expand...
Click to collapse
Seconded..
It's possible to introduce some new bugs by flashing a custom ROM (that's the price of development, you uncover new weird stuff), but not to physically damage the phone. You'd have to fiddle with the battery or greatly increase the voltages to accomplish that.
If you experience hardware issues after flashing a ROM, it means that the hardware was faulty before, and flashing the ROM just uncovered it and made it obvious to you whereas it was hidden before.
But don't let it get you down. Apparently a lot of SGS2's are faulty when coming out of the factory and need to be replaced.
The first one I had didn't last the night, it 'overcooked' itself when I plugged it to the mains to get it recharged (I knew those phones could get pretty hot but damn ! a 100°C is too much for it, it didn't stand the strain and gave up)..
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
wakers said:
In fairness they suggested a new phone in Vodafone today so it's gone back with the the request of a new phone rather than repair so we'll see
Also if anyone is interested I obviously flashed a few custom roms and reset the counter to zero and installed original Vodafone software and have had no issues warranty wise
Click to expand...
Click to collapse
I seem to have been lucky with a Vodafone SGSII, I'd have insisted on a new phone from it's first problem, Vodafone have always been pretty good at replacing.
I am wondering however how did you manage to reset the flash counter ? Even with a USB Jig mine won't reset. It will go into download mode, but that's it. I presumed my six week old SGSII was a newer one a jig won't work on.
Before trying to reset the counter you should flash the old boot loader (pre-KI1) on, the new one cannot be reset safely with a jig. Works just fine after this
What Snakeforhire said i flashed the old bootloader reset the counter with the USB Jig then reflashed the new bootloader...
Updated through kies and sent back...
I don't know who's going to read this and/or if there will be any comments to it. I just want to take this horrible frustration and downheartedness out of my chest. I hope this will be of some help for anybody out there trying the same.
Today, I've hit what I hope will be the lowest most bitter point for me as an Android aficionado. Ever since the G1 was announced and came out, I jumped on the wagon and pre-ordered from Tmo (I was a customer at that time). As soon as I had it in my hands, I began learning about its customization, user experience, etc. I came here and learned how to root it (although I registered a bit later). I've owned four G1s, two G2s, an HTC Sensation and two Tbolts. All of them motivated me to dare tweaking and customizing more and more. Always with more or less satisfying results at the end, after overcoming the always present unexpected troubles. This time, however... I feel like I've got a pretty ugly dose of failure.
<s>I'll try to make it short.</s> My in-laws came from China. They had very old phones and wanted to get iPhones. However, the screen ended up seeming pretty small for them compared to my Tbolt. They asked me if I could help them get a good phone. I came up with a couple of choices. The HTC One X and the Samsung Galaxy S2. After thinking about it, I went for the S2. Now, it was a matter of picking the right (GSM) one. Either the ATT or Tmo version. I did more research and picked the ATT (I777) version, since "that's closer" to the international version.
I purchased two of them, still sealed, from Craigslist. I just loved them! Immediately, I purchased the unlocking codes for both. I got home and inserted a Tmo SIM to test them. I couldn't wait to hand them over to them. Then, things started to go just wrong in every way...
I was shocked to see the S2 had no Chinese option in language. The only Asian language available was Korean. At some point later, I realized that the Chinese options in my other phones were probably due to HTC being a Taiwanese company. I kept searching for an answer and ended up trying a couple of apps from the market like Morelocale2, etc. But they only translated about %30 of the whole. Failure.
I kept reading and learned I could flash a ROM with the language included. After more and more reading and rooting it, I had two choices. I could flash the Hong Kong or Singapore version of the phone. Those two come with the language already installed. Even though I don't know Chinese, I managed to get some help from a dev acquaintance and found the HK (I9100) version that even had the ICS version. I followed the tut and flashed it using Odin. When it booted it looked all good. Looking at that Chinese all over the place even made me smile. I sighed and said "I'm done"... little did I know my failure was far from avoided.
First of all, I learned that only two of the four buttons work due to the kernel. Only Back and menu work. I tried to see the good side. It'd be easier for them to get used to using only two buttons. I started installing more goodies, like Chinese input (by strokes, not by keyboard), even a wonderful app I found called Buttonsavior to replace the physical buttons. I was "done" and handed over the phone; only one of them. I wanted to be sure of the procedure to go, before doing the other. Then, I realized something horrific...
As they were trying the phone, poking menus here and there to become familiar with the UI; suddenly, while testing making a phone call, I heard that phrase: "It has no sound!" I wanted to kick myself out of my own disbelief... I thought "OMG! It was so hard hard to get a hold of that ROM. Now what?" I sadly understood I'd have to restore and go back to trying to find a solution to the partially translated gingerbread version. Then, I restored and went cold when I realized what had happened.
During the restoring, I was quite glad I had backed up in case of a disaster. When I booted up and just out of curiosity of how good the sound of the call was supposed to sound, I made a call. Guess what? IT DIDN'T WORK EITHER! This is when I started panicking! I thought "OK, I restored, now what?" I quickly did a wipe, factory reset, even unrooting back to the stock ROM. Did it work? No!! No audio call! "OMG!! The phone I just bought on Craigslist it's defective!"
I didn't give up and let that make me feel down (completely). I said "OK, after all this struggle and time, at least I'm going to make the other one work." I took the other phone and made a call to finally hear the quality of the audio call. It was very good to say the least. It was very nice and clear. At this point I started to feel half of an epic failure. In less than 5 mins the phone was rooted and being updated to the HK ICS ROM. I went as quickly as I could through the initial setup. I hit the home screen and the first thing I touched was the phone call icon, dialed and waited to see what the phone was supposed to be like. Then, the half failure, became full failure. I don't remember feeling that down for something before. I threw in the towel...
The audio didn't work... that's when I realized I had just messed up two brand new S2s I bought out of a stranger's hands. I've thought about it, and I got the feeling something can be done, but at this point I'm not sure what. I feel like my brain has dried up. I struggled with this for about a week, having a massive headache at least three times. But the story didn't end there...
In a feeling of total defeat, I did the last thing I could think of... I called tech support and tell them about the lack of sound. After lot of talking and pushing for some solution (they wanted me to take it back to the 'store'), they said the warranty was good for another eleven months. They've got my info and emailed me a prepaid UPS label. You think think it's a happy ending? No. You want to know why? I can't even reset the binary counter. I even got a jig connector to do the job, but of course 'for some strange reason', it won't do it. If this isn't an example of a perfect failure, then what is it? Total lost: $900.
I'm not as good as most guys here, but I like to read and use common sense as much as I can. This time I thought to my self "I'm a dumbass, what else can I say?" Aren't I?
Thanks for reading,
Edit: Yes, I did flash a stock ROM.
Hi buddy,
I just read your story.. U will both phone work again, I am pretty sure! Try to get some experienced help! Fully restoring by flashing a stocks rom should be the help... Make sure I do it correct!
Good luck!!!
Sent from my GT-I9100 using xda premium
*you do it right..
Sent from my GT-I9100 using xda premium
I can tell you right off the bat that the reason the Home and Search buttons didn't work on your i777 (AT&T S2) is because you flashed an i9100 ROM. The i9100 has a physical home button and no search button. i9100 ROMs ARE compatible with the i777 since other than that they are identical phones, but you need to fix the key mappings. As for the audio, I'm not sure.
I don't know if I forgot to mention it, but I did flash a stock ROM.
I may not have the greatest knowledge of these things but are you sure it's not a radio issue? Have you tried flashing a different radio (one that's compatible with the ROM and region you want to install)? I know I mate who had an issue with calls after flashing a new ROM to his new S2 and the problem turned out to be the radio. Once he flashed a new one (it may have been the factory one he flashed back on to it) it all worked.
Sent from my HTC Desire using Tapatalk 2
Man that's a crazy story. Not sure if I over read it or not cuz I'm baked or not but maybe they were tinkered with before you got them? Like did audio work originally? I know I'm sure glad I found the sbf files for my old OG, since they've saved me numerous times being able to flash to out of the box status. Sounds like you might've jumped into it too quickly without ironing out all the details. Shoot I know it took me like 2 weeks thinking about just rooting my phone to finally do it a couple years ago.
Sent from my OG using XDA
Yes, that was my first thought after flashing that ICS regional ROM: the radio. And that was the reason why I decided to flash the unrooted stock ROM. But like I said, nothing! I'm sure there was nothing wrong with the phones. The second was working fine before I did it. I actually tested it over and over, kind of like to make me feel better that at least that one of them was going to work.
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
Like I said. The reason why I thought it was a radio issue (and flashed a stock ROM via Odin) was because they do have sound, but no during a call.
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
The_Forastero said:
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
Click to expand...
Click to collapse
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much mate! Really, I really appreciate it. The clock is ticking back. They're leaving tomorrow. I'll get into it and report back.
Thanks again,
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
The_Forastero said:
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
Click to expand...
Click to collapse
That one I'm not overly sure about sorry mate. Someone else might be able to chime in? But hey, considering they don't work in their current state it can't hurt to give it a try?
Sent from my HTC Desire using Tapatalk 2
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Product F(RED) said:
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
KanocX said:
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
Click to expand...
Click to collapse
The phones are identical in terms of hardware specs (i9100s I mean) but each region may have one that picks up different frequencies. No you can't reconfigure it unless the radio supports it which is rare and not the case for the S2. Like I said flash the radio that came with the phone. You most likely flashed a ROM for an S2 that was a different region and came with a different radio. The software for the radio is trying to tell the radio to tune to a frequency it doesn't support. Get it?
Hopefully you made a nandroid backup before you did anything and can restore it. Also you can always play around with it in English and then change the language to Chinese when you are done if you are able to find a rom that has the language support.
So I don't know ****. Yeah I said it, don't run away though. I'm still reading tons of information on the forum and you guys are awesome and I can't believe I never did this sooner!
I really wish I could have started from a stock phone but that was a great deal to me, and this is how things are.
The situation:
I bought a MINT Atrix 4 for $125. Great. Well the phone already has what the guy called "Jelly bean" installed which is cm10 if I understand correctly (the phone wont be activated till next week).
The problem:
He said "DO NOT try to record a video. The camera works, just not the video recorder. He also says WiFi doesn't work and DO NOT touch that either. Now that's a problem.
Phone specs:
Android version 4.1.1
baseband version N_01.77.37p
kernal 2.3.32.59-mb860-cm9-g89b8854
cm mod version 10-20120729-UNOFFICIAL-olympus
yada yada
If any specific threads can help besides the Nooby and FAQ threads I would appreciate that as well. The more information the more comfortable I will be with the phone.
I wouldn't call a broken phone mint. If wifi doesn't work, its likely that bluetooth doesn't either and if that's the case, you got screwed as the only way to repair it is to send to motorola. Which since you're not the original owner means you have to pay for the repair. I'd return it if he didn't disclose the broken wifi. Good luck
Try flashing a new radio and rom
Sent from my undervolted, underclocked, power saving Motorola Atrix.
pre4speed said:
I wouldn't call a broken phone mint. If wifi doesn't work, its likely that bluetooth doesn't either and if that's the case, you got screwed as the only way to repair it is to send to motorola. Which since you're not the original owner means you have to pay for the repair. I'd return it if he didn't disclose the broken wifi. Good luck
Click to expand...
Click to collapse
It wasn't an eBay purchase so returning it isn't an option. Besides, I never said bluetooth doesn't work. From what I read, when both are not working its hardware and software if only one (most of the time).
Regardless, thank you for your worthless opinion and lack of help.
zhillz said:
It wasn't an eBay purchase so returning it isn't an option. Besides, I never said bluetooth doesn't work. From what I read, when both are not working its hardware and software if only one (most of the time).
Regardless, thank you for your worthless opinion and lack of help.
Click to expand...
Click to collapse
You're right you didn't say bluetooth wasn't working. Its just a known error around the forums. Really no need to snap at me or get defensive. I was not in any way belittling you so I dont appreciate your attitude from a self proclaimed NOOB. That being said, I'm over it and I agree with the other post saying to try another rom. Is it joker or epinter cm10 that its on? (Those right now are the active developers of cm10 for the atrix) If its either of those, read thru their developer posts and see if wifi not working is a known issue.
Your initial post definitely came off as rude. I think I have an idea on what to do but I'm going to do a little more research before I dive in. Thanks for real this time.
So I have tried downloading different cm10 files, a cm9 file, and gapps. When I'm in my recovery and try to install from the sd card, they wont load
(bad)
Installation aborted.
What should I try now guys? Am I damaging the files? I downloaded from jokersax's site (firefox)>open containing folder and drag to F: (I tried E: but I guess that's the phones internal?)
zhillz said:
So I have tried downloading different cm10 files, a cm9 file, and gapps. When I'm in my recovery and try to install from the sd card, they wont load
(bad)
Installation aborted.
What should I try now guys? Am I damaging the files? I downloaded from jokersax's site (firefox)>open containing folder and drag to F: (I tried E: but I guess that's the phones internal?)
Click to expand...
Click to collapse
Put the file in the root of the phone's internal storage.
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Really need to start recovering the phone not throwing roms at it till its fixed. Atrix is an odd ball when you get tied up in partitions and file locations. My suggestion would be to checkout fruitcake and start from there . There are more risky ways of getting out of that rut by try the easy stuff first. Phone needs a clean start and all new files. Cm10 has some issues depending on the logic board revision you have. Before you ask the only way to tell is to physically compare one logic board to another and there are very subtle difference. I only stumbled across this by accident during some full tear downs . I usually judge by symptom then treat them accordingly .
Like I stated above fruitcake is my recommend and I have used it numerous times with trouble phones that need a clean start.
Sent from my MB860 using xda premium