so i had just htc dev unocked my one x, now i was using hasoons tool, and when i tried to flash a recovery in fastboot with commands, everything in the prompt said okay.. flashed successful and so on, and the bar on the top right hand side of my phone flickered as if to load, but didint. now when i go to recovery mode, it gives me the splash screen with some red letter **** about distrabution, then reboots. ive tried flashing every possible recovery for the one x, including stock, and seems to do nothing, help??
pic is the screen rite b4 reboot (thats what i get when i reboot into recovery)
EDIT:: now im stuck at the screen in the picture, will not boot into anything else, will not be recognized by adb. PLEASE HELP!!!!
EDIT EDIT: i can power off, and get back into fast boot with volume off, but im almost asuming i just have no recovery..... and it will NOT! boot into the phone no matter what, only booting into that screen... what the **** do i do lol this is kind of a panic now
Have you tried reflashing stock recovery? Also shouldn't you be in the AT&T One X forum unless of course you have the international version of the One X.
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
ixi_devo_ixi said:
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
Click to expand...
Click to collapse
You're suppose to flash stock recovery in fastboot.
I know, I tried when it was getting recognized, now I can't even pick it up with adb
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
ixi_devo_ixi said:
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
Click to expand...
Click to collapse
First of all ADB only works in RECOVERY mode not directly in bootloader. So do the following steps & instal custom rom (Any1 u like).
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!
Related
ive installed a rom and it wont boot (FC's loop), i tried to enter recovery (-vol and power when phone is off) but it keeps trying to boot, ive flashed loads of roms and entered recovery a fair few times so i dont know why i cant do it now!
Do you have the Android SDK or any other adb tool installed on your PC? If you do, try plugging the phone in to the USB port on the PC and open a command prompt.
Type this:
Code:
adb reboot recovery
Not sure if that will work if the phone doesn't boot into Android though. You might have to time it just right, to find a point when the phone responds to adb commands but before it reboots.
How far does the phone get before it reboots? Do you just get the splash screen, the bootanimation, or what exactly happens?
Actually, you might have more luck with using fastboot from a command prompt:
Code:
fastboot reboot-bootloader
I recently tried to flash back from Lego Rom to stock ZVC and have hit some trouble. I used CWM to clear the caches/data, as per usual, but after installing the ZVC rom the phone just boot loops at the Lego Rom boot screen.
Normally, I would jump into recovery, but my volume buttons no longer work (they failed after a screen replacement, I suspect the ribbon cable is damaged). What are my options? Can ADB force it into recovery for me?
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
LordKyleOfEarth said:
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
Click to expand...
Click to collapse
well first of all yes you can reboot recovery using adb.
But if you installed the zvc rooted ROM then why is it booting Lego?
You can install philz or twrp for a full touch recovery and not need volume buttons. You'll still need to use cmd to do "adb reboot recovery" or adb reboot fastboot". You can also flash recovery from adb. Just get a recovery.IMG I think it's adb fastboot flash recovery.IMG or whatever the name of the recovery is.
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
LordKyleOfEarth said:
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
Click to expand...
Click to collapse
I must have not been thinking the whole picture. What can the phone do? What happens when you turn it on, do the volume buttons work at all? Because if you can get into recovery or fastboot at all then something can be done try multiple combinations as much as possible. I'm thinking hold the power button down and plug in USB. Wait for something to happen then let go of power. Does your computer ever recognize something is plugged in? Maybe during boot?
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Which modes can you get into?
TWRP allows you to mount USB OTG. Try flashing something from there.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
Yes, like aniket0317 wrote: if all else has failed, put a ROM on a flash drive, connect it with a USB OTG adapter, and use TWRP.
I've lately had trouble getting my N7 recognized while in recovery mode, though everything's fine while in the bootloader and Android. But with TWRP it's easy to mount external flash storage and install from that.
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
are you able to go into fastboot mode? if so you still have hope
kmaq said:
are you able to go into fastboot mode? if so you still have hope
Click to expand...
Click to collapse
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
RecklessBrandon said:
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
Click to expand...
Click to collapse
download the 4.4.4 image
go to fastboot mode, connect the usb cable to laptop/pc
open command prompt and go to the folder where you have extracted the 4.4.4 image
fastboot oem unlock
type flash-all.bat
if all goes well device should reboot (initally will take some time) if it took more time, reboot again into fastboot mode
this time you can try manually commands one by one
in the folder where you have extracted the 4.4.4 image you will fine "image-razor-ktu84p.zip", extract this zip file as well
execute the following commands one by one:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
device should reboot and if it displays language screen then cool complete the wizard, reboot in to fastboot mode again to lock the bootloader
fastboot oem lock
fastboot reboot
and enjoy!!! do report back what happens.
fastboot -w update stockrom.zip
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
How does it appear in Device Manager? Have you downloaded and installed the drivers?
http://developer.android.com/sdk/win-usb.html
RecklessBrandon said:
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
Click to expand...
Click to collapse
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
I am having the exact same problem, it was installing got stuck on "erasing userdata" for over 2 hours and now nothing will work except for fastboot, and some how the device locked itself again. Only thing i can get to is fastboot mode, the computer recognizes the device. When I try to unlock it, it gets stuck in "erasing userdata" I let it run over night last night hoping it would some how work with no luck. I am unsure of what to do. Is there anyway to install a factory OS without unlocking? Every guide I've searched for has me doing an fastboot oem unlock and then the tablet freezes on erasing userdata. Any help would be greatly appreciated. Thanks!
kmaq said:
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
Click to expand...
Click to collapse
Reread your initial instructions, and it worked! Thank you so much!!!
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
ckpv5 said:
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
if yes then run
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Thank you for reply!
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now. It does not appear under the devices list. If I can just get adb talking with my phone everything else should be easy, I just can't figure out why it's not recognizing it.
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
Click to expand...
Click to collapse
Gitnerd said:
I have not been able to get ADB to recognize the device, which is pretty much my whole issue right now.
Click to expand...
Click to collapse
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
Gitnerd said:
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!!
Click to expand...
Click to collapse
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
ckpv5 said:
I repeat again my reply ...
ADB won't work while on fastboot mode. ADB only while in recovery or on OS running.
You don't need USB debugging on for fastboot
fastboot devices - see whether your device is listed with serial no.
When on bootloader/fastboot mode
run command
fastboot devices
not adb devices
then run these command to install recovery ... you can't install recovery via ADB, only fastboot
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
Oh.. My..God..
You just saved my life, this whole time I thought fastboot utility in AndroidSDK was just a stripped version of ADB. I'm a moron!
I have TWRP up and running holy crap thank you so so so so much, you are seriously a life saver.
try this
Gitnerd said:
I have an HTC One m8 that is stuck on Bootloader. It is an unlocked bootloader with S-Off. I had CWM but I installed stock recovery back onto the phone before flashing a stock kernel (I was trying to make the phone look untampered with before I turned it over to my provider), the Kernel came with a sha1 and was from a trusted website and I am 100% sure it was the right compatible Kernel I'm pretty sure I just had a bad flash.
I have tired the following to get the phone past the bootloader:
1. Fastboot USB Mode --> Try to get ADB to recognize the device --> Debugging mode isn't on (obviously) --> ADB can't recognize the device.
2. Use AndroidSDKSlim/ Android SDK tools / Android Utility to remotely turn on Debugging mode (I got nowhere with this)
3. Attempted to use PdaNet to remotely turn on Debugging mode (got nowhere)
4. HTC Sense doesn't even know whats going on
I just need to get TWRP or CWM or litearlly Any recovery installed. That's all I need, I can do everything from there. I can't remotely install a recovery via adb because adb can't recognize my device because I can't turn Debugging mode on because my device is softbricked!!! Gahhhh. I haven't been able to come up with a way to remotely enable debugging mode or to get adb to recognize my device.
Any ideas/comments/suggestions would be heavily appreciated - I've resourced from every relevant thread I could find. Posting here was a last resort I try to fix things on my own but I'm too many days into this with no results please anybody.
Click to expand...
Click to collapse
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears again (Should be around 10 seconds), press the volume down key.... Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
4) Once you are in the bootlader, select select fastboot by pressing power key.
5)you can flash either permanent or temporary a TWRP recovery once you are in fastboot.
6)Once you are in recovery mode, you can transfer any custom rom to memory or sd card, then install it from the place you chose.
7) you can flash RUU file at fatboot mode as well.