Is there a way I can use ADB without setting debug mode on my phone? I am unable to startup the phone to switch to debug mode. When I start up the phone it goes to the google logo screen and stops there.
I am able to go into fastboot mode however. I have adb installed and all the drivers set.
I can see the phone in my device manager, but when I open up cmd prompt and type in adb devices it says it does not see anything.
Any help would be greatly appreciated!
ADB is only for when the phone is booted up. In your case you will need to work with fastboot
Sent from my Nexus S 4G using xda premium
sj_martin said:
Is there a way I can use ADB without setting debug mode on my phone? I am unable to startup the phone to switch to debug mode. When I start up the phone it goes to the google logo screen and stops there.
I am able to go into fastboot mode however. I have adb installed and all the drivers set.
I can see the phone in my device manager, but when I open up cmd prompt and type in adb devices it says it does not see anything.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
What are you trying to use ADB to do? You can run ADB in recovery, but if you are unable to startup the phone, I don't know anything you could do with ADB to fix it.
Rem3Dy said:
ADB is only for when the phone is booted up. In your case you will need to work with fastboot
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes as stated all I can do is go into the fastboot screen. It sounds like that I cannot use adb in fastboot?
What options do I have to recover data in fastboot if i do not have adb?
Thanks.
derekwilkinson said:
What are you trying to use ADB to do? You can run ADB in recovery, but if you are unable to startup the phone, I don't know anything you could do with ADB to fix it.
Click to expand...
Click to collapse
I wanted to use ADB to extract some files on the sandisk internal hd. I cannot boot up the phone anymore but it still turns on (but freezes at the google logo).
I also cannot go into recovery as when I try it also stalls at the google logo screen.
sj_martin said:
Yes as stated all I can do is go into the fastboot screen. It sounds like that I cannot use adb in fastboot?
What options do I have to recover data in fastboot if i do not have adb?
Thanks.
Click to expand...
Click to collapse
Yes. Adb will Not work in fastboot. Fastboot flash commands will work.
sj_martin said:
I wanted to use ADB to extract some files on the sandisk internal hd. I cannot boot up the phone anymore but it still turns on (but freezes at the google logo).
I also cannot go into recovery as when I try it also stalls at the google logo screen.
Click to expand...
Click to collapse
Is your bootloader unlocked? If so, flash a new recovery image and do a nandroid backup
Sent from my Nexus S 4G
If recovery doesn't work u have 2 options from fastboot to try to get into recovery:
1) fastboot flash recovery recovery.img
2) fastboot boot recovery recovery.img
All u need is a cwr recovery image. And the files on ur PC to use fastboot.
1) flashes a new recovery
2) just boots up the new recovery without flashing it
Sent from my Nexus S using xda premium
Luxferro said:
If recovery doesn't work u have 2 options from fastboot to try to get into recovery:
1) fastboot flash recovery recovery.img
2) fastboot boot recovery recovery.img
All u need is a cwr recovery image. And the files on ur PC to use fastboot.
1) flashes a new recovery
2) just boots up the new recovery without flashing it
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
my understanding is that i need the have the device visible in command prompt via adb to do any of this which is the issue i'm trying to solve. once i can get my computer to see the phone via adb i think i'm home free to extract all the data i need.
{
"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"
}
Another interesting note (i don't know if this will help me at all) is that if I boot up into download mode (holding both vol buttons when plugging in the usb cord) it gets stuck at the "unlock bootloader?" screen but in windows under the device manager instead of showing it as an android device with adb it is now under the usb controllers as "samsung usb composite device".
If I could get this thing to mount to my computer that would be fantastic and I could just drag and drop files out of the phone.
Any ideas?
If you flash clockwork recovery, you can boot into recovery and then use cwm to mount USB storage.
Sent from my Nexus S using XDA App
If I flash clockwork I need to unlock the bootloader, if I unlock the bootloader I have to wipe all my data.
So by nature of getting clockwork on the phone is useless to me since i'll have no data to backup by that stage =/
I do have access to fastboot now and is recognized via command prompt; is there a way to extract data via fastboot?
sj_martin said:
I do have access to fastboot now and is recognized via command prompt; is there a way to extract data via fastboot?
Click to expand...
Click to collapse
No and its rather preferred you not start two threads about the same issue.
Sent from my Nexus S MV from the XDA Premium app.
help me
can i use adb to change build.prop...
i hav changed build.prop and aftrr i reboot it ends with a boot loop.
i hav to change the build.prop .so does adb help me to do that .
mfmohamedbilal said:
can i use adb to change build.prop...
i hav changed build.prop and aftrr i reboot it ends with a boot loop.
i hav to change the build.prop .so does adb help me to do that .
Click to expand...
Click to collapse
Yes you can, boot to recovery and use adb to overwrite existing and put the original build.prop back in place
Related
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Wrong section.
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.
polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I have the android sdk but after "adb devices" its saying command not found
ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.
i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"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"
}
No boot or recovery img
This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.
Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium
ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
{
"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"
}
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.
zach18 said:
ISSUE
I can not get into recovery mode.
What is happening is a loop. I get booted into the fastboot mode and when i click on recovery, the screen goes black and then right back to fastboot mode.
I read all the related posts, and nothing helped. I downloaded Nexus Root Toolkit v1.6.2 and tried to use it as well but it didn't fix my issue. i took a screen shot of the message from NRT. When i get that message, the phone is just sitting at the fastboot menu.
View attachment 1637759
I also tried one click stock, same issue.
Nexus S
Att
Andriod 2.3.4
baseband version: I9020AUCKE1
KernalVersion: 2.6.35.7-ge382d80 [email protected] #1
build number: gtj61
I kind of think i may have done something when i was trying to unlock this phone a few months ago. Any help is much appreciated. I just want to reset my phone to factory settings.
Click to expand...
Click to collapse
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
fastboot devices
Click to expand...
Click to collapse
It should list your phone.
Then type in
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.
try another computer to install recovery back or just rom manager by wi-fi.
Talal916 said:
First off, download the attached zip.Extract the zip to your desktop. Open up command prompt and navigate to the folder where you extracted the files. Now connect your phone to your computer and boot into fastboot. In command prompt, type in
It should list your phone.
Then type in
Now you can boot to recovery on your phone. Download a ROM you like and flash it from the recovery. Make sure to wipe data/cache before flashing the ROM though.
Lemme know if it works.
Click to expand...
Click to collapse
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.
zach18 said:
Quick question, do i need to do anything special to get into fastboot? other than power button + volume up? The first line on the screen says FASTBOOT MODE. Nothing happens when i type in that command. it goes to the next line but nothing shows up.
any idea why my computer can't see the phone in that line? i probably missing a step.
Click to expand...
Click to collapse
So being curious and trying to further troubleshoot, I followed this wiki to make sure everything was setup correctly.
Howto: Install the Android SDK (Google that, i can't post links yet)
When I typed
adb devices
Click to expand...
Click to collapse
and my device showed up.
But I am still not seeing it when I boot into FASTBOOT MODE, and type
fastboot devices
Click to expand...
Click to collapse
mypat said:
try another computer to install recovery back or just rom manager by wi-fi.
Click to expand...
Click to collapse
How do i install recovery back? where would i find that img?
zach18 said:
How do i install recovery back? where would i find that img?
Click to expand...
Click to collapse
Instal twrp.apk on your rooted phone. Connect to internet and twrp will download the IMG recovery for your phone. Reboot to boatloader and select recovery.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2
Is your phone unlocked?
ej8989 said:
Is your phone unlocked?
Click to expand...
Click to collapse
So I finally figured it out. I do apologize for how vague and un informative the question was. It was a case of me needing to dig a little more.
Here is what i did.
I had installed a Rom Manager, CyonGenMod when i rooted the phone. They had a recovery img in the app which i used. I think googled around for cyogenmod 10 and ICS 4.0.4. Then i realized i had to find google apps, so i could add my contacts from gmail. Then it was just messing around with bootloader to get the right setup.
I do appreciate the help, y'all put me on the right path. Made me find answers to the right questions. Again I apologize for not doing more due diligence.
Thanks for the help
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this
{
"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"
}
and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
johnson234 said:
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this View attachment 2454401 and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
Click to expand...
Click to collapse
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
cmendonc2 said:
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
Click to expand...
Click to collapse
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Edit: I am a first timer a.k.a. newbie. Sorry for that if i don't understand the short form/ slang u used.
johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
cmendonc2 said:
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
Click to expand...
Click to collapse
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
johnson234 said:
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
Click to expand...
Click to collapse
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Sorry to tell you but everytime i try to fastboot, (tried this even before posting the problem here) i get this error. Waiting for like 10mins, the 'waiting for device' message is still there.
Command I used,
fastboot flash recovery TWRP.img -i 0x0b05
Click to expand...
Click to collapse
After pressing enter, i get this
< waiting for device >
Click to expand...
Click to collapse
Edit; sorry for the screenshot, typed the command wrong but tried it with the correct 1 but the outcome still the same.
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
johnson234 said:
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
Click to expand...
Click to collapse
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Graiden05 said:
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Click to expand...
Click to collapse
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
johnson234 said:
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
View attachment 2457522
Click to expand...
Click to collapse
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
So, you suggest that i need to use a different pc to do the fastboot thing? What are the drivers do i need to install? Where can i download it? Maybe my wind8 64bit professional got some flaw/bug. Thanks for helping. Will try it out when i get back home.
cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I get something like this. But when i reboot into android and reboot it, i still get boot into CWM recovery. Nothing changed
Update : I try flashing the TWRP recovery again, but now its freezing on the fastboot mode. Probably still installing. Hopefully everything went well and i can successfully install it.
Graiden05 said:
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
Click to expand...
Click to collapse
After i run this command
fastboot -i 0x0b05 flash recovery TWRP.img
Click to expand...
Click to collapse
it freeze.(I have waiting for 30mins but still nothing significant comes up.)
There is three option to choose from (RCK, Android and WipeData)
Now under the "Device and Printer", there is a fastboot devices (unspecified). But when i see it in properties of this fastboot device, it's manufacturer is still under ClockworkMod. See attachment
Try this guide.
Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
EDIT
AWWW ..... after re-reading my post, I realized the command was wrong ..... its just boot ... not boot recovery ....jeeez
But anyway, even that results in a Bootloop .... so no way to access anything else but fastboot.
momsi said:
Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
Click to expand...
Click to collapse
it wont boot into recovery. boot into bootloader, then recovery, if no recovery, flash a recovery. btw, dont boot a recovery, flash it. if you run the script to boot it, itll only boot once. you need to fastboot flash recovery recoveryname.img
edit.. i noticed that you are booting a recovery. booting it only works for a one time use. dont boot it, flash it.
fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
fastboot boot recovery boots the phone to a recovery image on your PC.
So like fastboot flash...
fastboot boot path\to\recovery.img
Sent from my Nexus 5 using Tapatalk
I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.
momsi said:
I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.
Click to expand...
Click to collapse
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.
simms22 said:
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.
Click to expand...
Click to collapse
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk
rootSU said:
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.
simms22 said:
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.
Click to expand...
Click to collapse
Are you sure? It *shouldn't* work and certainly doesn't for me.
{
"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"
}
rootSU said:
Are you sure? It *shouldn't* work and certainly doesn't for me.
Click to expand...
Click to collapse
you are right
Ah ok
Sent from my Nexus 5 using Tapatalk
Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app
Atomix86 said:
Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
did that ... didn't work....
Didn't work as in the format failed, or the recovery flash failed?
Sent from my Nexus 5 using XDA Free mobile app
I didn't see it mentioned but, have you tried a different alternative recovery? I speak from experience at one point after rooting, my phone would not launch the stock recovery. I then tried to use CWM (it's what I was familiar with) and it wouldn't boot either. I then went to TWRP and it did work.
Is it maybe possible the recovery image you have is corrupted or incomplete? Possible maybe you have the wrong one you're trying to flash and boot? I once mistakenly flashed my tablet with the recovery for my phone. Fixed that issue but it drove me nuts for a few hours wondering why it wasn't working.
Didnt work as in it stuck in the same bootloop again ...
no luck with other recoverys or other ..tried several
i only can enter fastboot
Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
Click to expand...
Click to collapse
{
"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"
}
When in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...
Looks like USB Debugging isn't got successfully enabled on phone.
xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.
binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?
or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot
binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?