hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
The USB connector socket at the phone might not make a proper contact with the USB plug. Make sure they connect properly. You may try another cable, or have a look at your USB socket and compare it to another. Check out particularly the little horizontal part in the USB socket.
Make sure you're in bootloader/fastboot mode before attempting to connect in fastboot. Fastboot cannot detect your phone, make sure your udev related settings are appropriate. Check on a Linux PC: https://source.android.com/source/initializing.html Configuring USB Access section.
If after this your phone will not be recognized by fastboot, please post the output of the following command (as root), after seconds after connecting the phone in fastboot mode:
Code:
tail /var/log/messages
Harbb said:
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
Click to expand...
Click to collapse
fastboot does not show my device. I go into bootloader using adb reboot bootloader because my stupid power button wont work, thats why i want to sent it in to get fixed.
If drivers are properly installed this might not be working because the power button is stuck in or something. Not sure what to try to sort it out if that's the case.
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
bjuderas said:
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
Click to expand...
Click to collapse
if you read the first post it says that fastboot doesnt work
mikeydubbs said:
if you read the first post it says that fastboot doesnt work
Click to expand...
Click to collapse
Sorry, didn't read it right!
And I'm sorry, but I don't know the solution for your problem!
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
p1gp3n said:
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
Click to expand...
Click to collapse
yeah i have and i tried using my laptop, and ubuntu 11.10
this sucks so much
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
shahravi94 said:
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
Click to expand...
Click to collapse
so do you think as long as its not rooted they wont care?
yup! i flashed a stock image so it was unrooted and sent it in. they fixed it up for me
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Hi, I know this thread is old but I was having the same problem relocking my nexus 4 after installing stock Android 4.4.3 KitKat.
I'm using Nexus Root Toolkit, I don't know what tools you're using to lock your nexus S boblem ut this very easy to use it downloads the drivers and what ever you need to lock, unlock or flash stock and custom roms for any Nexus device.
So my problem was that I would launch OEM Lock on Nexus Root Toolkit and it would detect the device, reboot in Fastboot mode and it would proceed just fine but after saying "Launching TWRP.... something" it would reboot the phone and say to me "Waiting for device" untill it would time out.
I found out that when the program(NEXUS ROOT TOOLKIT) asked me to download a TWRP IMG files, I said no everytime because I didn't think I'd need it. So after trying 5 times, I allowed it to download it and i retryed to OEM Lock it and MAGIC!
Somewhere in the process of Locking the rom it is going to need the TWRP File so allowing the program to download it solved it for me.
I don't know if this will help you or if you still have the same phone, but if you do have use Nexus Root Toolkit and download all it asks and you'll be fine.
Good Luck.
"waiting for device" forever when "fastboot oem unlock:
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
I have the same exact problem.
ADB works fine when the phone is up & running, so I am suspecting a driver compatibility problem when the phone is in "FASTBOOT MODE".
I tried to install the "Universal Naked Driver 0.73 (Compatible with Nexus 5, 4, 7, 10 and S)" but Windows 7 64-bit refuses to pick it up. I use the Device Manager method which shows (when the phone is in "FASTBOOT MODE"):
Code:
"Other Devices
> Android 1.0"
When the phone is up & running, Device Manager shows it as:
Code:
"Android USB Devices
> SAMSUNG Android Composite ADB Interface"
Any idea how to proceed from here?
-----
Update: After a day went by, I searched Google some more and found a thread that describes exactly my problem:
http://forum.xda-developers.com/nexus-s/help/nexus-s-root-windows-requests-android-1-t878579
Which led me to:
http://forum.xda-developers.com/nex...oader-nexus-s-t875580/post9861928#post9861928
Which led me to:
http://pdanet.co/a/
I am rushing to try this now...
-------
Success!
~> fastboot oem unlock
...
OKAY [ 18.734s]
finished. total time: 18.734s
Click to expand...
Click to collapse
nunojpg said:
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
Click to expand...
Click to collapse
It helped. Thanks!
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
ericsundiu said:
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
Click to expand...
Click to collapse
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
ericsundiu said:
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
Click to expand...
Click to collapse
Unlocking and rooting are two different things. There is no known root method at this time for the 10.6.1.14.10 firmware. The Unlock Tool should still work.
I don't think it's a question which firmware you have - sometimes it works like a charm and other users cannot unlock at all due to incorrect or incomplete S/N database on Asus servers. At least I have not heard anything that people have trouble unlocking after the last update.
Just download the latest version, v8 I think, install and run it. The worst that can happen is it fails.
Do yourself a huge favor and educate yourself thoroughly before you try to flash custom software to the tablet.
There is little risk in flashing a custom rom IF you do it right. But yesterday night I tried to help someone who did it wrong and hard bricked his tablet. Read 3 times, ask twice, flash once!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot
Click to expand...
Click to collapse
For flashing via adb and the staging partition, Android must be rooted. Fastboot works without root.
I did a clean wipe of my tablet and installed 10.6.1.14.10 onto my tablet.
I have unlocked the bootloader, but when booting up I then have the default recovery and rom supplied by Asus with no root.
I tried motochopper and debugfs method, and as described above neither work, the cmd prompt windows just record failures.
Read this forum regarding what is what (fastboot, root, unlocked etc.) and why you do them
http://forum.xda-developers.com/showthread.php?t=1833212
The way I gave root to the stock rom was by loading into fastboot mode and pushing a twrp image to my tablet off CHROMI rom site. I then used that to root the system. To be honest I did not need to root as I could have just then flashed the CHROMI custom rom which comes with SU anyway....
Get fastboot into a folder and also copy the TWRP recovery img inside the fastboot folder
Attach your device to the PC
Start fastboot mode by switching off your tablet then switching on in bootloader by holding down power on and volumn down
Connect tablet to PC (need approperiate drivers)
Open cmd prompt as admininstrator and goto directory with recovery image in the fastboot folder
Type the following commands:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot (though I don't think i typed this if honest, struggling to remember)
Unplug tablet from the PC and reboot into recovery mode
If you got the image of twrp from CHROMI site which includes bootloader also, i think it includes SU, therefore just exit and close recovery and it should ask to install SU. Select yes
Reboot the device
Your device is now rooted, though think you need to run SU in the tablet to get it fully setup.
Sorry this is not 100% perfect, I will recall what I did tonight when at home in front of PC with files.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Click to expand...
Click to collapse
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
M1ster1 said:
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
Click to expand...
Click to collapse
You can try to install from your system, not stock recovery. You need to boot your system normally and look in the lower right corner at your notification. It should notify you that their is an update for you. When you click on it, it will walk you through the update process. You need to make sure that you have only one zip file in your directory which is the Asus firmware that you want to update.
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
LetMeKnow said:
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
Click to expand...
Click to collapse
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (right click on your device, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your phone.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
Good job! Congrats!
And thank you for putting this guide together. That's what I call sharing! :victory:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
It is a nice written How to do list, good job... :good:
You can add these command for fastboot to your list instead of using the power button and volume down..
> fastboot reboot-bootloader # Exit fastboot and reboot into bootloader.
> fastboot reboot # Exit fastboot and reboot to your system
Good job.. :good:
FAILED (InvalidSize)
I am attempting to install a ROM on my Transformer Infinity as it pretty much sucks these days but am a complete NOOB. Have never attempted this with any of my phones or tablets, but figure I would try since these directions are so detailed. After following most the steps you have listed, I get the error below in the command prompt. Can someone please help, I tried searching XDA and Google to no avail. If possible please be as basic and speak in layman's terms b/c all this technical jargon goes right over my head. Thank you in advance!!!
Step followed:
- Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
epps720 said:
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
Click to expand...
Click to collapse
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
epps720 said:
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
Click to expand...
Click to collapse
Actually yes.
Just read in another thread about someone having the same problem as you, getting the incorrect file size error.
Download the TWRP 2.5 blob and try it with that file. I have no idea why, but TWRP 2.6 may cause this error.
At least that bloke got the recovery installed that way. Once you have TWRP, it's easy to upgrade to the latest version.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
I have no idea why, but TWRP 2.6 may cause this error.
Click to expand...
Click to collapse
The blob for TWRP 2.6.3 is bigger than the recovery partition. 2.6.1 should work.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Ive had the same question as the OP, i also have a .10 version, i have a US sku, and i downlaoded said associating item but when I went but when i go to either do it with sd, or intewrnal sd, or how ever. through manual or through android, either method both resulted in error when trying to downgrade, i dont know if its because its a downgrade or what.
Ive some linux experience over the years, and have rooted and run custom roms in the past. im trying to achieve the same as the OP, fix my lag, and more options and tweaks.
I have the .zip of the rom i want whitch i found I liked the xcromi rom, so I downloaded it. so, i can put that in and name it what and how do i do the update than through the volume down + pwr combo into that menu? (not sure what its called) but i can't do sideloads because i can't havbe the ultity to sideload without rooting and i can't root with .10, so i have been trying to get past this single step all night and this morning now.
@M1ster1
Thanks for posting this guide. It doesn't do a perfect job however on the TF700t running Android build 10.6.1.14.10. Tried to use the "fix permissions" option in ROM Manager but failed due to insufficient permissions. I installed CWM Superuser and cleaned up the version of SuperSU (prefer Superuser anyhow)... updated the binaries and still no love when trying to correct the permissions, despite all tests showing the device fully rooted.
After a day of pulling my hair out I finally came across vRoot and after even longer found a guide in English. Ran that, again swapped out the Superuser that went with vRoot and again reinstalled Superuser. Used Ti to install as system app. After reboot ROM Manager was finally able to correct permissions and all is golden again.
Hi ,
My Transformer has 10.6.1.14.10 and I am trying to install TWRP thru fastboot as per "M1ster" instructions.
these are the results I see from my command prompt.
C:\Users\Ken>fastboot devices
015d2bbce7041e07 fastboot
C:\Users\Ken>cd c:\Android-adb
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
OKAY [ 0.066s]
writing 'recovery'...
OKAY [ 3.374s]
finished. total time: 3.441s
c:\Android-adb>
after I reboot and select RDK , i get the sick droid error,
I feel like I have missed something, hopefully somebody can point me in the right direction
Thanks
helihaole said:
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
Click to expand...
Click to collapse
Your "twrp.blob" apparently doesn't contain a recovery - it should be around 6 to 8 MB.
Hi guys here is a we guide on how to successfully de-brand you 3 device in order to get OTA updates working and installing correctly.
1. You will need adb and fastboot installed on your system in order to do the process.
For windows systems you can refer to this thread on installing adb and fastboot
https://forum.xda-developers.com/showthread.php?t=2588979
For linux based systems you can install both using this command
For Debain Based i.e Ubuntu, LinuxMint etc...
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
For Centos or Fedora you can use this command:
Code:
sudo yum install android-tools
2. Download the required Global Razer factory image
cheryl-global-851.zip
Mirror:
https://mega.nz/#!LFRhSR5Y!qAiyf3q3gmSt5bFtVd528qWAWmempSJLg3nyTjHxkw4
3. Unlocking the bootloader
WARNING: THIS PART FORMATS YOUR USER DATA SO MAKE A BACKUP OF YOUR INTERNAL STORAGE BEFORE PROCEEDING.
After you have everything installed and the image downloaded you will need to unlock two parts of the bootloader snippets from Razers site:
Unlocking the Bootloader
Enable OEM Unlocking
If necessary, enable OEM unlocking on the Razer Phone:
On Android 7.x, go to Settings > About phone > tap Build number seven (7) times.
Tap the back button once you see the “You are now a developer” message appear.
Tap Developer options, tap toggle OEM unlocking to enable.
Enter Download Mode
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Unlock the Bootloader
Run this command: fastboot flashing unlock
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
Unlock the Bootloader Critical Partitions
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
The unlock can be performed with this command: fastboot flashing unlock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
4. Flashing the image.
Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
Connect your Razer Phone to your computer over USB.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
Open a terminal on your computer and navigate to the unzipped system image directory.
Execute the flash_all.sh script if on linux or on windows run flash_all.bat. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
Once the script finishes, your Phone will reboot.
5. Covering up what you have done i.e removing the error during boot.
Locking the Bootloader
Locking the bootloader is recommended for security reasons. Some applications will not work with an unlocked bootloader.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader Enter Download Mode:
Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Lock the critical partitions of the Bootloader first by running this command: fastboot flashing lock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Locking the remainder of the bootloader can be performed with this command: fastboot flashing lock
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
Once you have done all that your phone will be de-branded
thanks to @Xplicit1992 for tipping me off that otas work after flashing the MR1 global image
OTA update found but fail to update. (Tested from MR2)
LttHckr said:
OTA update found but fail to update.
Click to expand...
Click to collapse
Did you flash the correct global image posted above cause I know it works as I tested before I made the thread and the OTA downloads and installed just fine for me
eoghan2t7 said:
Did you flash the correct global image posted above cause I know it works as I tested before I made the thread and the OTA downloads and installed just fine for me
Click to expand...
Click to collapse
I've tested from MR2, OK I will try again on MR1.
LttHckr said:
I've tested from MR2, OK I will try again on MR1.
Click to expand...
Click to collapse
@eoghan2t7 I try to flash from MR1 and OTA update to MR3 success thank you.
I bought the phone on contract with 3. If I do this will it break VoLTE ("4G Super Voice")?
Hey guys, when trying to push the file over, nothing happens. If i dont do the fastboot -i 0x1532 it gets stuck on waiting for device. i dont know what to do now
?
PS C:\Users\usera\Downloads\cheryl-global-851> fastboot -i 0x1532 flash partition:0 gpt_both0.bin
target reported max download size of 536870912 bytes
sending 'partition:0' (44 KB)...
OKAY [ 0.003s]
writing 'partition:0'...
OKAY [ 0.093s]
finished. total time: 0.097s
PS C:\Users\usera\Downloads\cheryl-global-851>
---------- Post added at 12:21 PM ---------- Previous post was at 12:08 PM ----------
C:\Users\usera\Downloads\cheryl-global-851>set fastboot_cmd=fastboot
C:\Users\usera\Downloads\cheryl-global-851>fastboot flash partition:0 gpt_both0.bin
< waiting for device >
thats what I get, and it doesnt move from there
comady25 said:
I bought the phone on contract with 3. If I do this will it break VoLTE ("4G Super Voice")?
Click to expand...
Click to collapse
Honestly don't know how to test volte that.
userade123 said:
Hey guys, when trying to push the file over, nothing happens. If i dont do the fastboot -i 0x1532 it gets stuck on waiting for device. i dont know what to do now
?
PS C:\Users\usera\Downloads\cheryl-global-851> fastboot -i 0x1532 flash partition:0 gpt_both0.bin
target reported max download size of 536870912 bytes
sending 'partition:0' (44 KB)...
OKAY [ 0.003s]
writing 'partition:0'...
OKAY [ 0.093s]
finished. total time: 0.097s
PS C:\Users\usera\Downloads\cheryl-global-851>
---------- Post added at 12:21 PM ---------- Previous post was at 12:08 PM ----------
C:\Users\usera\Downloads\cheryl-global-851>set fastboot_cmd=fastboot
C:\Users\usera\Downloads\cheryl-global-851>fastboot flash partition:0 gpt_both0.bin
< waiting for device >
thats what I get, and it doesnt move from there
Click to expand...
Click to collapse
For best results I recommend using a Ubuntu live disk when flashing the images or make a small dual boot on your PC dedicated to flashing your phone.
Hey another guy from Belfast
Nice guide man I'm glad people can finally get rid of the three ROM
Roxas598 said:
Hey another guy from Belfast
Nice guide man I'm glad people can finally get rid of the three ROM
Click to expand...
Click to collapse
Tell me about it now updates should be instantly available to us Belfast folk ?
eoghan2t7 said:
Tell me about it now updates should be instantly available to us Belfast folk
Click to expand...
Click to collapse
Just got my Razer Phone (again lol) And debranded successfully Thanks man!
Thankyou very much for the guide it worked a treat.
I had to slightly amend your script as I was also having the fasbtoot only recognising "fastboot -i 0x1532"
But only had to change one part of your it so the rest of the script would use "fasbtoot" as fastboot -i 0x1532
Worked as it should.
But thanks again. Anyone else having similar issues I can confirm this worked with my 3 branded device.
Sent from my Phone using Tapatalk
I reboot to download mode and issue the fast boot command phone just sits at download mode and cmd line has waiting for device ??
---------- Post added at 08:23 AM ---------- Previous post was at 08:20 AM ----------
I reboot to download command from cmd window download mode appears at the top left of the screen I issue the unlock command it just says waiting on the device I have OEM unlock selected in dev options have USB debugging enabled and accepted to allow reboot and commands when I issue unlock commands it sits at waiting on device
can you give instructions on how to use Ubuntu live disk when flashing the images? thank you!
nexy33 said:
I reboot to download mode and issue the fast boot command phone just sits at download mode and cmd line has waiting for device ??
---------- Post added at 08:23 AM ---------- Previous post was at 08:20 AM ----------
I reboot to download command from cmd window download mode appears at the top left of the screen I issue the unlock command it just says waiting on the device I have OEM unlock selected in dev options have USB debugging enabled and accepted to allow reboot and commands when I issue unlock commands it sits at waiting on device
Click to expand...
Click to collapse
While your phone is in download mode check the device manager on the PC see if it detects the device properly or has a warning triangle beside it. If it does then your PC isn't detecting the hardware properly and you'll need to download android ADB drivers.
Roxas598 said:
While your phone is in download mode check the device manager on the PC see if it detects the device properly or has a warning triangle beside it. If it does then your PC isn't detecting the hardware properly and you'll need to download android ADB drivers.
Click to expand...
Click to collapse
YIP has a warning triangle on android device
nexy33 said:
YIP has a warning triangle on android device
Click to expand...
Click to collapse
yep that's your issue then. right click on it and select "update drivers" then select the option that reads something like install from your computer then to chose a driver. if you can't see "Android ADB" then you'll need to install these https://developer.android.com/studio/run/win-usb.html then do what I said there.
Should get your computer talking to the phone in download mode
Roxas598 said:
yep that's your issue then. right click on it and select "update drivers" then select the option that reads something like install from your computer then to chose a driver. if you can't see "Android ADB" then you'll need to install these https://developer.android.com/studio/run/win-usb.html then do what I said there.
Should get your computer talking to the phone in download mode
Click to expand...
Click to collapse
tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3
nexy33 said:
tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3
Click to expand...
Click to collapse
Try installing wondershare mobilego on your pc, it get rid the missing drivers of mine after installing it.. i dont know why? might as well as yours
nexy33 said:
tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3
Click to expand...
Click to collapse
Tried installing the "Android ADB" Driver in device manager? cause that should be the only thing stopping you :S so odd.