Related
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.
Good luck on either with the warranty or bringing it back to life.
I also have problems such as your support Huawei says four weeks of waiting
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.
So I have a Samsung Galaxy S7 Edge, or rather my friend does but he brought it to me for some work. That being said he has about 20 different Gmail accounts with about 20 different passwords and he doesn't know which one belongs to which and I factory reset the phone part of discovering which one was the master account. In any case I try to use Chimera to do an FRP unlock but unfortunately because it is on Android 7.0 it did not let me do this. I also try to roll it back to 6.0 or 6.1 rather butt same.
I read a few different online guides and one of them was on how to do the network unlock by doing a bypass of the Wi-Fi to get around the initial settings and then from there you open up the terms and policies with the long press and allows you to open up the app manager in you go to settings there. The problem is is that unfortunately that seems be disabled on some security update to happen for 6.1 on one of the OTAs at some point in time
I saw there were few different tools out there but the one that I was able to read the guide on seem to not work at all because when I hit the button the response I got was green but the diamond ever popped up if that makes any sense. In any case it's 2017 about halfway through the year and it seems that every FRP unlock has changed modestly since 2015 near the end of the year.
Is there a current method on how to refresh that are peel off whether it is the change out Sims 2 loaded if in firmware to do something. But the phone is not even to root it yet but I intend to do so after we get into the phone directly. Please provide any assistance if you have it.
Thus, uh... Really sounds like your "friend" stole this phone ?
No. If we provide you any solutions even if what you said is true, other people with stolen phones can bypass the very measure that Samsung incorporated to disable stolen phones. If it is truly your 'friend's device, tell him ANY Google account he used with the phone will get rid of the frp lock. It doesn't have to be a specific one.
williamschromebook said:
So I have a Samsung Galaxy S7 Edge, or rather my friend does but he brought it to me for some work. That being said he has about 20 different Gmail accounts with about 20 different passwords and he doesn't know which one belongs to which and I factory reset the phone part of discovering which one was the master account. In any case I try to use Chimera to do an FRP unlock but unfortunately because it is on Android 7.0 it did not let me do this. I also try to roll it back to 6.0 or 6.1 rather butt same.
I read a few different online guides and one of them was on how to do the network unlock by doing a bypass of the Wi-Fi to get around the initial settings and then from there you open up the terms and policies with the long press and allows you to open up the app manager in you go to settings there. The problem is is that unfortunately that seems be disabled on some security update to happen for 6.1 on one of the OTAs at some point in time
I saw there were few different tools out there but the one that I was able to read the guide on seem to not work at all because when I hit the button the response I got was green but the diamond ever popped up if that makes any sense. In any case it's 2017 about halfway through the year and it seems that every FRP unlock has changed modestly since 2015 near the end of the year.
Is there a current method on how to refresh that are peel off whether it is the change out Sims 2 loaded if in firmware to do something. But the phone is not even to root it yet but I intend to do so after we get into the phone directly. Please provide any assistance if you have it.
Click to expand...
Click to collapse
If you're still in need of help see this post >>>> https://forum.xda-developers.com/tmobile-g6/how-to/frp-unlock-lg-g6-using-headphone-jack-t3616166
It's aimed at LG users but it may help. There's also a guide linked within post for samsung folks.
If it helps send a thanks.
I used realterm, but ill keep that post bookmarked Thanks
Sent from my HTC 0PJA2 using XDA Labs
My buddy gave me his phone to try to fix the same issue.
It is his 71 year old mother's phone and she can't remember her email address much less her password. I have tried everything I can think of to no avail.
Sent from my SM-G935U using XDA Premium HD app
Try blowfish unlocks in Google.
Sent from my SM-G935T using Tapatalk
Eric1084 said:
No. If we provide you any solutions even if what you said is true, other people with stolen phones can bypass the very measure that Samsung incorporated to disable stolen phones. If it is truly your 'friend's device, tell him ANY Google account he used with the phone will get rid of the frp lock. It doesn't have to be a specific one.
Click to expand...
Click to collapse
Not true at all.
It has to be the account that was logged into at the time of the reset. You can easily link your Google account to the phone and it still won't allow you to use your account to open it back up.
Not a troll either but in about same place this guy is just mine is legit
So basically this is what has got me messing around with flashing and trying to mess with the firmware also different settings on the android system. However so like the previous user which actually does sound like his "friend " did steal it. This one is a S7 I actually purchased in la. It is not a nightmare of a drive but for $200 it almost is. Im almost about to sell the phone on ebay. I immediately after purchase spoke with t-mobile and was told phone was good just it was sim locked. I would need to sign up with there service. The phone was supposedly frp free and sim unlocked for any carrier in the americas and europe. Very far from the case. I put my personal sim card in for att get the same network id message or the puk when i enter it wrong have tried even new att sim cards. Att is offering me the same deal but said to prepay for 90 days. I am not sure how this makes sense since how is unlocking the sim also going to unlock the google account from previous owner??? I keep trying different methods with odin and smart synch. Any other random apps basically and best I do is make a paper weight or can get to my imei on a legit dial pad however I try to go to even change to imei from previous phone which is still active just broken screen but still have the same issue. I am thinking at this point mabye t mobile and att are the hassle here and half the videos have helped me about 10% from youtube and different docs. I have been going on trial and error for about 2 weeks now. Called t mobile back last night same story just due to all the the theft but she again checked my imei on the device and said it was all good still to get back to them when ready to commit to service. yeah.... right. But Im trying to avoid just throwing the thing the next time I brick it or sell it on ebay. I am doing everything correctly and all is legit. Even trying to transfer my other phones info if needed. Obviously it is still sim locked and has frp through google. Please help any ideas. I am about to probably throw it before I ever get the chance to sell it is that frustrating. One thing I cannot get to work correctly is rooting. I even went loaded apps on sd card went into apply updates or data from sd card and reads folders but not the program im trying to use for rooting. I have done multiple times on many devices. I dont know if t mobile is just like jumping through hoops or am i just skipping some small detail somewhere in the process. IDK HELP PLEASE ANY FEEDBACK IS APPRECIATED. I AM USING THE NOUGHAT FIRMWARE, I TRIED ON MARSHMELLOW AND EVERYTHING GOES THROUGH THEN AT END GETS CAUGHT UP WHEN I GO BACK TO UPDATE BACK TO CURRENT FIRMWARE.
sapi3nt said:
So basically this is what has got me messing around with flashing and trying to mess with the firmware also different settings on the android system. However so like the previous user which actually does sound like his "friend " did steal it. This one is a S7 I actually purchased in la. It is not a nightmare of a drive but for $200 it almost is. Im almost about to sell the phone on ebay. I immediately after purchase spoke with t-mobile and was told phone was good just it was sim locked. I would need to sign up with there service. The phone was supposedly frp free and sim unlocked for any carrier in the americas and europe. Very far from the case. I put my personal sim card in for att get the same network id message or the puk when i enter it wrong have tried even new att sim cards. Att is offering me the same deal but said to prepay for 90 days. I am not sure how this makes sense since how is unlocking the sim also going to unlock the google account from previous owner??? I keep trying different methods with odin and smart synch. Any other random apps basically and best I do is make a paper weight or can get to my imei on a legit dial pad however I try to go to even change to imei from previous phone which is still active just broken screen but still have the same issue. I am thinking at this point mabye t mobile and att are the hassle here and half the videos have helped me about 10% from youtube and different docs. I have been going on trial and error for about 2 weeks now. Called t mobile back last night same story just due to all the the theft but she again checked my imei on the device and said it was all good still to get back to them when ready to commit to service. yeah.... right. But Im trying to avoid just throwing the thing the next time I brick it or sell it on ebay. I am doing everything correctly and all is legit. Even trying to transfer my other phones info if needed. Obviously it is still sim locked and has frp through google. Please help any ideas. I am about to probably throw it before I ever get the chance to sell it is that frustrating. One thing I cannot get to work correctly is rooting. I even went loaded apps on sd card went into apply updates or data from sd card and reads folders but not the program im trying to use for rooting. I have done multiple times on many devices. I dont know if t mobile is just like jumping through hoops or am i just skipping some small detail somewhere in the process. IDK HELP PLEASE ANY FEEDBACK IS APPRECIATED. I AM USING THE NOUGHAT FIRMWARE, I TRIED ON MARSHMELLOW AND EVERYTHING GOES THROUGH THEN AT END GETS CAUGHT UP WHEN I GO BACK TO UPDATE BACK TO CURRENT FIRMWARE.
Click to expand...
Click to collapse
Nothing I read stated that you have, or even know, what an FRP Locked device [is]. I'll skip badgering you with pointless questions & just jump straight to giving you solutions:
1) Flash & boot into TWRP Recovery > Wipe the IntrnlStrg/Cache/Dalvik/System (system is key > Flash stock firmware
2) Find my Galaxy S7 & S7e FRP Bypass post here on XDA (for advanced users)
3) Do more research
I'm not trying to sound like an asshole so I apologize if I come off strong - I'm [almost literally] sick of reading all these f*cking crybabieson XDA, or other sites, begging for somebody to solve their problem instead of doing their own research & trial error runs. I have successfully bypassed FRP on 30+ different devices from different carriers with different security patch updates on Lollipop-Nougat OS by using various different methods that are(n't) common (S7 included)
Bypassing FRP is Elementary school difficult. This sh¡t is checkers, not chess. My spiel is done with
Good luck.
I think I ended up with this guy's phone from Craigslist...
☆KØŁØЯΛĐØ☆ said:
Nothing I read stated that you have, or even know, what an FRP Locked device [is]. I'll skip badgering you with pointless questions & just jump straight to giving you solutions:
1) Flash & boot into TWRP Recovery > Wipe the IntrnlStrg/Cache/Dalvik/System (system is key > Flash stock firmware
2) Find my Galaxy S7 & S7e FRP Bypass post here on XDA (for advanced users)
3) Do more research
I'm not trying to sound like an asshole so I apologize if I come off strong - I'm [almost literally] sick of reading all these f*cking crybabieson XDA, or other sites, begging for somebody to solve their problem instead of doing their own research & trial error runs. I have successfully bypassed FRP on 30+ different devices from different carriers with different security patch updates on Lollipop-Nougat OS by using various different methods that are(n't) common (S7 included)
Bypassing FRP is Elementary school difficult. This sh¡t is checkers, not chess. My spiel is done with
Good luck.
Click to expand...
Click to collapse
I have a similar model that I got off of Craiglist:
- Samsung SM-G900T
- completely up to date
- freshly re-imaged and FRP locked
- no soft FRP bypass works (probably updated to the absolute most current version of Android)
- not detected by Odin/Octopus (appears USB connectivity is disabled - it won't even show up when plugged in, anywhere).
- doesn't appear that USB debugging was enabled before the reset
- ADB and download mode just sit on "downloading/looking for filename" - I assume both options are being blocked from the USB connection, so there's no activity on the PC/Odin/tools when I use these options
The only activity when plugging in is that on the phone it goes 'blip blip' and has a little graphic over the USB port.
I liked your suggestion of do more research but this is stumping me, mostly because the USB appears to have 0 life other than to charge the phone.
Only thing I have not tried it OTG cable apk but I'm not hopeful. Friend is giving me a cable when I see him in a few days.
U-TK said:
I have a similar model that I got off of Craiglist:
- Samsung SM-G900T
- completely up to date
- freshly re-imaged and FRP locked
- no soft FRP bypass works (probably updated to the absolute most current version of Android)
- not detected by Odin/Octopus (appears USB connectivity is disabled - it won't even show up when plugged in, anywhere).
- doesn't appear that USB debugging was enabled before the reset
- ADB and download mode just sit on "downloading/looking for filename" - I assume both options are being blocked from the USB connection, so there's no activity on the PC/Odin/tools when I use these options
The only activity when plugging in is that on the phone it goes 'blip blip' and has a little graphic over the USB port.
I liked your suggestion of do more research but this is stumping me, mostly because the USB appears to have 0 life other than to charge the phone.
Only thing I have not tried it OTG cable apk but I'm not hopeful. Friend is giving me a cable when I see him in a few days.
Click to expand...
Click to collapse
• A new cable would be ideal
• Try different versions of Odin
• Reinstall Device divers
What OS version is installed & are you able to boot completely?
☆KØŁØЯΛĐØ☆ said:
• A new cable would be ideal
• Try different versions of Odin
• Reinstall Device divers
What OS version is installed & are you able to boot completely?
Click to expand...
Click to collapse
Open to anything! A different came (not new) doesn't do anything when I plug it in. The cable that came with it charges it and is detected by phone, but not by PC.
I'll go buy a new cable and see it it does anything. Meanwhile I'll try all the previous versions of Odin. I also suspect the most recent version might not be doing the trick for some reason (having rooted and flashed about a dozen phones on prior versions).
It completely boots either Oreo 8.0 or 8.1 to the Welcome setup wizard every time. None of the soft tricks get me any further than the FRP.
Want me to post a picture or anything? Download bootloader or FRP screen? I've also ordered an OTG cable to try out the apk work around.
edit: also tried jodin on a mac mini and odin on a different laptop. I have an older laptop I may try too.
U-TK said:
I have a similar model that I got off of Craiglist:
- Samsung SM-G900T
- completely up to date
- freshly re-imaged and FRP locked
- no soft FRP bypass works (probably updated to the absolute most current version of Android)
- not detected by Odin/Octopus (appears USB connectivity is disabled - it won't even show up when plugged in, anywhere).
- doesn't appear that USB debugging was enabled before the reset
- ADB and download mode just sit on "downloading/looking for filename" - I assume both options are being blocked from the USB connection, so there's no activity on the PC/Odin/tools when I use these options
The only activity when plugging in is that on the phone it goes 'blip blip' and has a little graphic over the USB port.
I liked your suggestion of do more research but this is stumping me, mostly because the USB appears to have 0 life other than to charge the phone.
Only thing I have not tried it OTG cable apk but I'm not hopeful. Friend is giving me a cable when I see him in a few days.
Click to expand...
Click to collapse
U-TK said:
Open to anything! A different came (not new) doesn't do anything when I plug it in. The cable that came with it charges it and is detected by phone, but not by PC.
I'll go buy a new cable and see it it does anything. Meanwhile I'll try all the previous versions of Odin. I also suspect the most recent version might not be doing the trick for some reason (having rooted and flashed about a dozen phones on prior versions).
It completely boots either Oreo 8.0 or 8.1 to the Welcome setup wizard every time. None of the soft tricks get me any further than the FRP.
Want me to post a picture or anything? Download bootloader or FRP screen? I've also ordered an OTG cable to try out the apk work around.
edit: also tried jodin on a mac mini and odin on a different laptop. I have an older laptop I may try too.
Click to expand...
Click to collapse
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
T-Mobile S7 Galaxy - all drivers up to date on both systems. What did I say? Sorry I used an S5 for years and probably quoted the model wrong. It's an SM-G930T
---------- Post added at 11:07 PM ---------- Previous post was at 11:04 PM ----------
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
Site was being screwy - sorry for the PM man. Same as below:
Sorry - I used an S5 for years and miquoted you the model. It's an SM-G930T (T-Mobile S7) The drivers on both systems are all up to date as well. It's 0x0, qualcomm, k1 s3 if that helps.
Again, sorry for PM, just curious on your thoughts with this one. Also wondering if you know if Download Mode would supercede any FRP or security settings. I keep trying various versions of Odin while connected in Download Mode - no COM port getting assigned.
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
T-Mobile S7 SM-G930T running Nougat 7.x
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
S7 Nougate, new cable worked like a charm. New firmware in 5min, thanks for the advice!
edit: new (old) firmware, but security patches still in place. Still need help with FRP lock!
U-TK said:
S7 Nougate, new cable worked like a charm. New firmware in 5min, thanks for the advice!
Click to expand...
Click to collapse
So are you through FRP or you still need assistance?
☆KØŁØЯΛĐØ☆ said:
So are you through FRP or you still need assistance?
Click to expand...
Click to collapse
I got ahead of myself and still need assistance.
I've managed to fix a few things (it would fail constantly in odin and result in a failed firmware screen upon restart).
Current situation:
- USB debugging was not enabled
- FRP is locked on Android 7.x
- I can upgrade/downgrade the firmware, but upon restart it pops up "Erasing" then "Installing updates" then "Erasing" so its basically undoing any security unpatching I'm try to do. Currently it's got G930TUVU4BQG5 July 2017 firmware, but the security patches to prevent RealTime, SideSync, Smart Switch and other dialer programs etc seem in place.
- I can put a COMBINATION firmware which gets me into a factory binary, but I don't see anything in here and have to reflash back to G930TUVU4BQG5
- Spamming RealTime to repeat dial a number shows me the traditional "calling" screen, but bluetooth, end call, etc are all greyed out.
- I have no SIM installed.
This guy did an FRP unlock (most up to date security patch) in 10 minutes. EXCELLENT service.
https://simunlockremote.com/contact/
Hey there, first time poster , long time user of this site. I started using this site about four years ago when I needed help modifying a HTC one V, and from there on out I haven't been able to stop modding and rooting. This site has been so helpful, you have no idea
To date I haven't had many issues with the unlocking of boot loaders and rooting, installing roms and also network unlocking.....Until today.
I am currently trying to network unlock a Samsung s5 neo. I did indeed buy the unlock code from Koodo (the original service provider). However (heres where its going to get weird), no matter how many times I try putting the darn code in, it plain well just refuses to take it. I can sit here all day and nadda a thing will happen.. IN FACT I thought after 10 times it would hard lock its self, resulting in me having to buy a unfreeze code. But nupe.
I'v used 3 different sim cards to try to get this phone unlocked but nothing, Bell Mobility from my LG G5 phone, A PC mobile sim and a Eastlink sim (By the way I'm from Canada)
I tried flashing (odin) with koodo OEM roms, from the first one which i think was 5.1 up to 6.** not sure where it left off. Even went as far as flashing with Telus rom, as koodo is the sister of Telus, and still it sits there pretty much laughing at me.
Factory reset from both with in the OS and the recovery menu, used every code for the phone dialer and half refuse to work. Installed shortcut master (Yes I'm rooted) and keeps saying locked. Also been trying to sim unlock both unrooted and rooted.
I'm completely mind blowen, i even said what the heck and bought a code off line for kicks and sure enough as soon as it showed up in my inbox, same EXACT code Koodo gave me. So we know the code is right.
Any help would be great as I'm at a complete lost. this is the first phone iv had , i'v ever had this much troubles unlocking. OH and if it helps "KNOX" is disabled
P.S I have no idea if i posted this in the right forum , sorry if i didn't.
Thanks
So the other day I accidentally turn off OEM unlock -> FRP locked out of my phone (can't boot, not the google account things). Everyone on this forum told me to just re-flash the ROM. I decided to go to the local repair shop since I don't want to deal with all the hassle of reflashing. The guy plugged my phone into his computer and in about 10s it booted up fine - my ROM and all app and data are exactly where I left it. He then just go to the developer options and turn OEM unlock on again. He did charge me a not small amount for 30s of works, so I don't bother asking him since most likely he won't answer.
So, anyone know what could possibly been done?
he uses a paid app that needs dongle that unlocks frp
I was planning on buying a brand new Pixel (the first one, not 2, 3, C, XL, etc...) from ebay and loading Lineage OS on it. There were a few things I wasn't sure about though. Do I install Lineage OS before or after activating the phone with the carrier or does it not matter? Also, if I have to activate first is there anything Verizon could/would do that might prevent me from installing this after it's activated?
I don't currently have a smartphone or know much about them but I get the impression Verizon doesn't like people doing things like this. The setup process seems straighforward enough but since I haven't seen anything address the questions above I worry I may wind up wasting money if I don't find out for sure first. Any input would definitely be appreciated! Sorry if these questions are redundant, I've spent a bit of time these past few days looking into setting this up and haven't seen anything that says one way or the other.
You're going to need to lookup a guide for unlocking the Verizon Pixel bootloader if a Verizon SIM has ever been inserted into the device. You don't have to worry about carrier locking however. A carrier lock and a locked bootloader are not the same thing.
What many online guides don'tmention (at least last I checked) is that you should actually factory reset the device twice without a Verizon SIM, then after doing so, you must connect to an internet-connected WiFi source, enable USB debugging, go to developer options, back out of developer options, and then wait 3-5 minutes and then you can go back into developer options and toggle OEM unlocking (so you can actually unlock your bootloader and load a custom ROM.)
The alternative, if there's never even been a Verizon SIM in the phone, is that you can just connect to WiFi and enable OEM unlocking. The bootloader doesn't actually semi-permanently lock until a SIM has been inserted.
Pixels are factory unlocked even when you buy them from Verizon, you can use them on any network without even having to fully pay off the phone. The SIM being read by the motherboard will lock the bootloader, but under no circumstances will a Pixel ever be carrier locked.
Lineage runs great on my first gen Pixel XL (originally purchased from Verizon), so well I actually have decided to sell my Galaxy Note 9 because it feel sluggish by comparison.
Bongzerker said:
You're going to need to lookup a guide for unlocking the Verizon Pixel bootloader if a Verizon SIM has ever been inserted into the device. You don't have to worry about carrier locking however. A carrier lock and a locked bootloader are not the same thing.
What many online guides don'tmention (at least last I checked) is that you should actually factory reset the device twice without a Verizon SIM, then after doing so, you must connect to an internet-connected WiFi source, enable USB debugging, go to developer options, back out of developer options, and then wait 3-5 minutes and then you can go back into developer options and toggle OEM unlocking (so you can actually unlock your bootloader and load a custom ROM.)
The alternative, if there's never even been a Verizon SIM in the phone, is that you can just connect to WiFi and enable OEM unlocking. The bootloader doesn't actually semi-permanently lock until a SIM has been inserted.
Pixels are factory unlocked even when you buy them from Verizon, you can use them on any network without even having to fully pay off the phone. The SIM being read by the motherboard will lock the bootloader, but under no circumstances will a Pixel ever be carrier locked.
Lineage runs great on my first gen Pixel XL (originally purchased from Verizon), so well I actually have decided to sell my Galaxy Note 9 because it feel sluggish by comparison.
Click to expand...
Click to collapse
Thanks for the reply! The phone I pick up should be brand new so no worries about a SIM having already been in it. Based on what you say about the bootloader locking when the SIM is inserted it sounds like installing Lineage OS before activating the phone and putting the SIM in is the way to go so that’s what I’ll do.
Also, glad to hear this performs so well compared to your newer phone!