Database Users

Help with Rooting my Nexus One?

I'm having problems Rooting my Nexus One and would be extremely greatful if someone could help me. I got my Nexus One directly shipped to the UK, I am using Windows 7 Ultimate 64bit.
Here's what I've been doing;
I checked 'about' screen and saw it's ERE27 on my N1.
1) I download Superboot for ERE27 - download MD5: 19d302e1bcb18932f009d2a36a3d688f and extracted it to directory (C:\)
2) Turned off phone then plugged in the USB to the N1 (sound on my Windows 7 confirmed the USB connection was made)
3)I I put my N1 in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader.
4) I double click 'install-superboot-windows.bat' extracted file on my pc.
BUT then Command Prompt pops up and I get - C:\Users\Bukhtiar\Desktop\1.0-ERE27-nexusone-superboot>fastboot-windows.exe flash boot boot.ERE27.superboot.img
< waiting for device >
After that nothing happens, please could someone help me with a step by step guide as I am new to this.
Many Thanks

You need the USB drivers for the nexus (http://djdoprkngutub.cloudfront.net/usb_driver.zip)
Also, did you unlock the bootloader? You didnt mention it

You need to download the Android SDK and run "Fastboot OEM Unlock"

Do I need to have the phone connected while downloading the Android SDK? Sorry about the Q's but I'm new to all this.

Follow step 1 and 2 in this link
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
then do your superboot step that you have mentioned.
Afterwhich, your phone is unlocked,has a new recovery img, rooted and ready for flashing of custom roms.

Worsty said:
Follow step 1 and 2 in this link
androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
then do your superboot step that you have mentioned.
Afterwhich, your phone is unlocked,has a new recovery img, rooted and ready for flashing of custom roms.
Click to expand...
Click to collapse
I downloaded the Android SDK folder and downloaded the files within it then I followed the links instructions....as follows;
# Reboot phone into fastboot: Power off device and hold down trackball while powering back on. (The fastboot screen is the one with the Androids on skateboards)
# Open a command prompt and navigate to your Android SDK tools folder.
# Type ‘fastboot devices‘ to make sure your phone is recognized.
I opened Command Prompt and navigated to the Android SDK tools folder but I get nothing coming up when I typed ‘fastboot devices‘ nor any message saying my phone is recognized, except in 'Fastboot USB' the phone screen.

[How-to]Root Android 4.2.2 And Install CWM v6.0.2.3

Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10

Reserved...

udimars30 said:
Reserved...
Click to expand...
Click to collapse
Thank you a lot...but the link for the fastboot its not aviable

Nano23 said:
Thank you a lot...but the link for the fastboot its not aviable
Click to expand...
Click to collapse
link updated

and this belongs in original development how? why not post a thread in original development asking about need for speed too..

Step 4 and step 7
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?

thanks
Thanks its worked for my nexus 7..
udimars30 said:
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Click to expand...
Click to collapse

Thanks a million man! I was having all kinds of trouble updating to 4.2.2 and finally figured that out. Then I was having problems rooting again until I found this. Your method worked great but I used TWRP instead and it still did the trick. Thanks again.

I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?

Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Click to expand...
Click to collapse
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).

No need for holding the power button, the vol down button does the whole trick

worked for me. thanks very much

sicameron32 said:
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
Click to expand...
Click to collapse
yes you can do that for the normal boot

Spenzert said:
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
Click to expand...
Click to collapse
Thanks..
I don't have N7 that's why did not know!

Leonhan said:
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Click to expand...
Click to collapse
re-install the fastboot with all it's extensions in the same folder!

If you want to use fastboot by a easy way, use this guide you don't need adb line command, just fastboot line command and it's an child game by this way
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "Fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
If you want to flash a boot.img:
Code:
c:\fastboot>fastboot flash boot boot.img
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

don´t i have to unlock bootloader first ?

Domx92 said:
don´t i have to unlock bootloader first ?
Click to expand...
Click to collapse
Yes, it is a prerequisite if you want to root your android device.

Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!

vmancini3 said:
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
Click to expand...
Click to collapse
Hi, vmancini3...
Forget about ADB when your tablet is in FASTBOOT/BOOTLOADER mode...
Here are the salient commands....
Code:
fastboot devices
- should return a serial number to confirm your FASTBOOT connection -
Code:
fastboot oem unlock
- will unlock the BOOTLOADER and will WIPE and FACTORY RESET THE DEVICE; unfortunate, but necessary .
--------------------
With the BOOTLOADER unlocked, begin to set up your Nexus 7 again... as though it was a brand new, just purchased tablet... ie., country, regionalization, WiFi key... etc.
Go online with your Nexus 7 browser (Chrome), and download Chainfire's SU Updater .ZIP package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Upon completion of this download, shut down the tablet.
--------------------
Reboot again into FASTBOOT/BOOTLOADER mode... VOL down button + POWER ON button.
From your PC, run this command...
Code:
fastboot flash recovery recovery.img
....where the recovery.img is your CWM or TWRP .img file.
Both of which are available here...
CWM - http://www.clockworkmod.com/rommanager
TWRP - http://www.teamw.in/project/twrp2/103
--------------------
Congratulations.... you've just FLASHED a CUSTOM RECOVERY!!!
--------------------
When the self-congratulatory round of self applause has died down, ... and with the Nexus 7 still in FASTBOOT/ BOOTLOADER MODE, use the VOL buttons to navigate and the POWER button to select... reboot into RECOVERY.
Using the new CUSTOM RECOVERY, flash Chainfires SU updater package that you downloaded earlier... usually found in the /download folder...
Done.
Reboot.
Rooted.
--------------------
I really don't understand why some people seem to have a problem with this procedure... it takes less time doing it, than actually describing how to do it.
Rgrds,
Ged.

Computer stuck dead while running "15 seconds ADB Installer"

Computer stuck dead while running "15 seconds ADB Installer"
For the purpose of flash new recovery to my Nexus s ,I searched and used the tollkit from
http://forum.xda-developers.com/showthread.php?t=2588979
And when I CmD the command line
fastboot flash recovery recovery.img
My computer stuck to dead! Though,fortunately the phone weren't bricked at that moment.
1 ,And where did u guys get the proper functional revision of fastboot.exe and adb.exe?
2, Does the "15 seconds ADB Installer" contain some torjan? (as u know it made PC dead)
BTW my phone is nexus s

faraway001 said:
Computer stuck dead while running "15 seconds ADB Installer"
For the purpose of flash new recovery to my Nexus s ,I searched and used the tollkit from
http://forum.xda-developers.com/showthread.php?t=2588979
And when I CmD the command line
fastboot flash recovery recovery.img
My computer stuck to dead! Though,fortunately the phone weren't bricked at that moment.
1 ,And where did u guys get the proper functional revision of fastboot.exe and adb.exe?
2, Does the "15 seconds ADB Installer" contain some torjan? (as u know it made PC dead)
BTW my phone is nexus s
Click to expand...
Click to collapse
This the best and the easiest guide to install adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2141817
In my opinion, it is always good to type commands and manually setup everything than using 1-click installers. This helps in debugging and avoiding issues.
Probably your PC needs a Startup repair. Start it and press F8 continuously to get repair options. Let me know how it goes.

smit.sanghavi said:
This the best and the easiest guide to install adb and fastboot.
http://forum.xda-developers.com/showthread.php?t=2141817
In my opinion, it is always good to type commands and manually setup everything than using 1-click installers. This helps in debugging and avoiding issues.
Probably your PC needs a Startup repair. Start it and press F8 continuously to get repair options. Let me know how it goes.
Click to expand...
Click to collapse
Hey I am back...
As for your reply ,thanks but what I wanna say is the first,my PC has purely good configured and not any system deformity.
And I haven't found any working adb.exe/fastboot.exe version before I one day surfed a board and droped with a working bundle.
The bunldle included adb and fastboot which had the different md5 from the ones in "15 seconds ADB Installer".
*15 sec
81d188a849c8768e8f3694eb1c0e6086 adb.exe 800k
2782d10e7d3370cfefbadae0e8eaaa35 fastboot.exe 157K
**working version
8ae827f316e4fd4500c8d5b2845bcbe9 adb.exe 2400k
6bbf05d97585c3c515bdb172eb9e7d12 fastboot.exe 969 K
What's the difference between the "15 sec" and the working version. Weren't they coming from the same Google adt-bundle？
Or has somebody compiled the origin fastboot.exe and twisted it in order to make it work straight out there.

How to downgrade to OS 1.5 on Remix Ultra tablet?

My Remix Ultratablet current running 2.0.305 keep random restart everyday.
So I wish to downgrade to OS 1.5
I ask for help form office Jide support , they told me I need to
Q1) Problem # stuck on step #1 already , When I ask where is the Remix Ultratablet driver when I install adb and fastboot ? Offical jide support told me I don't need a driver? How so ?
I can't get the tablet connect ??
Note: 1, I connect the tablet with USB to PC
Note: 2, I turn the USB debugging option on Tablet already.
Note: 3, I Test it on pc adb folder by trying "fastboot devices" only get "Waiting for Device" error
Q2) I also try other method (Power key + Volume up) on tablet which show
"Continue
Fastboot Protocol
Recovery Kernel
Reboot
Poweroff
Forced Recovery"
But when i press"Fastboot Protocol" , doesn't do anything ?
For your references:
Steps of instruction I receive from Jide offical support so far....
1) have ADB and Fastboot running, I download the Minimal ADB and Fastboot[/URL])
2)Download Remix OS 1.5 ROM[/URL]
3) Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
Make sure the fastboot binary is in your PATH ) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot

did u download the correct fastboot? you need Android 5.0 to get Remix 1.5

AmoraRei said:
did u download the correct fastboot? you need Android 5.0 to get Remix 1.5
Click to expand...
Click to collapse
That makes no sense what so ever.
Maybe it would be better to ask what platform he is using to flash his device with, as the instructions he has copy and pasted refer to Linux (udev rules)

it makes sense to me cause you have download the correct Android SDK to work on certain Android platforms.
https://developer.android.com/studio/releases/platforms.html
To compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release.

AmoraRei said:
it makes sense to me cause you have download the correct Android SDK to work on certain Android platforms.
To compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release.
Click to expand...
Click to collapse
Thanks of the reply ,
I'm using Win7 amd the Remix Ultratablet current running 2.0.305
I can't post link , but the ADB /Fastboot verson I download is also from xda Title "[TOOL]Minimal ADB and Fastboot [10-22-16]"
I download the "Version 1.4.1 Portable Here" with
MD5 Checksum: D7B1C009C87C77AAF045FA3ED239E591
Thanks for all the help in advance

When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979

AmoraRei said:
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
not exactly,i said to try this ,to install adb drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089

tailslol said:
not exactly,i said to try this ,to install adb drivers.
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
Click to expand...
Click to collapse
well thank u for coming here and posting
:victory:

AmoraRei said:
When u plugged up the tablet to the pc, what did device manager say?
my associate said try this fastboot http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
when the tablet plugin to WIN7 , I got pop up windoes "Autoplay"
Name REMIX SK1WG
-Sync digital media file to this device
-Open device to view files
-Import picture and Video
when I click "Open device to view files" , I get to to see tablet "Internal Storage"
Thanks

sfbay998 said:
when the tablet plugin to WIN7 , I got pop up windoes "Autoplay"
Name REMIX SK1WG
-Sync digital media file to this device
-Open device to view files
-Import picture and Video
when I click "Open device to view files" , I get to to see tablet "Internal Storage"
Thanks
Click to expand...
Click to collapse
and what happens when you plug it when the device is in fastboot mode?

tailslol said:
and what happens when you plug it when the device is in fastboot mode?
Click to expand...
Click to collapse
That's the part I'm lost : What is consider "in fastboot mode"
I go to the WIN7 Folder there is unzip the "[TOOL]Minimal ADB and Fastboot [10-22-16] Version 1.4.1 Portable" and type fastboot devices , nothing happen
then I go to the tablet : turn off, then I try other method (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Nothing Happen ??
Note: I'm a first time ADB/ Fastboot user, but not totally a newbie. thanks

sfbay998 said:
That's the part I'm lost : What is consider "in fastboot mode"
I go to the WIN7 Folder there is unzip the "[TOOL]Minimal ADB and Fastboot [10-22-16] Version 1.4.1 Portable" and type fastboot devices , nothing happen
then I go to the tablet : turn off, then I try other method (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Nothing Happen ??
Note: I'm a first time ADB/ Fastboot user, but not totally a newbie. thanks
Click to expand...
Click to collapse
you should look the picture i gave you in my first message.

tailslol said:
you should look the picture i gave you in my first message.
Click to expand...
Click to collapse
Thanks, I will try the install "15 seconds ADB Installer v1.4.3" tonight when back home.
on side question: anyone know WHEN to use the (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
The reason I ask because when I press "Fastboot Protocol" , it doesn't do anything. !!??
Also , the whole purpose for me to do the ADB/fastboot is to download back to OS 1.5, because my OS 2.0.305 keep random reboot ! So if anyone can tell me how to fix the OS 2.0.305 random reboot ? I might not have to do all this ADB/fastboot things ?
Thanks

sfbay998 said:
Thanks, I will try the install "15 seconds ADB Installer v1.4.3" tonight when back home.
on side question: anyone know WHEN to use the (Power key + Volume up) on tablet which show
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
The reason I ask because when I press "Fastboot Protocol" , it doesn't do anything. !!??
Also , the whole purpose for me to do the ADB/fastboot is to download back to OS 1.5, because my OS 2.0.305 keep random reboot ! So if anyone can tell me how to fix the OS 2.0.305 random reboot ? I might not have to do all this ADB/fastboot things ?
Thanks
Click to expand...
Click to collapse
when you turn it on,it seems you do not have the minimum knowledge required to flash a device... you should stay away from downgrading it or study adb and fastboot videos and tutorials on google and youtube before doing anything.if you do anything wrong and brick your device,the warranty will not work,any bad flash could void your device warranty.

tailslol said:
when you turn it on,it seems you do not have the minimum knowledge required to flash a device... you should stay away from downgrading it or study adb and fastboot videos and tutorials on google and youtube before doing anything.if you do anything wrong and brick your device,the warranty will not work,any bad flash could void your device warranty.
Click to expand...
Click to collapse
I have try
Connect the Remix to the computer via USB.
fastboot devices
Which show:
xxxxxxxxxxxxxx fastboot
Then I type the following commands
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
ALL successful , then when reboot , it stuck on "Remix" flashing logo forever !!
Any help ?

sfbay998 said:
I have try
Connect the Remix to the computer via USB.
fastboot devices
Which show:
xxxxxxxxxxxxxx fastboot
Then I type the following commands
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
ALL successful , then when reboot , it stuck on "Remix" flashing logo forever !!
Any help ?
Click to expand...
Click to collapse
yea you forgot to wipe your device...
return to fastboot if you can then use those commands:
fastboot -w
fastboot reboot

update:
Now when i type
fastboot devices
I got :
xxxxxxxxxxxxxxxxxxxxxxxxxxxx fastboot
When I type: adb devices
I got:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On the Tablet side:
Bootloop only
But I can still press "Vol up + Power" and see the following menu
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Any help would be appreciated !!
Thanks

sfbay998 said:
update:
Now when i type
fastboot devices
I got :
xxxxxxxxxxxxxxxxxxxxxxxxxxxx fastboot
When I type: adb devices
I got:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
On the Tablet side:
Bootloop only
But I can still press "Vol up + Power" and see the following menu
-Continue
-Fastboot Protocol
-Recovery Kernel
-Reboot
-Poweroff
-Forced Recovery"
Any help would be appreciated !!
Thanks
Click to expand...
Click to collapse
go to fastboot protocol ,hook it to your pc and proceed with the command i told you,but anyway caution,i told you you could brick your device...

tailslol said:
go to fastboot protocol ,hook it to your pc and proceed with the command i told you,but anyway caution,i told you you could brick your device...
Click to expand...
Click to collapse
Will try
but just want to check When I type: adb devices , iy did not list my drvice number , does it matter since I will be using "Fastboot -W" only?

sfbay998 said:
Will try
but just want to check When I type: adb devices , iy did not list my drvice number , does it matter since I will be using "Fastboot -W" only?
Click to expand...
Click to collapse
don't forget fastboot reboot and yes it matter,if the computer does not see the device the device can't receive commands...

A1 stuck in bootloop

Let me know if this post belongs somewhere else.
My Mi A1 is stuck in a bootloop as a result of trying to install magisk 14.4. At the moment I can boot it into fastboot mode, but not into recovery mode. In fastboot I can execute the command
fastboot devices
that returns the hex number followed by "fastboot." However, it does not respond to any other fastboot commands, e.g.
fastboot reboot
fastboot oem device-info
I have been attempting to flash the stock rom without success as follows:
in win10 32-bit environment:
fastboot responds as above. I cannot install the MiFlash-2017-7-20 version. Windows complains. I conclude that version must be a w10 64-bit app, although it doesn't say so.
win10 64-bit
MiFlash-2017-7-20 installs and runs, but does not see the device. Apparently, the adb drivers are at fault. I have turned off signature enforcement and tried installing various versions of the adb drivers. The device manager shows them as installed, but reports that they cannot start.
Centos 7 linux
Adb drivers install. "Fastboot devices" reports correctly. All other fastboot commands fail, i.e. they hang. I tried installing the tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image using the linux shell script provided, but that just hung also.
Is this phone well and truly bricked at this point? Is there any other recovery available?

I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.

Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works

GalihBK said:
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
Click to expand...
Click to collapse
As he said, he can't execute fastboot commands so that isn't a option.

@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well

Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong

dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.

The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps

Edwin Hamal said:
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Click to expand...
Click to collapse
1. I tried this method to boot into EDL with no luck. Is there any other way?
C:\Downloads\xiaomi mi a1 root>adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
2. On my win10 32-bit installation I am able to run MiFlash-2017045. It reports the device. I attempted to flash this image:
tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
It completed and reported "success" however it did so in only 7 seconds, so it must not actually have succeeded. In any case the phone still will not boot.
3. However, I distrust MiFlash 20170425 because it comes from an androidmtk.com site and the processor is Qualcomm, not Mediatek. So I attempted to install MiFlash2017-07-20. However, that program will not install on my win10 32-bit installation. There is a Windows msg saying it cannot be installed, but does not give a reason. I suspect it is a 64-bit program. So, I installed MiFlash2017-7-20 in a win 10 64-bit installation. The program does run, but it does not see the device. I suspect that the adb drivers do not install correctly. I did turn off signature enforcement and the drivers appear to install, but the device manager reports that the drive cannot start.
The tissot images include bourne shell scripts to install, so I installed the adb drivers on my Centos box. Fastboot reports the device, but just as in win10 no other fastboot commands work. So, even though I did try to execute the install_all.sh script, it just hung on the first "fastboot getvar product" command.
So, I do not have a way to flash the stock rom.

_mysiak_ said:
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Click to expand...
Click to collapse
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.

dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Use fastboot commands manually. Mi flash tool is very buggy. Many time it doesn't work.

_mysiak_ said:
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
Click to expand...
Click to collapse
Did the command:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
"Missmatching image and device"
So this is a little interesting. However, I don't think that the image is actually the wrong one, but that the script cannot get the device info since both "fastboot getvar product" and "fastboot oem device-info" fail on a timeout.

zazzy24 said:
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Click to expand...
Click to collapse
When I do that it just keeps going back to the "no command" screen. I think the recovery image is either damaged or gone.

yuoip said:
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
Click to expand...
Click to collapse
1. & 2. It sounds like you don't have installed fastboot drivers (install them manually via device manager) or phone isn't connected in fastboot mode (make sure there is a picture with fastboot written on the phone).
3. this IS the recovery mode, just press power + volume up again to show the menu
4. you won't see ADB devices in fastboot or recovery mode, unless you enable ADB sideload from recovery

Device Manager shows:
Android Phone

yuoip said:
Device Manager shows:
Android Phone
Click to expand...
Click to collapse
Wrong drivers then, it should say Android bootloader interface. Reinstall them correctly.

1. I did the manual install, but I don't see anything labeled "fastboot driver."
Device manager now reports:
Android Phone
Android ADB Interface
Android Bootloader Interface
Android Bootloader Interface
Android Composite ADB Interface
However, all these entries have a warning symbol on them. The Device status for each is:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Is one of these the fastboot driver? Apparently not, since the behavior of the fastboot command hasn't changed.
When I try using the fastboot command the A1 shows "Fastboot" with the rabbit character and the sick robot.
I should mention that in the Centos environment I have installed the android-tools package, which include adb and fastboot drivers and tools. The behavior of the fastboot command there is the same.
So, this leads me to believe that the problem is the A1, not the windows or linux environment, but I don't know enough to know for sure. Also, I would assume that if the fastboot drivers were not installed, the command "fastboot devices" would fail, but it doesn't.
3. At the "no command screen" if I do press and hold the power button and then the vol. up button it boots right back into the "no command" screen. There is no menu.
4. With no recovery menu I can't set any options.

Uninstall/remove everything with android name in it, disconnect phone, reconnect phone in fastboot mode. Make sure that there is only one item under Android Phone - Android Bootloader Interface. You should not see 4 devices - do you have Android emulator running or anything else connected?
When in recovery, do not hold power + volume up, just press it briefly. Sometimes it takes few tries to show the menu, but I can assure you that it's there.

Yes! You're right. The recovery menu is indeed there. I didn't know that it had to be a short press to bring it up. Thanks.
Device manager now shows only one "Android Bootloader Interface" entry. I am not running any emulator.
So now what do I do? Do I need to flash the tissot... image? The fastboot command still behaves as before.

Quick Google search suggests to avoid using USB 3.0 ports. So..maybe try another ports on your PC..?