Develop Bugs

[GUIDE] Flash CWM Manually (for noobs)

It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
*--*--* I am not responsible for any damage that may occur to your phone by following this guide or any other guide. If you are at this step, your warranty is already void, and if you lie to Verizon to get a replacement, an angry bear will break into your house and molest you quite thoroughly. Those people are the reason why Verizon is forcing locked bootloaders, and why I had to wait two months to root my Inc2. Don't be one of those people. You might be a noob, but that doesn't excuse you from doing research. In short, anything that happens is your own damn fault, and you can't blame anyone else. /rant *--*--*
Now that that is out of the way, the steps:
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe and adbwinapi.dll, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Boot into fastboot by powering the device off, then powering back on while holding the volume down button on the side. It should boot to a white screen, similar to what you saw when you first rooted it. Plug your phone into usb if you haven't already.
6. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot".
7. Rooting the phone is only the beginning. You still need a rooted kernal, and su and busybox. Without these, rooting does you little practical good. To that end, follow RMK's guide here: http://forum.xda-developers.com/showthread.php?t=1160745. That will get you all set up to start enjoying root fully. I would recommend installing ROM Manager from the market and using it to flash the latest CWM (4.0.0.8). ****NOTE that you need to already have CWM to flash the su and then flasht he new CWM. I know, it seems silly, but that's the way things are. Also, a disclaimer: a few people have had problems with the newest CWM not working properly for them. It worked for me, though, and there is a fix on page four of this thread.
Credit goes to attn1 for the modified CWM, xgunther for posting it/original instructions, and crazythunder of Android Community for the original instructions for using fastboot with a G1. Hope this helps
Some information from supersonic that those trying this on linux will find useful. Thanks!
supersonic2.5 said:
Download this recovery: http://forum.xda-developers.com/showthread.php?t=1134520
BTW, if you havn't installed fastboot, download it here.
http://developer.htc.com/adp.html
1.First rename your android sdk folder to "sdk" just like that. Dont use quotation marks on anything fyi.
2.Next step is to move the sdk folder to your home folder.
3.Move adb, fastboot, and the recovery image from the link above into the tools folder of the sdk.
4.Open up terminal and type or copy this in there.
"cd sdk/tools" hit enter.
5. "./adb kill-server" hit enter.
6. "./adb start-server" hit enter. should look something this. (below)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7. "./fastboot" hit enter.
8. "./fastboot flash recovery cwm-recovery-vivow.img" hit enter
give it some time to flash.
9. "./fastboot reboot" hit enter
10."./fastboot adb reboot recovery" hit enter
And there you go, wait for your phone to reboot and what not and you should have CWM installed. I would immediately do a nandroid of the stock rom. after that i didnt bother messing with superuser on stock froyo because who the hell wants to be on froyo!? lol, so i installed the GB ota rooted version with superuser already because its very stable....found here http://forum.xda-developers.com/showthread.php?t=1161411 as i wait for a stable version of rewind,you can then install and update CWM through rom manager to the current version once you've done this.
there you go buddy sorry so long. if you encounter any problems let me know so i can boot into ubuntu and help out. i'd give you a little more details but im on my mac right now. hit the thanks button if i was any help
Click to expand...
Click to collapse

devator22 said:
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe, adbwinapi.dll, and ddms.bat, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot". And you should be done.
Credit goes to attn1 for the modified CWM, and xgunther for posting it/original instructions. Hope this helps
Click to expand...
Click to collapse
Just a heads up, if you are S-Off, you can enjoy these instructions on Mac, Linux, or Windows. ADB and fastboot give you options for all! <3

Here is another link i found to help out!
http://forum.xda-developers.com/showthread.php?t=1122694

In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.

I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit

b0gman said:
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
Click to expand...
Click to collapse
Dumbest solution ever... I was having the same problem. As long as you've installed the jdk file from the link it shows on the initial error on sdk install...
Just click 'back' then 'next' again on the SDK installer... It worked for me.

Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?

Grouper said:
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
Click to expand...
Click to collapse
Guess I forgot to mention that this is for the people with problems with the automatic installer, including myself.
Sent from my Incredible 2 with Xda app

Clutch McWinner said:
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Click to expand...
Click to collapse
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app

devator22 said:
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
I was, but it turns out I didn't have the HTC sync drivers. S-Off, Rooted, and running overclocked CM7 now!!!!!!!

This must be in Fastboot USB mode while doing?

Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?

SHAKEJONES said:
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
Click to expand...
Click to collapse
Should HTC Sync be opening? I think you're supposed to uninstall HTC Sync, but leave the drivers. AlphaRevX provided a link to the drivers only, so it might be easier to just completely uninstall everything and then reinstall the provided driver instead.

Just tried that and its still stuck... I'll mess with it more tomorrow

Yeah i've been having the exact same problems with the drivers. I have a completely fresh install of windows 7, and it still wont work. I installed the HTC Sync, and it still doesnt recognize my device. I tried using Ubuntu, however it makes absolutly zero sense in my mind, so unless i have a detailed instuctional text, windows is my only choice really. Its funny, this thread is for noobs, yet i can't get even do this, but other phones i've rooted without any problems, and they we're much harder for me. Blah.

I've tried all variations of connection modes, triple checked I had all the files in the right spot, and tried different usb ports and it still wont work... does someone have a more detailed guide for this?

Seriously frustrated about this. S-Off was no problem. I'm triple booted with OSX, Win XP Pro and Linux. Used linux to get s-off but didn't get a CWM install. Window won't allow the driver to install and Linux is a mystery. Anybody have luck with OSX or Linux and want to write it up?

OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.

devator22 said:
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
Click to expand...
Click to collapse
Thank you kind sir hahaha I JUST got done doing that and it worked like a charm! this thread will be a great help to anyone else ---> http://forum.xda-developers.com/showthread.php?t=1122694
The directions for fastboot are in the OP

Haha, yea. I guess I am a noob when it comes to writing guides. I updated the OP with an extra step for booting into fastboot.

Mounting SD card in CWM to PC

So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks

threepio said:
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
Click to expand...
Click to collapse
You can adb pull the dcim folder to your PC.
Edit: You would also be better served in the long run learning to return to stock yourself instead of using a toolkit.
http://forum.xda-developers.com/showthread.php?t=1626895
JM2C

3rdstring said:
You can adb pull the dcim folder to your PC.
Edit: You would also be better served in the long run learning to return to stock yourself instead of using a toolkit.
http://forum.xda-developers.com/showthread.php?t=1626895
JM2C
Click to expand...
Click to collapse
Thanks JM2C. I thought that I might be able to do the ADB pull. I have no idea how ADB works though...
Thanks for the link on the

It's not too complicated. It is a lot of steps but a developer novice can follow the instructions to install and use adb just to pull a few files. Also that's one reason why I let dropbox sync my photos as I take them, so if something happens I have an auto cloud backup.
Sent from my Galaxy Nexus using xda premium
---------- Post added at 05:56 PM ---------- Previous post was at 05:51 PM ----------
threepio said:
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
Click to expand...
Click to collapse
Here is a link to some basic adb instructions:
http://forum.xda-developers.com/showthread.php?t=517874

exportsmedia said:
It's not too complicated. It is a lot of steps but a developer novice can follow the instructions to install and use adb just to pull a few files. Also that's one reason why I let dropbox sync my photos as I take them, so if something happens I have an auto cloud backup.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So I found a tutorial for setting up ADB for the nexus, but all i can get into is the bootloader and the recovery. I cant get my computer to recognize my phone...even though its plugged in. So how would ADB work?

threepio said:
So I found a tutorial for setting up ADB for the nexus, but all i can get into is the bootloader and the recovery. I cant get my computer to recognize my phone...even though its plugged in. So how would ADB work?
Click to expand...
Click to collapse
If you have a custom recovery you should be able to get adb access. You just need to set up the drivers
I believe the previous link I gave even has a small platform-tools download so you wouldn't have to set up the sdk.

3rdstring said:
If you have a custom recovery you should be able to get adb access. You just need to set up the drivers
I believe the previous link I gave even has a small platform-tools download so you wouldn't have to set up the sdk.
Click to expand...
Click to collapse
So when i go into device manager I have Android 1.0 listed under other devices. But when i try to have windows search for drivers, it doesnt find anything. Is ther a specific driver from samsung that I can download somewhere and then point the driver update to it?

threepio said:
So when i go into device manager I have Android 1.0 listed under other devices. But when i try to have windows search for drivers, it doesnt find anything. Is ther a specific driver from samsung that I can download somewhere and then point the driver update to it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1

3rdstring said:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
Ok that worked I now have the android bootloader interface in my device manager....now what? When I open cmd and type "adb devices" nothing comes up

threepio said:
Ok that worked I now have the android bootloader interface in my device manager....now what? When I open cmd and type "adb devices" nothing comes up
Click to expand...
Click to collapse
Boot into recovery (You do have a custom recovery installed?)

3rdstring said:
Boot into recovery (You do have a custom recovery installed?)
Click to expand...
Click to collapse
I have Clockwork mod installed. and still when i try adb devices nothing comes up.

So I got something to work. When I typed adb devices under "list of adb devices attached" i got 0146A5B1301C007 recovery
Is this my phone?

threepio said:
So I got something to work. When I typed adb devices under "list of adb devices attached" i got 0146A5B1301C007 recovery
Is this my phone?
Click to expand...
Click to collapse
yes

now im trying to get the command right.
what is the whole string for adb pull?
*edit*
I found that is---> adb pull <remote> <local>
So I type " adb pull /sdcard/dcim c:\nexus
(i made a file on the root of my c: drive to make it easy to type to pull the files.
but it says /sdcard/dcim does not exist.

threepio said:
now im trying to get the command right.
what is the whole string for adb pull?
Click to expand...
Click to collapse
I've pushed a ROM a few times, never pulled. I would try...
adb pull /sdcard/DCIM c:\
or
adb pull /data/media/DCIM c:\

threepio said:
now im trying to get the command right.
what is the whole string for adb pull?
*edit*
I found that is---> adb pull <remote> <local>
So I type " adb pull /sdcard/dcim c:\nexus
(i made a file on the root of my c: drive to make it easy to type to pull the files.
but it says /sdcard/dcim does not exist.
Click to expand...
Click to collapse
MOTHER EFFING CAPTALIZATIONS! GOT IT WOOOOO pulling all my files as we speak. I wasnt typing the directories with captial letters like they are. I was typing all lowercase. gosh dangit!
THANK YOU THANK YOU THANK YOU

threepio said:
MOTHER EFFING CAPTALIZATIONS! GOT IT WOOOOO pulling all my files as we speak. I wasnt typing the directories with captial letters like they are. I was typing all lowercase. gosh dangit!
THANK YOU THANK YOU THANK YOU
Click to expand...
Click to collapse
Glad you got it working. As was mentioned previously DropBox photo syncing can be a lifesaver. :good:

3rdstring said:
Glad you got it working. As was mentioned previously DropBox photo syncing can be a lifesaver. :good:
Click to expand...
Click to collapse
You know i just got into dropbox. I am going to start using it more.
Now i gotta figure out how to restore the phone. Now that I have the pictures off it, i can toy with resetting it to stock. and starting from the ground up.....fun...

Now I just flashed back to stock using the fastboot from the link posted on page one.
Thanks for your help guys

threepio said:
Thanks JM2C. I thought that I might be able to do the ADB pull. I have no idea how ADB works though...
Thanks for the link on the
Click to expand...
Click to collapse
qbking77 has a great YouTube video walking you thru it. Also has how to return to stock/unbrick
*This Jedi master be a Ninj-ESS*

[WIP] [TUT] How to Root HTC One Xv

Want closed till me and 8trix figure what the hboot update IMG is called
PLEASE HIT THANKS.... READ ALL BEFORE PROCEEDING
FIXED COMMANDS HAD A COMMON MISTAKES
Hi, I am a developer from the " HTC Droid Incredible 4G LTE " My Rom http://forum.xda-developers.com/showthread.php?t=2065615 and I am still a newbie at this developing thing.. So with this being said I am not resposable for anything that could or may happen.*
Now I'm this TUTORIAL I will be providing the links and the instructions on how to proceed on the rooting process
*Requirments*:
-Android SDK - http://developer.android.com/sdk/index.html
-HTC drivers -*http://www.htc.com/us/support/
-The Su .zip - attachment
-And.... The HTC One Xv of course.
STEPS:
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4. To makes matter safer your gonna need to Temp Root, download this : http://uploaded.net/file/h44f6vni
5.Once downloaded, unzip it to C:\Root. Navigate to the folder in the command Prompt by typing *please follow directions CLEARLY
- *cd c:\Root\stuff
- *adb devices
- *adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet! Now type:
- *adb shell "while ! ln -s
/data/local.prop /data/data/com.android.settings/a/file99; do
:; done"
(errors will appear, ignore) Accept the restore on the device, then type:
-adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.) After reboot type:
- adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over. At this point, you can optionally do this ONLY if you want to revert changes:
- rm /data/local.prop
- exit
- adb reboot
Close cmd and start a new one then type
- adb devices
- adb install /system/apps/superuser.apk
- adb push su /system/bin or try adb push su /system/bin/su
6. - adb reboot
7. reboot twice, and if this don't work then please leave a comment and I will explain a new way.
ATTENTION
2nd way to try to root
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4.read carefully
5. create a folder were the superuser.apk and Su file is and name it system and inside that make a bin folder and place the Su file in the bin folder
6.Go to the folder were you extracted root folder in the last root alternative
7.Open cmd in that folder and make sure to extract the files ( superuser.apk and Su file to the root of the root folder )
8.Type : adb devices
9. Type: adb shell
10. Type: adb install ( locate were apk is on your pc.... Here is an Example of what ide put: adb install c:/root/nameOf app.apk , then press enter )
11. Type: adb push su /system/xbin or try adb push su /system/xbin/su or try adb push system/xbin/su /system/xbin/su
12. Use the following command to add the correct permissions to the su binary on the device adb shell chmod 6755 /system/bin/su
13. Adb reboot
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

I'll try when I get ack home tonight,
thanks for this

avid.aria said:
I'll try when I get ack home tonight,
thanks for this
Click to expand...
Click to collapse
Download a ruu to be on the safe side too... There's 2 ways on how you could root
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

Reserved

Another reserved

Hope this helps everyone

Not working
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.

8trix said:
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
Click to expand...
Click to collapse
Me and you will work on finding a way
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

but there is no support for unlocking the bootloader in htc dev , how did you do it ??

Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.

hasoon2000 said:
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
Click to expand...
Click to collapse
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!

lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
To unlock the bootloader is easy, its like any other htc. Go to htc dev site and choose "all other supported devices" and follow the guide. It'll give you the file to fastboot flash to unlock. We're just working on getting root now. HTC definitely did something different with this phone because none of the other methods seem to work. Seems like there are some smart dedicated people working with us so please be patient and keep a watch on this thread!

lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
24ky said:
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Click to expand...
Click to collapse
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?

flipinfin said:
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
Click to expand...
Click to collapse
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app

jose51197 said:
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip

8trix said:
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
Click to expand...
Click to collapse
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium

jmztaylor said:
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
Click to expand...
Click to collapse
I know this is old and not needed anymore since you're putting up root tomorrow, but I wanted to close this with yes, I did re-lock, and it kind of almost worked, like it finished sending the file, but then errored out with some other bs. No woory now though, I am back to fully stock unlocked and will test your root tomorrow if it's up then. Thanks again jmz, great work!

So... how do I get the UI working again? I'm stuck with an unusable UI ._. !

zeratos said:
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
Click to expand...
Click to collapse
Whats wrong?

None of the methods described on the main post work and I got stuck on the unusable UI, I google how to do a factory reset and now it's working again.
Thanks.
Also, is there a way to root this thing?

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1

lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways

lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app

when i tried to push error device not found lol

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.

If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.

Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks

lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.

sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.

tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*

xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.

UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1

Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again

adb issues. tough case.

ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux

If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you

ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..

pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.

Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.

did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons

thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.

I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?

I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app

xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas