Database Info

[Q] Water Damage - Please Help Recover Data!

I had a unfortunate incident where my waterproof jacket failed. My phone was inside the waterproof pocket and ended up being soaked.
The phone turned it self off and when I had turned it on the screen turned yellow.
Immediately pulled out the battery and let it sit in rice for 3 days.
Now when I turn it on it gets stuck at the google logo screen and never shuts off. I have to pull the batter to turn it off.
I can go into fastboot mode and my options are:
reboot bootloader
reboot
recovery
power off
If I choose recovery it simply goes back to the google logo again and sits.
Some additional info about the phone:
product name - hearing
hw versoin - rev 11
bootloader version - 19020xxka3
lock state - locked
I can access the unlock bootloader screen however it says if I unlock it it will erase all of my data which I do not want to do.
My main goal is recovering the data on the phone. I have a few files that I absolutely need to recover.
If my phone never works again, that is fine so long as I can access the data off of this phone.
Any help troubleshooting would be greatly appreciated.

sj_martin said:
I had a unfortunate incident where my waterproof jacket failed. My phone was inside the waterproof pocket and ended up being soaked.
The phone turned it self off and when I had turned it on the screen turned yellow.
Immediately pulled out the battery and let it sit in rice for 3 days.
Now when I turn it on it gets stuck at the google logo screen and never shuts off. I have to pull the batter to turn it off.
I can go into fastboot mode and my options are:
reboot bootloader
reboot
recovery
power off
If I choose recovery it simply goes back to the google logo again and sits.
Some additional info about the phone:
product name - hearing
hw versoin - rev 11
bootloader version - 19020xxka3
lock state - locked
I can access the unlock bootloader screen however it says if I unlock it it will erase all of my data which I do not want to do.
My main goal is recovering the data on the phone. I have a few files that I absolutely need to recover.
If my phone never works again, that is fine so long as I can access the data off of this phone.
Any help troubleshooting would be greatly appreciated.
Click to expand...
Click to collapse
HMMMMMMMMMMM. If you were rooted already I might have been able to sugest something more from here. Maybe someone else can elaborate based on my suggestion as far as how to get it done not
In fastboot: when you connect to the PC does it give you an option to connect USB Storage? Or, better: Go into recovery. Then, from there hit power and volume up at the same time. See what options are there. (I don't remember if there is one to mount US storage Try this before that and after your fully in recovery: connect and see if the usb storage will mount to your computer.
Wait, instead of erasing that: you said you couldn't get into recovery. But if you happen to: try that.
Otherwise first see if it mounts usb storage when in fastboot. I'm not sure if it would. I know if fastboot you can run fastboot program on your computer and pull the imgs if you needed system files and what not; but, you wouldn't be able to get them if you can't read the usb storage from your computer in the first place.
Edit again: Sorry, just tried mounting in fastboot. Doesn't work. Hmmmmmmm.
---------- Post added at 10:40 PM ---------- Previous post was at 10:27 PM ----------
BlackHawkA4 said:
HMMMMMMMMMMM. If you were rooted already I might have been able to sugest something more from here. Maybe someone else can elaborate based on my suggestion as far as how to get it done not
In fastboot: when you connect to the PC does it give you an option to connect USB Storage? Or, better: Go into recovery. Then, from there hit power and volume up at the same time. See what options are there. (I don't remember if there is one to mount US storage Try this before that and after your fully in recovery: connect and see if the usb storage will mount to your computer.
Wait, instead of erasing that: you said you couldn't get into recovery. But if you happen to: try that.
Otherwise first see if it mounts usb storage when in fastboot. I'm not sure if it would. I know if fastboot you can run fastboot program on your computer and pull the imgs if you needed system files and what not; but, you wouldn't be able to get them if you can't read the usb storage from your computer in the first place.
Edit again: Sorry, just tried mounting in fastboot. Doesn't work. Hmmmmmmm.
Click to expand...
Click to collapse
Ok, again. I don't know if this would work: I can't test this out. If anyone else knows or could confirm.
IF, you can use ADB while in fastboot (Anyone know if you can or can't? Never tried it; can't test it right now) check this post out about how to mount the storage using ADB: http://groups.google.com/group/android-developers/browse_thread/thread/485d7b04bc61d7be
I'm not sure if you can use ADB in fastboot though as you usually do it while the OS is on and debugging mode is enabled. Not sure how it would work from fastboot.

I feel like I have a chance at salvaging the data. Here are some additional notes after poking around a little bit.
This phone is completely stock, never unlocked, never rooted. Never even had a chance to turn on debugging mode before it was water logged.
With that said, here is what I have done and am able to do so far.
I've installed the Android SDK + ADB drivers. I am using both XP and Win 7 to test. I can see the phone in the device manager in windows and adb is working correctly in command prompt.
However when I do "adb devices" it does not show the phone as a device. I think it might be because it needs to be in debugging mode however I cannot turn on the phone to get to that stage.
With that said, it looks like once someone can help me get ADB to recognize my device there are commands where I can extract the data out of the phone via adb.
So, can anyone help troubleshoot getting windows to recognize my phone in command prompt? Again, I can see the phone in the device manager and have installed the correct drivers.
Thanks

sj_martin said:
I feel like I have a chance at salvaging the data. Here are some additional notes after poking around a little bit.
This phone is completely stock, never unlocked, never rooted. Never even had a chance to turn on debugging mode before it was water logged.
With that said, here is what I have done and am able to do so far.
I've installed the Android SDK + ADB drivers. I am using both XP and Win 7 to test. I can see the phone in the device manager in windows and adb is working correctly in command prompt.
However when I do "adb devices" it does not show the phone as a device. I think it might be because it needs to be in debugging mode however I cannot turn on the phone to get to that stage.
With that said, it looks like once someone can help me get ADB to recognize my device there are commands where I can extract the data out of the phone via adb.
So, can anyone help troubleshoot getting windows to recognize my phone in command prompt? Again, I can see the phone in the device manager and have installed the correct drivers.
Thanks
Click to expand...
Click to collapse
heres what you can do, unlock boot loader, install clockwork mod make a backup of the current rom installed, and try to work with that somehow heres the link for unlocking the bootloader and installing the recovery!
btw if you get clockwork installed you'll be able to access the sd card storage!
http://forum.xda-developers.com/showthread.php?t=895545
I'm not exactly sure that you can install a recovery without unlocking the bootloader but I'm sure one of the devs can use their tools to pull the /system & /data off of your device. if that's not what you need I'm pretty sure your sd card isn't wiped when you unlock the bootloader, I'm assuming only the phone is reset. Just read all the similar posts here about recovering data using recovery or ADB

anishs said:
heres what you can do, unlock boot loader, install clockwork mod make a backup of the current rom installed, and try to work with that somehow heres the link for unlocking the bootloader and installing the recovery!
btw if you get clockwork installed you'll be able to access the sd card storage!
http://forum.xda-developers.com/showthread.php?t=895545
I'm not exactly sure that you can install a recovery without unlocking the bootloader but I'm sure one of the devs can use their tools to pull the /system & /data off of your device. if that's not what you need I'm pretty sure your sd card isn't wiped when you unlock the bootloader, I'm assuming only the phone is reset. Just read all the similar posts here about recovering data using recovery or ADB
Click to expand...
Click to collapse
The issue here is that if I unlock the bootloader it will wipe EVERYTHING. There seems to be a way to side load clockwork via ADB if I could actually connect via ADB if I had debugging mode on which I cannot turn on.
Everything I read says unlocking bootloader will wipe all data. I haven't seen anything that states the data is maintained, have you?
Thanks.

download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.

sj_martin said:
The issue here is that if I unlock the bootloader it will wipe EVERYTHING. There seems to be a way to side load clockwork via ADB if I could actually connect via ADB if I had debugging mode on which I cannot turn on.
Everything I read says unlocking bootloader will wipe all data. I haven't seen anything that states the data is maintained, have you?
Thanks.
Click to expand...
Click to collapse
as i said just try to load the recovery following that guide, try it without unlocking the bootloader if it doesn't work you have to unlock the bootloader, and maybe your sd won't be wiped but you phone data will

Luxferro said:
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
Click to expand...
Click to collapse
I understand how to use cwr however i need to get that loaded onto the phone first, and for me to load it to the phone i need adb i need the computer to be able to recognize it first which it wont. it shows it in the device manger, and all the drivers are installed correctly however in command prompt when i type "adb devices" it does not list it.

Luxferro said:
download the SDK, or just the necessary files to use adb and fastboot.
then download a CWR recovery.img
the do a fastboot boot recovery CWR_filename.img. that will boot the CWR image without flashing it, from there you can try a backup. then mount the SD card from CWR, and then copy the backup to your pc.
if it won't backup your files, or won't mount your sd card partition, then most likely your data is corrupted.
Click to expand...
Click to collapse
When your phone is plugged into your PC and in fastboot mode, does the command
fastboot devices
show any results? If so, follow Luxferro's advice.
If you've got no warranty, you could take your phone apart to see the motherboard, and spray it with isopropyl alcohol which will properly dry it.
Sent from the future to put right what once went wrong.

For those telling him to try fastboot boot it doesn't work without an unlocked bootloader.
Sent from my Nexus S MV from the XDA Premium app.

If the bootloader is locked it might prevent u from flashing recovery (I dunno mine always been unlocked). But I'm not telling him to flash a new recovery. U can just boot a recovery without flashing it (again not sure if locked bootloader prevents this... but its not writing to the phone just booting a external recovery.img).
Fastboot boot recovery filename.img
Worth a try
Sent from my Nexus S using xda premium

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"
}
Also it looks like I have 2 threads in the same section now, it looks like mods moved my posts so sorry for double replying.

bedalus said:
When your phone is plugged into your PC and in fastboot mode, does the command
fastboot devices
show any results? If so, follow Luxferro's advice.
Click to expand...
Click to collapse
Yes, it sees it now. It looks like I kept trying "adb devices" as shown on the screen shot. So now when I do fastboot devices I see my device and try to boot clockwork 5.0.2.0 but run into a boot fail:
It says i need to unlock the bootloader which I cannot do if i want to preserve data =/

10 character delete

Ive seen some uncertainty here, so I'll offer my advice (the limited I feel qualified to give).
Unlocking the boot loader will erase everything. Considering your goal is data retrieval, I would definitely NOT ever do that.
Unfortunately, having a locked bootloader severely limits your options.
My opinion on the matter is your best bet is ADB, but if the data is not time sensitive, I would let this topic get a bit more exposure. (perhaps mirror post on some other forums like xda too)
Hopefully someone more knowledgeable can post and help you out.

sj_martin said:
Yes, it sees it now. It looks like I kept trying "adb devices" as shown on the screen shot. So now when I do fastboot devices I see my device and try to boot clockwork 5.0.2.0 but run into a boot fail:
It says i need to unlock the bootloader which I cannot do if i want to preserve data =/
Click to expand...
Click to collapse
I just tried cw 3.0.0.5 per this thread:
http://forum.xda-developers.com/showthread.php?t=931865
and still get the same failure stating i need to do fastboot oem unlock

Is your bootloader even unlocked?

mathkid95 said:
Is your bootloader even unlocked?
Click to expand...
Click to collapse
No it is not. That's the point of this thread. It was a completely stock phone trying to recover data.
There is a method to root + recovery with locked bootloaders
"WITHOUT oem unlock & wipe" http://forum.xda-developers.com/showthread.php?t=931865
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Click to expand...
Click to collapse

kenvan19 said:
For those telling him to try fastboot boot it doesn't work without an unlocked bootloader.
Sent from my Nexus S MV from the XDA Premium app.
Click to expand...
Click to collapse
Just want to restate this. If his bootloader is locked he is pretty much SOL. He needs data off if it but to get the data he has to wipe the phone.
To the poster above me, that method no linger works. You cannot root without unlocking the bootloader. You cannot flash or boot a custom recovery without unlocking the bootloader. The links in that thread are dead.
One more time just to be sure Ira clear: you CANNOT get into a custom recovery without unlocking the bootloader.
Sent from my Nexus S MV from the XDA Premium app.

I've been looking everywhere on how to get ADB to work without debugging on; however, the only shred of hope I saw was the ability to get into your stock recovery. I didn't read on as you said you can't so it wouldn't help you anyways.
BUT!, if somehow do get into it (Or want to try to get into it over and over again and hope it works) you might be able to use ADB there. Then, that link I posted in the beginning should work to mount the storage.
Edit: Just looking at the pictures and you said you don't see the device in ADB. Have you tried actually going into ADB Shell and seeing if it connects to the phone? Mine device didn't "Show" in the list when I was using ADB but it worked.

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[Q] Custom ROM on TF300T

HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!

robscar said:
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
Click to expand...
Click to collapse
You need a custom recovery! download twrp here: http://techerrata.com/browse/twrp2/tf300t
DOWNLOAD THE ONE THAT SAYS "openrecovery-twrp-2.5.0.0-4.2" and flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob" make sure you rename the blob to "twrp.blob"
*update your info your bootloader is "10.6.1.15.3" instead of "10.6.1.12.3"
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

You can also follow this guide. It explains what you need to do pretty well. But you do need a custom recovery, which i prefer TWRP http://forum.xda-developers.com/showthread.php?t=2187982

I was confused at first too. I think they need to change the wording in the tutorials. They say "If you're on JB bootloader, this twrp, if you're on 4.2 BL, that TWRP" and i was just thinking... WTF, both of them, 4.1 and 4.2 are jellybean.... it should be changed to 4.1 BL and 4.2 BL, none referred to as JB.
Sent from my TF300T using Tapatalk 2

So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.

robscar said:
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
Click to expand...
Click to collapse
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!

I've a TF300TG but I think my question is associated to the title of this thread. Do I have to note the sku of my Pad or isn't that important when I flash a custom Rom?
In the threads of many custom Roms I've read nothing about the sku. So I'm not sure if I have to take care for this.
Sent from my HTC One X using xda app-developers app

noahvt said:
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
Click to expand...
Click to collapse
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.

robscar said:
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
Click to expand...
Click to collapse
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2

diesburg said:
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
Click to expand...
Click to collapse
I got these files from the SDK download for MAC.

robscar said:
I got these files from the SDK download for MAC.
Click to expand...
Click to collapse
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!

robscar said:
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
Click to expand...
Click to collapse
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

diesburg said:
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
So, no matter what I do, the bootloader has to be unlocked, correct?

robscar said:
So, no matter what I do, the bootloader has to be unlocked, correct?
Click to expand...
Click to collapse
for a custom rom, as far as i know, yes
but for just root on stock rom i believe theres ways to root stock without unlocking the bootloader
Sent from my TF300T using Tapatalk 2

I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!

robscar said:
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
Click to expand...
Click to collapse
It's most likely drivers.
http://forum.xda-developers.com/showthread.php?t=1917237
Maybe that'll help?
Sent from my TF300T using Tapatalk 2

I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!

robscar said:
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
Click to expand...
Click to collapse
not sure exactly how a mac works but i believe its some sort of linux. can you by chance start the terminal with "administrator" priveleges or type "su" in the terminal to get root priveleges? Just my thoughts with a "permission denied" error, you dont have administrator/root access.
In that link i shared above about mac and fastboot, it says to use " ./ " in front of every command. So try the fastboot commands i said above to flash the recovery but do it with ./ infront like this: ./fastboot flash commands
Sent from my TF300T using Tapatalk 2

Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!

robscar said:
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
Click to expand...
Click to collapse
In the steps I told you above. The part where you do the fastboot commands in the terminal. "fastboot flash 0x(somenumber) recovery twrp.blob"
put a ./ in front of the fastboot command... so its "./fastboot flash 0x(thatnumber) recovery twrp.blob"
Sent from my TF300T using Tapatalk 2

Help please.

Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?

C-4Nati said:
Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?
Click to expand...
Click to collapse
if you are on S-ON flash 4ext recovery
format all partitions except sdcard from 4ext
enable smartflash from 4ext
flash the rom
done

@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"

JJeamy said:
@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to

C-4Nati said:
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to
Click to expand...
Click to collapse
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)

jmcclue said:
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)
Click to expand...
Click to collapse
This is it.
{
"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"
}

C-4Nati said:
This is it.
Click to expand...
Click to collapse
ok, have u fastboot setup on ur pc?

jmcclue said:
ok, have u fastboot setup on ur pc?
Click to expand...
Click to collapse
I'm not sure so I'm assuming that means no lol.

C-4Nati said:
I'm not sure so I'm assuming that means no lol.
Click to expand...
Click to collapse
click the first link i posted n set it up

jmcclue said:
click the first link i posted n set it up
Click to expand...
Click to collapse
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.

C-4Nati said:
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.
Click to expand...
Click to collapse
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..

JJeamy said:
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..
Click to expand...
Click to collapse
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
edit -it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up.

C-4Nati said:
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
Click to expand...
Click to collapse
what OS you have on your computer?

Mile_zdr said:
what OS you have on your computer?
Click to expand...
Click to collapse
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1

C-4Nati said:
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1
Click to expand...
Click to collapse
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.

C-4Nati said:
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.
Click to expand...
Click to collapse
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer

Mile_zdr said:
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer
Click to expand...
Click to collapse
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.

C-4Nati said:
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.
Click to expand...
Click to collapse
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work

Mile_zdr said:
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work
Click to expand...
Click to collapse
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).

C-4Nati said:
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).
Click to expand...
Click to collapse
?
I don't know what to tell you... :/ do you have another sim card from other carrier just to see everything work's okey?

[Q] Nexus 5 power button doesn't work anymore

Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.

PeauMorte said:
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
Click to expand...
Click to collapse
Hoping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?

Primokorn said:
Hopping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Click to expand...
Click to collapse
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.

PeauMorte said:
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
Click to expand...
Click to collapse
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.

Primokorn said:
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Click to expand...
Click to collapse
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?

PeauMorte said:
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
Click to expand...
Click to collapse
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)

Primokorn said:
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Click to expand...
Click to collapse
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*

PeauMorte said:
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
Click to expand...
Click to collapse
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
PeauMorte said:
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
Click to expand...
Click to collapse
Put the file into your platform-tools folder (where you have fastboot.exe file)

Primokorn said:
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
Put the file into your platform-tools folder (where you have fastboot.exe file)
Click to expand...
Click to collapse
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?

PeauMorte said:
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
Click to expand...
Click to collapse
Did you rename the downloaded file to "TWRP.img"? The file name must be the same into your command prompt.
Copy TWRP.img into your platform-tools folder then open a command prompt from this folder and enter: fastboot boot TWRP.img
The path is the directory of your file you want to use. If you open the command prompt from the folder you have TWRP.img (platform-tools) then you don't need to mention the path.

I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.

vin4yak said:
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
Click to expand...
Click to collapse
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.

Primokorn said:
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Click to expand...
Click to collapse
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:

PeauMorte said:
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
Click to expand...
Click to collapse
Happy for you... and your data

Primokorn said:
Happy for you... and your data
Click to expand...
Click to collapse
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.

PeauMorte said:
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
Click to expand...
Click to collapse
Yes, you can! Just make sure you don't restore the /efs partition which contains the imei and other files which are unique to every device!
- Sent from an IceCold Hammerhead!