Related
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.
Ok, so I just got my awesome new 6P and have been banging my head into this all night. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't. I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: imgur.com/COwQaaC (sorry, stupid thing wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently >.< )
I know I must be doing something wrong, and HOPEFULLY it's something simple. I've searched and haven't been able to find anything recent (ie, within 90 days) on this issue and am hoping someone can show this poor confused fool some mercy in the form of an answer
paintedtarget88 said:
Ok, so I just got my awesome new 6P and have been banging my head into this all night. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't. I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: imgur.com/COwQaaC (sorry, stupid thing wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently >.< )
I know I must be doing something wrong, and HOPEFULLY it's something simple. I've searched and haven't been able to find anything recent (ie, within 90 days) on this issue and am hoping someone can show this poor confused fool some mercy in the form of an answer
Click to expand...
Click to collapse
It's a new command. Type fastboot flashing unlock
Yeah, tried that one too. That's the problem. When I type it in the image link is what it spits back at me
Need the latest version. Try adb version, and check if it's version 24 or higher.
paintedtarget88 said:
Yeah, tried that one too. That's the problem. When I type it in the image link is what it spits back at me
Click to expand...
Click to collapse
My guide contains everything you need to know, and it should have been easy to find as it's pinned at the top of the general section.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Your adb/fastboot is out of date, update those packages via SDK Manager and you'll be good to go.
Sent from my Nexus 6P
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.
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?
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..