Related
Is there any way to updatinng radio and spl from recovery?
Because i don't understand to do it from fastboot
I'm using hboot : 1.33.2005 and radio : 2.22.19.26I
Sent from my HTC Dream using XDA Premium App
What's the problem in typing
Code:
fastboot flash radio <radio.img>
where <radio.img> is the name of the radio image you want to flash? It's *much* more safe than flashing by recovery.
The only thing to consider: put <radio.img> into the same directory where fastboot is located and start fastboot from that directory, it will ease your life.
There's no problem in there I think but the problem is I can't set up my android sdk in my pc. The pc didn't recognize my phone so I can't go to fastboot
Sorry if my english bad
Sent from my HTC Dream using XDA Premium App
Find the drivers for your phone and u will be set. It should see it. They should install when u plug your phone into the PC. Make sure u are in the right directory when u type fastboot devices
Sent from my HTC Magic using XDA Premium App
I already plug my phone but the notification won't come out. Maybe when the first time long ago i plug my phone i don't pay atention to that. Is there any way to make the notification came out again?
I'm sorry if my english bad
Sent from my HTC Dream using XDA Premium App
For Windows there is the usb removal tool. Google search it. I don't have that at the moment. It will take care of your problem for the usb driver.
Okay. I'll try it and tell you the result
Thank you
Sent from my HTC Dream using XDA Premium App
i already re-install my phone on my pc but it still doesn't work
it only read my phone as a 'memory card'
not an 'android phone'
what should i do?
I ran into a very similar thing two weeks ago. I had previously installed the android USB driver for my Nexus One. Now, when connecting the G1, it was only recognized as USB Mass Storage. After a few reboots and failed reinstallations of the driver, when I had already given up, it suddenly started to work and I was asked for the driver, gave it the correct path and it works just fine since...
Yees
I already tried it so many time too. Even when i'm using htc sync to make it recognized my phone sadly hc sync can read my phone. Eventhough i already reboot my phone many time and i restarting my pc but it still won't work
I'm sorry if my english bad
Sent from my HTC Dream using XDA Premium App
Make sure you don't turn on the mass storage option.
BeenAndroidized said:
Make sure you don't turn on the mass storage option.
Click to expand...
Click to collapse
yes
i'm not turn it on
and i wait if the notification will come out
but it still nothing
use camera+power when you turn on your G1, then connect it to your PC. See if it reconize it as Android phone.
BeenAndroidized said:
use camera+power when you turn on your G1, then connect it to your PC. See if it reconize it as Android phone.
Click to expand...
Click to collapse
I alredy can set my adb and fastboot
Thank you so much for the help
AndDiSa said:
The only thing to consider: put <radio.img> into the same directory where fastboot is located and start fastboot from that directory, it will ease your life.
Click to expand...
Click to collapse
You say I have to put what I want to flash to the same folder as fastboot
So if I want to flash radio, SPL and recovery I have to put them in the 'tools' folder right?
Sorry for my bad english
Sent from my HTC Dream using XDA Premium App
Yes. Tools folder then run the fastboot flash command
Sent from transparent xda app by theimpaler747
Okay
When I want to flash that using fastboot should I go to bootloader mode in my phone?
Sorry for my bad english
Sent from my HTC Dream using XDA Premium App
Yes.
Sent from transparent xda app by theimpaler747
Okay I'll try that and let you know the result
Thank you so much for everything
Sorry for my bad english
Sent from my HTC Dream using XDA Premium App
Just to let u know I don't think I get a notification on my PC when I'm on fastboot mode and plug it in. Just a sound I believe. Just make sure when you plug up and open the cmd prompt u change directories to tools dir before typing fastboot devices and u should get a serial number. Then u are ready to go. If u can boot into recovery u should make a backup first. Put the rom u want to flash on your sdcard too along with the kernel and anything else to make it easier. All after partitioning your card for apps2ext if you plan to use it.
Sent from transparent xda app by theimpaler747
johnson8cyl said:
Just to let u know I don't think I get a notification on my PC when I'm on fastboot mode and plug it in. Just a sound I believe. Just make sure when you plug up and open the cmd prompt u change directories to tools dir before typing fastboot devices and u should get a serial number. Then u are ready to go. If u can boot into recovery u should make a backup first. Put the rom u want to flash on your sdcard too along with the kernel and anything else to make it easier. All after partitioning your card for apps2ext if you plan to use it.
Sent from transparent xda app by theimpaler747
Click to expand...
Click to collapse
Okay
Thank you for your advice
I'll do it
Sent from my HTC Dream using XDA Premium App
Hi!
I'm about to put my SNS up where the sun don't shine..
I've followed this guide:
http://forum.xda-developers.com/showthread.php?t=895545
But when i come to part 2 i have some problems.. The Command Prompt hangs at < Waiting for Device > and nothing happens from here.
All drivers are installed as they should. What would be wrong?
Phones info:
Baseband: I9020XXKD1
Version: GRJ22
Kernel: 2.6.35.7-ge382d80
[email protected] #1
Please help my phone to survive
What operating system are you using? If you're using windows going to device manager and see what it says for android devices.
Sent from my Nexus S 4G using XDA Premium App
cteneyck said:
What operating system are you using? If you're using windows going to device manager and see what it says for android devices.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
I'm using Windows 7 x64 Ultimate - And it says what it should:
When phone is turned on normally:
Android Composite ADB Interface
Phone in Fast-Boot:
Android Bootloader Interface
Nothing should be wrong there..
i would try another usb cable. they have been know to not work. also make sure that your android sdk has been updated fully before starting step 2
Installing PDAnet had proven time and time again to be the easiest and most foolproof method of getting the correct up to date drivers installed. Please try that. Install PDAnet on your machine and follow the prompts. Then try again.
Sent from my Nexus S using XDA App
matt2053 said:
Installing PDAnet had proven time and time again to be the easiest and most foolproof method of getting the correct up to date drivers installed. Please try that. Install PDAnet on your machine and follow the prompts. Then try again.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
truth!
here is their site http://www.junefabrics.com/android/index.php install the free version onto your computer then just follow the on screen instructions. itll install the proper driver for you.
Tried another cable, and using PDAnet - still hangs at Waiting for device...
Does ADB work?
Sent from my Nexus S using XDA App
I am having same problem, so I can relate, but not unhappy with stock. I also can not find anything wrong even on device manager everything looks like out ought to work.
I tried adb fastboot devices and my phone is supposed to show up, but didn't. You might try yours as well, probably get same result.
Makes me think still a problem with the driver.
Sent from my Nexus S 4G using XDA App
matt2053 said:
Does ADB work?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
No idea, i actually don't know what ADB actually is and does?
Hansen1142 said:
No idea, i actually don't know what ADB actually is and does?
Click to expand...
Click to collapse
It is a Command Line Interface application that comes packaged with the Android SDK, just like fastboot. ADB is used to interface with your device while it is booted normally, and fastboot interfaces with your device at the bootloader level.
With your phone booted up into Android, plug in USB and do "fastboot devices". What happens?
But before you do that, let me ask: are you sure when you were having trouble with fastboot that you had the phone in bootloader? You have to hold volume up + power until you see a screen that says FASTBOOT MODE at the top with a lot of other text. You can only use fastboot commands such as "fastboot oem unlock" when the phone is in bootloader.
matt2053 said:
It is a Command Line Interface application that comes packaged with the Android SDK, just like fastboot. ADB is used to interface with your device while it is booted normally, and fastboot interfaces with your device at the bootloader level.
With your phone booted up into Android, plug in USB and do "fastboot devices". What happens?
But before you do that, let me ask: are you sure when you were having trouble with fastboot that you had the phone in bootloader? You have to hold volume up + power until you see a screen that says FASTBOOT MODE at the top with a lot of other text. You can only use fastboot commands such as "fastboot oem unlock" when the phone is in bootloader.
Click to expand...
Click to collapse
I am sure i'm in fastboot, and not Android system
The ADB finds a Device - Screenshot added..
If you are not sure what adb is, I am wondering what method you are using to root?
Sent from my Nexus S 4G using XDA App
q711179 said:
If you are not sure what adb is, I am wondering what method you are using to root?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I am following the guide i'm linking to in first post
Sorry, but using phone and didn't catch the first post after reading few of the others. Since we having same problem I will try it tuesday, which is my next day off work and let you know how out goes.
If you do get this resolved, let me know how you did out.
Sent from my Nexus S 4G using XDA App
Possible problem
So I checked on my device manager and the android device driver says; Android ADB Interface, rather than Android Bootloader Interface.
Anyone that can help me change it to the correct one as I can use ADB to get phone to bootloader but when I type bootloader devices my phone is not found.
Thanks in advance.
Figured it out (maybe lucky guess)
I moved a copy of bootloader from tools folder to platform tools then opened a terminal from that window and it worked.
Bootloader unlocked and on way to full root.
When I saw the port for ICS come out I got really excited and flashed it right away. Then I realized for whatever reason I didnt have SU permissions so I couldn't tether to my computer. I was disappointed but I thought, "no biggie, I'll just restore from my back up." When I flashed my back up the SU app was in my app drawer but I still couldn't tether. As a matter of fact I can't do anything that requires SU but the bootloader still reads unlocked. WTF?
I can't flash a new recovery either. I tried installing from ROM manager, I tried pushing it from my computer but I can't get to the recovery any more. ROM manager says that I have CWM 5.0.2.0 currently installed but I can't get to it at all. Again, WTF?
Sent from my Nexus S 4G using XDA App
^clearly the phone is working perfectly fine with the stock ROM from the back up but obviously I want my SU back.
Root your phone and read the development thread versus making blog posts.
Sent from my Nexus S 4G using xda premium
Flash this http://www.tylerwatt12.com/XDA/ics/root_and_theme.zip and please post in right section
Sent from my Nexus S 4G using xda premium
Thanks for not answering my questions. The bootloader is unlocked but I don't have root and I don't have access to recovery mode even tho ROM Manager says I have Clockwork Mod 5.0.2.0 currently installed. I cannot access the recovery mode AT ALL. I cannot flash or push a new recovery but it fully boots into Gingerbread w/o any issues. What is wrong with my phone and how do I fix it.
Sent from my Nexus S 4G using XDA App
Try from rom manager to reinstall a previous recovery version.
Sent from my LG-P920 using XDA App
That doesn't work either. It goes through the prompts but it doesn't actually reboot do the installation.
I just tried unrooting and then re - rooting but that didn't work and I think that actually wiped my phone completely. I don't even know where an SD card would get into this thing.
Sent from my Nexus S 4G using XDA App
Use adb on your computer and push a clockworkmod recovery.img. And we are trying to help u no need for the sarcasm
Sent from my Xoom using xda premium
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
I also I can't download that zip you linked to. Every time I try it just says failed.
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Esteway.619 said:
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Get cwm image from here CWM Recovery
Sent from my Xoom using xda premium
relock the phone then unlock it again i had the same problem
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
manually go into recovery with volume down and power flash the su.zip and u should be good to go that wat I did
Sent from my Nexus S 4G using xda premium
No suggestions have worked so far. It does not matter what the recovery image name is, whenever I try the flash it Terminal says that it cannot load "***.img" or if I try an install command it says that it cannot find "***.zip" I'm on a snow leopard iMac so I don't need drivers n such.
Let me pose the question like this, what would I do to completely restore the phone to factory condition and try to root it again? Like I said before, the bootloader says that it is unlocked but I do not have any root privileges, could not access the recovery I had before nor install a new recovery after having locked the unlocked the phone's bootloader again.
Sent from my Nexus S 4G using XDA App
http://forum.xda-developers.com/showpost.php?p=13773677&postcount=1
go to the link above and follow the directions for returning to stock.
find yourself a one-click root method on XDA that includes superuser, busybox, and CWM.
EDIT: Also, double check the md5 sum for the CWM .zip. use
Code:
md5 recovery-aaaaaa.img
in the terminal and make sure the output matches whatever is given on the CWM site. if they dont have one up, ask for it
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
hp420 said:
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
Click to expand...
Click to collapse
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Esteway.619 said:
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Click to expand...
Click to collapse
I missed that...my mistake
I'm stuck in TWRP with no OS installed and I'm trying to fix things through adb but I can't access usb debug and enable it so I'm stuck again... What should I do?
Adb should work while in recovery, so you shouldn't need to enable USB debugging.
Use this command:
Code:
adb push ROM.zip /sdcard
Sent from my HTC Desire using xda app-developers app
chromium96 said:
Adb should work while in recovery, so you shouldn't need to enable USB debugging.
Use this command:
Code:
adb push ROM.zip /sdcard
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Yeah that makes sense... thing is device is not being recognised... I'm stuck between fastboot and recovery with no OS installed and I'm trying to flash a ROM to no avail... Been looking at the phone for 2 hours now.
So when you go into recovery and run "adb devices" the phone doesn't show up?
Sent from my HTC Desire using xda app-developers app
Yeah.. Is there anything I could do?
Incredible2011 said:
Yeah.. Is there anything I could do?
Click to expand...
Click to collapse
Try to reinstall the drivers and then try adb commands. Might help.
Sent from my GT-N7100 using xda premium
Fixed. Tried the only USB port out of 4 I hadn't tried. Thanks again.
Incredible2011 said:
Fixed. Tried the only USB port out of 4 I hadn't tried. Thanks again.
Click to expand...
Click to collapse
Good to hear that you solved your problem
Sent from my GT-N7100 using xda premium
So I managed to break the digitiser on my Nexus 4 last weekend. I have most things off it anyway but there are a couple of apps I need to run to get the data I need. I would like to be able to use android screencast to run the couple of apps or use it to set up my bluetooth mouse so I can use that as the screen itself still views fine. However, I need to enable USB Debugging in regular operation.
My phone is rooted, has CWM as the recovery and I have the ADB platform tools downloaded to my mac. This for a Nexus 7 is the closest I have come to an answer of how to do it. However, I can't find these files so I guess they are somewhere else to change these settings?
Any help would be much appreciated, thanks!
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
mike_dangerous said:
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
Click to expand...
Click to collapse
In your recovery, I use twrp, mount system. It should work then.
Sent from my Nexus 5 using XDA Free mobile app
Works! Brilliant thanks! Hopefully the rest of this works!
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
mike_dangerous said:
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
Click to expand...
Click to collapse
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
mike_dangerous said:
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
Click to expand...
Click to collapse
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Your link doesnt seem to work?
mike_dangerous said:
Your link doesnt seem to work?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
mike_dangerous said:
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
Click to expand...
Click to collapse
You most likely wiped the data partition while trying to fix the bootloop.
Would the data partition not be where everything else is stored?
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
theman5511 said:
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
Click to expand...
Click to collapse
If you boot into recovery and then type adb devices is it still offline? It shouldn't be. You can recovery data while in recovery if that's what you're trying to do
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
theman5511 said:
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
Click to expand...
Click to collapse
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well I'll start there and keep you posted. Thanks!
I was able to get TWRP running as my recovery. When I run adb, my device appears as "recovery", however, I'm not able to access the "build.prop" file to edit it so I can ENable USB Debugging. I think this is because I'm not able to remount "system" as read/write. Not sure what my issue is, but when I run adb root, it claims to be already in root, however when I run su in adb shell, it claims it can't find su. Any ideas?