Today I bought the HTC One X
I immediately jumped on xda looking to root, I've rooted in the past with Samsung Infuse and Motorola Backflip, and I'm very discouraged right now
I installed the One_X_ATT_All-In-One_Kit_v2.1 and everything was going well, until I tried to flash the TWRP recovery, and it ran, but didn't at the same time it was very odd
Anyway, in Fastboot I can't flash a recovery because the cmd promt says "error: device not found"
also, there is no OS installed so I'm in a constant bootloop
Main Issues:
- device not found
- boot loop
- recovery won't work because the SD card won't mount, something along those lines
- also day of the super bowl...
Not sure why this is all happening, who can help me out? Willing to donate...
***** TAMPERED *****
***** UNLOCKED *****
EVITA PVT SHIP S-ON RL
HBOOT - 1.14.0002
RADIO - 0.19as.32.09.11_2
OpenDSP - v29 1.0.45.0622
eMMC - boot
Jun 11 2012 14:26:28
You probably factory reset in bootloader by accident... You'll have to plug the phone in and right click on removable storage and format. Even though it doesn't recognize it should still format.
When in fastboot, type in --> fastboot devices
See if it sees anything
Sent from my One X using Tapatalk 2
It also sounds maybe drivers aren't working? I have no idea. Just throwing an idea out there.
Sent from my One X using xda app-developers app
InflatedTitan said:
You probably factory reset in bootloader by accident... You'll have to plug the phone in and right click on removable storage and format. Even though it doesn't recognize it should still format.
When in fastboot, type in --> fastboot devices
See if it sees anything
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I ended up relocking my device, and below **** RELOCKED **** it says **** Security Warning ****
also, typing in fastboot devices worked at first, it showed up, then i relocked device and now it doesn't show up.
Plugged into computer, doesn't show up though, it's charging can't format
Since your relocked (you shouldn't have but its cool lol) download the RUU matching the firmware your phone is using... Run that and it should get you back to stock
Sent from my One X using Tapatalk 2
InflatedTitan said:
Since your relocked (you shouldn't have but its cool lol) download the RUU matching the firmware your phone is using... Run that and it should get you back to stock
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
How am I gonna be able to do any of this if the device can't be found in order to try and flash it?
Can you take the SD card out,and use external SD card to USB to format
Sent from my Dell Streak using xda app-developers app
Reinstall HTC drivers.. Restart computer, and plug USB into back of comp if on desktop, main USB if laptop and try again. Make sure when in bootloader if says fastboot USB in red.
Once again type fastboot devices
See what happens...
Also... Try to right click on your adb/fastboot folder and choose "open command prompt here"... Run CND from that path and see if it helps... Just a thought....
Sent from my One X using Tapatalk 2
GREATTT!!! for some reason now, on my HOX the fastboot usb is only available for one second...
I can't find anything anywhere on this problem, when i boot into bootloader, it's for less than a second... Unbelievable
Relax, then try a different port and cord combo. Then if possible try a different pc
Sent from my HTC One XL
swagglikerichie said:
GREATTT!!! for some reason now, on my HOX the fastboot usb is only available for one second...
I can't find anything anywhere on this problem, when i boot into bootloader, it's for less than a second... Unbelievable
Click to expand...
Click to collapse
ok I fixed this problem, so now I am still stuck on the error: device not found issue
that's my main concern, I can't flash because it can't find the device
Man there's some funny business going on... Try to right click on your adb/fastboot folder and "open command prompt here".... See if that does anything better
It should find it if your in fastboot. You at least sound fairly knowledgeable about most of it.. So I can't say user error... As wrecker said try different ports, try reinstalling HTC drivers and restart computer... Try unplugging and plug back in
Sent from my One X using Tapatalk 2
you can always try with linux then you dont have to mess up with additional drivers
InflatedTitan said:
Man there's some funny business going on... Try to right click on your adb/fastboot folder and "open command prompt here".... See if that does anything better
It should find it if your in fastboot. You at least sound fairly knowledgeable about most of it.. So I can't say user error... As wrecker said try different ports, try reinstalling HTC drivers and restart computer... Try unplugging and plug back in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
fastboot can find it now, and I was able to read the CID, just 11111111
going to try and flash from fastboot command prompt, how long does it take usually to download boot.img through DOS?
swagglikerichie said:
fastboot can find it now, and I was able to read the CID, just 11111111
going to try and flash from fastboot command prompt, how long does it take usually to download boot.img through DOS?
Click to expand...
Click to collapse
Have no clue, why would you do that? Why not just download a recovery image and fastboot it
Sent from my One X using Tapatalk 2
InflatedTitan said:
Have no clue, why would you do that? Why not just download a recovery image and fastboot it
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
What are other methods of flashing not through the AIO Kit Hansen2000 or something like that?
Also, I tried this http://www.androidauthority. com /one-x-revert-stock-recovery-76854/
and it seemed like it worked, but still no OS installed, constant boot loop
swagglikerichie said:
What are other methods of flashing not through the AIO Kit Hansen2000 or something like that?
Also, I tried this http://www.androidauthority. com /one-x-revert-stock-recovery-76854/
and it seemed like it worked, but still no OS installed, constant boot loop
Click to expand...
Click to collapse
Don't use anything that's not from xda. OS stands for OPERATING SYSTEM! you need to install a recovery first. The toolkit should have contained the recovery image. It should be like open recovery.twrp.2.3.3.img or something like that. Download that file, and drop it in your adb/fastboot folder. Enter fastboot, right click on adb/fastboot folder and choose open command prompt here. Type this --> fastboot flash openrecoveryname.img
^^^ of course replace the end with the exact name if the recovery script you downloaded. Easy peasy right? If you manage to become successful, reboot bootloader and now you can boot into your "custom" recovery (twrp) . if you manage to be inside twrp, High five yourself.
Back on your computer, download cleanrom 5.1.. I'll explain why later once you have a working phone again.
"Mount" in twrp. Watch for your computer to prompt you if what you want to do. Choose "open to view files" or something like that. Next window is your sdcard. Drag cleanrom5.1.zip anywhere on your SD card, just remember where.
In twrp, unmount. Choose install, find the cleanrom5.1.zip. Flash that biootch. Let it boot and report back with any questions
Sent from my One X using Tapatalk 2
So if you run into any more device not found stuff, put the folder of the one x toolkit directly in the root of your C drive. That worked for me.
Edit: I think this actually solves a different issue that I may have confused with yours, but worth a try.
Sent from my HTC One X using xda app-developers app
you should of just run a ruu when phone said fastboot usb and left it stock for life until you learn something
you should also stop using the toolkit and learn to do it all manually first, i haven't yet used the toolkit since this phone is super easy once you learn the basic android stuff and read. flashimagegui is ok since it allows for flashing roms on fly without using pc.
InflatedTitan said:
Don't use anything that's not from xda.
Click to expand...
Click to collapse
Agreed. This webpage the OP mentioned is not even for our phone, its for the quad core version (code named ENDEAVORU). Which is often the case if you go to other websites. They don't clearly delineate between the dual core and quad core versions, which can lead to a real brick.
Particularly in this case, if the file had flashed properly, you would have bricked. Installing the recovery from the wrong device is a bad idea. And recovery is not the same as the OS or ROM.
As others have suggested, it seems the OP needs to read and learn a lot more before doing anything more with the phone, or else permanent damage is going to happen.
Related
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot
heh...not bad
Cool but next time try themes and apps
I like the skeleton, very different.
Did you sign this? I get signature verification failed.
Mast3rpyr0 said:
Did you sign this? I get signature verification failed.
Click to expand...
Click to collapse
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
RikusHaven said:
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
Click to expand...
Click to collapse
Thats what i did.
Mast3rpyr0 said:
Thats what i did.
Click to expand...
Click to collapse
Try the one I have attached then. All I did was load the .png into EVOSplash from this tread: click. Should work.
Mast3rpyr0 said:
Did you sign this? I get signature verification failed.
Click to expand...
Click to collapse
dont mean this to be offensive, but just to double check and be thorough, you do have the eng hboot loaded, yea?
as a general FYI, fastboot is basically very limited on all other RUUs, except eng. perhaps the OP could list, eng hboot required.
i guess the OP cant read this is the DEV section no the theme app section !
It would also be nice if the OP didn't post a new thread in apps/themes for every splash screen he makes. OP, do everyone a favor and put them all in one thread.
Got you!, thanks for the reminder
RikusHaven said:
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
Click to expand...
Click to collapse
Thanks for the help!
Sweet ass twist with the Powell ripper splash, man. Think you could do one up with the Powell screaming hand?
neckface said:
Sweet ass twist with the Powell ripper splash, man. Think you could do one up with the Powell screaming hand?
Click to expand...
Click to collapse
Wow... You are bringing up some past... The old Lucero behind bars logo or the Natas Claw/prism would be sweet too.
thenewguy821 said:
Click to expand...
Click to collapse
Dude! Those would be so sick. Especially the behind bars logo. Is the signed Natas deck yours? That thing is worth money.
Nah.. I had both of those back a few years (cough 23-25 years ago). I actually had the First Lucero behind bars, which was just eyes looking out and the bars were straight, as my first board. Later got one like the one I linked, but in a dark tealish color. A couple years later, I had the Natas design I posted, on a black board. The later designs had a little more detail, but similar logo. Some of the old Dogtowns were sweet. I think I remember them having an old ST (Suicidal Tendencies) logo board.
ok, I had to formatt my computer the other day and reinstall windows, i reinstalled sync and not sure what Im missing here, when I go into bootloader and open a command window, I type in adb devices and it wont show my device, but my computer shows that the phone connected with its little "ding" and yes usb debugging is on, before I formatted I had successfully pushed the "black splash" screen so Im not sure whats goin on here.
BAleR said:
ok, I had to formatt my computer the other day and reinstall windows, i reinstalled sync and not sure what Im missing here, when I go into bootloader and open a command window, I type in adb devices and it wont show my device, but my computer shows that the phone connected with its little "ding" and yes usb debugging is on, before I formatted I had successfully pushed the "black splash" screen so Im not sure whats goin on here.
Click to expand...
Click to collapse
i'm having a similar problem. i can mount my sd card and transfer files back and forth all day, so communicating between my phone and pc isn't a problem, but i cannot get adb or fastboot commands to work to save my life.
full root, yadda yadda.
Did you reinstall sync?
Goto device manager and verify the drivers are installed. Also make sure u reinstalled android ask.
Sent from my PC36100 using XDA App
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Did you boot up the xoom? And do a DB reboot bootloader? Then fastboot OEM unlock?
Sent from my Xoom using xda premium
Yes I did...
Was it unlocked when you sent in? If so it may still be unlocked.
Sent from my Xoom using xda premium
It was unlocked, but they've upgraded the software to 3.2.2 and it's locked again.
It might not be. They don't have to lock it to flash it. And they probly didn't check either.
Sent from my Xoom using xda premium
Ok....pardon the ignorance but how can I tell? I no longer have Superuser. I can't even flash a custom image. Should I downgrade it to 3.0, Root, and then flash it with the Custom 3.2.2 found here on XDA?...
No not that way it screws it up! Use this and only this! Skip the unlock and see if the files work, then you know you were still unlocked.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
tdetroit said:
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
Click to expand...
Click to collapse
That's because your timing is slightly off, and you're letting the stock recovery overwrite your custom recovery. You have to "catch the boot"
You can follow these steps:4. Install recovery image (CWM)
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/show....php?t=1074979 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery recovery-solarnz-100611-1150.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
tdetroit said:
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Click to expand...
Click to collapse
I got mine back yesterday morning then used the Universal Xoom Root instructions and files to root it yesterday afternoon. Perfect!
-ts
I've tried that...won't work. As far as my timing being off....I'm literally watching the Screen the whole time...I never even get anything except the Fastboot Protocol screen...nothing changes. I simply can't go further. I've tried loading the img file (Step 4), but can't even get that far. I've spent an hour on the phone with Motorola yesterday and after being bounced to 5 different techs, they told me to contact the developer.....which I've done, with no success. I'm almost tempted to send this damn thing back and ask them to revert my device and install an older OS onto it.
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
hammer4203 said:
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
It is. That was the first thing I've checked.
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
hammer4203 said:
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Ah, I will do that. Matter of fact, I'll download it to my other laptop...which never had any sort of anything SDK related on it, give it a fresh start. Thanks....will do this when I get home this evening.
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
tdetroit said:
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
Click to expand...
Click to collapse
Nevermind. IT WORKED. I ended up using my work laptop. Something's wonky with both of my personal laptops....either way, it's now unlocked. Thanks for everyone's help and patience.
Ur welcome! Also remember your mouse on a desktop? Took me weeks to figure out the damn thing was causing the bsod errors, and it seemed to work perfectly fine. I would back up your computers you have issues with and do a fresh install on them. I do every 6mo or so.
Sent from my Xoom using xda premium
So here is what I did... Last night i successfully unlocked my bootloader on my AT&T HTC Onc X and established root. I was running the AT&T RUU_Evita_UL_Cingular_US-1.82.502. I then tried to update this morning to AT&T RUU_Evita_UL_Cingular_US-1.85.502(desktop installer type) it kept giving me errors and would not complete. Like an idiot i tried to flash CleanROM 2.0 -★| 1.85.502.3 | Tweaked! | Stable! | CWM Install! through CWM and it installed successfully but my WIFI would not work at all. So i decided to reload CleanROM DE 1.0 -★| which had worked fin in the past. At the end of the installer it said to do a factory reset and I did. After the reboot is where i noticed my problem. I am stuck on the boot animation screen. Not able to get into the phone at all now. I am able to get back to the bootloader menu.. boot into CWM but unable to reflash the room on the sdcard. It will not mount USB storage. None of the stock desktop installer will recognize my device is plugged in....... ANY SUGGETIONS...or am I screwed....
Is it in a boot loop or is it frozen on the HTC One screen? That happened to me last night but I was able to run the RUU installer. Did you make sure HTC Sync wasn't running, and that you killed adb by using adb kill-server before trying the RUU installer?
Apologies if you've done these things already, I'm just grasping at straws here.
If you can do adb reboot bootloader, you should be able to run the RUU installer from there, no?
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
taterdog2 said:
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
Click to expand...
Click to collapse
If you have adb on your computer (from the Android SDK) and the drivers installed, you should be able to access the device from fastboot (bootloader). RUU will work if you can get your device into fastboot. I'm doing it right now (I wanted to try it before telling you).
Just remember, if you were on an unlocked 1.82 when you borked it, you need to be locked again before you can use RUU. Just use fastboot oem lock from the command prompt.
If you can get to the bootloader screen you are not bricked. Why can't you run the RUU like normal from there? Just re-lock your bootloader first.
Poster above beat me to it while I was taking forever to post.
1. Hold down your Volume Down Button and your power button
2. Wait for the device to turn off and keep holding the combination until you boot into the bootloader (It might take a couple tries, don't give up)
3. Plug your device into your computer via the OEM USB Cable
4. Use the Volume Up/Down keys and the Power button to select the Fastboot Option
5. Wait till the device is recognized (The text on screen where it said Fastboot should become Fastboot USB)
6. Go to the folder where you have fastboot installed and type:
fastboot oem lock
7. Go back to the bootloader and into fastboot when its done with relocking. Make sure the text on the top of the screen says "Relocked" or "Locked" (under the Tampered flag)
8. Run the RUU while in fastboot mode. Use version 1.85.
I sorry for being a NOOB... step 6. Go to the folder where you have fastboot installed and type:
fastboot oem lock...
when you refer to "having fastboot installed" I am taking it that you are not refering to the RUU installer... where do I get this FASTBOOT file from to install?
I think I figured it out... will let yall know in a few minutes
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
taterdog2 said:
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
Click to expand...
Click to collapse
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
jmattp said:
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
Click to expand...
Click to collapse
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
ted77usa said:
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
Click to expand...
Click to collapse
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
jmattp said:
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
Click to expand...
Click to collapse
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
ted77usa said:
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
Click to expand...
Click to collapse
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
jmattp said:
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
Click to expand...
Click to collapse
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
ted77usa said:
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
Click to expand...
Click to collapse
Once you unlock your bootloader on 1.85 you will not need root to flash CWM Recovery
i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...
albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question
like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.
looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes
i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.
I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.
Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above
rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..
snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers
rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?
snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading
jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.
theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight