Related
So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks
Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App
If your phone shows any signs of life they will most likely be able to tell that you are not stock.
Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0
For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."
Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.
Thought this was very odd. I was on phone with tech support cuz my phone bricked itself today. not sure how or why i wasnt even using it. The tech sending me replacement suggested i root my phone because it would help a lot with the random reboot issue i originally had called ina bout last week.
Proceeded to tell me that Verizon does not care if you root as long as the factory data reset will work as intended for them.
Didnt know if this information was well known or not just thought it was odd that a tech tell me to root my phone.
cbrebel said:
Thought this was very odd. I was on phone with tech support cuz my phone bricked itself today. not sure how or why i wasnt even using it. The tech sending me replacement suggested i root my phone because it would help a lot with the random reboot issue i originally had called ina bout last week.
Proceeded to tell me that Verizon does not care if you root as long as the factory data reset will work as intended for them.
Didnt know if this information was well known or not just thought it was odd that a tech tell me to root my phone.
Click to expand...
Click to collapse
I am guessing that means the LG/Stock Factory Reset but CWM Factory Reset does the exact same thing so I am still wondering what that means.. very suspicious
That's very odd. I used to work for AT&T and they said we could loose our job of we told a customer to change the core software on any device. Strange indeed.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
drt054 said:
I am guessing that means the LG/Stock Factory Reset but CWM Factory Reset does the exact same thing so I am still wondering what that means.. very suspicious
Click to expand...
Click to collapse
yeah that is what he was saying (he was telling me how he rooted his and was using cwm as well) but he said that verizons policy is that as long as the "STOCK" factory reset takes it back to original condition then they will not persue anything any further. (which btw is stock zv7 right now) the new phone they shipped me doesnt have zv8 yet either.
who knows i just thought i would elaborate what the tech told me.
the phone i sending back had CWM on it and wouldnt boot or charge battery. so i manage to get it into emergency mode and left it for about 18 hours which gave me almost 35 % charge( seems very low) but i managed to push the zv7 tot and revivie it to send back. YAY
Vzn and root
There is a lot of misconception about rooting, I used to co manage a vzn reseller.
If you go to the android market there are root apps all over the place, if rooting voided any warranties there would be huge liability issues for legal software developers and customer uproar. Plus the hardware OEMS would not alllow it to be sold legally. Rooting is a software change you are not hacking or modifying hardware here. Plus android is marketed as open source unlike iphone OS.
drutman said:
There is a lot of misconception about rooting, I used to co manage a vzn reseller.
If you go to the android market there are root apps all over the place, if rooting voided any warranties there would be huge liability issues for legal software developers and customer uproar. Plus the hardware OEMS would not alllow it to be sold legally. Rooting is a software change you are not hacking or modifying hardware here. Plus android is marketed as open source unlike iphone OS.
Click to expand...
Click to collapse
+1 U.S already has declared that rooting any android device is not under any circumstances classed as illegal.
Sent from my Sensation using XDA
RevoRooting
Verizon might also be less persnickety about rooting on the Revolution because it's on its way out. I know Verizon was much pickier about my Droid 1 when it was new than they were a few months ago.
sensation lover said:
+1 U.S already has declared that rooting any android device is not under any circumstances classed as illegal.
Sent from my Sensation using XDA
Click to expand...
Click to collapse
This was only a 1 year term on that ruling. it is coming up again soon whether or not it is viable to do it or not.
cbrebel said:
yeah that is what he was saying (he was telling me how he rooted his and was using cwm as well) but he said that verizons policy is that as long as the "STOCK" factory reset takes it back to original condition then they will not persue anything any further. (which btw is stock zv7 right now) the new phone they shipped me doesnt have zv8 yet either.
who knows i just thought i would elaborate what the tech told me.
the phone i sending back had CWM on it and wouldnt boot or charge battery. so i manage to get it into emergency mode and left it for about 18 hours which gave me almost 35 % charge( seems very low) but i managed to push the zv7 tot and revivie it to send back. YAY
Click to expand...
Click to collapse
Oh man, I totally did that when I had gotten my Revo. Fortunately Thecubed was around, and he took control of my computer and fixed the phone. It was awesome. I recall the battery taking for ever to recharge. We had to wait 30 minutes before we could try anything. We needed enough juice to run ADB and push stuff to my phone.
yep what the verizon sales/ tech guy said
walked into verizon today. my phone messed up but thats another thread... and he literally said verizon does not care if u root your phone... didnt say as long as or anything else. just said they dont care. so yeah feel free to ask them yourself.
LaggyWizard said:
walked into verizon today. my phone messed up but thats another thread... and he literally said verizon does not care if u root your phone... didnt say as long as or anything else. just said they dont care. so yeah feel free to ask them yourself.
Click to expand...
Click to collapse
That's the glory of open source...
Sent from my VS910 4G using XDA
Yeah they Dont care, but brick one & try to get a replacement in warranty if you do.
Last month i made a boo boo installing Clockwork Mod and locked it up.
While they were very helpful, nice, and understanding; And a couple weeks later when I came in with my repaired phone (thanks to un_brickable) were more than happy to get me back online with a new sim card (I had to use my sons old HTC Incredible until I FINALLY found the fix). The warranty is now VOID and I was NOT going to get a new one.
I also dropped the protection plan & bought a "development" Revolution off of E-bay. So if i blow one up i can be back up & running in a couple minutes. cheaper in the long run.
Sometimes being Honest doesnt pay off. But in the end I have a BETTER phone for the experience. (2 of them actually)
cbrebel said:
Proceeded to tell me that Verizon does not care if you root as long as the factory data reset will work as intended for them.
Click to expand...
Click to collapse
I find this hard to believe. If they don't care, why do they keep shutting the door on every new exploit?
Sent from my BrokenOut 1.1 4G VS910 LG Revolution using Tapatalk 2.
stackrat said:
I find this hard to believe. If they don't care, why do they keep shutting the door on every new exploit?
Sent from my BrokenOut 1.1 4G VS910 LG Revolution using Tapatalk 2.
Click to expand...
Click to collapse
Because an exploit is just that, something that can be used maliciously. They aren't trying to screw with rooted people, they are patching security holes.
Sent from my Gingervolt-ed VS910 4G using xda premium
stackrat said:
I find this hard to believe. If they don't care, why do they keep shutting the door on every new exploit?
Sent from my BrokenOut 1.1 4G VS910 LG Revolution using Tapatalk 2.
Click to expand...
Click to collapse
any vulnerable area in the code HAS to be patched because the first people we blame for the phone getting hacked, is Verizon, for not having the security it should have in the software
Sent from my VS910 4G using XDA
Rooted phones are a liability...
For Verizon. The reps don't care (of course), but the main company does. It does void your warranty if they find out about it.
See, the tethering apps, Google navigation, Google voice, etc, etc are all lost profits. This is especially true with this phone, where in stock form, they nickel and dime you for "Verizon Navigation," "Verizon Voicemail," and "Verizon Tether."
Another negative impact for them is the number of returns the early rooting and experimentation process creates. I can remember the number of "forced failures" and nit-picking occurring on my old Eris when people were flashing the leaked upgrade that permanently disabled root, just so they had an excuse to return them.
The Verizon reps are "next-to-minimum-wage," 18-30 year old employees who could give a rat's patootie what you do with your phone. The RMA techs, on the other hand, may not be so forgiving.
My samsung captivate had never given me any problems(in the very short but good few months I've had it) until I tried to downgrade from Gingerbread(2.3.5) to Froyo about 4 days back.
While using Odin 1 click (and the phone was rooted) to accomplish what I just said, the process seemingly carried out perfectly, the "passed" message appeared in Odin and it looked like it was a success, but instead of rebooting as usual after flashing, my Cappy just went completely blank, and has stayed like that ever since. :crying:
I have tried every button combo there is, and since Jigs are for soft bricks, I guess there's no use.
The only remedy that I haven't gone for yet, is Jtag.
Can someone, anyone, PLEASE help me here!?
Hoping someone gets it working here..
Yep. If zero signs of life...even when wall charging, then sounds like hard brick.
Which Odin did u use to downgrade ??
Just curious...
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Yep. If zero signs of life...even when wall charging, then sounds like hard brick.
Which Odin did u use to downgrade ??
Just curious...
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Well I've used Odin 3 v 1.8.5 and even Odin3 v1.7 many, many times and it's all run perfectly, but this one was Odin 3 One Click v 1.00
I've never bricked a phone ever, and yeah this one's a badass hard brick for sure.
ANY help would be really appreciated, all!
Can you provide a link to the thread you dl'd from?
mrhaley30705 said:
Can you provide a link to the thread you dl'd from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=731989
As you can see, it's from here. That's the Odin I used, but I don't think there was anything wrong with the file(at least I hope not)
It completed the process, gave the "passed" message, and then the phone went blank, like immediately.
Any thoughts on how that may have happened? 'Cause I thought it may have been bricked due to Odin crashing, but it did go through till the end, seemingly successful.
Anup7 said:
http://forum.xda-developers.com/showthread.php?t=731989
As you can see, it's from here. That's the Odin I used, but I don't think there was anything wrong with the file(at least I hope not)
It completed the process, gave the "passed" message, and then the phone went blank, like immediately.
Any thoughts on how that may have happened? 'Cause I thought it may have been bricked due to Odin crashing, but it did go through till the end, seemingly successful.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=841512
^ ^ This jig, is it for a hard bricked captivate or a soft bricked one? 'Coz although I'm definitely not confident with tearing up a micro USB cable, I'm going to give it a shot tomorrow. Heading to Radioshack first thing in the morning. Last shot God dammit :/
^
Jig won't do anything for a "Hard" Brick...only J-tag and/or Unbrickable Mod.
Sent from my SAMSUNG-SGH-I777 using xda premium
Anup7 said:
http://forum.xda-developers.com/showthread.php?t=731989
As you can see, it's from here. That's the Odin I used, but I don't think there was anything wrong with the file(at least I hope not)
It completed the process, gave the "passed" message, and then the phone went blank, like immediately.
Any thoughts on how that may have happened? 'Cause I thought it may have been bricked due to Odin crashing, but it did go through till the end, seemingly successful.
Click to expand...
Click to collapse
Something had to go wrong when the jf6 bootloaders were flashed, obviously. If u did not close that Odin yet (unlikely, i know) u could scroll through the log and see what it says about the boot.bin and sbl.bin.
Sent from my SAMSUNG-SGH-I777 using xda premium
Well Odin was closed, as expected. So that's not an option obviously.
Is Jtag doable by users, like could I get instructions on how to go about it? Or would I have to send it in?
And any other ideas?
Regardless, i recommend mobiletechvideos.com for the fix.
Respected and reliable !!
Sent from my SAMSUNG-SGH-I777 using xda premium
How long have you had the phone?? Only three months?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Anup7 said:
Well Odin was closed, as expected. So that's not an option obviously.
Is Jtag doable by users, like could I get instructions on how to go about it? Or would I have to send it in?
And any other ideas?
Click to expand...
Click to collapse
Here are some threads from the dev forum...
Developing methods to recover bricks without JTAG
The Captivate Development Platform mod AKA UnBrickable Mod
[HOW-TO]UnBrick the UnBrickable Captivate
....or like I said before, check out mobiletechvideos.com
Anup7 said:
Well Odin was closed, as expected. So that's not an option obviously.
Is Jtag doable by users, like could I get instructions on how to go about it? Or would I have to send it in?
And any other ideas?
Click to expand...
Click to collapse
Dude if nothing works and you have had the phone for less than 1 year call at&t tell him you had your phone plugged into your computer over night charging, you woke up and the phone won't turn on now. And yiur house lost power and regained and there must have been a power surge around your area. You don't know what happened but it won't respond to anything....also do you know if your tripped the flash counter at all? Or did you reset it? P.m. me if any help needed I just went through this with my note....if all else fails p.m. me I have another fix but it isn't free but its cheaper than buying a new phone outright...
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
No flash counter with the Captivate.
4-2ndtwin said:
No flash counter with the Captivate.
Click to expand...
Click to collapse
Well I thought of that too, but then there's a problem. I actually bought this phone from a friend, a couple months ago, since I wasn't sure how good of a model this was and I didn't want to go get myself a new Cappy just to be let down and want another one, you know?
Still, spent 160$ on it.
Anyway, he doesn't have the receipt, there's no way I can get att to replace it like you suggested.
And just a side note, the phone was in mint condition, never even been rooted before it got to me, lol!
Btw nope, no flash counter.
Huh? Att will not ask for a receipt when doing a warranty exchange...I've never had an issue with people not having receipts for a manufacturer defect....you will be fine as long as the phone was purchase less than a year ago
This Public Service Announcement brought to you by a pimped out At&t gNote rocking *The Collectives* AOCP CP1...
Kflan22 said:
Huh? Att will not ask for a receipt when doing a warranty exchange...I've never had an issue with people not having receipts for a manufacturer defect....you will be fine as long as the phone was purchase less than a year ago
This Public Service Announcement brought to you by a pimped out At&t gNote rocking *The Collectives* AOCP CP1...
Click to expand...
Click to collapse
I thought they'd need it as proof, but thanks!
I'll head over to ATT in a couple hours and see what they say.
I'll let you know.
FYI - the return may have a hiccup in it. Since you bought it from a friend and not from AT&T (or an authorized reseller), they don't have any proof of how long you've had it. There's no way for them to know whether you got it yesterday or 2 years ago, so they may put up a fight about honoring the warranty.
This is just speculation, but I just wanted to throw it out there that it may not go as smoothly as we would all like it to go for you.
jmtheiss said:
FYI - the return may have a hiccup in it. Since you bought it from a friend and not from AT&T (or an authorized reseller), they don't have any proof of how long you've had it. There's no way for them to know whether you got it yesterday or 2 years ago, so they may put up a fight about honoring the warranty.
This is just speculation, but I just wanted to throw it out there that it may not go as smoothly as we would all like it to go for you.
Click to expand...
Click to collapse
Thanks for the heads up though!
Any suggestions on how I should go about it then? Should I even tell ATT that I got it from a friend? Instead I could say I got it from ATT but lost the receipt...maybe a loophole somewhere.
If the phone had been activated for less than a year and its not a refurbished unit, they should replace it.
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
mr23 said:
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
Click to expand...
Click to collapse
I also bought my device about a week ago but im still on 4.1. i think i will wait before i apply any update, to make sure things getting stablized with a new version
Edit.. Nevermind.. I'm in a jumping to conclusions bad mood.. Away from the keyboard I go.
4.2 update won't brick your device. It is a Nexus - just about impossible to brick. You had a problem - but it was not the update.
Sent from my Nexus 7 using xda app-developers app
There are many running 4.2 Builds (Eclipse being one of them) and are having no issues.
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I concede with approximately three million people updated by now, you could have been the one to find the error in the update.
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Jellybean 4.2 Ruined my Asus nexus 7.
X_Fact0r said:
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Click to expand...
Click to collapse
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Kpennett said:
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
Click to expand...
Click to collapse
The guy you were replying to was talking about the OP's issue which was supposedly a bricked Nexus as a result of upgrading to 4.2. It has nothing to do with the items you mentioned, so I would suggest that he is not the one who needs to "get a clue".
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Click to expand...
Click to collapse
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
mr23 said:
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed.
Click to expand...
Click to collapse
THANK YOU. The term brick started with the Linksys routers and a brick was just that, a brick, a paperweight, doorstop, and was a very real possibility (though rare).
Before that PCs would be called anchors or door-stops but those terms were also used for PCs that were beyond any possible usefulness rather than just being beyond repair.
At least say soft-brick.
Sent from my Nexus 7 using xda premium
---------- Post added at 02:07 PM ---------- Previous post was at 01:51 PM ----------
dilldoe said:
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
Click to expand...
Click to collapse
If you can pull or remove the battery you can leave the battery out for 15 minutes. That can revive a device that has become non responsive.
I dunno is the battery on the N7 soldered in or use a ribbon connector?
Sent from my Nexus 7 using xda premium
OP, your device probably wasn't bricked, you need to press the power button for 5>7 seconds and it would of powered on, if for you get the count wrong the Nexus 7 wouldn't power up, this is why you thought it was bricked, in any case, all you needed to do is press and hold the power button for 20>30 seconds and i would of powered on.
fernando sor said:
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
In some parts of the world the day comes before the month, the UK > 24/11/2012, US > 11/24/2012.
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I only mentioned the above because you didn't say in any of your posts that you had tried this.
Just what this forum needed, more *****ing.
May be a defect device most likely due to hardware. Other than the some performance issues and some minor ones here and there, I don't think anyone got their device bricked. I hope the new one will be a better experience. Also it'll be informative if you could have mentioned the first four alpha numeric serial number.
Sent from my Nexus 7 using xda premium
I used to work at the Best Buy Samsung Experience Shop. I went by there the other day. They have a tool that updates your phone to MF3 and it doesn't remove hardly any data. I rerooted and reinstalled safestrap and everything was still there.
So, this begs the obvious question: do you have any friends at that Best Buy that could maybe, you know... <hint hint> hit you up with a copy of whatever software they're using to do that?
HEY I HAD TO ASK!!!
I did this the other day and say that this works perfectly! So glad to be back on MF3!!
I don't think I can get a copy. The best I can do is make a flashable backup afterward and upload it. = / the software downloads it from a server.
chronicaust said:
I don't think I can get a copy. The best I can do is make a flashable backup afterward and upload it. = / the software downloads it from a server.
Click to expand...
Click to collapse
I don't think he was asking for the file specifically but rather a copy of the software they are using. It's logical to assume that if we were able to obtain a copy of the software they use at best buy the it could still be made to download and flash the appropriate mf3 firmware file from anywhere with an internet connection.
Sent from my GT-I9295 using XDA Premium HD app
Does every Best Buy have a Samsung Rep?
Sent from my GT-P5110 using XDA Premium 4 mobile app
dave5777 said:
Does every Best Buy have a Samsung Rep?
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not every one, but most.
dave5777 said:
Does every Best Buy have a Samsung Rep?
Sent from my GT-P5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your best bet is to call and ask at your local best buy. That's what I did. My best buy is small but they have one there. I'll be going there this weekend to see if they can update mine.
Sent from my LG-E970 using XDA Premium 4 mobile app
tmease1 said:
Your best bet is to call and ask at your local best buy. That's what I did. My best buy is small but they have one there. I'll be going there this weekend to see if they can update mine.
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They can choose to either give you complete factory or just update only just do you know. Good luck it's a great tool I've used it. You should be good = ).
Please
chronicaust said:
I don't think I can get a copy. The best I can do is make a flashable backup afterward and upload it. = / the software downloads it from a server.
Click to expand...
Click to collapse
Upload a backup Please!
-TransformixS3
Well I stopped by a local Best Buy here in Vegas this morning, sat in line waiting to speak to the "Samsung rep" (there were like 4 people in front of me) and when I was finally up the guy said "Oh, the Samsung rep is right behind me in the other section..." DOH!!!
Anyway, I had returned my GS4A (I537 of course) to MF1 earlier this morning, no root, nothing else but the ROM flashed from that ODIN One-Click that's available and...
The software they're using at Best Buy basically ignored my GS4A completely, recognizing it's running MF1 but it wouldn't do anything else and said the ROM wasn't compatible. The guy asked if I'd been rooted and of course I said "No..." then he said is it unlocked and I said "Yes..." and he said that's why.
I commented that would be a bit stupid since they do sell the phones off-contract and by doing so a person could get the unlock code from AT&T (as I did, actually, through an eBay seller who got it from AT&T) and he just shrugged his shoulders and handed me my phone and that was that. The rep specifically stated 3 times in a row that if it's unlocked you can't flash it with their software, so I made note of it and I'm passing along what at least this one "Samsung rep" stated to me - I can't verify or confirm it's true but that's what he said, 3 times in a row. He never mentioned rooting more than the one question, but was quite adamant that I understood the reason it wasn't working which by his statements was that if the phone is unlocked they can't flash it; I personally think it's a combination of mine being rooted in the past with activeroot and also being (carrier) unlocked as well.
So... I don't think being rooted caused the problem more than being unlocked, but at this point I don't have any clue to be honest, it could actually be a combination of both for whatever reason but this MF1 isn't rooted, that much I know for certain.
Anyway, that's a dead end for me so I'll just put Safestrap back on and load up the AOSP ROM with the MF1 kernel modules and the camera fix and be done with it, that's enough ROM swapping for me for the time being.
So just for the record: if you're thinking about doing this and you've rooted your I537 at any point, that may stop this potential flash of MF3 at Best Buy on your device cold - if it's unlocked that might have something to do with it as well but I'm going to guess they're checking for root even if you've completely restored an unrooted ROM like MF1, or they're just getting wise to us with the MF1 and MI2 pre-release ROMs we've been toying around with, I just don't know.
Would be nice to get MF3 back on here just in case AT&T does drop 4.3 during October but, I guess I'm somewhat "stuck" now since I'd prefer to have working screenshots so that means MF1 or the AOSP ROM.
Just passing along my experience...
br0adband said:
Well I stopped by a local Best Buy here in Vegas this morning, sat in line waiting to speak to the "Samsung rep" (there were like 4 people in front of me) and when I was finally up the guy said "Oh, the Samsung rep is right behind me in the other section..." DOH!!!
Anyway, I had returned my GS4A (I537 of course) to MF1 earlier this morning, no root, nothing else but the ROM flashed from that ODIN One-Click that's available and...
The software they're using at Best Buy basically ignored my GS4A completely, recognizing it's running MF1 but it wouldn't do anything else and said the ROM wasn't compatible. The guy asked if I'd been rooted and of course I said "No..." then he said is it unlocked and I said "Yes..." and he said that's why.
I commented that would be a bit stupid since they do sell the phones off-contract and by doing so a person could get the unlock code from AT&T (as I did, actually, through an eBay seller who got it from AT&T) and he just shrugged his shoulders and handed me my phone and that was that. The rep specifically stated 3 times in a row that if it's unlocked you can't flash it with their software, so I made note of it and I'm passing along what at least this one "Samsung rep" stated to me - I can't verify or confirm it's true but that's what he said, 3 times in a row. He never mentioned rooting more than the one question, but was quite adamant that I understood the reason it wasn't working which by his statements was that if the phone is unlocked they can't flash it; I personally think it's a combination of mine being rooted in the past with activeroot and also being (carrier) unlocked as well.
So... I don't think being rooted caused the problem more than being unlocked, but at this point I don't have any clue to be honest, it could actually be a combination of both for whatever reason but this MF1 isn't rooted, that much I know for certain.
Anyway, that's a dead end for me so I'll just put Safestrap back on and load up the AOSP ROM with the MF1 kernel modules and the camera fix and be done with it, that's enough ROM swapping for me for the time being.
So just for the record: if you're thinking about doing this and you've rooted your I537 at any point, that may stop this potential flash of MF3 at Best Buy on your device cold - if it's unlocked that might have something to do with it as well but I'm going to guess they're checking for root even if you've completely restored an unrooted ROM like MF1, or they're just getting wise to us with the MF1 and MI2 pre-release ROMs we've been toying around with, I just don't know.
Would be nice to get MF3 back on here just in case AT&T does drop 4.3 during October but, I guess I'm somewhat "stuck" now since I'd prefer to have working screenshots so that means MF1 or the AOSP ROM.
Just passing along my experience...
Click to expand...
Click to collapse
Wow that sounds like a horrible experience. What I'm gathering from this is that the rep didn't know what he was talking about. My i537 is also unlocked, rooted, triple booting roms (safestrap) and I got the update just fine.
Here is what I bet happened. The tool they use has 2 different functions, and one isn't as well known. The one they usually use is basically connecting your phone (no download mode) and it updates, and that's that. That one never works. The other one requires them to press ALT + F10 on their keyboard and enter a password to get into the actual system that will give you the update to MF3. My guess is the rep didn't know about this.
I am 100% positive it can be done Br0adband. That rep was clueless.
chronicaust said:
Wow that sounds like a horrible experience. What I'm gathering from this is that the rep didn't know what he was talking about. My i537 is also unlocked, rooted, triple booting roms (safestrap) and I got the update just fine.
Here is what I bet happened. The tool they use has 2 different functions, and one isn't as well known. The one they usually use is basically connecting your phone (no download mode) and it updates, and that's that. That one never works. The other one requires them to press ALT + F10 on their keyboard and enter a password to get into the actual system that will give you the update to MF3. My guess is the rep didn't know about this.
I am 100% positive it can be done Br0adband. That rep was clueless.
Click to expand...
Click to collapse
Yah, he just plugged in the phone with it on and operational, clicked a tile on the screen (there were like a dozen of them each one supposedly for a different device), and after 20-30 seconds of it reading data from the device it just pulled up the ROM build (MF1) and then said it was incompatible.
Interesting, but I'm not sure if it's worth going back and dealing with the guy a second time - maybe I'll try again later tonight before they close and hopefully someone else will be on shift and I can mention the ALT+F10 thing, hopefully they'll have a clue.
My question to you is: did they require doing the ALT+F10 to get your device flashed properly?
Thanks for that tidbit of info, kinda wish you'd mentioned it earlier but but but...
It took the rep a few tries with mine... And one of those he switched the cable. I'd try a different best buy (if u can) or wait till someone else is at the keyboard. The last few months talking to AT&T tech support, they gave me all kinds of excuses too, but I could tell they had no clue or real skills beyond their training courses. Mine is not unlocked though.
br0adband said:
Yah, he just plugged in the phone with it on and operational, clicked a tile on the screen (there were like a dozen of them each one supposedly for a different device), and after 20-30 seconds of it reading data from the device it just pulled up the ROM build (MF1) and then said it was incompatible.
Interesting, but I'm not sure if it's worth going back and dealing with the guy a second time - maybe I'll try again later tonight before they close and hopefully someone else will be on shift and I can mention the ALT+F10 thing, hopefully they'll have a clue.
My question to you is: did they require doing the ALT+F10 to get your device flashed properly?
Thanks for that tidbit of info, kinda wish you'd mentioned it earlier but but but...
Click to expand...
Click to collapse
Yes sir it did. If they don't know the password, it's probably smart100 if they act like it's a big deal tell them to call their field support hotline. Lolol
Not sure if it's worth all this hassle but, we'll see what happens if I decide to head back to Best Buy later. Thanks again for the info.
Going to best buy in the am
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
I went at 10 when they opened the Samsung rep doesn't come in til noon. I'll try it tomorrow.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
I just got my phone updated to MF3 at my local Best Buy. First try said it was incompatible, so he called his support line and was told to put phone in download mode to update firm ware. Now I'm on official MF3. The Samsung rep was very cool let me watch the whole process.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Will have to pass along that info to the Samsung rep if I do decide to head back to get MF3 installed. Running nicely on MF1 right at this moment so I'll stick with this for the time being. Thanks for the report.
Now if we could just yank that MF3 off yours into a flashable zip or whatever...
Pretty sure those days are coming to a close with the 4.3+ releases as Samsung apparently has every intention of locking down everything to as many degrees as possible.