Database Info

[TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)

Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!​I'm NOT responsible if you bork your tablet because you can't follow simple instructions!​
INSTRUCTIONS:
1) Download and install Win 7 DRIVERS
2) Download and extract Nexus7_2013_KTU84P_Restore.zip WIFI Flo, or Nexus7_Deb_KOT49H_Restore.zip for LTE version Deb, or Nexus7_Deb_KVT49L_Restore.zip for Verizon LTE Model
3) Turn on your tablet, and connect your tablet to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus7_2013_KTU84P_Restore.zip WIFI Flo, or Nexus7_Deb_KOT49H_Restore.zip for LTE version Deb, or Nexus7_Deb_KVT49L_Restore.zip for Verizon LTE Model
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your tablet will not boot and you need to restore, boot your tablet into fastboot (volume down and power) and click the "Dead_Nexus7.bat" file found in the folder.
For those that couldn't find their azzes if a target was painted on it, here's a link to the video.
http://www.youtube.com/watch?feature=player_embedded&v=hectdvR9Y6c
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!​
FAQ:
1) You will have to relock your bootloader after you restore. Tablet in fastboot and connected to pc open up command prompt in the folder where these files reside and type: "fastboot oem lock".
2) You will be unrooted after this procedure
3) Your bootloader must be unlocked before using this utility.
If you can't handle these simple instructions, pickup one of these.
If you want to use pre-rooted images for FLO download this toolkit (will restore your tablet pre-rooted)
Nexus_7_Restore_Flo_Rooted.zip
CHANGE LOG:
06/22/14:
Updated With Images KTU84P Flo Wifi (Android 4.4.4)
06/04/14:
Updated With Images KTU84 Flo Wifi (Android 4.4.3)
12/12/13:
Updated With Images KOT49H Flo/Deb 4.4.2
11/20/13:
Updated With Images KRT16S Flo/Deb 4.4
11/15/13:
Updated With Images KRT16o Flo 4.4
11/14/13:
Updated With Images KRT16o Deb 4.4
10/13/13:
Updated With Images JLS36i Deb 4.3.1
09/19/13:
Updated With Images JSS15R Flo
09/16/13:
Updated With Images for Deb (LTE)
08/23/13:
Updated With Google Factory Images JSS15Q
08/09/13:
Updated With Google Factory Images JSS15J
08/08/13:
Uploaded new version with updated Bat files so they reflect being in "fastboot" before continuing for the few that couldn't follow a simple video

Is that a rooted image that you have linked?

dexgen said:
Is that a rooted image that you have linked?
Click to expand...
Click to collapse
First sentence in the OP:
"Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!"

ATGAdmin said:
First sentence in the OP:
"Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!"
Click to expand...
Click to collapse
So it'll end up relocking your device? I didn't see any OEM lock command in the bat files.

dexgen said:
So it'll end up relocking your device? I didn't see any OEM lock command in the bat files.
Click to expand...
Click to collapse
This is to restore your tablet back to the way it was when you first turned it on...just what is it that you don't understand??
I think you want this:
http://forum.xda-developers.com/showthread.php?t=2380268

ATGAdmin said:
Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!​
INSTRUCTIONS:
1) Download and install DRIVERS
2) Download and extract Nexus 7 Restore.zip
3) Turn on your tablet, and connect your tablet to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus 7 Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your tablet will not boot and you need to restore, boot your tablet into fastboot (volume down and power) and click the "Dead_Nexus7.bat" file found in the folder.
Click to expand...
Click to collapse
thank you so much! now I can get a warranty exchange from Best Buy, since I have 2 black dots under the screen :crying:

I guess he is asking will bootloader be locked ?

munchy_cool said:
I guess he is asking will bootloader be locked ?
Click to expand...
Click to collapse
And that was answered in the very first sentence of the OP.
Sent from my Nexus 7 using xda premium

dexgen said:
So it'll end up relocking your device? I didn't see any OEM lock command in the bat files.
Click to expand...
Click to collapse
munchy_cool said:
I guess he is asking will bootloader be locked ?
Click to expand...
Click to collapse
bootloader will not be locked when using this process. but it is easy to lock the bootloader
in fastboot, type this in the command prompt:
Code:
fastboot oem lock

Is this a windows only command or can I run this on a Mac? I have ADB and Fastboot running on the mac which is how I installed TWRP and rooted.
Thanks

androidfr33k said:
Is this a windows only command or can I run this on a Mac? I have ADB and Fastboot running on the mac which is how I installed TWRP and rooted.
Thanks
Click to expand...
Click to collapse
Sorry, PC only.
Sent using XDA premium on my Nexus 7 (2) tablet.

0.0 said:
bootloader will not be locked when using this process. but it is easy to lock the bootloader
in fastboot, type this in the command prompt:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Then technically you can't say the device is restored to "when it was first turn on". I think fresh devices all have the bootloader locked.

You guys are worrying way too much about the bootloader. Its a nexus. It takes one simple command in fastboot to unlock it. Again, it's a nexus. Its meant to be easy to unlock so developers can mess with it.
This isn't some HTC or Samsung on Verizon.
Bootloader is not an issue.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Why in adb it says my device is offline??
Sent from my Nexus 7 using Tapatalk 4 Beta

casonswag said:
Why in adb it says my device is offline??
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
make sure USB debugging is checked.
if you don't know how to turn on USB debugging, go to settings > about tablet> clicked like 7 times on the build number. it should then say you're a developer
go back and into "developer options" and it will be there

0.0 said:
make sure USB debugging is checked.
if you don't know how to turn on USB debugging, go to settings > about tablet> clicked like 7 times on the build number. it should then say you're a developer
go back and into "developer options" and it will be there
Click to expand...
Click to collapse
I have that checked adb sees my device but it says offline for some reason
Sent from my Nexus 7 using Tapatalk 4 Beta

androidfr33k said:
Is this a windows only command or can I run this on a Mac? I have ADB and Fastboot running on the mac which is how I installed TWRP and rooted.
Thanks
Click to expand...
Click to collapse
Mac can use the code
zeroxia said:
Then technically you can't say the device is restored to "when it was first turn on". I think fresh devices all have the bootloader locked.
Click to expand...
Click to collapse
trust me, it isn't hard to unlock and lock the bootloader. it's really, really simple. Idk how to express how simple it is to lock and unlock
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
casonswag said:
I have that checked adb sees my device but it says offline for some reason
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
maybe the cable is bad, or the USB port is bad
I find that using one cable doesn't work and using another one does. so just mess with the cables

0.0 said:
Mac can use the code
trust me, it isn't hard to unlock and lock the bootloader. it's really, really simple. Idk how to express how simple it is to lock and unlock
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
maybe the cable is bad, or the USB port is bad
I find that using one cable doesn't work and using another one does. so just mess with the cables
Click to expand...
Click to collapse
I tries my other cord and other usb port on my laptop but still saying offline this sucks i used the same chord and usb ports on my first gen n7 and it worked fine this weird
Sent from my Nexus 7 using Tapatalk 4 Beta

casonswag said:
I tries my other cord and other usb port on my laptop but still saying offline this sucks i used the same chord and usb ports on my first gen n7 and it worked fine this weird
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
did you update the android SDK and drivers? possibly only the drivers need to be updated

0.0 said:
did you update the android SDK and drivers? possibly only the drivers need to be updated
Click to expand...
Click to collapse
Yessir just downloaded the nexus7 root zip from zedo max which has the latest sdk files but the drivers im not sure how to do that i went through the steps to manually find the android_winusb file but its not letting me install it
Sent from my Nexus 7 using Tapatalk 4 Beta

Root Memo Pad 10 FHD

Hi,
is ist possible to root the new android asus memo pad 10 fhd with intel z2560 soc (x86) and android 4.2.2?
There are no recovery images avaliable yet.Even source code.
But id like to get root for it.
Does somone know how ?
So please report it!
There are so many german people how like to root it.
Please help
Big thanks
Bye

I searched for several hours and tried numerous different rootkits, but none of them worked.
There seems to be someone providing a method for Memo Pad 7 HD, but I didn't want to try it out of fear that it would semi-brick my device (particularly the bootloader).
I love the device though. Only problem is that the screen is too reflective.

My friend,
have a look at my post inside german forum!
I rooted the memo pad successfully
http://www.android-hilfe.de/asus-me...5825-howto-root-fuer-das-memo-pad-10-fhd.html
In some days i will translate it to english
Nice flash.

Hi there. I'd like to ask how is the translation going? I tried to read the whole procedure in German with Google translator, and couldn't get anything clear enough to try to do it...
Oh, and no pressure meant!
Thank you very much in advance!!

1.Download the two links in the post (system.img.gz and superuser.apk)
Put system.img.gz and superuser.apk in the same folder as adb.exe.
2. Put the tablet into bootloader mode (Power+Vol Up)
3. Run these commands in command prompt with administrator priviledges:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash system system.img.gz
5. Reboot and again run in command prompt
adb install Superuser.apk

matt1513 said:
1.Download the two links in the post (system.img.gz and superuser.apk)
Put system.img.gz and superuser.apk in the same folder as adb.exe.
2. Put the tablet into bootloader mode (Power+Vol Up)
3. Run these commands in command prompt with administrator priviledges:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash system system.img.gz
5. Reboot and again run in command prompt
adb install Superuser.apk
Click to expand...
Click to collapse
Hi, my friend
Anyone can provide more detail of the root process?
Many thanks!!!!!

Thank you very much, Matt, for the info. I think I'd better wait a little bit longer to gain root access, not really needing root right now..
Alright, I have to confess I am not sure I could get it rooted with that method, still a newbie! xD. I will wait for a easier one-click root.
Thank you very much though!
Enviado desde mi GT-N7000 usando Tapatalk 4

Wohoo!!
Grimmlocks said:
Thank you very much, Matt, for the info. I think I'd better wait a little bit longer to gain root access, not really needing root right now..
Alright, I have to confess I am not sure I could get it rooted with that method, still a newbie! xD. I will wait for a easier one-click root.
Thank you very much though!
Enviado desde mi GT-N7000 usando Tapatalk 4
Click to expand...
Click to collapse
I just rooted using the commands above, only difference is i used the latest system_4_6_2_root.img file since i've upgraded my pad to 4.6.2.
Im root again!! Thanks guys

O. T. Theoretically this device can even run windows 8, can't it?
Back in thread. I think it's even easier than what described above:
1) Make sure that your device is updated with the last firmware 4.6.2, check the OTA updates on your tablet.
2) If you don't have it already installed, download and install fastboot here.
3) Download and install Intel USB drivers from here.
4) Download the rooted system image from here and move in the directory where you have fastboot installed (see point 2).
5) Reboot you tablet in download mode by pressing Power + vol up.
6) Launch a command window and type fastboot flash system system_4_6_2_root.img.gz
Voila, your device is rooted, you just need to download from the market the SuperSU app.
I didn't lose any setting / application.
All the information is taken from the german forum. Thanks to them.

linusplus said:
O. T. Theoretically this device can even run windows 8, can't it?
Click to expand...
Click to collapse
yes it should be possible, do you maybe know where to get windows 8 with touch support for tablets?
And how come we dont have a forum for our tab on xda developers?
Sent from my ME302C using xda premium

QuanticZero97 said:
yes it should be possible, do you maybe know where to get windows 8 with touch support for tablets?
Click to expand...
Click to collapse
I don't know if it is that easy. I think the bootloader should somehow support the Windows boot, even if we had the Windows 8 installation media.

These just came out in the US and mine should be here tomorrow. Excited to get her rooted! Hope we get a thread/some development!

Got my memo pad fhd 10! I personally think it's pretty amazing. Stock launcher is lacking but with nova is a LOT better. Still need to root as I would like to freeze some of the junk. It's very snappy and the screen looks great. Extremely happy with the purchase but would love to see some devs jump on it.
Also, just did some browser hopping. Boat browser is complete butter on this. Glassy smooth and quick, much better than chrome.

i need usb driver for memopad 10 fhd
jee82 said:
I just rooted using the commands above, only difference is i used the latest system_4_6_2_root.img file since i've upgraded my pad to 4.6.2.
Im root again!! Thanks guys[/QUO
usb driver can't setup in my computer(windows 7) , so enter"fastboot erase cache", stay "waiting for device" , can you send me for your usb driver?please!
Click to expand...
Click to collapse

system img gz cannot be reached
Unfortunately the link you mention to get system[dot]img[dot]gz is not valid anymore.
can you tell me where I can find it, or if any system[dot]img[dot]gz file can fit for asus fhd 10, android version 4.2.2?
Thanks in advance
Jacques
djsven said:
My friend,
have a look at my post inside german forum!
I rooted the memo pad successfully
455825-howto-root-fuer-das-memo-pad-10-fhd.html
In some days i will translate it to english
Nice flash.
Click to expand...
Click to collapse

OTA Updater misery
Hello Linus Plus
I run Android 4.2.2
I am trying to follow your process. Phases 2,3,4,5 are ok
but the first is not:
when I go to OTA update I get:
"Unsupported ROM
The ROM developer has not enabled support for the OTA
updater. ..."
What should I do?
Thanks for your help
Thanks
Jacques
linusplus said:
O. T. Theoretically this device can even run windows 8, can't it?
Back in thread. I think it's even easier than what described above:
1) Make sure that your device is updated with the last firmware 4.6.2, check the OTA updates on your tablet.
2) If you don't have it already installed, download and install fastboot here.
3) Download and install Intel USB drivers from here.
4) Download the rooted system image from here and move in the directory where you have fastboot installed (see point 2).
5) Reboot you tablet in download mode by pressing Power + vol up.
6) Launch a command window and type fastboot flash system system_4_6_2_root.img.gz
Voila, your device is rooted, you just need to download from the market the SuperSU app.
I didn't lose any setting / application.
All the information is taken from the german forum. Thanks to them.
Click to expand...
Click to collapse

Hi,
i will create a new one.
Because 4.7 is just release
bye

If I use Pro SuperSu I update without losing root?

My mistake, it works
I finally understood that 4.6.2 refers to the build number and not to the Android version.
Therefore I could go through all of the process and the device is rooted now.
thanks a lot, your process is very easy
Jacques
Jacques Siboni said:
Hello Linus Plus
I run Android 4.2.2
I am trying to follow your process. Phases 2,3,4,5 are ok
but the first is not:
when I go to OTA update I get:
"Unsupported ROM
The ROM developer has not enabled support for the OTA
updater. ..."
What should I do?
Thanks for your help
Thanks
Jacques
Click to expand...
Click to collapse

I was foolish enough to upgrade from rooted 4.6.2 to 4.7.0 and i keep getting crashes.. the worst crash is the keyboards.. none of them work.. cant do anything with my memopad at all.. anyone know if it's possible to re-flash the cracked 4.6.2 image?? On asus site they say that the firmware u download from there cant be used to downgrade... really hope thats wrong since the latest firmware on their site is 4.6.2 and i've got 4.7.0 which i got through OTA

[Q] Nexus 5 No OS installed!

Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!

Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5

if you can enter fastboot just flash a ROM through it ...you'll be fine

sirajgoku said:
if you can enter fastboot just push a ROM through adb ...you'll be fine
Click to expand...
Click to collapse
Massive contradiction in terms - you can't use adb commands in fastboot, you use fastboot commands in fastboot
Sent from my Nexus 5 using XDA Premium 4 mobile app

If this were me I would adb push a custom rom via recovery. Although I love stock, if I were in your shoes I would go with cataclysm or slim.

mmavani said:
Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!
Click to expand...
Click to collapse
Have you tried flashing the factory image? This should be a requirement before coming on here and asking for help.

instruction
El Daddy said:
Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5
Click to expand...
Click to collapse
can you send me guide? instructions? video?

mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
The sticky threads in general and Q&A would be a good place to look.
Sent from my Nexus 5

mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
Ay yay yay, I hear kittens dying.

This is a perfect example of why toolkits aren't beneficial to new users. If the OP had rooted manually, he'd be familiar with both fastboot and adb, and would be able to solve this issue easily.
Toolkits should only be used by experienced users, in order to save time... NOT as a pacifier for the uninitiated. :-\
Sent from my Nexus 5 using Tapatalk

@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk

Fixed
jjhiza said:
@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's already fixed.
Thanks for your help

Jacked myself up - help please

o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S

you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer

meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.

bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.

So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905

aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?

RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.

RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.

Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.

I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.

I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).

Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app

Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.

TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5

Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk

Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.

Glad you got it sorted.

Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.

Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?

Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.

US Sprint u11 relock bootloader difficulty, need assistance please bootloader gurus.

Why is it so hard to relock the bootloader ? I've pretty much followed ALL the threads for the u11 and even combing the 10 threads a bit, please forgive my noobness if this is easily fixed.
I'd like to at least acheive a "relocked" state so I can use android pay. When I try to relock it I get this:
C:\android\platform-tools>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
OKAY [ 0.065s]
finished. total time: 0.066s
Also OEM unlock is greyed out in the options. I have tried all kinds of permutations of the syntax and even HTC_Fastboot.exe.
What is this killswitch business trying to tell me, and what do I do ? Please spell it out step by step as I am not a developer, just tinker sometimes.

royalcrown said:
Why is it so hard to relock the bootloader ? I've pretty much followed ALL the threads for the u11 and even combing the 10 threads a bit, please forgive my noobness if this is easily fixed.
I'd like to at least acheive a "relocked" state so I can use android pay. When I try to relock it I get this:
C:\android\platform-tools>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
OKAY [ 0.065s]
finished. total time: 0.066s
Also OEM unlock is greyed out in the options. I have tried all kinds of permutations of the syntax and even HTC_Fastboot.exe.
What is this killswitch business trying to tell me, and what do I do ? Please spell it out step by step as I am not a developer, just tinker sometimes.
Click to expand...
Click to collapse
Are you running the command in bootloader or download mode? I could be wrong, but I believe it needs to be ran from download mode.

bluemooncityzen225 said:
Are you running the command in bootloader or download mode? I could be wrong, but I believe it needs to be ran from download mode.[/QUOTE
that is correct, must be in download mode
Click to expand...
Click to collapse

Aldo101t said:
bluemooncityzen225 said:
Are you running the command in bootloader or download mode? I could be wrong, but I believe it needs to be ran from download mode.[/QUOTE
that is correct, must be in download mode
Click to expand...
Click to collapse
Thank you guys, I am putting the phone into download mode using the hardware keys. In bootloader mode, the phone just ignores any kinds of ADB commands entirely (I believe this is the way it should be on the U11).
Also I am using the factory cable. Also tried USB 2 and 3 ports.
What I did was unlock the bootloader in order to replace the Roboto system font while keeping Sense as a launcher (I actually like Sense). I was having really flakey WIFI and Bluetooth and was thinking about returning the phone, so I extracted the zip from the stock Sprint Ruu and haven't touched the system.
Click to expand...
Click to collapse

Are you using adb commands in fastboot? Because you should be using fastboot commands. More specifically:
To test if your phone is recognized, fastboot devices .
To lock bootloader, fastboot oem lock.
Edit: I didn't read the OP. That's what I get for using XDA at work.

You also might have better luck with HTC's build of fastboot
https://www.htcdev.com/process/legal_fastboot_win
EDIT: Re-read OP, sorry. I'll leave this link here anyway for future reference...
EDIT2: (bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp < Interesting? Do you have full stock firmware currently?(boot+recovery+system)
EDIT3: Yeah looks like you need to do an RUU first before relocking in most situations. Assumedly to ensure FRP remains intact afterwards.

you can simply use Magisk for android pay...or is that not a thing anymore?

Fixed guys !!
For future reference:
Yes, I used fastboot as well as htc_fastboot.
I bet you guys will never guess WTF took care of the relock AND the killswitch error.
ALL I DID WAS PULL THE MICRO SD CARD AND THE PHONE LOCKED AND BEHAVED LIKE IT'S POS' TO. NO, the SD card wasn't set up as internal or expanded storage, I am guessing something to do with the changes to the android file system where it creates symbolic copies of sd card files on internal flash. You know that whole cant write to the SD card stuff from android lollipop on up ?
TWRP gave me the idea because I flashed it the first time with no SD card, just took a shot in the dark and crossed off that variable !
I have seen some suggestions to reflash with a custom ROM, and run RUU. Also, have seen some posts that said that the 5 second unlocked screen will still show. Disabling reset protection was also suggested.
No need for the custom firmware, then wipe and RUU suggestion.
The 5 second screen doesn't show and android pay seems to work properly. Gonna check and let you all know.

royalcrown said:
For future reference:
Yes, I used fastboot as well as htc_fastboot.
I bet you guys will never guess WTF took care of the relock AND the killswitch error.
ALL I DID WAS PULL THE MICRO SD CARD AND THE PHONE LOCKED AND BEHAVED LIKE IT'S POS' TO. NO, the SD card wasn't set up as internal or expanded storage, I am guessing something to do with the changes to the android file system where it creates symbolic copies of sd card files on internal flash. You know that whole cant write to the SD card stuff from android lollipop on up ?
TWRP gave me the idea because I flashed it the first time with no SD card, just took a shot in the dark and crossed off that variable !
I have seen some suggestions to reflash with a custom ROM, and run RUU. Also, have seen some posts that said that the 5 second unlocked screen will still show. Disabling reset protection was also suggested.
No need for the custom firmware, then wipe and RUU suggestion.
The 5 second screen doesn't show and android pay seems to work properly. Gonna check and let you all know.
Click to expand...
Click to collapse
** just to keep my promise Android Pay passes the test and runs fine, haven't actually used it at a register yet, but it sets up and passes verification.