Well, I'm pretty new to this stuff but yesterday I had a friend bring me an HTC desire that she bought on CL from someone. At the time of purchase she said it worked and then not even an hour later it was locked and they wouldn't answer her calls. Well I told her I would took a stab at it, so within a short period of time I found the OTG method. Well...like I said I'm new to all of this stuff and I don't have any OTG accessories at all so I went online to see who I could buy one from retail. staples website SAID they had one in stock but they closed at 6:00pm. it was 5:10. I hopped in the car and made it with 20 mins to spare...except they didn't have it. I checked best buy, walmart, target, hell I even went to car toys. No one had one, last store I checked online was Radio shack. I hadn't even thought of them until I seen them pop up in an ad on google, They had them in stock but...FML they closed at 6 also. Well I was kinda bummed I wasn't going to get to try this out until this morning so I kept at it. I googled every damn thing I could thing of to find different results. Eventually I stumbled upon the software for XTC 2 Clip, XTC 2 Tool. I didn't honestly know exactly what it was at first because I'm new to all of this and didn't know those box deals even existed but after a few mins I did figure out what it was actually for. On the main app screen I hit "Read phone info", it pulled up the info on the phone. Then I noticed there was a tab on the side for terminal and I was like ahh that's pretty cool. Well I had the screen lit up and decided to hit the TEST MENU button. It pulled up a menu almost like settings. From there I figured out if I hit battery and then hit the back button within the menu it would take me to settings. From there I tried to do a soft reset but it grayed out the button at first. So I decided I would enable ADB since I hadn't had it before now and then I also enabled bootloader unlock. I played around in there for a bit and it eventually let me hit the reset button.
If anyone cares to try this out and see if it works for them as well that would totally be awesome and if this method was already found please let me know as well. If it was a known method I honestly didn't know at all, I was prepared to drive to radio shack at 10am PST to get a cord and connect my flash drive haha.
Do you have links for the software? I'm not unable to unlock my boot loader. Maybe this will work.
Sent from my HTCD200LVW using XDA Free mobile app
Could you possibly give more detailed instructons?
20twins10 said:
Do you have links for the software? I'm not unable to unlock my boot loader. Maybe this will work.
Sent from my HTCD200LVW using XDA Free mobile app
Click to expand...
Click to collapse
unlock boot-loader u can do via https://www.htcdev.com/
the x2 clip tool is hardware based tool that can bypass s-on on the htc hardware, so if u buy the hardware u can use or pay someone who has this x2clip to do bypass for you.
htcdev method doesnt work on the Verizon version.
Sent from my HTCD200LVW using XDA Free mobile app
We can not unlock the bootloader without disabling frp because we can not get the correct token needed to generate the unlock code. Hopefully the original poster will give a more detailed explanation.
hey sorry, I hadn't been looking at this very often. What I was referring to was bypassing an FRP lock on a phone that you did not have the info to. I have a friend who bought a desire 626s off of CL and when she reset it she ended up locked out and didn't have the guy who she bought it from's number anymore. I used just the software for XTC2 tool and a usb cord to my PC. using the XTC 2 tool program I was able to bring up the test menu while at the FRP activation screen when normally nothing should be accessible, after clicking battery under the test menu and then hitting the back button it would glitch out and I would end up in settings. The options to reset the phone from inside settings were initially grey'd out and not accessible. Trying to devise another way to reset this phone I turned ADB on and enabled bootloader unlock so that I had a backup plan just in case I couldn't figure out a way to get the phone to reset from the glitched out settings menu. I don't remember exactly how I ended up getting the reset button to become clickable, I don't actually own this phone I was just trying to fix it for a friend otherwise I'd try and duplicate it again. I suppose I could see if it works on my M8? So to clarify, mentioning adb and bootloader oem unlock was more of a backup plan to try and bypass FRP activation just in case I couldn't get the glitched out settings menu to allow me to reset the phone. (for those that are not familiar with the OTG FRP bypass method essentially you stick an otg thumbdrive in your phone and the file explorer will pop up, there is a file you run and it will allow you to access your phones settings and from there you reset the phone. It was explained to me that resetting the phone with no account synced to it will remove the FRP once the reset is complete which is why I was looking to reset the phone once I got into the settings menu) Hope this helps explain what was going on in this post and hopefully it will help at least one person. *to clarify just a little further, I only used XTC2 tool to bring up the test menu. I wasn't really sure what I was looking for when I downloaded that program, it honestly was more of a fluke thing that I even discovered it. I'm sure any computer program that can bring up the test menu over usb will work to do this exact same thing until they patch the bug hitting the back button from the battery menu.
E36Nick90 said:
hey sorry, I hadn't been looking at this very often. What I was referring to was bypassing an FRP lock on a phone that you did not have the info to. I have a friend who bought a desire 626s off of CL and when she reset it she ended up locked out and didn't have the guy who she bought it from's number anymore. I used just the software for XTC2 tool and a usb cord to my PC. using the XTC 2 tool program I was able to bring up the test menu while at the FRP activation screen when normally nothing should be accessible, after clicking battery under the test menu and then hitting the back button it would glitch out and I would end up in settings. The options to reset the phone from inside settings were initially grey'd out and not accessible. Trying to devise another way to reset this phone I turned ADB on and enabled bootloader unlock so that I had a backup plan just in case I couldn't figure out a way to get the phone to reset from the glitched out settings menu. I don't remember exactly how I ended up getting the reset button to become clickable, I don't actually own this phone I was just trying to fix it for a friend otherwise I'd try and duplicate it again. I suppose I could see if it works on my M8? So to clarify, mentioning adb and bootloader oem unlock was more of a backup plan to try and bypass FRP activation just in case I couldn't get the glitched out settings menu to allow me to reset the phone. (for those that are not familiar with the OTG FRP bypass method essentially you stick an otg thumbdrive in your phone and the file explorer will pop up, there is a file you run and it will allow you to access your phones settings and from there you reset the phone. It was explained to me that resetting the phone with no account synced to it will remove the FRP once the reset is complete which is why I was looking to reset the phone once I got into the settings menu) Hope this helps explain what was going on in this post and hopefully it will help at least one person. *to clarify just a little further, I only used XTC2 tool to bring up the test menu. I wasn't really sure what I was looking for when I downloaded that program, it honestly was more of a fluke thing that I even discovered it. I'm sure any computer program that can bring up the test menu over usb will work to do this exact same thing until they patch the bug hitting the back button from the battery menu.
Click to expand...
Click to collapse
anyone that has access to xct2clip can bypass s-off security system and is able to turn s-off on any htc phone so anyone that got such tool could make a copy of system.img and make availible to others as this as far as i know is the file i need to continue to cook a new custom room to get full root control to our phone if anyone has such tool please could they make a copy of their system files for htc 626 a32_ul qcom 410 64 bit system to be precise as i possible can not the htc626s a32e_ul qcomm 210 type phone, i think with system files for htc 626 qcomm410 type i can build a custom rom for this phone. but is a catch 22 cant copy files without root, or without this xct2clip that is able to bypass s-on .
---------- Post added at 10:46 PM ---------- Previous post was at 10:24 PM ----------
and this exploit isnt no accident it is a method junnipter took advantage of in past by shorting a contact between sdcard and circuit board to gain access to bypass s-on, which i think is no longer available without device such as xct2 clip. that has taken advantage of this bypass, probability the contact that was used to bypass s-on has now got plastic undercover over it . would be my guess.
E36Nick90 said:
Well, I'm pretty new to this stuff but yesterday I had a friend bring me an HTC desire that she bought on CL from someone. At the time of purchase she said it worked and then not even an hour later it was locked and they wouldn't answer her calls. Well I told her I would took a stab at it, so within a short period of time I found the OTG method. Well...like I said I'm new to all of this stuff and I don't have any OTG accessories at all so I went online to see who I could buy one from retail. staples website SAID they had one in stock but they closed at 6:00pm. it was 5:10. I hopped in the car and made it with 20 mins to spare...except they didn't have it. I checked best buy, walmart, target, hell I even went to car toys. No one had one, last store I checked online was Radio shack. I hadn't even thought of them until I seen them pop up in an ad on google, They had them in stock but...FML they closed at 6 also. Well I was kinda bummed I wasn't going to get to try this out until this morning so I kept at it. I googled every damn thing I could thing of to find different results. Eventually I stumbled upon the software for XTC 2 Clip, XTC 2 Tool. I didn't honestly know exactly what it was at first because I'm new to all of this and didn't know those box deals even existed but after a few mins I did figure out what it was actually for. On the main app screen I hit "Read phone info", it pulled up the info on the phone. Then I noticed there was a tab on the side for terminal and I was like ahh that's pretty cool. Well I had the screen lit up and decided to hit the TEST MENU button. It pulled up a menu almost like settings. From there I figured out if I hit battery and then hit the back button within the menu it would take me to settings. From there I tried to do a soft reset but it grayed out the button at first. So I decided I would enable ADB since I hadn't had it before now and then I also enabled bootloader unlock. I played around in there for a bit and it eventually let me hit the reset button.
If anyone cares to try this out and see if it works for them as well that would totally be awesome and if this method was already found please let me know as well. If it was a known method I honestly didn't know at all, I was prepared to drive to radio shack at 10am PST to get a cord and connect my flash drive haha.
Click to expand...
Click to collapse
Just wanted to let you know that I tried this as well and "SUCCESS" so thank you for the help and Happy Holidays!:good:
I just used this on an HTC OPM9200 (Desire 626) and it worked like a charm. I was having a Helluva time until I stumbled across this thread. Thank you!
Same problem, no dice
I'm working on a Desire 626s with the same problem and have installed the XTC2 program as suggested by the op, but clicking "Test menu" under the terminal tab doesn't seem to have any effect, so I'm guessing this is just another dead end. I heard that this device's original stock ROM was a Kitkat one, and since Kitkat doesn't have any of this nonsense, would flashing the original stock ROM effectively sidestep the problem?
Any ideas?
I figured out a way to get past frp but I'm still deciding weather I should share how to or not... I don't want the exploit to be used wrongly.
getting to the bottom of this
723i said:
I figured out a way to get past frp but I'm still deciding weather I should share how to or not... I don't want the exploit to be used wrongly.
Click to expand...
Click to collapse
What did you have in mind? Would downgrading to a KitKat Rom work or can Roms not be flashed when the phone is in that state?
723i said:
I figured out a way to get past frp but I'm still deciding weather I should share how to or not... I don't want the exploit to be used wrongly.
Click to expand...
Click to collapse
if you are able to gain root access to your phone you should share, root access i think is fundamental right one should have to make use of the hardware we have paid for , instead of the limited use of the availible hardware set by htc, if u are not able to gain access to rooting your phone then you have found nothing and just leading ppl down a path that doesn't do anything to gain root access, as for your part saying ... I don't want the exploit to be used wrongly. wtf almost every android phone and iphone has root access too root do you think the other 99% phones that have root access availible are being used wrongly.
rofl you either found root method or you found nothing.
It just uses adb I never needed root access.
Can eny one creat a cm rom 4 htc d626p
Just wanted to say a big thanks! As a metro employee I had a customer bring me in an FRP locked Desire 626s. I tried USB-OTG to no avail.. After a few days of scratching my head and trying to figure out how you got the XTC2Clip software to recognize your device (when on the home setup screen) I had about given up.
Thats when I found out opening the RUU executable (flashes the stock metro rom) automatically puts the phone into debug mode before flashing it.
BINGO! After opening the RUU to flash the phone I kept it open in the background, clicked read phone information on the software, a usb debugging window popped up on the phone and from there it was gravy!
On a side note: The option to reset the phone is grayed out when entering the settings menu. You need to click Okay as quickly as possible upon entering the factory reset screen (before it grays itself out), a prompt to factory reset will very quickly pop up and disappear, so also be quick to click confirm on this prompt as well. (I'm talking trigger finger fast, it took me like 25 tries.)
no go
revulv said:
Just wanted to say a big thanks! As a metro employee I had a customer bring me in an FRP locked Desire 626s. I tried USB-OTG to no avail.. After a few days of scratching my head and trying to figure out how you got the XTC2Clip software to recognize your device (when on the home setup screen) I had about given up.
Thats when I found out opening the RUU executable (flashes the stock metro rom) automatically puts the phone into debug mode before flashing it.
BINGO! After opening the RUU to flash the phone I kept it open in the background, clicked read phone information on the software, a usb debugging window popped up on the phone and from there it was gravy!
On a side note: The option to reset the phone is grayed out when entering the settings menu. You need to click Okay as quickly as possible upon entering the factory reset screen (before it grays itself out), a prompt to factory reset will very quickly pop up and disappear, so also be quick to click confirm on this prompt as well. (I'm talking trigger finger fast, it took me like 25 tries.)
Click to expand...
Click to collapse
Could you be more specific about what you did in the XTC Tool because this is not working for me?
Couldn't this just be fixed by flashing a stock KitKat ROM for this phone? If so, where would I need to go to find one of those?
I Found another way to disable FRP.
I downloaded the XTC 2 V 1.17 but that didn't work. So the software told me to update it to V 1.19.
But this time while on the setup screen i had accidentally left it on the emergency call screen.
So launch XTC 2 v .11.19(Run as Administrator) then as soon as the software turns on. Look at the phone screen. while on the emergency call. It will ask you for "Allow USB Debugging" Just check mark Always and then OK
If it doesn't. just try clicking for read phone info. then it should ask for USB debugging.
Next Open up the ADB Folder ( Need to have ADB installed on the computer)
Then Run the Following commands in adb .
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
then reboot and you have just bypassed FRP on HTC Desire 626s running 5.1 Firmware
FIXED!!!!
djkid said:
I Found another way to disable FRP.
I downloaded the XTC 2 V 1.17 but that didn't work. So the software told me to update it to V 1.19.
But this time while on the setup screen i had accidentally left it on the emergency call screen.
So launch XTC 2 v .11.19(Run as Administrator) then as soon as the software turns on. Look at the phone screen. while on the emergency call. It will ask you for "Allow USB Debugging" Just check mark Always and then OK
If it doesn't. just try clicking for read phone info. then it should ask for USB debugging.
Next Open up the ADB Folder ( Need to have ADB installed on the computer)
Then Run the Following commands in adb .
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
then reboot and you have just bypassed FRP on HTC Desire 626s running 5.1 Firmware
Click to expand...
Click to collapse
Ah ha! That did it! Excellent work.
Related
Hey guys, my first post here. I signed up for this forum a little while ago and I've just been a lurker since today. Lots of great stuff on this forum!
I finally got my Nexus 4 phone when they went back on sale in late January, I came from an iPhone 3GS and I've been loving the switch every day since!
But now I have a problem that I hope you guys can help me with.
When I first got my phone the first thing I did was unlock the bootloader and root the device, I had 4.2.1 on my phone and forced the 4.2.2 update by clearing the cache/data of a few apps when it was mentioned on this forum (Bad mistake I think). I went to download titanium with root the other day to start to backup my apps/phone before I started messing with kernels and audio upgrades in case I messed something up and needed to reinstall. Unfortunately since this is my first Android phone I didn't know that upgrading would also remove my root access. Not a problem I though, I'll just go ahead and re-root the device, well that's where I started to see various problems.
I installed the SUser 1.0.4 zip on my phone (After I tried .98), booted up into the clockwork recovery option, extracted the zip from within clockwork to root my device again and nothing. I tried a couple of times, even tried the Nexus 4 toolkit but that didn't seem to work either. Rootchecker won't recognize that my phone is rooted.
In fastboot mode it shows my phone is
Secure boot - enabled (Green)
Lock State - unlocked (red)
When I was in the Nexus 4 toolkit I also noticed that it wouldn't recognize my phone's serial USB debugging mode even when I turned it on (Pressing the build number 7 times and checking the usb debugging box in developer options). When in fastboot mode my computer recognized my phone without a problem. I am still able to move stuff on and off of the phone through windows explorer, but only when it's NOT in debugging mode, my computer beeps like something is connected when in USB debugging mode but nothing shows up anywhere except in device manager. I tried installing the drivers that were posted for 4.2.2 and also tried installing the drivers through the toolkit but neither would fix that problem. Another thing I noticed was that I never got a prompt on my phone to allow my computer access to debugging mode like people mentioned that I should get.
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Anyone have any suggestions as to what I can do or how I can get my root access back?
Thanks a bunch in advance for any help you guys can give me, and if I left some info out of here that you need let me know.
kelmino said:
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Click to expand...
Click to collapse
Oh wow... yup I'm an idiot and missed something really obvious....
I just installed the SuperSU app from the playstore and I do have root access again and apps request access.
ugh I'm a moron, I spent hours on this yesterday and as soon as I post this I fix the issue
Sorry guys
Now my only problem is I can't see my phone from the playstore on my computer but I'm not worried about that, I think I can fix that as I see another post up here for that same issue.
perhabs this helps
http://forum.xda-developers.com/showthread.php?t=2159744
u dont need to extraxt su zip file....download drivers..use tool kit to unlock bootloader..then flash temporary clockwork recovery...flash su in recovery....download goo manager from playstore to flash permanent recovery
Sent from my Nexus 4 using xda app-developers app
dont use toolkit. do it the long way so you know what you're doing otherwise you're walking in a room blindedly hoping you'd get through the maze.
in the long run, it'll be worth it. very simple & easy to do.
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N
So is this usable in all situations? If yes then should download it & store it safely
Interesting thing, can this update bypass factory reset protection?
iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.
This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you
Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?
holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.
TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939
just want to ask would this method work if the phone has not been authorized to a specific PC ?
iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:
I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying
Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)
MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...
Have you tried flashing a stock ROM with the qcom download tool
abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.
Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.
I am looking to remove the Google account from a Samsung Galaxy On5 MetroPCS SM-G550T1. The phone has Marshmallow 6.0.1 . The FRP is on download mode. I already tried modem flash but the phone is still asking for the account. I also tried a couple bypass methods but the security patch does not allow any internet access. Any ideas guys?
If you bricked your On5 phone, Try reflashing on of your corresponding full firmware:
Galaxy On5 MetroPCs (SM-G550T1)
https://docs.google.com/uc?id=0BwvezwPRpyjkY2g5emtsZ2tyb2s
Galaxy On5 T-Mobile (SM-G550T)
https://www.androidfilehost.com/?fid=24723757092307323
Do not forget to click the thanks button
Download compatible Full 4 File Android Marshmallows 6.0.1 version : G550TUVU1APF1 G550TUVU1APDE G550T1UVU1APF1
SOLVED:
Update, Hey guys, I found the solution for this problem. Here is the step by step proccess:
01. You need to download the "RealTerm" program and install it in your computer (Thanks Root Junky for the links) : http://rootjunkysdl.com/files/?dir=Apps/FRP.
02. Go to phone. You need to have a SIM in your phone for this process to work for the ORIGINAL CARRIER of the phone.
03. Go to your setup screen and connect to WIFI.
05. Using a USB cable, connect your phone to your computer. Make sure that your computer is reconizing your phone by instaling the last Samsung drivers available (http://www.samsung.com/us/support/downloads)
06. Once the phone is reconized by the computer and USB connected, we need to find out in what USB port your phone is connected to. To do that, you need to go you "Device Manager" in your computer. Click on "Modems". Then click on "SAMSUNG Mobile USB". On that screen, open the "Modem Tab". The first thing that you will find is: "PORT: COM09" (COM09 is in example, your phone could be connected to another port like COM41, COM39, and so on).
07. Now that we know our USB port number, open your RealTerm program. In the Realterm "Display" tab, make sure to check the "HALF DUPLEX" box.
08. Then, click on the "PORT" tab. Now, here we are going to enter the port number that our phone is without the COM in the Port box (For Example, COM43 = 43). The click on the "OPEN" button next to it.
09. Go to the "SEND" tab. In the first box, type the following command: at+creg?\r\n and click on "SEND NUMBERS"
10. Then, in the same box, type: atd1234;\r\n and also click "SEND NUMBERS". At this step, you need to look at the phone screen because the dealer is going to try to dial "1234". If not, keep sending the atd1234;\r\n commands.
11. When the dialer shows up, end the call and immediately click on the "MESSAGE" button. The phone is going to go to SMS to send a message to the "1234" number that the phone tried to dial. Send this 1234 number "YOUTUBE.COM" message. Send it. After the message is sent to this number, the words "Youtube.com" would became a blue internet link, click on it. The browser is going to go to Youtube. After you are in YouTube, click on the 3 dots at the upper right hand side of the screen. Click on "Settings", then click "About", then "GOOGLE Privacy Policy". the phone will ask you to choose an internet browser. Use the "Internet Browser"
12. When you are in the browser, again go to " http://rootjunkysdl.com/files/?dir=Apps/FRP " (Thanks Root Junky for the Links) and download "com.rootjunky.frpbypass-1.0.apk".
13. Then, go on Google.com and search for "Samsung App Store" : http://www.samsung.com/levant/apps/mobile/galaxyapps/ . Click on the "App Store" button. The Samsung is going to open and ask you to sign in. You would have to either create an account or use your existing Samsung account. Do not worry, you would get to remove it later.
14. Once you are at the Samsung account, search for "ES FILE Explorer" and install it in your phone. Once, it is installed, open the app. The app will allow you to go to the "Download" folder of your phone. There you will find the "com.rootjunky.frpbypass-1.0.apk" that you previously downloaded. Open and Install the "com.rootjunky.frpbypass-1.0.apk". The App will send you to the "Google Sign In" windows. DO NOT SING IN. Click on the three dots at the upper right hand side of the screen and click on "BROWSER SIGN IN". Then a new Google browser sign in screen will appear. Yes, you can Sign in there with your existing Google account (Again, do not worry, you can remove it later). Once you are signed in, you need to restart your phone.
15. Follow the setup instructions. The phone is not going to ask you for the Google account because you already entered.
16. Once at the home screen, click on 'Settings". Then go to "Accounts” and click on the "Samsung Account", click on "Remove Account". The phone is going to ask you for a confirmation to enter your password. Enter it and click on Remove. Go back and click on your "Google Account". Click on "Remove Account".
17. Go back to settings, and then click on "BACKUP AND RESET". Then click on "FACTORY DATA RESET". Then "RESET DEVICE". The phone will factory reset and the FRP will be removed.
DO NOT FORGET TO CLICK ON THE THANKS BUTTON
Solved frp lock sm-g550t1
GalaxyVibe said:
I am looking to remove the Google account from a Samsung Galaxy On5 MetroPCS SM-G550T1. The phone has Marshmallow 6.0.1 . The FRP is on download mode. I already tried modem flash but the phone is still asking for the account. I also tried a couple bypass methods but the security patch does not allow any internet access. Any ideas guys?
Click to expand...
Click to collapse
After facing the same problem for better than a week and even purchasing a replacement phone I have bypassed the FRP/Custom Binary Lock for the sm-g550t1.
1.) Start by using Odin 3.10.7
2.) After install, along with Samsung drivers, and the like, Fire Odin up and go ahead and place your phone into Download Mode (Vol up + home button + power) but wait to insert your USB until we've got Odin ready to rock.
3.) First we'll be going to the options tab and checking the box labeled "Nand Erase All". YES THIS IS ABSOLUTELY GOING TO TAKE THE PHONE BACK TO STOCK. Beats the hell out of having a paperweight just lying around though doesn't it...
4.) Without checking any boxes on main console, Apply each one of the files listed into their designated slot. (ex.. AP=ap BL=bl... just try not to be a boob is all..)
5.) Download and unzip the attached package to whatever location you can remember.
6.) One at a time, click the appropriate buttons to insert the file (MAKE SURE NONE OF THE WHITE CHECK BOXES ARE HIGHLIGHTED OR YOU'LL SCREW YOURSELF UP AND HAVE TO START OVER)
7.) Once all appropriate files are in correct locations, and the correct options are set; Highlight/Check ALL white boxes, it'll take a second for the md5's to clear.
8.) If you think you're set go ahead and hit the start button. This process takes between 2-8 mins depending on variables involved beyond my control.
9.) After all files have been transferred the On5 will reboot automatically. It will require you login to whatever Google account you had on there to begin with.
There are several, well documented, methods for bypassing that portion of the lock so I'll leave you to it...
Happy Hunting.. let me know if it gives you any ****.
Special Thanks to:
JUSMEJOSE - for the original firmware zip package
1ExtremeWife - for constantly *****ing, I mean motivating me to move from one project to the next. Love u babe...
note: since ive never taken the time to post on this particular site, i cannot yet upload the link. email me if you need the files directly, otherwise just follow the instructions above and use the files from http://click.xda-developers.com/api...www.dropbox.com/s/7dosx927uq...overy.zip?dl=0
extrememachinist said:
After facing the same problem for better than a week and even purchasing a replacement phone I have bypassed the FRP/Custom Binary Lock for the sm-g550t1.
1.) Start by using Odin 3.10.7
2.) After install, along with Samsung drivers, and the like, Fire Odin up and go ahead and place your phone into Download Mode (Vol up + home button + power) but wait to insert your USB until we've got Odin ready to rock.
3.) First we'll be going to the options tab and checking the box labeled "Nand Erase All". YES THIS IS ABSOLUTELY GOING TO TAKE THE PHONE BACK TO STOCK. Beats the hell out of having a paperweight just lying around though doesn't it...
4.) Without checking any boxes on main console, Apply each one of the files listed into their designated slot. (ex.. AP=ap BL=bl... just try not to be a boob is all..)
5.) Download and unzip the attached package to whatever location you can remember.
6.) One at a time, click the appropriate buttons to insert the file (MAKE SURE NONE OF THE WHITE CHECK BOXES ARE HIGHLIGHTED OR YOU'LL SCREW YOURSELF UP AND HAVE TO START OVER)
7.) Once all appropriate files are in correct locations, and the correct options are set; Highlight/Check ALL white boxes, it'll take a second for the md5's to clear.
8.) If you think you're set go ahead and hit the start button. This process takes between 2-8 mins depending on variables involved beyond my control.
9.) After all files have been transferred the On5 will reboot automatically. It will require you login to whatever Google account you had on there to begin with.
There are several, well documented, methods for bypassing that portion of the lock so I'll leave you to it...
Happy Hunting.. let me know if it gives you any ****.
Special Thanks to:
JUSMEJOSE - for the original firmware zip package
1ExtremeWife - for constantly *****ing, I mean motivating me to move from one project to the next. Love u babe...
note: since ive never taken the time to post on this particular site, i cannot yet upload the link. email me if you need the files directly, otherwise just follow the instructions above and use the files from http://click.xda-developers.com/api...www.dropbox.com/s/7dosx927uq...overy.zip?dl=0
Click to expand...
Click to collapse
The link works. I downloaded the stock firmware and followed all the steps. However, the Google lock is still there.
My phone is still google locked
extrememachinist said:
so Im at a loss here. I have personally removed the "custom bianary lock FRP" from several of the metropcs version sm-g550t1's without any issues.
just to confirm:
all settings in odin are set to factory, (reboot enabled, and f time) and you've selected the nanderase option?
afterwards, you unzipped, the package, which should have displayed somthing like 4 or 5 files. which then were inserted into corresponding slots on odin?
did you flash over twrp at any time?
Click to expand...
Click to collapse
The FRP is still on. I can still go to the Google account set up page on the phone. I thought that I could remove the Google account by using these files. But I now understand that these files are only usefull if the phone is "custom bianary lock FRP".
Turn oem unlock on. That will do it.
whodisname said:
Turn oem unlock on. That will do it.
Click to expand...
Click to collapse
Thank you for your suggestion. However, I can not get pass the google sign in screen
I already tried the Odin, OTG, and SideSync methods and none of them work
Have you tried this?
https://9to5google.com/2015/11/03/how-to-to-bypass-factory-reset-protection-samsung-phone-hack/
Sent from my SM-G550T1 using XDA-Developers mobile app
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
http://visihow.com/ADB_commands_to_bypass_Google_Account_Verification
Sent from my SM-G550T1 using XDA-Developers mobile app
whodisname said:
Have you tried this?
https://9to5google.com/2015/11/03/how-to-to-bypass-factory-reset-protection-samsung-phone-hack/
Sent from my SM-G550T1 using XDA-Developers mobile app[/URL]
Click to expand...
Click to collapse
I tried this OTG method but it does not work
whodisname said:
http://visihow.com/ADB_commands_to_bypass_Google_Account_Verification
Sent from my SM-G550T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
I also tried this but the phone needs to be rooted for this to work You can not root this phone because the FRP lock does not allow it
I am still trying new methods but nothing yet ;(
Call google.
confusion about FRP locks..
On a previous post I mentioned steps required to unlock FRP from the g550t1. There has been some confusion as to the results.
My phone, when FRP was engaged, wouldn't even boot. I'd get maybe 2.5sec before complete shutdown.(no recovery, no loading what so ever..) The steps I provided did not remove the lock, that required alot of patience and, quite frankly, a lot of smashing my head into my desk until something useful came out. I'll build on my previous post with the steps I TOOK THAT WORKED FOR ME. This is in no way a guarantee, promise, or anything of the sort that it'll work as it did for me...
so no whining if you can't figure it out...
Maybe you should have researched more before attempting to modify your device...
I'm just saying..
log into your google account-from diff device
remove locked device from connected devices section
activate sign-out from all accounts
change your Google password
make sure the 2-step verification is off as well as the sign-in with device option
boot device
login/activate account with new password
follow setup instructions on-screen
activate developer options menu
turn on OEM Unlock (and leave it ON PERMANENTLY) without it, you are asking to be bricked and hit with another FRP lock.
continue in any manner you choose
try to use more caution and do a little more research in the future.
Happy Hunting...
& Good Luck...
extrememachinist said:
On a previous post I mentioned steps required to unlock FRP from the g550t1. There has been some confusion as to the results.
My phone, when FRP was engaged, wouldn't even boot. I'd get maybe 2.5sec before complete shutdown.(no recovery, no loading what so ever..) The steps I provided did not remove the lock, that required alot of patience and, quite frankly, a lot of smashing my head into my desk until something useful came out. I'll build on my previous post with the steps I TOOK THAT WORKED FOR ME. This is in no way a guarantee, promise, or anything of the sort that it'll work as it did for me...
so no whining if you can't figure it out...
Maybe you should have researched more before attempting to modify your device...
I'm just saying..
log into your google account-from diff device
remove locked device from connected devices section
activate sign-out from all accounts
change your Google password
make sure the 2-step verification is off as well as the sign-in with device option
boot device
login/activate account with new password
follow setup instructions on-screen
activate developer options menu
turn on OEM Unlock (and leave it ON PERMANENTLY) without it, you are asking to be bricked and hit with another FRP lock.
continue in any manner you choose
try to use more caution and do a little more research in the future.
Happy Hunting...
& Good Luck...
Click to expand...
Click to collapse
I really appreciate your help. I kept the firmware files in case of an emergency. I bought this phone online and it is actually Google locked. I do not know the Account or the password. Again, I appreciate your help. Thanks man!
So let me get this straight. You cant even flash new rom with odin because it wont let you, says frp protect, and it has the stock recovery, correct?
It wont let you use wifi? It seems lile it has to let you use wifi, how else is it going to confirm your account? Make sure it doesnt conect to wifi. There is another way besides what I have said here but it requires wifi.
Its a low tech hack (I love those).
whodisname said:
So let me get this straight. You cant even flash new rom with odin because it wont let you, says frp protect, and it has the stock recovery, correct?
It wont let you use wifi? It seems lile it has to let you use wifi, how else is it going to confirm your account? Make sure it doesnt conect to wifi. There is another way besides what I have said here but it requires wifi.
Its a low tech hack (I love those).
Click to expand...
Click to collapse
The stock firmware I can reflash it. I can not install a custom recovery because the phone is FRP locked. Yes, i get access to WIFI. I have tried many bypasses but this Marshmallow firmware has all the security patches updated. But i will appreciate any suggestions.
I am running G550T1UVU1APF1. I was wondering what would happen if I could downgrade to G550T1UVU1APED. Does anybody have this G550T1UVU1APED firmware file?
GalaxyVibe said:
I am running G550T1UVU1APF1. I was wondering what would happen if I could downgrade to G550T1UVU1APED. Does anybody have this G550T1UVU1APED firmware file?
Click to expand...
Click to collapse
This is for metropcs on5 apparently but I saw on other forums it is also for s7. s G550T1UVU1APED firmware file is what I need though for my frp lock phone so I would appreciate if you could link me to where I can download sG550T1UVU1APED firmware files pls?
---------- Post added at 05:32 PM ---------- Previous post was at 05:05 PM ----------
extrememachinist said:
On a previous post I mentioned steps required to unlock FRP from the g550t1. There has been some confusion as to the results.
My phone, when FRP was engaged, wouldn't even boot. I'd get maybe 2.5sec before complete shutdown.(no recovery, no loading what so ever..) The steps I provided did not remove the lock, that required alot of patience and, quite frankly, a lot of smashing my head into my desk until something useful came out. I'll build on my previous post with the steps I TOOK THAT WORKED FOR ME. This is in no way a guarantee, promise, or anything of the sort that it'll work as it did for me...
so no whining if you can't figure it out...
Maybe you should have researched more before attempting to modify your device...
I'm just saying..
log into your google account-from diff device
remove locked device from connected devices section
activate sign-out from all accounts
change your Google password
make sure the 2-step verification is off as well as the sign-in with device option
boot device
login/activate account with new password
follow setup instructions on-screen
activate developer options menu
turn on OEM Unlock (and leave it ON PERMANENTLY) without it, you are asking to be bricked and hit with another FRP lock.
continue in any manner you choose
try to use more caution and do a little more research in the future.
Happy Hunting...
& Good Luck...
Click to expand...
Click to collapse
Hi I tried using your step. I signed on my google account from both my pc and tablet and I can't find:
remove locked device from connected devices section
Where is it? ON my pc I did see my on5 phone but when I click on it I don't see that is locked or something? Or I cant find it:
remove locked device from connected devices section
A little help? Ok from my pc when I click on my frp lock phone. I see
Account access: REMOVE
So what happens if I click remove? IS that what will solve the frp lock?
asianrocker said:
This is for metropcs on5 apparently but I saw on other forums it is also for s7. s G550T1UVU1APED firmware file is what I need though for my frp lock phone so I would appreciate if you could link me to where I can download sG550T1UVU1APED firmware files pls?
---------- Post added at 05:32 PM ---------- Previous post was at 05:05 PM ----------
Hi I tried using your step. I signed on my google account from both my pc and tablet and I can't find:
remove locked device from connected devices section
Where is it? ON my pc I did see my on5 phone but when I click on it I don't see that is locked or something? Or I cant find it:
remove locked device from connected devices section
A little help? Ok from my pc when I click on my frp lock phone. I see
Account access: REMOVE
So what happens if I click remove? IS that what will solve the frp lock?
Click to expand...
Click to collapse
I do not have the G550T1UVU1APED. I am actually looking to get it. I will upload it if I ge it. Please do the same if you find it first.
GalaxyVibe said:
The FRP is still on. I can still go to the Google account set up page on the phone. I thought that I could remove the Google account by using these files. But I now understand that these files are only usefull if the phone is "custom bianary lock FRP".
Click to expand...
Click to collapse
Hi. your phone was flashed without you flashing the AP file? What is the AP file anyway? IT is the largest file on the custom rom I have. I also still have the google verify I can't bypass.
But I want to try to flash again like on your pictures: just flash without the AP file. Will it brick my phone?
Just want to make sure coz I'd rather have a google verify lock than a logo screen FRP lock.
So I was poking around the settings, and I found how to enable developer mode on the Nook.
You just tap on the Build number (Not the serial number) in Settings > About Tablet
then go back one menu and it's there "Developer options".
I was able to turn on "OEM unlocking" -- does this mean the boot loader is unlocked?
Which means, you could run the "root anything" boot.img ?
Ok, the Nook shows up in ADB!
fastboot devices worked as well.
However, fastboot oem unlock
and
fastboot flashing unlock
both do nothing
fastboot oem unlock works but you have to go into developer options in settings and enable OEM Unlocking (3rd option on the screen). It's an extra little safety step.
dokihara said:
Ok, the Nook shows up in ADB!
fastboot devices worked as well.
However, fastboot oem unlock
and
fastboot flashing unlock
both do nothing
Click to expand...
Click to collapse
jsonger said:
fastboot oem unlock works but you have to go into developer options in settings and enable OEM Unlocking (3rd option on the screen). It's an extra little safety step.
Click to expand...
Click to collapse
I did enable that. How long do you have to wait? I waited about 5 minutes. at the "..." prompt before cancelling.
this is the 2016 Nook right? the brand new one..
dokihara said:
I did enable that. How long do you have to wait? I waited about 5 minutes. at the "..." prompt before cancelling.
this is the 2016 Nook right? the brand new one..
Click to expand...
Click to collapse
Once you're in fastboot on the device (adb reboot bootloader after enabling USB debugging on the tablet) and you get the "FASTBOOT mode ..." prompt. Then do "fastboot oem unlock" and it should prompt you on the screen with the usual warranty voiding, going to wipe the device, etc. Press Volume Up to confirm and that should be it. It'll spin it's wheels for a bit while it's doing the wipe and all.
---------- Post added at 04:45 PM ---------- Previous post was at 04:31 PM ----------
jsonger said:
Once you're in fastboot on the device (adb reboot bootloader after enabling USB debugging on the tablet) and you get the "FASTBOOT mode ..." prompt. Then do "fastboot oem unlock" and it should prompt you on the screen with the usual warranty voiding, going to wipe the device, etc. Press Volume Up to confirm and that should be it. It'll spin it's wheels for a bit while it's doing the wipe and all.
Click to expand...
Click to collapse
I went back and rechecked everything and I hadn't unlocked the Nook yet. (I have a couple of different tablets I'm messing with right now.) The procedure is right but it looks like there is another firmware glitch (along with the lack of brightness control) where it isn't reading the volume up or down buttons in fastboot.
Wow the software on this thing is sloppy.
I went back and rechecked everything and I hadn't unlocked the Nook yet. (I have a couple of different tablets I'm messing with right now.) The procedure is right but it looks like there is another firmware glitch (along with the lack of brightness control) where it isn't reading the volume up or down buttons in fastboot.
Wow the software on this thing is sloppy.
Click to expand...
Click to collapse
Yeah, running that command doesn't do anything.
Hi, I'm new to Android development and stuff.
It seems that there are conflicting reports. Is the bootloader for the Nook Tablet 7" unlockable?
I picked up this Nook on this past Black Friday. I'm using a SD card formatted as internal, but I'm running out of space on the actual internal storage. I want to root this thing so I can remove the Nook bloatware and move unmovable apps to SD card.
I tried towelroot and Kingo root, but after it failed I found out Marshmallow isn't supported...
I saw the how to geek's article here - howtogeek(dot com)/115297/how-to-root-your-android-why-you-might-want-to
It explains how to root by unlocking the bootloader then flashing superSU using TWRP. I'm wondering if it will work. Can I actually unlock the bootloader without an OEM code? But I looked at the TWRP website, and the Nook 7 isn't supported. I know this is a really new device; how long does it usually take for TWRP to add a device?
Sooooo... is there another way to root?
I'm also waiting for CyanogenMod to release a build. If I understand correctly, my device must be rooted before flashing any custom ROM, right? So does that mean that every device for which a custom ROM has been written is rootable? Anyway, how long will it take for a build to be written? Should I stop looking because it will be a long time?
Thanks!
I am also able to run 'fastboot oem unlock', but then I run into the issue where it doesn't detect the input of either volume button, and my only option is to power off the device. I fear we won't see a fix for this. It may even be deliberate as a way for them to lock down the device. Has anyone so far had luck actually getting the oem unlock to work and wipe the device?
Did you enable OEM unlocking from developer options as jsonger suggested?
soundtoxin said:
I am also able to run 'fastboot oem unlock', but then I run into the issue where it doesn't detect the input of either volume button, and my only option is to power off the device. I fear we won't see a fix for this. It may even be deliberate as a way for them to lock down the device. Has anyone so far had luck actually getting the oem unlock to work and wipe the device?
Click to expand...
Click to collapse
Yes, of course. This is not my first rodeo. Have you gotten this working? It sounds like everyone is stuck at the same point.
soundtoxin said:
Yes, of course. This is not my first rodeo. Have you gotten this working? It sounds like everyone is stuck at the same point.
Click to expand...
Click to collapse
Sigh. We must be stuck, then.
No, I haven't tried anything yet. I was trying to install the ADB but then I learned that SDK Manager needs Java to run, apparently? So I started downloading the JDK but my internet is slow so I canceled it. I'll try again later.
I've been trying a number of different root tools, but no luck yet. IF I successfully root my Nook (kind of unlikely) and TWRP adds it as a supported device (even more unlikely), would it be possible to flash TWRP recovery using the app from the Play Store?
Has anyone tried unlocking the bootloader after this last update?
I believe I have discovered the complete firmware for the T8370, the Chinese tablet that Nook rebranded. As emdoor (the company behind the T8370 tablet) still handles the Nook's software, I'm guessing the firmware will be very similar. At the very least the firmware should give me an idea of why the bootloader is not unlocking and/or what the bootloader does in the unlocking process. Sadly, the firmware is stored on unreliable Chinese servers, so it may be a day or two before I can finish the download. While we did receive Chinese malware with the Nook, the rebranding of a Chinese tablet may ultimately pay off... I doubt B&N would have readily released the complete firmwares for their devices.
I tried unlocking after doing the upgrade and it still has the same problem of not responding to Volume up/down in fastboot.
kingramon0 said:
I tried unlocking after doing the upgrade and it still has the same problem of not responding to Volume up/down in fastboot.
Click to expand...
Click to collapse
That is unfortunate. :/ Let us know if you make any progress.
I haven't been serious in my efforts to unlock the bootloader. But the one time I tried, I sent an adb reboot bootloader, and the nook went to fastboot mode. But then adb lost the connection, and when I sent fastboot oem unlock, adb said waiting for device. So I hadn't even gotten to the problem of the volume button.
This was before the update, btw.
Is anyone else getting tired of micromanaging storage space? I have a huge 32GB SD card, but preloaded apps are eating up my space. And they can't be moved to SD card.
*Sigh*
smileygon10 said:
Is anyone else getting tired of micromanaging storage space? I have a huge 32GB SD card, but preloaded apps are eating up my space. And they can't be moved to SD card.
*Sigh*
Click to expand...
Click to collapse
Yeah.... it's getting to be a real pain in the arse. That and there's no way to force it to install two micro SD card if you've got the card formatted as unified storage you would think that Google Play would realize that and automatically move everything over. What's worse is that when you update apps move them back to internal storage and then you you have to move them again.
I wish someone would go ahead and figure out how to root this thing so we can get rid of things like YouTube kids which no one with this tablet is going to use.
smileygon10 said:
Is anyone else getting tired of micromanaging storage space? I have a huge 32GB SD card, but preloaded apps are eating up my space. And they can't be moved to SD card.
*Sigh*
Click to expand...
Click to collapse
Ditto. Anybody have luck with this yet? B&N is probably about to put these on sale for $39.99 again, and I'd like to pick up a couple more if I can beat the "no space" issue by adding a fully integrated microSD.
Was thinking about grabbing one of these once I got the money. Has anybody tried making an MTK Scatter file to load a custom TWRP in SPFT?