hard reset help password protected and all i get is the nvflash rsd fastboot scrolls. - Xoom Q&A, Help & Troubleshooting

I'm trying to help a member of xoomforums.com but usb debugging isn't checked. Is there a way to unlock it with it being unchecked. He has a xoom that doesn't toggle to android recovery.
hi
yesterday i bought this xoom from a shop returns auction knowing that it was password protected.
but i had read the guides how to hard reset on this forum and thought it would be an easy fix, as i have rooted and installed many different roms on my htc hd desire and my onda vi40 tablet with relative ease.
i got back from the auction and went to hard reset and quickly found out the xoom does'nt have the recovery mode, just 'nvflash' 'rsd' and 'fastboot'
searching more i found there are few like this all wi fi models but no real answer how to fix??
the closest help i found was this guide external factory reset?
i got to the point where you type 'adb devices' into 'cmd' but it doesn't find mine?
but then i don't know what mode i should put my xoom in 'nvflash' 'rsd' 'fastboot' or the password screen?
when my xoom is on the password screen it it shows up on the computer as mz604 (portable media player)
SOMEBODY PLEASE HELP!!!!!!!!!!!!
i hope i have'nt bought myself a heavy paperweight!!!!
for anybody that is worried that i have maybe stole this i have the invoice that i could take a picture of as proof of purchase and post it on here if i have to. it came boxed still with clear protectors on the back....
http://www.xoomforums.com/forum/mot...-all-i-get-nvflash-rsd-fastboot-scrolls.html#

Boot into fastboot, then unlock it (fastboot oem unlock)
You don't actually need to use adb to unlock these devices.

solarnz said:
Boot into fastboot, then unlock it (fastboot oem unlock)
You don't actually need to use adb to unlock these devices.
Click to expand...
Click to collapse
Thanks man.

solarnz said:
Boot into fastboot, then unlock it (fastboot oem unlock)
You don't actually need to use adb to unlock these devices.
Click to expand...
Click to collapse
Not really sure how to use fastboot without the sdk.

Install the sdk then.
It's exactly the same, the only reason you need 'USB Debugging' enabled, is to be able to reboot into the bootloader.
So to skip that, just choose fastboot from menu in the bootloader, which the user has obviously been able to get into.

Thanks, he got it wiped.

Related

[Q] Rooting Issues

Hello,
So I'm trying to unlock and root my tf700t now that my warranty is expired and hope for an ASUS update is diminishing. I downloaded the unlock app from the website and went through the procedure. It took a few weeks and several emails with ASUS support but I think it is unlocked. The reason I say I think its unlocked is whenever I reboot the device, I don't get the message that says its unlocked. The unlock app however says the device is unlocked. So is my device unlocked?
I operated under the assumption that it was and tried to install the twrp recovery using the minimal adb and fastboot exe file. My tablet is recognized by my PC and I put the tablet in fastboot. The error I get when I do that is a writing error. It says writing recovery.... FAILED <remote: <INVALID STATE>>. Does this mean that I am not unlocked or did I do something incorrectly? Any help would be appreciated. I've been working on this for a few weeks and really want to get it moving.
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
berndblb said:
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
Click to expand...
Click to collapse
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Jkeeper18 said:
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Click to expand...
Click to collapse
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
sbdags said:
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
Click to expand...
Click to collapse
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Jkeeper18 said:
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Click to expand...
Click to collapse
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
berndblb said:
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
Click to expand...
Click to collapse
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
I am in the same boat - they think it is unlocked but it is not
The Asus v7 and v8 bootloaders both say "device is unlocked" but the fastbook info shows that it is not. I do not see any unlock inormation after the boot process starts. Also , the unlocker did not automatically restart my tablet. It also asked for my google credentials the first 5 times until the unlock said it worked. Now it does not ask that, it just says that it is unlocked. When I try to fastboot install the TWRP rom, it fails.
(remote - invalid state)
I called Asus and they have my tabler listed as unlocked. They are opening a case so that I can prove that it is unlocked.Then hopfully if they reset that setting, I can re-unlock it...
I was following this thread:
http://forum.xda-developers.com/showthread.php?t=2571542
Is there any work around? Please help!
I want TWRP and CM 10.2 on this slow TF700T tablet.
Thanks!
Jkeeper18 said:
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
Click to expand...
Click to collapse
Well you typed fastboot device not fastboot devices.
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
berndblb said:
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
No, I did not have two-step verification. I hope Asus creates a case and actually looks into it and resets my device's status in their system. It sounds like that is my only option -- a very lengthy and painful one.
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
Well you typed fastboot device not fastboot devices.
Click to expand...
Click to collapse
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Jkeeper18 said:
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Click to expand...
Click to collapse
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
berndblb said:
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
Click to expand...
Click to collapse
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Jkeeper18 said:
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Click to expand...
Click to collapse
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
sbdags said:
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
Click to expand...
Click to collapse
Sorry Im still new at this. Where is the fastboot folder?
Jkeeper18 said:
Sorry Im still new at this. Where is the fastboot folder?
Click to expand...
Click to collapse
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
sbdags said:
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
Click to expand...
Click to collapse
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Jkeeper18 said:
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Click to expand...
Click to collapse
I have followed the TF700 forums for the last year pretty extensively and until about 2 weeks ago never read about anyone having this problem: Asus database having you unlocked, but it actually isn't. Since then I think I've read about 4 cases.
My best guess: It's a problem with the v8 Unlock app or the way their servers store/process the information they get from the Unlock Tool.
That you got to a support person willing to contact Taiwan is a big plus already. Other users just ran into a wall of: We do not support unlocking this device.
So stick with the person you contacted already. Take pictures of your boot process (to document that it does NOT say: This device is unlocked) and they always seem to ask for a screen shot of your About Tablet page with your SN number and MAC address.
Persistence seems to be the key. And luck to get someone at Asus willing to help....
There is no other way to unlock the bootloader. So you would be limited to rooting the tablet which would give you more freedom to tweak it and uninstall bloatware, but you still would have to deal with the slow stock rom.... :fingerscrossed:

I cannot do fastboot commands. Please help, I've been doing this all day!

My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb

Your device is corrupt. It can't be trusted and it will not boot

Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/

Question How would I use fastboot commands to retrieve my lockscreen pin code?

My daughter locked herself out of a nokia mediatek helio p22 by pin lock. During my relentless searching I came across an article showing how to use fastboot cmd commands to get the userdata pin password encryption and how to decipher it by taking out certain things. To be able to enter into the phone. I CAN'T FIND THE ARTICLE NOW!! . The phone itself will not hard reset by hardware keys. Will not enter into recovery mode only fastboot works. I've tried using many screen unlocking software but they all say device not supported o need usb debugging which I can't enable. Fastboot erase userdata ver throws up errors. Does anyone know the fastbood I'm looking for. I've tried all other possibilities that I can find. Any and all help would be greatly appreciated.
Fastboot operates on device's bootloader, not on Android OS. The FRP code is stored within Android file system what can only get accessed by ADB.
jwoegerbauer said:
Fastboot operates on device's bootloader, not on Android OS. The FRP code is stored within Android file system what can only get accessed by ADB.
Click to expand...
Click to collapse
Correct I know. But the device isn't recognized with adb only fastboot recognizes it. I've tried erasing the device with all fastboot commands and everything results in error. When I try to fastboot recovery it has the no command andriod guy and if I press any hardware buttons it reboot back to lock screen. Do u have any ideas on a work around. Or how to access the userdata using cmd promt?
Try to connect phone in USB-MTP mode via a USB-C cable - requires phone supports USB-C.
@Tlink00
Plug up to your PC and do:
sudo fastboot -w (push enter)
That will format data and erase everything on the device, pictures and all. If you are trying to get in your phone I've been able to delete lockscreen.db and a few other directories using TWRP file manager in the past on OnePlus 6t and also on a few Motorola phone's I've owned. But I believe you have to have encryption disabled to go that route. Best to just wipe it with fastboot -w. Just be sure you know your password to your Google account because if your phones signed in and has a Google account on it the password will be required to use the device again.
Tlink00 said:
My daughter locked herself out of a nokia mediatek helio p22 by pin lock. During my relentless searching I came across an article showing how to use fastboot cmd commands to get the userdata pin password encryption and how to decipher it by taking out certain things. To be able to enter into the phone. I CAN'T FIND THE ARTICLE NOW!! . The phone itself will not hard reset by hardware keys. Will not enter into recovery mode only fastboot works. I've tried using many screen unlocking software but they all say device not supported o need usb debugging which I can't enable. Fastboot erase userdata ver throws up errors. Does anyone know the fastbood I'm looking for. I've tried all other possibilities that I can find. Any and all help would be greatly appreciated.
Click to expand...
Click to collapse
I can send you tools that support the Nokia 2.2/2.3 (I'm assuming from chipset) that can erase user data and frp
areallydumbperson said:
I can send you tools that support the Nokia 2.2/2.3 (I'm assuming from chipset) that can erase user data and frp
Click to expand...
Click to collapse
Yeah...that be great! I'm willing to try anything. But the usb debugging isn't enabled.
flash713 said:
@Tlink00
Plug up to your PC and do:
sudo fastboot -w (push enter)
That will format data and erase everything on the device, pictures and all. If you are trying to get in your phone I've been able to delete lockscreen.db and a few other directories using TWRP file manager in the past on OnePlus 6t and also on a few Motorola phone's I've owned. But I believe you have to have encryption disabled to go that route. Best to just wipe it with fastboot -w. Just be sure you know your password to your Google account because if your phones signed in and has a Google account on it the password will be required to use the device again.
Click to expand...
Click to collapse
I've tried the fastboot -w but it comes up with an error about not having permission. Idk about the encryption being disabled or not. And I haven't been successful with TWRP even coming up. Maybe I'm missing something
jwoegerbauer said:
Try to connect phone in USB-MTP mode via a USB-C cable - requires phone supports USB-C.
Click to expand...
Click to collapse
Are you taking about changing it in the PC device manager properties? Bc I don't have access to change it on the device itself. I will try it though. I'll let u know what happens. Thanks for the idea!
Have found it that your Nokia 2.2 supports OTG.
Tlink00 said:
Yeah...that be great! I'm willing to try anything. But the usb debugging isn't enabled.
Click to expand...
Click to collapse
Doesn't matter because it uses fastboot and the way the tool works bypasses permission errors
areallydumbperson said:
Doesn't matter because it uses fastboot and the way the tool works bypasses permission errors
Click to expand...
Click to collapse
Ok thanks! I'll let u know if it works!
Tlink00 said:
Ok thanks! I'll let u know if it works!
Click to expand...
Click to collapse
did it work?
areallydumbperson said:
did it work?
Click to expand...
Click to collapse
I haven't had a chance to try it, yet. But I will really soon. I'm very eager to use it.
areallydumbperson said:
did it work?
Click to expand...
Click to collapse
It says request permission fail. I have phone in fastboot mode
Nvm I GOT IT!!! OMG u are a life savor. Thank you, thank you,thank you!!! I've been working on this for 2 months now. Thank u so much!!
Tlink00 said:
Nvm I GOT IT!!! OMG u are a life savor. Thank you, thank you,thank you!!! I've been working on this for 2 months now. Thank u so much!!
Click to expand...
Click to collapse
Haha np
Having the same issue here, my son locked his nokia with a passcode he can't remember. Unable to get it into recovery mode, stuck on "no command"
djekl said:
Having the same issue here, my son locked his nokia with a passcode he can't remember. Unable to get it into recovery mode, stuck on "no command"
Click to expand...
Click to collapse
should be able to get in by pressing power + volume up or power + volume down at that no command screen
Tried that, just got back from the local phone repair shop, and they were unable to factory reset it also, and get past the no command screen.

T-Mobile OP8 5g (IN2017); I have my unlock token from T-mobile, but I'm unable to flash it.

Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.

Categories

Resources