I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
bmckeeoneill said:
I unlocked the bootloader on an old HTC One S through the directions on the HTC Developer website. I then loaded the CWM recovery and did the rooting and installed the Rom manager app. The SuperSU update had to be added with the abd sideloader and the rootcheck said it had root access. Both of those programs seemed to be working fine. Then I send the Zip file of a ROM (idk which one because I renamed it so it would be easier to enter) and from the ROM manager I select the one I just sent and go to install it.
Then the phone turns off and a long string of code ends with "transfer successful" or something to that effect but stays there. I rebooted and tried again and the same thing. Tried again and did a factory reset from the recovery but nothing would get the phone to boot past the HTC screen. I tried Wiping the davlik cache and the regular wipe and hard reset and adding the recovery again but NOW MY PHONE DOESNT SHOW UP WITH ADB DEVICES CMD.
I am already in over my head but I have been enjoying learning from this and other websites about how android works. However I think I have exhausted my research options and I am at dead end...
How can I get the adb commands to work again?
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
Related
I've installed TripNRaver's AOKP ROM on my One X and now I can't boot into recovery.
I've unlocked the bootloader
ADB seems to work fine but when I try adb reboot recovery it says device not found
I can connect my phone to my laptop and transfer files on to it
I've managed to get CWM on it by downloading the APK and transferring it to my phone
I can boot into bootloader but when I select Recovery it just boots into TripNDroid's ROM
I have downloaded the RUU and try to run it off my friend's PC (i'm on osx) but that couldn't seem to locate my phone either
When my phone is plugged in fastbood does change to fastboot USB
Any ideas?
It sounds like you have "fastboot" checked somewhere in settings. Not the fastboot you use to flash, but the one that makes the phone boot up quickly.
I don't think so. I can't even find that in settings. I think that's a Sense thing not an aokp thing. I've discovered that I need to lock the bootloader to run ruu so i've done that. I'll borrow my friend's pc again and try that again. If that fails... any other ideas?
under options/power there's a checkbox which enables fastboot, what lowandbehold mentioned. disable this and you should be able to boot with power+volumedown to fastboot and from there to recovery.
I'm pretty sure that's a Sense thing you know. It's not on here.
get in the bootloader, fastboot erase cache, problem solved...
I did this before and it didn't work. I tried it again just now and somehow it worked. I have no idea why or how but it did. So thank you!
Won't go into recovery
First post on here, so be gentle!
Rooted One X that I'm trying to install the ARHD on using the instructions here: http://forum.xda-developers.com/showthread.php?t=1562603
Before I tried this, I had root access and Clockwork Recovery installed. All working fine.
So, read the instructions on the thread, but have only got as far as flashing the boot.img - which gave me the OKAY! to tell me it was successful and the cache erase OKAY as well.
So all I need to do is the superwipe and then flash the ARHD ROM from recovery.
That is the problem - I now can't access recovery. Fastboot isn't enabled, I've tried using vol-down/power, QuickBoot app and select 'recovery', etc., but each time it tries to go to recovery I see an Android character with his stomach internals on show for a split second, and then the phone just reboots normally. I've tried erasing the cache again from bootloader, but after that it still won't go into recovery.
Am I missing something simple here, or can anyone suggest what I need to do?
JC12345 said:
First post on here, so be gentle!
Rooted One X that I'm trying to install the ARHD on using the instructions here: http://forum.xda-developers.com/showthread.php?t=1562603
Before I tried this, I had root access and Clockwork Recovery installed. All working fine.
So, read the instructions on the thread, but have only got as far as flashing the boot.img - which gave me the OKAY! to tell me it was successful and the cache erase OKAY as well.
So all I need to do is the superwipe and then flash the ARHD ROM from recovery.
That is the problem - I now can't access recovery. Fastboot isn't enabled, I've tried using vol-down/power, QuickBoot app and select 'recovery', etc., but each time it tries to go to recovery I see an Android character with his stomach internals on show for a split second, and then the phone just reboots normally. I've tried erasing the cache again from bootloader, but after that it still won't go into recovery.
Am I missing something simple here, or can anyone suggest what I need to do?
Click to expand...
Click to collapse
Have the same problem.
what can we do?
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
So, newb me did a bad thing. I managed to install TWRP Recovery on my Nexus 5 to attempt rooting it. It didn't work a t first so I tried cleaning up some existing data. I did a factory reset, a format data, and... drumroll... advanced wipe, where I selected everything.
When I went to reboot, TWRP told me there was no OS.
I've already downloaded the stock KitKat for my device and the sdk tools (and even the unified android toolkit found here in the forums). I couldn't find a way to flash stock yet
It seems my device does not connect on USB in ADB mode, it only shows Recovery mode. Trying "fastboot flash" gets stuck on "< waiting for device >". Using "adb devices" shows something like "some_number recovery".
Any suggestions? I can do adb shell but I don't know how to restore the files I deleted without flashing or how to make flashing work.
Thanks a lot
Someone resolved this same issue. http://forum.xda-developers.com/showthread.php?t=2533148
That worked like a charm.
Thanks a lot!
Hey,
i've got a few problems with my HTC One S, running Cyanogenmod 11 (4.4.4) with TWRP as recovery.
Since a few days nearly every app crashes, ca. 3 minutes after I start the phone. In these minutes everything is working. After that there are only messages that "android.process.acore", "com.google.process.gapps" and nearly every other app has been closed. When I press OK, the message appears again.
So I tried to flash another ROM, which isn't possible because I first can't copy anything to the phone, the copying process stops after the half. I also couldn't download a ROM directly to the phone. Then I tried to flash again my actual ROM which is still on the phone, I selected the .zip in TWRP, but then the phone is restarting and nothing happened.
There are also other problems:
1. I tried a soft reset in the settings, isn't possible because nothing happens when i press the "Confirm" button
2. Clear storage and Factory reset in the boot loader isn't possible, when I select one of that the phone only starts into the recovery, without anything has been resetted
3. Pushing a zip with ADB doesn't work, it says I don't have permissions to copy anything on the storage
4. The ADB sideload mode doesn't start in TWRP
5. I tried to flash CWM as recovery, it says "successful", but when I start into recovery there is still TWRP..
6. Relocking the bootloader doesn't work, it also says "successful" but in the bootloader appears "*** unlocked ***" After that I tried to turn back to stock ROM with the RUU exe by HTC, but when the process starts, the phone just turns off.
Does anyone have a idea? Do I maybe have a virus? Sometimes it appears to me that there are problems with the storage or anything like that..
I really tried to do everything, and also searched in this forum and in other but I didn't find anyone with the same problem..
Thank you!
Give the Mount option a try in TRWP and see if you can copy a ROM over to the phone.
Okay I had to install the right driver for adb..
Then adb push worked, I could select the .zip in the Install option in TWRP, but the phone again just restarts without installing the rom..
ADB Sideload also worked with the driver, but after I tried to ADB sideload the ROM it said "* failed to write data 'protocol fault (no status)' *"..
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Just do a manual restore using the google factory images (google them, first result usually and a VERY user friendly page, thanks google!).
Don't use the script, just reformat everything via fastboot, then manually flash the images to their respective partitions.
"cd [path to unzipped images]"
"fastboot format /[partition] ext4"
"fastboot flash /[partition] [path to image]"
and so on and so on. Then after, "fastboot reboot". I assume you've found a fix by now but maybe someone else will stumble on this. Keep in mind, I'm writing this from memory and with no drivers or way to test this on my mac, my Nexus S is coming in the mail soon so take what I say with a grain of salt and try to double check the commands. For the most part however, they should be correct. format, reflash, reboot. All you should have to do.
padhpataka said:
Hi guys, I'm normally the one who reads these forums, not starts them, so i'm in pretty desperate help.
I have a Samsung Nexus S phone that somehow got stuck in a bootloop after my dad attempted to fix the problem by wiping everything he could from the recovery; cache, system, data, factory reset. I am able to access fastboot (obviously). In fastboot mode, the only 4 options it gives are POWER OFF, REBOOT, RECOVERY, REBOOT BOOTLOADER. None of these options leads to any progress. Only one that makes sense is to click and run recovery. When recovery loads, i can:
Reboot system now
apply update from ADB
apply update from sd card
wipe/factory reset
wipe cache partition
I recently rooted and custom ROMed my Galaxy J7 Pro, and as you experts may know it wasn't too easy finding the correct files or even the support for it.
I know you have to have developer options enabled and OEM and USB Debugging as the prereqs for rooting, but this phone has nothing. I'm not sure what to do. The bootloader is locked and I obviously can't enable developer options. I guess where I'm stuck is how i can flash a custom recovery like twerp for a phone that has a locked bootloader that can't be unlocked through developer options.
As I'm writing this, i was thinking, can i prepare an SD card with the lollipop OS for the nexus to install and run on. Ive already wiped the internals and cache of the phone, meaning there is nothing on it?
Help would be appreciated, bringing back a phone that has the potential (working hardware) to run would be great.
Click to expand...
Click to collapse
I have the same problem.I know this was 4 years ago but as a noob I find that guides tend to assume greater levels of knowledge than I have. Trying to bypass FRP as I think this is what is causing the "system error" message when I try to access play store or Google plus. I haven't even been able to unlock bootloader or root phone . In fact I find "fastboot" and ADB downloads a mystery? How to get them to work?