Related
[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...
Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)
scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back
ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software
Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.
seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen
NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.
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.
All I find online is that the Gear VR is only compatible with the Note 4. Does that mean any carrier's Note 4, or only AT&T, since they're the only ones who are also selling the device?
Is compatibility ready out of the box, or does it need a specific update?
More specifically, how's compatibility with the T-Mobile Note 4?
Website says only verizon is no go until update
Sent from my SM-N910T using XDA Free mobile app
What website? Could you please provide a link?
Man I am in Canada on bell and ordered one of these right when they came out because I really want one and they won't be selling in Canada like the gear circle which I had to order in the usa as well. Have to pay shipping to canada to ship it from the mail forwarding company I use, I really really hope it works or that's going to be roughly $275 collecting dust. I love Samsung and everything in my house is Samsung but this really pissed me off that somehow a carrier has to be involved with a vr headset.
Ashtear said:
What website? Could you please provide a link?
Click to expand...
Click to collapse
http://www.samsung.com/us/mobile/we...38267&MKM_MID=5423369&CID=eml-mb-cph-1214-785
Sent from my SM-N910T using XDA Free mobile app
http://www.samsung.com/us/mobile/wea...b-cph-1214-785
Click to expand...
Click to collapse
Thanks a lot. I can't believe I hadn't seen it.
erik10002 said:
Man I am in Canada on bell and ordered one of these right when they came out because I really want one and they won't be selling in Canada like the gear circle which I had to order in the usa as well. Have to pay shipping to canada to ship it from the mail forwarding company I use, I really really hope it works or that's going to be roughly $275 collecting dust. I love Samsung and everything in my house is Samsung but this really pissed me off that somehow a carrier has to be involved with a vr headset.
Click to expand...
Click to collapse
im in the same boat, should have mine tomorrow, in on telus though, rooted and running a tmobile based rom and custom kernel so who knows, ill keep you posted
Yours should work then as long as it's a t-mobile rom with the latest firmware, I on the other hand stopped rooting and all that last year so I hope it works. I think it was only verizon that wasn't working but they released the update pretty quick which I hear is rare for them lol. Worst case I will have to wait till January when Bell hopefully releases the lollipop update which should no dought include compatibility with the gear vr!
perryh1 said:
im in the same boat, should have mine tomorrow, in on telus though, rooted and running a tmobile based rom and custom kernel so who knows, ill keep you posted
Click to expand...
Click to collapse
Sadly, i have mine being shipped to Buffalo and ready for pickup next week. Knowing what we know, I'm no longer in a rush to pick it up.
Anyway, I'll keep an eye on your findings. Thanks!
Worse case,,,,maybe post it for sale?
le10017 said:
Sadly, i have mine being shipped to Buffalo and ready for pickup next week. Knowing what we know, I'm no longer in a rush to pick it up.
Anyway, I'll keep an eye on your findings. Thanks!
Worse case,,,,maybe post it for sale?
Click to expand...
Click to collapse
i cant get it to work, get everything installed and all i see is a bluescreen, its the occulus homescreen but blank, none of the apps, flashed stock tmobile fw and the stockish starkiss kernel to avoid the bootloops but nada.
Not good news so far, I should have mine on Monday or Tuesday and I am on bell with no mods or anything so we will see how that goes and I will report back. Like I said though worst case the lollipop update should have the required files.
Well, got my gear vr and went to try it, put SD card in then put phone into headset and was told to take it out to finish installing the software and It did but then said I needed to update my phone. Any ideas? Bell mobility stock and not rooted or anything. Not looking good for us Canadians, maybe if we can get a hold of the gear vr manager apk!
erik10002 said:
Well, got my gear vr and went to try it, put SD card in then put phone into headset and was told to take it out to finish installing the software and It did but then said I needed to update my phone. Any ideas? Bell mobility stock and not rooted or anything. Not looking good for us Canadians, maybe if we can get a hold of the gear vr manager apk!
Click to expand...
Click to collapse
Brutal. I'll need to decide whether to leave it in the box and sell it, or hold out for the updates. BTW, I read in another forum that once the note 4 gets lollipop, it'll full support the VR. Any truth behind that?
le10017 said:
Brutal. I'll need to decide whether to leave it in the box and sell it, or hold out for the updates. BTW, I read in another forum that once the note 4 gets lollipop, it'll full support the VR. Any truth behind that?
Click to expand...
Click to collapse
I said that and I am only assuming it will, would be kinda dumb to put out a major update then have to put out a small one just for the vr. I got mine to work by rooting and using the dk 3.0 rom for t-mobile with the ael kernel. Would have liked to stay stock but sometimes you have to do what you have to do when you don't want to stare at a useless box on your coffee table!
Rom help for Gear VR
HI there. I am new here. I thank you all for the work people put into the Roms and making all 4 of my notes a much more enjoyable product.
I have some questions if someone who knows could please answer them for me as I am left a bit confused with everything I have read.
1. I am in Australia and everytime I load up the Gear VR, or actually the Oculus apps, it says I need to update. I know I can not do this yet so I would like to know if there is a rom I can use?
2. I didnt want to root this note 4 just yet but I will. Is there a way to root it without tripping knox?
3. What is the best way to root it and what do I use? I have used odin many times, but what md5 file should i use for note 4?
4. Can someone please point me to a link of some firmware that I can put on my note 4 that will straight away mean I have the update to use the GEAR VR on my note 4?
Currently when I download the Oculus mobile sdk, each time i try to load an app from it up, it tells me i need the latest update, but then my phone says it has the latest update.
So obviously need to root and load a rom in that will work. I really have always like the x-note rom for note 3, so is there one that will let me use gear vr that is on its way or is there any firmware i can use?
I'm under the impression there must be a rom that allows the gear vr to work.
If someone could help me please get my gear vr working would be great. I have downloaded Vanguard V and that works on my phone, but there is no oculus home, only oculus cinema and others.
Thanks
Please help
Please can someone help me here. The person who writes the post that allows me to follow and i end up with my note 4 being able to work in my Gear VR, I will personally buy them a "RidgeWallet" of their choice. You can google the item and choose one you want me to buy you. I offer this item only because I got one myself and think they are superb and I think it is a great gift to give to someone who makes it so my Gear VR works for my nephews christmas day
Just so you guys know, when you decompile the oculus home and oculus horizon apk. It says the supported models are SM-N910A , SM-N910F, SM-N910C, but we all know it works on the SM-N910T as well. So who knows what there basing support on at this time. Had anyone else dug around in the code?
livesinaline said:
HI there. I am new here. I thank you all for the work people put into the Roms and making all 4 of my notes a much more enjoyable product.
I have some questions if someone who knows could please answer them for me as I am left a bit confused with everything I have read.
1. I am in Australia and everytime I load up the Gear VR, or actually the Oculus apps, it says I need to update. I know I can not do this yet so I would like to know if there is a rom I can use?
2. I didnt want to root this note 4 just yet but I will. Is there a way to root it without tripping knox?
3. What is the best way to root it and what do I use? I have used odin many times, but what md5 file should i use for note 4?
4. Can someone please point me to a link of some firmware that I can put on my note 4 that will straight away mean I have the update to use the GEAR VR on my note 4?
Currently when I download the Oculus mobile sdk, each time i try to load an app from it up, it tells me i need the latest update, but then my phone says it has the latest update.
So obviously need to root and load a rom in that will work. I really have always like the x-note rom for note 3, so is there one that will let me use gear vr that is on its way or is there any firmware i can use?
I'm under the impression there must be a rom that allows the gear vr to work.
If someone could help me please get my gear vr working would be great. I have downloaded Vanguard V and that works on my phone, but there is no oculus home, only oculus cinema and others.
Thanks
Click to expand...
Click to collapse
What version of the Note do you have. If you have the N910G you should be able to get it to work, but you need to flash the ANK3 firmware.
I am still waiting on my GVR (bloody AusPost...) but this is what I did to get ANK3 firmware on my Aussie N910G. I now have the Oculus app and have downloaded all the VR games already
Go to Sammobile, I cant post the direct link but you want the search for N910G, XSA model
Download the November 2014 firmware, ending in ANK3
Follow the instructions on Sammobile for downloading and using Odin to flash your firmware, these instructions show up after you click the download link. Its pretty straighforward
Phone will restart and install the new firmware
you should then be able to plug the phone into the GVR and it will install the app and any required updates.
The XSA model is the generic Australian model (my phone is a Telstra branded phone). You should have no problems if you have the N910G model. If you have an N910U then you are out of luck as that is the Exynos version.
FYI you can check the model number by looking at "about device" under settings.
Let me know if you have problems. This was the first time I ever flashed a phone firmware so you should be ok. I would be interested to know if, after the update your GVR does acctually work.
Cheers,
Luke
Thanks Luke. I am same as you. Telstra with 910g. I will give it a go and get back to you.
Thanks for replying. Take me up on my offer if you like.
sussed
livesinaline said:
Thanks Luke. I am same as you. Telstra with 910g. I will give it a go and get back to you.
Thanks for replying. Take me up on my offer if you like.
Click to expand...
Click to collapse
So on Sam mobile it appears to have Optus and Vodafone december firmware. Ending with ANK3. Do you think this will ahve the update i need? and why does telstra not have it for FFS? I wouldnt have to root my phone then as I am on that free new phone feeling and instant replacement plan.
Just as the title says, I am looking to sell my verizon s6 edge on Swappa. I am undecided if I should take it back to stock or not before I list it. I feel like a huge amount of normal users may be scared away by the fact that it's rooted on oe2 with clean rom.
What do you guys think? I am wanting to get the 64 gig moto x pure so I can unlock the bootloader and have my way with it, so I think a $500 price for a mint phone would be fair, but I just don't want to scare away potential buyers.
Opinions??
jsminnis said:
Just as the title says, I am looking to sell my verizon s6 edge on Swappa. I am undecided if I should take it back to stock or not before I list it. I feel like a huge amount of normal users may be scared away by the fact that it's rooted on oe2 with clean rom.
What do you guys think? I am wanting to get the 64 gig moto x pure so I can unlock the bootloader and have my way with it, so I think a $500 price for a mint phone would be fair, but I just don't want to scare away potential buyers.
Opinions??
Click to expand...
Click to collapse
~90% of users do not even know what root means.
If you sell the phone to one of those users the buyer will likely panic and ask why every update is failing to install.
Your smartest move would be to unroot through Odin.
If the buyer wants root he/she can root.
Snowby123 said:
~90% of users do not even know what root means.
If you sell the phone to one of those users the buyer will likely panic and ask why every update is failing to install.
Your smartest move would be to unroot through Odin.
If the buyer wants root he/she can root.
Click to expand...
Click to collapse
Actually, they couldn't root, because the latest update doesn't allow it. I guess I just hate to unroot a phone and render it unrootable because rooting is at the core of my nature, lol. I just have to remember it won't be mine to tinker with anymore, haha
jsminnis said:
Actually, they couldn't root, because the latest update doesn't allow it. I guess I just hate to unroot a phone and render it unrootable because rooting is at the core of my nature, lol. I just have to remember it won't be mine to tinker with anymore, haha
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
This thread gives the appropriate firmware used to unroot.
Every time I use it, I am able to root again.
It restores the phone to the original factory settings, the OC3 build.
OC3 obviously can be rooted.
Snowby123 said:
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
This thread gives the appropriate firmware used to unroot.
Every time I use it, I am able to root again.
It restores the phone to the original factory settings, the OC3 build.
OC3 obviously can be rooted.
Click to expand...
Click to collapse
I got ya, that's a good Idea. I will just sell it on oc3. If they know what they are doing then they can take it from there.
jsminnis said:
I got ya, that's a good Idea. I will just sell it on oc3. If they know what they are doing then they can take it from there.
Click to expand...
Click to collapse
I totally agree. At least keep it on the rootable firmware. Its a smaller percentage of people who root, but many of those people use swappa. Its even an option for your listing. I have myself bought an mdk s4 just because it was the only place I could find the last vzw Samsung device with an unlocked bootloader. I payed more for it too, after mine broke. I would imagine those interested in a rootable s6 edge would probably do the same.
Sent from my SM-G925V
When I sold my galaxy s4 the person buying the device wanted it to remain rooted, and paid extra for it. It all depends on the buyer.
Sent from my SM-G925V using Tapatalk
If I were to right now get the Samsung Galaxy S5 AT&T ( http://www.att.com/cellphones/samsung/galaxy-s-5.html#sku=sku7120234 ), is it known whether it will have a rootable version or not?
If I am unable to root the phone and keep it rooted, I'll most likely have to go with another phone. (Which would be a shame.)
I've read up some on the situation, and it seems as long as it is version 4.4.4 I would be fine.
And I would be able to update while keeping root if I follow this thread: http://forum.xda-developers.com/att...w-to-update-to-g900aof2-5-0-keeproot-t3149146
So, I suppose the real question is how sure is it that you'll get the 4.4.4 (rootable) version of android?
And are there any downsides to doing so right now?
(I have a rooted phone now: An HTC First. The failed "Facebook" phone. It was very easy to root and receives no updates, so it's been hassle free, but it'd be nice to finally update.)
I'm not sure if you are buying direct from AT&T or not, but I think it's been confirmed that they have only been selling S5s with 5.0 on them out of the box.
Root may come eventually for those who have factory Lollipop images on their S5s, but I wouldn't count on it. Unfortunately, the window for an easy root on a brand new AT&T branded S5 has closed.
How much are you willing to spend? I'd consider selling my almost mint condition rooted 5.0 GS5 for the right price. I just got it in the Spring and it's in fantastic shape.
Dark_Vortex said:
I'm not sure if you are buying direct from AT&T or not, but I think it's been confirmed that they have only been selling S5s with 5.0 on them out of the box.
Root may come eventually for those who have factory Lollipop images on their S5s, but I wouldn't count on it. Unfortunately, the window for an easy root on a brand new AT&T branded S5 has closed.
Click to expand...
Click to collapse
Thanks for the reply. Going to look at other options, then.
slicetwo said:
How much are you willing to spend? I'd consider selling my almost mint condition rooted 5.0 GS5 for the right price. I just got it in the Spring and it's in fantastic shape.
Click to expand...
Click to collapse
Well, I was going with this phone because it is 'free' with the existing contract.... Looking at the other 'free' options now.
Motok0 said:
Well, I was going with this phone because it is 'free' with the existing contract.... Looking at the other 'free' options now.
Click to expand...
Click to collapse
If root is a deal breaker I suggest not getting the GS5 unless you are positive that you can get one with KitKat out of the box.
That being said...I have an unrootable one on AT&T that I got free for extending my contract; and I found that their 5.0 build for this phone is probably the most stable phone I've ever had on AT&T ever. Besides the battery and back cover nag alerts and not being able to save Amazon video to the SD card...I have no other complaints re: not having root. But even when I had devices that were rooted...they were stock-rooted. As always...YMMV.
Sent from my Nexus 7 using Tapatalk