HELP! SEANDROID and FRP Issues. - Galaxy Note5 Q&A, Help & Troubleshooting

I realize this has been mentioned before but, I couldn't find a solid answer specific to my problem.
As it currently stands, my Note 5 bootloops or so it seems with the SEANDROID and FRP Binary errors appearing with the Note 5 logo, and fade to black. Rinse, repeat.
I'll back up a little bit, my friend got me a Note 5 on his plan with Bell last November. After just 30 days he was fed up with the service and went to epic ends to cancel and return both his phone and mine, of course this didn't work. So, after a litany of calls and driving to different stores for various credits. He effectively was left with our phones and a bill total of around $800 after everything said and done. Somewhere in this mix though Bell, decided or someone he was laying into to blacklist both his phone and my beloved Note 5.
I was using the phone for work at the time and suddenly it didn't work!? So he told me his wasn't working either and alas we set off to figure out some circumvention around this, which ended up with some nerdy guy in a Tim Horton's changing the IMEI's of my Note 5, which had it's own issues itself.
First we had to root the phone, then he used an octoplus box to unlock it and pop another IMEI in there. I remember after the rooting portion though he had me remove my fingerprint, my google account and my samsung account. This was back in mid December. I, yesterday after all this time finally began to re-add my accounts. I added my google account and fell asleep after a old friend stopped by and smoked me up on a spliff which I haven't touched in years. For obvious reasons, I passed out to wake up to my phone dead, so I plug it in and BOOM I have the above errors popping up above my logo. For note though, the one error "SEANDROID" was present after the IMEI change. Now, I'm just bootlooping. I did read that I can flash a different kernel or another ROM, my biggest issue is I have client's files stored on my phone along with a bunch of sexy pictures of my girlfriend
So, I ask my fellow XDAer's what steps can I take to remedy this without losing my internal storage.
A happy footnote more to those that may think I'm a wily thief or some petty criminal looking to break a code or do something illegal with the phone. I am not and in an ironic twist my friend the account holder actually got both phones off the blacklist after yet another tear into Bell. Doesn't help me now but, it does show that had I waited I wouldn't have been in this predicament or even had a reason to go onto Kijiji and find a seedy IMEI guy.
Thanks anyone for reading this entirely too long post and I appreciate any help!
More info:
Galaxy Note 5
Bell - Unlocked
Android 5.1.1 - I never updated it if that helps.

Just flash stock rom on it. It happens when someones tried to root it without turning oem unlock on
---------- Post added at 07:07 PM ---------- Previous post was at 07:06 PM ----------
It wont touch your data partition.

Related

Wifi not connecting.

As the title suggests, i'm having great difficulty connecting to any network (secure network at home which was working w/o problem and 2 other open networks).
It will show them "name - secured (wps available)" and upon putting in my password will remain "connecting" before staying "disconnected" or after it scans again turn to "saved - secured" and repeat this process.
I can manage to connect it via WPS however cannot get any access to the internet or it will repeat the process.
This happened after many trouble free days using a custom ROM. I'm not sure whether it started happening before or after i flashed a new rom, however nothing I do now seems to help. There doesn't seem to be any defaults to clear (looking through running applications and titanium backup), I've re-flashed different roms, kernels and modems with every combination of wipes and performed a 1-File factory firmware install on ODIN. I've read through towers of threads and haven't found an issue like this one but am getting frustrated in my limited knowledge of the android system.
Any advice is appreciated!
*edit*
I will also add that using my phone as a Wireless AP works fine.
Another update which may help diagnose whats going on.
After getting it to connect to wifi via WPS button I can use it however bandwith is quite low and it connects on these channels, and after increasing my distance from the router it disconnects however is still visible
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
once this happens it begins cycling through "disconnected" and "connecting" again
I wish i could interpret all this information but i've exhausted my knowledge and would love it if someone had something to share.
Have you tried resetting the modem router. When I had a s2 I had a similar kind of issue that was resolved by resetting the gateway.
My wifes motorola razr also had a similar problem and after upgrading firmware, wipes I had to factory reset the gateway to resolve the issue with that device.
I have only had it happen to me once with a samsung galaxy phone but I would give that a try
txr33 said:
Have you tried resetting the modem router. When I had a s2 I had a similar kind of issue that was resolved by resetting the gateway.
My wifes motorola razr also had a similar problem and after upgrading firmware, wipes I had to factory reset the gateway to resolve the issue with that device.
I have only had it happen to me once with a samsung galaxy phone but I would give that a try
Click to expand...
Click to collapse
I've tried unfortunately it's just peculiar to me how it will connect when close to the router but not when far (despite showing good signal), I also couldn't connect at the airport to 2 different APs either
can you get another identical phone to test with?
a non LTE sgs3 (i9300) should be good enough.
omniwolf said:
can you get another identical phone to test with?
a non LTE sgs3 (i9300) should be good enough.
Click to expand...
Click to collapse
yes, i used my father's i9300 last night before bed to update his app's on wifi.
one thing that's crossed my mind is how well i've flashed the roms. as each rom i've gone to i've had my APN's in most and saved connections in some of them. is there something that isnt getting re-written or deleted when flashing or formatting? i've formatted the mounts in CWM, performed factory resets and cleared my caches in any number of ways... is there something i'm doing wrong :\
even after flashing a stock rom i still had my mobile AP's and misc. files on internal SD
have you tried any of these two fixes that work for some people
http://www.gottabemobile.com/2012/07/11/how-to-fix-samsung-galaxy-siii-wi-fi-connection-problems/
_adamk said:
yes, i used my father's i9300 last night before bed to update his app's on wifi.
Click to expand...
Click to collapse
sorry, so are you saying it works fine with the i9300? no reception issues? is it on ICS?
one thing that's crossed my mind is how well i've flashed the roms. as each rom i've gone to i've had my APN's in most and saved connections in some of them. is there something that isnt getting re-written or deleted when flashing or formatting? i've formatted the mounts in CWM, performed factory resets and cleared my caches in any number of ways... is there something i'm doing wrong :\
even after flashing a stock rom i still had my mobile AP's and misc. files on internal SD
Click to expand...
Click to collapse
i don't understand what you're saying here. what does APNs have to do with wifi? what do you mean APN and "saved connection" (??) "IN" some of them? what does that even mean?
it doesn't sound like your wiping process is the problem here.
omniwolf said:
sorry, so are you saying it works fine with the i9300? no reception issues? is it on ICS?
i don't understand what you're saying here. what does APNs have to do with wifi? what do you mean APN and "saved connection" (??) "IN" some of them? what does that even mean?
it doesn't sound like your wiping process is the problem here.
Click to expand...
Click to collapse
yes, the i9300 works fine, no reception issues with it nor any device at home. it is on ICS. as did my previous i9300 on ICS or JB...
THIS phone (my i9305) was working fine for the past 2 weeks on L335K1s 1.1.. until flashing a few other roms
what i was saying that after performing a full wipe (and obviously clearing cache), and flashing different roms i've found that sometimes it will keep my mobile APN's as well as some still have my saved wifi connection and some don't..
by comparison, when i first got the phone on an optus firmware i had to send myself the telstra APN via their mobile setup page. when flashing the same optus firmware last night my access points were already there when on first boot as was my wifi network name "saved & secured".
txr33 said:
have you tried any of these two fixes that work for some people
http://www.gottabemobile.com/2012/07/11/how-to-fix-samsung-galaxy-siii-wi-fi-connection-problems/
Click to expand...
Click to collapse
have also tried this, no luck.
_adamk said:
As the title suggests, i'm having great difficulty connecting to any network (secure network at home which was working w/o problem and 2 other open networks).
It will show them "name - secured (wps available)" and upon putting in my password will remain "connecting" before staying "disconnected" or after it scans again turn to "saved - secured" and repeat this process.
I can manage to connect it via WPS however cannot get any access to the internet or it will repeat the process.
This happened after many trouble free days using a custom ROM. I'm not sure whether it started happening before or after i flashed a new rom, however nothing I do now seems to help. There doesn't seem to be any defaults to clear (looking through running applications and titanium backup), I've re-flashed different roms, kernels and modems with every combination of wipes and performed a 1-File factory firmware install on ODIN. I've read through towers of threads and haven't found an issue like this one but am getting frustrated in my limited knowledge of the android system.
Any advice is appreciated!
*edit*
I will also add that using my phone as a Wireless AP works fine.
Another update which may help diagnose whats going on.
After getting it to connect to wifi via WPS button I can use it however bandwith is quite low and it connects on these channels, and after increasing my distance from the router it disconnects however is still visible
once this happens it begins cycling through "disconnected" and "connecting" again
I wish i could interpret all this information but i've exhausted my knowledge and would love it if someone had something to share.
Click to expand...
Click to collapse
Im having the EXACT same issue (i9305 LTE 2gb UK on orange), HOWEVER i can confirm i've been running a stock ROM since i got it (around 2 weeks ago) so i can confirm its not just you having the issue, and it mightnt be through modding your firmware.
I get 6ft wifi range *at best*, although the range for network discovery is normal (i can see my router anywhere in the house as normal with max strength), but it only connects when within 6ft of range. Means WiFi is pretty much useless im physically sitting on/beside the router. I've tried this at my house, my mothers, friends, and at work, including wireless B, G, N and multiple brand routers (tp-link, Virgin Superhub, BT Home hub) and i can confirm nothing has worked.
Ive tried the *#0011# turning off wifi power saving to no avail. Tried turning off notification, and keep wifi on during sleep, and disabling check for internet service. nothing makes a difference.
All that happens is that it sticks on "connecting" for ages, then disconnects, occassionally saying theres no signal strangth despite there being full strength. Means unless i forget my networks its in a constant state of trying to connect which hammers the battery, and it doesnt connect when it should in the first place.
Tried doing a factory restore 3 times which has made no difference. My phone is rooted so i can use apps like titanium backup but apart from that its stock. I now need to figure out how to un-root it (to get rid of the red ! on bootup) so i can send this POS back
if you find a solution, please post it here and i will do the same. Any help or suggestions is appreciated
Livid to think we've only had the bloody thing a couple of weeks and this happens
Cheers
C
Not sure if this has been tried but what if you forget the network you are trying to connect to so the login info is erased for it and then re connect to it. I saw a similar thing on the weekend with a relatives phone after I made some changes on the router and forgetting the network and reconnecting solved his issue
Sent from my GT-I9305 using XDA Premium HD app
Not sure if this has been tried but what if you forget the network you are trying to connect to so the login info is erased for it and then re connect to it. I saw a similar thing on the weekend with a relatives phone after I made some changes on the router and forgetting the network and reconnecting solved his issue
Click to expand...
Click to collapse
I'd definately tried this and didn't have any luck
bigc90210 said:
Im having the EXACT same issue (i9305 LTE 2gb UK on orange), HOWEVER i can confirm i've been running a stock ROM since i got it (around 2 weeks ago) so i can confirm its not just you having the issue, and it mightnt be through modding your firmware.
I get 6ft wifi range *at best*, although the range for network discovery is normal (i can see my router anywhere in the house as normal with max strength), but it only connects when within 6ft of range. Means WiFi is pretty much useless im physically sitting on/beside the router. I've tried this at my house, my mothers, friends, and at work, including wireless B, G, N and multiple brand routers (tp-link, Virgin Superhub, BT Home hub) and i can confirm nothing has worked.
Ive tried the *#0011# turning off wifi power saving to no avail. Tried turning off notification, and keep wifi on during sleep, and disabling check for internet service. nothing makes a difference.
All that happens is that it sticks on "connecting" for ages, then disconnects, occassionally saying theres no signal strangth despite there being full strength. Means unless i forget my networks its in a constant state of trying to connect which hammers the battery, and it doesnt connect when it should in the first place.
Tried doing a factory restore 3 times which has made no difference. My phone is rooted so i can use apps like titanium backup but apart from that its stock. I now need to figure out how to un-root it (to get rid of the red ! on bootup) so i can send this POS back
if you find a solution, please post it here and i will do the same. Any help or suggestions is appreciated
Livid to think we've only had the bloody thing a couple of weeks and this happens
Cheers
C
Click to expand...
Click to collapse
What a relief that i'm not the only one, that is exactly what was happening to mine. (All I know is mine is an early model i9305, perhaps different to a majority of the i9305T's sold here, perhaps earlier hardware?)
After testing all I could, trouble-shooting with samsung through some pretty basic stuff, and performing hard and soft resets between flashing roms, I decided to send it off for repair, suspecting a hardware fault.
My advice to you, would be to get it exchanged immediately as if it is under a month old, it will fall under "Early Life Failure" (ELF). Whilst the issue doesnt completely render the phone useless, it was a fully functioning part of the phone that stopped working out of nowhere!
To un-root download Triangle away from here:
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-galaxy-s3-i9300/
And download your stock firmware.
Triangle away appears to require a custom kernel to reset to 0 on this phone.
When you are ready to send it away, install a custom kernel, then install the Triangle Away app.
Run this, and then turn off your phone (do not restart or go into recovery as this will reset the counter again).
Now boot straight into download mode (or the binary counter will go up), and flash your stock firmware through ODIN.
It should now be a completely stock i9305, and after performing a hard reset (with *2767*3855# in the dialer), you should now have a clean phone to send away. :good:
I'll let you know the outcome of the warranty claim and what Samsung say.
Alright chap, update time. Let me break down your post so i can answer it bit by bit.
I ran triangle away, it got rid of the red "!" showing on the top left of my phone boot screen, cheers for that!
I next grabbed the latest firmware which is I9305XXALI5_I9305EVRALI5_EVR.zip from sammobile
flashed that with mobileODIN, now back on stock firmware which I already was on, and no red "!". however when i go to settings->about device and software update, it says "there are no updates available as your device has been modified" and when you go to Settings->about device->Status, then scroll to the bottom, device status shows as "Modified". I'm gonna need to get this back to "Normal" before i send it back.
Anyways, regarding my ****uation with orange. *******************************
My contract was upgraded renewed on the 9th, I got my S3 LTE on Monday 12th (of November). On Friday the 23rd I discovered something had happened with the WiFi, and it was completely borked for no apparent reason and is now since then reduced to its 6ft range distance. spent all of Friday night and Saturday morning trying to figure it out, including rooting on Friday night to see if that helped, to no avail.
Note: between getting the phone and rooting it (AFTER i got this issue), the phone was completely stock. Now i know how stupid it was to root after discovering the issue, but sod it I've done it now, so imma have to undo it. ANYWAYS....
Saturday (the 24th) afternoon, I went to an EE / Orange retail store, where all of the employee's in the store had a try to figure out the issue, with no success. They tell me to contact Orange via the telephone for a replacement (as apparently because I ordered my handset via the telephone, i had to contact them for a replacement).
I contact Orange on the phone on Wed the 28th (by now its passed the 14 days cooling off by a couple of days) and I get through to an absolute idiot who fills the foreign call center staff stereotype perfectly.
He gets my name, phone number and handset wrong several times EACH during the call, and tells me all i'm eligible for is my phone repaired. When I tell him i'm not happy, he changes his mind and says he will "make a call" and get a new handset sent out to me, and even asked me when the following day (today) i would like to take delivery of my new phone. This call takes approx 50 minutes, 20 mins of which was waiting for someone to answer, then 10 of the remaining 30 of the actual "call" was spent on hold.
He then calls me back to tell me my iPhone has been ordered and i should have it tomorrow (today). When i pointed out i don't want an iPhone, and my phones an S3 LTE (for about the 10th time) he says "the phone line for getting a new phone has just closed at 9pm" (it was then a couple of minutes past 9) and he gave ME a number to call since HE made a f*** up of the order.
Wake up today, go to work. On my lunch break call the number, which turns out to be the insurance hotline (Orange care) The lady on the phone reads my notes and is confused, according to what the guy last night had wrote down, My phone was a Galaxy note 2, later in the story it became an S3, and then he put in a claim for me having a broken iPhone.
I re-explain everything to her, and she was very sympathetic. She told me it wasn't an insurance issue, but a fault, and I needed to speak to someone from faults. I asked her to find me a English speaking person, of which she agreed. She came back twice after putting me on hold to say she'd found someone to speak to , but they could barely speak English. On the third attempt, she found someone who "can just about speak English, I've explained everything to her, so you should be OK".
After a 5 minute wait I get put through
I get put through to a lady who is speaking in broken English sentences. She first puts me on hold while she reads my notes (insert 10 minute hold time). She says all that can be done is for it to be sent away to be repaired. I say I want a new phone, as it was within 14 days of getting the phone, and I don't want to mess about with waiting to get my phone back, I just want a new one. She says "all that's popping up on my screen is repair". I said I'd go into the Orange store and take it up with someone in person.
/end of ****uation *********************
il update you on this once i get to the Orange store, which won't be until tomorrow.
in the meantime, any ideas on how to change it so settings->About Device->Device Status back to "Normal" and not "modified"?
bigc90210 said:
Alright chap, update time. Let me break down your post so i can answer it bit by bit.
I ran triangle away, it got rid of the red "!" showing on the top left of my phone boot screen, cheers for that!
I next grabbed the latest firmware which is I9305XXALI5_I9305EVRALI5_EVR.zip from sammobile
flashed that with mobileODIN, now back on stock firmware which I already was on, and no red "!". however when i go to settings->about device and software update, it says "there are no updates available as your device has been modified" and when you go to Settings->about device->Status, then scroll to the bottom, device status shows as "Modified". I'm gonna need to get this back to "Normal" before i send it back.
Anyways, regarding my ****uation with orange. *******************************
My contract was upgraded renewed on the 9th, I got my S3 LTE on Monday 12th (of November). On Friday the 23rd I discovered something had happened with the WiFi, and it was completely borked for no apparent reason and is now since then reduced to its 6ft range distance. spent all of Friday night and Saturday morning trying to figure it out, including rooting on Friday night to see if that helped, to no avail.
Note: between getting the phone and rooting it (AFTER i got this issue), the phone was completely stock. Now i know how stupid it was to root after discovering the issue, but sod it I've done it now, so imma have to undo it. ANYWAYS....
Saturday (the 24th) afternoon, I went to an EE / Orange retail store, where all of the employee's in the store had a try to figure out the issue, with no success. They tell me to contact Orange via the telephone for a replacement (as apparently because I ordered my handset via the telephone, i had to contact them for a replacement).
I contact Orange on the phone on Wed the 28th (by now its passed the 14 days cooling off by a couple of days) and I get through to an absolute idiot who fills the foreign call center staff stereotype perfectly.
He gets my name, phone number and handset wrong several times EACH during the call, and tells me all i'm eligible for is my phone repaired. When I tell him i'm not happy, he changes his mind and says he will "make a call" and get a new handset sent out to me, and even asked me when the following day (today) i would like to take delivery of my new phone. This call takes approx 50 minutes, 20 mins of which was waiting for someone to answer, then 10 of the remaining 30 of the actual "call" was spent on hold.
He then calls me back to tell me my iPhone has been ordered and i should have it tomorrow (today). When i pointed out i don't want an iPhone, and my phones an S3 LTE (for about the 10th time) he says "the phone line for getting a new phone has just closed at 9pm" (it was then a couple of minutes past 9) and he gave ME a number to call since HE made a f*** up of the order.
Wake up today, go to work. On my lunch break call the number, which turns out to be the insurance hotline (Orange care) The lady on the phone reads my notes and is confused, according to what the guy last night had wrote down, My phone was a Galaxy note 2, later in the story it became an S3, and then he put in a claim for me having a broken iPhone.
I re-explain everything to her, and she was very sympathetic. She told me it wasn't an insurance issue, but a fault, and I needed to speak to someone from faults. I asked her to find me a English speaking person, of which she agreed. She came back twice after putting me on hold to say she'd found someone to speak to , but they could barely speak English. On the third attempt, she found someone who "can just about speak English, I've explained everything to her, so you should be OK".
After a 5 minute wait I get put through
I get put through to a lady who is speaking in broken English sentences. She first puts me on hold while she reads my notes (insert 10 minute hold time). She says all that can be done is for it to be sent away to be repaired. I say I want a new phone, as it was within 14 days of getting the phone, and I don't want to mess about with waiting to get my phone back, I just want a new one. She says "all that's popping up on my screen is repair". I said I'd go into the Orange store and take it up with someone in person.
/end of ****uation *********************
il update you on this once i get to the Orange store, which won't be until tomorrow.
in the meantime, any ideas on how to change it so settings->About Device->Device Status back to "Normal" and not "modified"?
Click to expand...
Click to collapse
Sounds like you were having just as much a PITA situation as me. It surprised my friend the other day that I had to send my phone away for repair (being an iPhone user...) and surprises me too for such a premium handset. I wish more companies took a page out of apples' book on this one. I generally try and be as patient as I can with these people and show them that i have done a lot of troubleshooting myself to save time. Often it will result in being transferred to the correct person to talk to a lot quicker.
Ok I should've made it a little clearer, I found that the phone would only be unrooted if I flashed a rooted firmware with custom kernel, and after running triangle away flashing the firmware ON A PC. This is what I meant by going straight into download mode (something about the way mobile Odin installs the firmware still causes the custom binary to appear)
Samsung have however repaired my phone (according to their online job tracker) and my phone is being sent back to me! (After almost 10 days.. probably 14 before I get it back!!!!!!). I will try find out what was wrong although I'm not sure how much Samsung will tell me. I am glad that the unrooting procedure worked without trace and my warranty was honored!
Another update: used desktop Odin to flash my phone back to stock rom after previously using triangle away. Still showing as modified in Settings->About Device->Status.
gonna go into the Orange/EE store tomorrow and complain (when i say complain, i mean about the dodgy wifi issues, not complain about it showing as modified XD). Any suggestions about how to get the modified status back to normal is most appreciated.
Did you flash from stock rooted rom? I had the same issue doing that. It was fine flashing from a rooted rom with a customer kernel
yeah i did, so that could be why. im pretty new to android (been an iOS guy for the last 4 years) so still trying to figure stuff out. doesnt really help that theres not much info out there for the i9305.
What custom kernal/firmware should i use from here? im guessing you mean to flash the rom again but to a completely modded firmware of some type, then back again to the stock one yeah? I've read something about backing up your imei and elf/efi data incase stuff goes wrong but ii havent done this yet, should i do that first?
Another Update:
Went into the Orange/EE store. was messed about by a member of staff who told me i had to go home and phone orange, then arrange repair via them. Left the store pissed off and went to Burger King. Went back to the store as by this point i'd wound myself up into a frenzy about the whole situation, Demanded to see the manager, demanded HE phone orange for me there and then, and sort this sh** out.
he got a regular call centre guy who said "all the computer is saying as a solution is repair, so thats it" so i demanded we got his boss on the line.
His boss comes on and says its out of his hands and he cant do anything about it, i told him "in that case you're no use, put someone who can" i demanded the orange store manager ask the call centre manager for his boss. He also tried being a smart arse saying it was out of the 14 day return period when i called orange to say i wanted it replaced. I pointed out it was INSIDE the 14 day period i first reported it as an issue to the orange store, and it was tough sh** that they hadnt acted to fix it then.
10 mins of hold later, guy next up the chain comes on, and says hes the person who over-rides the system for returns in odd cases like this, but says he cant override it without HIS bosses permission (you see where im going with this)....
10 minutes of hold later we get HIS boss on the line, who agrees to authorise the replacement.
we get passed back down the chain all the way to the beginning person, who arranges for a new phone to be delivered to my house between 9am - 1pm tomorrow via a courier (on a sunday).
Win.
I get home, my phones been flashed back to stock rom, but is still showing modifed as mentioned before. I do another factory reset on it (i already done one before) and its now showing as "normal", so maybe the un-rooting proceedure takes 2 factory resets? as i already done 1 earlier but it was still showing as modified? Either way, thats that done. My phone is now ready to be sent back to orange tomorrow, fully un-modded as it came, and im due a replacement as I wanted.
Finally Happy, but it wasn't easy.
Just hope my next S3 LTE doesn't suffer from the same issue, as there literally seemed to be nothing that would fix it.
Hope that helps anyone who has this problem with theirs.
C
Reset
SGS+ Tapatalk MCMV
How's this for a joke....
I recieved my phone back yesterday! (Yay?) I read my service report and find that the handset has had the latest firmware installed (the same one I had on it) and it has been tested to Samsung's Quality Control standards. Great?
I turn it on and within 10 seconds of starting it up (getting to the "connect to wifi" screen), I have the exact same issue and phone I sent off 2 weeks ago! They didn't "repair" anything, and now i'm being pushed around to other departments because apparently no one can deal with it directly. I'm now awaiting a reply (in 5-7 Business days) as to what the next step is in this saga, it's just so frustrating that someone didn't even properly test the phone after "repairing" it.
Sure enough my new phone arrived on sunday, the guy only took away the broken phone and charger, so i scored for a free pair of headphones and the box etc heheh.
I would bet my life samsung have got your phone and went "hmmm.... wifi signal shows as full strength", then tried to connect it to a router/tethering phone that theyre sitting next to/holding in their other hand, then said "well it connects, so it works" then sent it back, without even trying it at any sort of distance. I nearly flipped my lid in the Orange/EE store when they tried to tell me "the wifi is working as its working here" so i made the girl leave the note2 she was tethering from on the counter and take 3 steps away from the counter with my phone in her hand (at which point the wifi dropped). Its like you have to demonstrate to them what the issue is.
Also, this is something completely different, but i thought i should bring this up.
Hold your phone in 1 hand by its sides, then flick the centre of the screen with the other hand. Does it feel like its vibrating inside? almost like theres springs inside? Im just asking because the phone that broken was VERY "springy" inside, almost to the point of where you could hear the vibrations inside seconds after flicking it and it felt a bit like it was rattling, whereas the replacement lte (despite being an identical handset) has much less spring to it and feels a lot more solid in comparison, it only vibrates slightly inside when flicked. Tried with my mates regular S3 i9300 which has no spring to it at all, and feels much more solid, wonder if it just with the LTE's. Seems strange to try the same thing on 2 brand new phones and them to have a completely different feel to them though

[Q] Tmobile Note 4 randomly restarting

Hello all,
Firstly, I hope this is the right place to put this thread. I did a search and did not find anyone else having this issue so I decided to put my post here. I am having a problem with my note 4 randomly restarting a few times every hour. It goes through its shutdown procedure and turns right back on. Occasionally it will shutdown and stay off. It seems to be software related, but I'm no expert on these things. I did however download 'Device Temperature' from the play store to check to see if it might be overheating. As far as I can tell it has stayed a cool 24-25 degrees Celsius (77 Fahrenheit) the entire time.
It does this at unpredictable times, whether or not the phone is in my pocket, in my hands, or laying flat on a desk with or without the charger plugged in.
I don't think I can take it back to Tmobile to have it replaced as I bought it from a friend a few weeks ago to use on cricket. This just started 2 days ago.
The device is SIM unlocked, but not rooted with stock everything. It's still in mint condition and to my knowledge has never been dropped.
Can anyone help?
More Information
I did a Google search for "Galaxy Note 4 Random Reboot" and I found some information saying to reformat my SD card or try doing a factory reset on the phone.
I tried both (I actually removed the SD card completely instead of just reformating it), and about a half hour later... boom restart again. FML.
Once again I turn to the wonderful folks at XDA for help. Thanks to all in advance.
Sounds like it could be bad eMMC flash memory. Go with your friend and have Tmobile replace it. Also get Square Trade insurance if you can.
Got it fixed
I called Samsung about the issue and after some brief troubleshooting they recommended having it reflashed at a samsung experience center. The closest one to me was in a Best Buy. I dropped it off, after explaining what was happening, and an hour later it was ready to be picked working good as new. I haven't noticed it restart even once since.
Samsung offered to replace the entire unit but it would cost me $28 for 2 day shipping (assuming that they had my model in stock). I will go that route if the issue returns. I'm hoping not to go this route because I already paid for this phone to be unlocked once - I'd rather not pay again if I don't have to.
I'll keep you guys updated if the rebooting issue returns again.
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
railshot said:
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
Click to expand...
Click to collapse
This. I kept having this issue with my Note 3 and could not figure it out. Eventually I just took out the battery, cleaned the contacts, put it back in, and it never had a random reboot after that.
Are you guys running any custom roms, or is it still stock?

Nexus 6 Speakers Lower on their Own

So I have read about this issue a couple of other times on here, where the device is playing music and it randomly lowers the volume and it may/not come back up to full volume. Well this is happening to me. I can't make it reproduce, but if I throw on some Spotify for a little bit or YouTube I notice it randomly. For me, if I keep hitting the volume up, 5-10 times, the volume comes back up. It's important to note the volume indicator in Android never says it lowered, it says its full. But after hitting the volume up numerous times, it'll come back up. It's also worth noting I don't have any notifications coming through at these times, and my screen has been on so the notification screen that pops up wouldn't be lowering it.
I have done multiple factory resets, flashed to M, to L, flashed different ROMs / Kernels etc, but I always stick to stock. I only flashed those to see if I could get it to go away.
I went to the Sprint store and the tech said he needed to see the issue for him to replace it free of charge. I have insurance, so I should be able to get a free replacement IF its a device fault and not my own. If it were my own I'd have to pay. So here's where the issue comes in. I took it in the first time, and he hooks it up the the Cellebrite machine to see if he can see a fault in the device through that, and it says its rooted (which it was w/ bootloader unlocked). He is cool about it, telling me he is supposed to flag my phone so I can't have it replaced free of charge, but he isn't going to. He said if I come back and it isn't rooted he'd try again. I flash the newest Android M dev preview from factory images (no root) and bring it back in. He hooks it up, and it shows up as an N7 to the Cellebrite MAchine / diag app. He manually selected N6 but it still says its rooted so he can't do anything.
Before I moved I would go to Sprint all the time if I had a device fault (different devices) and that particular store said Sprint didn't care if it was rooted, it didn't matter as per Sprint employee guidlines. But now it seems it does? Neither of these stores (before I moved and now) are corporate stores either. But I know my local corporate store used Cellebrite too.
So I have a couple questions here:
1) Would my bootloader being unlocked really throw the "rooted" flash to the Cellebrite diag app? It had TWRP but was definitely NOT rooted the second visit.
2) I've read that relocking bootloader on 5.1.1 can be a little risky, is this true?
3) And he mentioned that he knew of the issue but since it was "rooted" he couldn't get me a replacement, but that I could try to get customer service phone support to send me one. He said I would need a reason I couldn't bring it in the Sprint store, though.
I didn't buy it through the Play Store so Google said they won't replace it (even though its within the year warranty) but to get Motorola to replace it. The problem there is almost the same as insurance. With insurance, I just pay a $200 deductible and get a new N6. With Motorola, they have to put a hold on my card for like $580, then they will refund all of it but the $25 fee for them sending me the phone first and then me sending it back. (Alternative is me sending my phone in first, but I can't since I don't have an alt phone).
Anyone know a direction I could go?
P.S. Sorry for the wall of text, but its just been a long drawn out process.
DRatJr said:
So I have read about this issue a couple of other times on here, where the device is playing music and it randomly lowers the volume and it may/not come back up to full volume. Well this is happening to me. I can't make it reproduce, but if I throw on some Spotify for a little bit or YouTube I notice it randomly. For me, if I keep hitting the volume up, 5-10 times, the volume comes back up. It's important to note the volume indicator in Android never says it lowered, it says its full. But after hitting the volume up numerous times, it'll come back up. It's also worth noting I don't have any notifications coming through at these times, and my screen has been on so the notification screen that pops up wouldn't be lowering it.
I have done multiple factory resets, flashed to M, to L, flashed different ROMs / Kernels etc, but I always stick to stock. I only flashed those to see if I could get it to go away.
I went to the Sprint store and the tech said he needed to see the issue for him to replace it free of charge. I have insurance, so I should be able to get a free replacement IF its a device fault and not my own. If it were my own I'd have to pay. So here's where the issue comes in. I took it in the first time, and he hooks it up the the Cellebrite machine to see if he can see a fault in the device through that, and it says its rooted (which it was w/ bootloader unlocked). He is cool about it, telling me he is supposed to flag my phone so I can't have it replaced free of charge, but he isn't going to. He said if I come back and it isn't rooted he'd try again. I flash the newest Android M dev preview from factory images (no root) and bring it back in. He hooks it up, and it shows up as an N7 to the Cellebrite MAchine / diag app. He manually selected N6 but it still says its rooted so he can't do anything.
Before I moved I would go to Sprint all the time if I had a device fault (different devices) and that particular store said Sprint didn't care if it was rooted, it didn't matter as per Sprint employee guidlines. But now it seems it does? Neither of these stores (before I moved and now) are corporate stores either. But I know my local corporate store used Cellebrite too.
So I have a couple questions here:
1) Would my bootloader being unlocked really throw the "rooted" flash to the Cellebrite diag app? It had TWRP but was definitely NOT rooted the second visit.
2) I've read that relocking bootloader on 5.1.1 can be a little risky, is this true?
3) And he mentioned that he knew of the issue but since it was "rooted" he couldn't get me a replacement, but that I could try to get customer service phone support to send me one. He said I would need a reason I couldn't bring it in the Sprint store, though.
I didn't buy it through the Play Store so Google said they won't replace it (even though its within the year warranty) but to get Motorola to replace it. The problem there is almost the same as insurance. With insurance, I just pay a $200 deductible and get a new N6. With Motorola, they have to put a hold on my card for like $580, then they will refund all of it but the $25 fee for them sending me the phone first and then me sending it back. (Alternative is me sending my phone in first, but I can't since I don't have an alt phone).
Anyone know a direction I could go?
P.S. Sorry for the wall of text, but its just been a long drawn out process.
Click to expand...
Click to collapse
Known issue. Please see this thread:
http://forum.xda-developers.com/showthread.php?t=3136759
---------- Post added at 08:33 AM ---------- Previous post was at 08:30 AM ----------
For relocking the bootloader:
http://forum.xda-developers.com/showthread.php?t=3067302
---------- Post added at 08:35 AM ---------- Previous post was at 08:33 AM ----------
Also, if you're going to RMA, just flash a factory image first, relock, and you're all set.
@danarama
i don't think an RMA will help.
danarama said:
i don't think an RMA will help.
Click to expand...
Click to collapse
So all nexus 6 have this issue? Getting a new device would still have it too?
DRatJr said:
So all nexus 6 have this issue? Getting a new device would still have it too?
Click to expand...
Click to collapse
Did you read the link?

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!

(fixed before I even finished typing post) G900A Stuck on AT&T Logo, please help

As I was typing this large portion of text below, my phone kinda just came back to life on its own.....that was really ****ing weird. Thank you all for being here for newbies, I searched for help and my phone kinda did it's own thing. first post fail. lol
"I had broken my S6 a few days ago and the screen is completely blank and no touch. Sad story because that was my 3rd one, I have had two replacements due to the battery and it being a crap phone.
Anyways, to the man subject, I had a S5 laying around that I accidentally dropped while I was factory restoring it and the battery came out. I fixed THAT boot loop two days ago and yesterday I somehow managed to do something that caused it to get stuck on the AT&T screen, again. I am a noob but I have tried several thing such as trying to update from SD, tried ODIN as suggested, but it won't detect my device whatsoever. I do not understand how this all is so confusing and nobody can seem to make one golden post to explain it all to people simply. "

Categories

Resources