I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
bozo089 said:
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
Click to expand...
Click to collapse
fastboot clockwork recovery then flash a rom.
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
bozo089 said:
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
Click to expand...
Click to collapse
do you have the recovery.img file in the same folder as fastboot?
simms22 said:
do you have the recovery.img file in the same folder as fastboot?
Click to expand...
Click to collapse
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
bozo089 said:
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
Click to expand...
Click to collapse
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
simms22 said:
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
Click to expand...
Click to collapse
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
bozo089 said:
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
Click to expand...
Click to collapse
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
bozo089 said:
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
Click to expand...
Click to collapse
OK, i did a system restore and now i have pdaNet back. I have no idea how to use it or what to do next.
Please help!
EDIT: when i typed "fastboot devices" into CMD, it shows my device!
take a screenshot of your /sdk/tools folder.
(seriously do it).
OR if you don't want to.. does fastboot appear as "fastboot" or "fastboot.exe" ?
Uploaded with ImageShack.us
There you go
bozo089 said:
Uploaded with ImageShack.us
There you go
Click to expand...
Click to collapse
Okay, yeah. I see the problem, your extensions are hidden "recovery.img" is actually "recovery.img.img" so you're fastbooting a invalid file. What I want you to do is on the top left of a Windows explorer, it says Organize. Press that and go to folder options -> view -> hide extensions for known file types (UNCHECK THIS). Rename recovery.img.img so it appears as recovery.img not recovery.img.img
Put your phone in bootloader mode if it isn't already with USB plugged in.
The phone needs to be in bootloader mode in order for it to recognize the fastboot command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^ appears as that.
through command prompt
cd C:\android-sdk-windows\tools\
(optional -- do this if your phone isnt in bootloader mode) adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
and you're set. click on "thanks" if this helped you!
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
bozo089 said:
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
Click to expand...
Click to collapse
yeah that meant it worked. you can access clockwork menu by going down to RECOVERY in the menu or "adb reboot recovery"
you install a ROM by...
1. Shop around the Dev forums and look for what ROM you want to use. I personally use CM7.
2. Use netarchy's kernel (its worth it).
Steps:
1. Put ROM onto your sdcard
2. Boot into Clockwork Recovery (told you above on how to do it)
3. Wipe Factory, Dalvik, Cache
4. Flash ROM (Proceed to flash CM7 Gapps afterwards if you decide to go with CM7)
5. Flash Kernel (Optional)
6. Reboot!
Ahhh, i updated without looking at your post first. Can i put the kernal on now that ive rebooted?
thank you for your help and time
Related
Here is a Splash Screen i wanted to share with the community, It's simple just the original with inverted colors
Please enjoy.
As always please backup before trying, I won't be responsible for anything that may go wrong if this fails
and mods if this is posted in the wrong place please move thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To apply just unzip the contents of the package below into the tools folder of the android sdk
How-to Enter fastboot mode .... While the phone is off hold down "Volume down key" and then "power button" hold both till you get a white screen with the androids and skateboards
to confirm your device is seen by adb use this command
Code:
fastboot devices
you should see your phone listed under the command you just typed. After that type the next command to flash the splash image
Code:
fastboot flash splash1 splash1.nb
Then you should see that it was successful and rebbot the phone and preview your new image by typing
Code:
fastboot reboot
Please Thank and post comments as needed, if there is any trouble i'll try to help if i can i'm rather busy lately...lol
There was a huge thread on how to change splash with win 7 and I am stuck in osx thanks for a tut on how to to it in fastboot
Thanks! I followed the instructions and applied it no problem. Makes booting up look seamless with Fresh's bootscreen
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Criimson said:
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Click to expand...
Click to collapse
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Am I missing something? I do everything step by step and it won't find fastboot command in the terminal (using OS X). I can't do anything.
JSZESZE said:
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Click to expand...
Click to collapse
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Is there a way to flash from the EVO itself? I can copy files with no problem if I connect as a HDD.
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Criimson said:
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Click to expand...
Click to collapse
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
JSZESZE said:
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Click to expand...
Click to collapse
Awesome! Thanks man, I appreciate it. Looks great.
beautiful! thank you VERY much for this
JSZESZE said:
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
Click to expand...
Click to collapse
No it is in fastboot
From what I gather a lot of people have this issue with Vista 32bit and HTC Sync. I haven't been able to track down a solution. Even when trying to use Sync..it always just errors and says:
Unable to find HTC Sync on your PC. Please make sure.....
Kind of a pain, but so far I have been able to do everyting I want just doing it from the phone with files copied over. Using the terminal emu or file manager
Criim
imaxreed said:
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
Click to expand...
Click to collapse
sounds like a permission issue... are you rooted and nand unlocked?
JSZESZE said:
sounds like a permission issue... are you rooted and nand unlocked?
Click to expand...
Click to collapse
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
imaxreed said:
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
Click to expand...
Click to collapse
in adb type
Code:
adb shell
then you should see
Code:
#
A $ prompt is the prompt for normal terminal ...
whereas:
a # prompt is the prompt for root (super user)
i am running osx and can access adb shell
http://imgur.com/t8MKg.jpg
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
JSZESZE said:
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
Click to expand...
Click to collapse
yes exactly. I haven't had a problem before this is strange.
Works great for me, no problems. This is a great way to save battery!
haha.
Hi everyone,
So this is my issue. Yesterday i tried to root my working nexus s i9020t with a one click root on my mac computer. Terminal said 'root ok' everything was ok then the phone didnt get past the google startup.
So i tried recovery... that didnt do anything.
Then i started with SDK on my windows 7 machine and with fastboot.
Basically i erased everything on the phone (boot and recovery)
Fastboot is unlocked. At the top it says no boot or recovery img.
When i do 'fastboot flash recovery recovery.img' with my recovery.img in the same folder on windows it says 'cannot load or mount recovery.img'
Fastboot is seeing the phone since it is listed when I write 'fastboot devices'.
Basically i think i ruined the recovery file, dont care about rooting right now, just want to load a recovery image or boot image.
If i go down to recovery on the phone in fastboot it will start fastboot again and say ' no boot or recovery img'
Any help?
THANK YOU!
AllGamer said:
GRH78
Bootloader v.JK1
Baseband v.JK8
Yes, there are tons of guides out there, and even one click scripts that can ROOT the SNS (Samsung Nexus S) for you, but none of them go into enough detail for any of them to work properly.
Having many android devices working properly via ADB on your computer doesn't automatically guarantees it will see the SNS.
So, before jump to the exiting stuff of ROOTing the SNS, lets cover some basics to actually get you started and make sure you can actually ROOT the SNS, else all is in vain.
MOD EDIT: This guide does not apply to the AT&T/Rogers/Telus variants of the Nexus S (i9020A). For those models, please refer to this guide.
Part 1
Download Android SDK 2.3 or click the file name android-sdk_r08-windows.zip (32 MB) direct from Google, instead of wasting your time jumping through hoops and dodging pop up/flash ADs from those FileSharing places.
Turn Off your SNS
Make sure the SNS is connected to the PC via the USB cable
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it reads LOCK STATE - LOCKED
open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
Do a right click and select Update Driver Software
Select Brose my computer for driver software
point it to where you downloaded the Android SDK 2.3 (..\android-sdk-windows\google-usb_driver)
Make sure to CLICK "Let me pick from a list of device drivers on my computer"
Then from the list 3 choices select Android Bootloader Interface
If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Now that the basic preparations are done, we can finally get to have fun with the SNS & hack away via ADB.exe / FASTBOOT.exe
Part 2
open a command prompt go to run & type CMD hit enter
switch to the directory where you downloaded & unzipped the ..\android-sdk-windows\tools
type fastboot oem unlock and hit enter
Then you will get this
Code:
fastboot oem unlock
...
meanwhile on the SNS you'll see this screen
selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done
Code:
... OKAY [435.433s]
finished. total time: 435.433s
now back on this screen you should read
LOCK STATE - UNLOCKED
Download the clockwork recovery recovery-clockwork-5.0.2.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Code:
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS
...meanwhile the SNS is rebooting Download superuser from http://forum.xda-developers.com/showthread.php?t=682828
choose the Eclair/Froyo version
Mount the USB storage
drag/drop the su-version#-signed.zip file into the root of the internal SD of the SNS
Power Off the SNS
Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
select Recovery
then it should boot into this screen, if not then repeat the steps to download the image
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
done!
Enjoy your unlocked & rooted phone!
Click to expand...
Click to collapse
Sent from my Nexus S using XDA Premium App
Sent from my Nexus S using XDA Premium App
Follow the recovery part,
Sent from my Nexus S using XDA Premium App
osugsxr,
Thanks for the reply, but that is the tutorial i tried and i get stuck at the part:
'Fastboot flash recovery recovery.img'
it says that the recovery.img cannot be loaded....
ever see something like that?
To me it sounds like fastboot can't find your recovery image.
Could you try doing fastboot with the absolute path?
On windows (path for example):
fastboot flash recovery C:\android\recovery.img
Make sure you get the backspaces right.
On linux (for example)
fastboot flash recovery /home/user/android/recovery.img
Good luck.
Greetz
michaeljameson1985 said:
osugsxr,
Thanks for the reply, but that is the tutorial i tried and i get stuck at the part:
'Fastboot flash recovery recovery.img'
it says that the recovery.img cannot be loaded....
ever see something like that?
Click to expand...
Click to collapse
Is it in the correct folder?
Sent from my Nexus S using XDA Premium App
osugsxr said:
Is it in the correct folder?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Progress report - So i now have clockworkmod recover v5.0.2.0 on my android nexus s 9020t and have tried everything from Stock rom to a different rom to update.zip the file.... nothing has worked.
I tried to install the update.zip from the recovery and get the error that there is an error in /sdcard/update.zip
is it possible clockworkmod recovery v5 wont work with my nexus s?
thanks!
Mike
You know that you have to copy the ROM zip file to the SDCard and then choose 'Install zip from sdcard' option in CWM, selecting the download ROM zip file, right?
Greetz
Sorry if the question isnt clear, here is my delemma
So My N5 I had deleted the system partition (or folder) and I no longer had a rom, now my problem is that I cannot get a new rom installed.
I have TWRP as my recovery but no roms.
I also cant do adb sideboot, It always says: Error: Device not found
What Can I do about this?
Does adb Sideboot need usb debugging enabled?
Thanks!
Sounds like you may have to install the drivers for adb on your computer
Sent from my Nexus 5 using XDA Premium 4 mobile app
kevkid said:
Sorry if the question isnt clear, here is my delemma
So My N5 I had deleted the system partition (or folder) and I no longer had a rom, now my problem is that I cannot get a new rom installed.
I have TWRP as my recovery but no roms.
I also cant do adb sideboot, It always says: Error: Device not found
What Can I do about this?
Does adb Sideboot need usb debugging enabled?
Thanks!
Click to expand...
Click to collapse
Why not just flash the factory images from fastboot?
So I tried to using this: http://forum.xda-developers.com/showthread.php?t=2509428 one of mthe multi tools, and it seems to go through and it stays boot looping in the boot animation.
hrmm.... very weird
EDIT: Ok I was able to flash stock via the direct google link, Now a question about adb sideload, How does that function? Do I have to have usb debugging enabled?
kevkid said:
So I tried to using this: http://forum.xda-developers.com/showthread.php?t=2509428 one of mthe multi tools, and it seems to go through and it stays boot looping in the boot animation.
hrmm.... very weird
Click to expand...
Click to collapse
1. Go here: https://developers.google.com/android/nexus/images
2. Download the Nexus 5 Android 4.4 (KRT16M) image.
3. Unzip.
4. Run the .bat file while in fastboot.
That's it. It's going to wipe everything but atleast it will work.
bahnburner said:
1. Go here: https://developers.google.com/android/nexus/images
2. Download the Nexus 5 Android 4.4 (KRT16M) image.
3. Unzip.
4. Run the .bat file while in fastboot.
That's it. It's going to wipe everything but atleast it will work.
Click to expand...
Click to collapse
Thanks worked!!
bahnburner said:
1. Go here: https://developers.google.com/android/nexus/images
2. Download the Nexus 5 Android 4.4 (KRT16M) image.
3. Unzip.
4. Run the .bat file while in fastboot.
That's it. It's going to wipe everything but atleast it will work.
Click to expand...
Click to collapse
Having a little trouble I was hoping you could help clarify how to run the .bat file while in fastboot. I tried to flash the image and I am still stuck on a bootloop. Thanks
capathy21 said:
Having a little trouble I was hoping you could help clarify how to run the .bat file while in fastboot. I tried to flash the image and I am still stuck on a bootloop. Thanks
Click to expand...
Click to collapse
Open a new command prompt, drag and drop the bat file into the terminal window, press enter.
bahnburner said:
Open a new command prompt, drag and drop the bat file into the terminal window, press enter.
Click to expand...
Click to collapse
I am having trouble with what the bat file is. When I unzip the download I have
bootloader-hammerhead-HHZ11d(disc image file).
flash-all(windows batch file)
flash-all.sh(SH File)
flash-base.sh(SH File)
image-hammerhead-krt16m(WinRar zip archive)
radio-hammerhead-M8974A-1.0.25.0.17(Disc Image File)
I am not seeing anything that says .bat file.
Sorry for being so ignorant on this.
capathy21 said:
I am having trouble with what the bat file is. When I unzip the download I have
bootloader-hammerhead-HHZ11d(disc image file).
flash-all(windows batch file)
flash-all.sh(SH File)
flash-base.sh(SH File)
image-hammerhead-krt16m(WinRar zip archive)
radio-hammerhead-M8974A-1.0.25.0.17(Disc Image File)
I am not seeing anything that says .bat file.
Sorry for being so ignorant on this.
Click to expand...
Click to collapse
Windows batch file = .bat file. If you're going to screw with your phone, at the very least you should probably make sure explorer shows all file extensions...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bahnburner said:
Windows batch file = .bat file. If you're going to screw with your phone, at the very least you should probably make sure explorer shows all file extensions...
Click to expand...
Click to collapse
Thanks for the help! Sorry to annoy. I've been rooting and such for several years but was just a bit lost.
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what to do?
Are you sure you are in fastboot mode?
root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:
quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!
Good morning,
I'm new here, and i hope you can help me with my problem.
I have a mi MJJGYY02FM projector and i did a update with USB stick with files from Xiaomi.
Now after the update the projector start with MI logo and than shuts down, after that he start up with no screen and do nothing.
Can someone help me how to fix this. i can't get the projector in a boot menu with the remote, maybe he dont recognize the remote.
Kind Regards,
Bas
Reflash projector's Stock ROM.
jwoegerbauer said:
Reflash projector's Stock ROM.
Click to expand...
Click to collapse
I have the stock ROM on USB now, but hè will not install it. When i press the home and enter button and plug the power cable. Hè start up with the MI logo and shuts down, then start up with no screen.
Are there other ways to install the stock ROM?
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Thanks
Im gonna search out and try that option.
I let it know when it works. maybe i have some questions.
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Im trying something, but do you have a discription how to make that USB with the Stock Rom?
I got your files on my pc. I have a 16GB USB format FAT32.
What is the way to make that sideload with the ROM version?
Im sorry for the questions, but i have never done this before.
I have done thist thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
jwoegerbauer said:
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
Click to expand...
Click to collapse
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Vross46 said:
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Click to expand...
Click to collapse
My drive letter is :e
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
jwoegerbauer said:
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
Click to expand...
Click to collapse
ah ok. lets try.
It seems not so difficult but, for the first time is everything more difficult
What do i wrong. sorry! I do really my best
1, i have a format 16gb usb FAT32
2. i have install ADB installer.
3. i have download the stock rom (see picture)
4. my drive name is e:
5. When i zip my stock rom file, i got an another zip file, and an file of 1kb
in the next picture is what i do in CMD
anglee_full_9.0.0.1911 is my zipped stock rom downloadfile
the other 2 are the unzipped files from the first file
1st screenshot provided above shows
1. Device isn't connected via USB-cable with PC or, if, not powered on
2. The ROM's archive name you entered is without fileextension -> required :ZIP
If ROM's archive is packed as .RAR file then you have it to repack to .ZIP file
I think it will not gonna help.
When i connect my projector to the pc, the pc dont recognize him.
What i try, nothing works.
but thanks for your help anyway
Have you ever enabled "USB Debug" in Android's Settings -> Developer otions?
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Vross46 said:
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Click to expand...
Click to collapse
Hello Vross46, have you been able to solve your problem? I’m stuck with the logo as well