Database Info

Access ADB without Debug mode?

Is there a way I can use ADB without setting debug mode on my phone? I am unable to startup the phone to switch to debug mode. When I start up the phone it goes to the google logo screen and stops there.
I am able to go into fastboot mode however. I have adb installed and all the drivers set.
I can see the phone in my device manager, but when I open up cmd prompt and type in adb devices it says it does not see anything.
Any help would be greatly appreciated!

ADB is only for when the phone is booted up. In your case you will need to work with fastboot
Sent from my Nexus S 4G using xda premium

sj_martin said:
Is there a way I can use ADB without setting debug mode on my phone? I am unable to startup the phone to switch to debug mode. When I start up the phone it goes to the google logo screen and stops there.
I am able to go into fastboot mode however. I have adb installed and all the drivers set.
I can see the phone in my device manager, but when I open up cmd prompt and type in adb devices it says it does not see anything.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
What are you trying to use ADB to do? You can run ADB in recovery, but if you are unable to startup the phone, I don't know anything you could do with ADB to fix it.

Rem3Dy said:
ADB is only for when the phone is booted up. In your case you will need to work with fastboot
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes as stated all I can do is go into the fastboot screen. It sounds like that I cannot use adb in fastboot?
What options do I have to recover data in fastboot if i do not have adb?
Thanks.

derekwilkinson said:
What are you trying to use ADB to do? You can run ADB in recovery, but if you are unable to startup the phone, I don't know anything you could do with ADB to fix it.
Click to expand...
Click to collapse
I wanted to use ADB to extract some files on the sandisk internal hd. I cannot boot up the phone anymore but it still turns on (but freezes at the google logo).
I also cannot go into recovery as when I try it also stalls at the google logo screen.

sj_martin said:
Yes as stated all I can do is go into the fastboot screen. It sounds like that I cannot use adb in fastboot?
What options do I have to recover data in fastboot if i do not have adb?
Thanks.
Click to expand...
Click to collapse
Yes. Adb will Not work in fastboot. Fastboot flash commands will work.

sj_martin said:
I wanted to use ADB to extract some files on the sandisk internal hd. I cannot boot up the phone anymore but it still turns on (but freezes at the google logo).
I also cannot go into recovery as when I try it also stalls at the google logo screen.
Click to expand...
Click to collapse
Is your bootloader unlocked? If so, flash a new recovery image and do a nandroid backup
Sent from my Nexus S 4G

If recovery doesn't work u have 2 options from fastboot to try to get into recovery:
1) fastboot flash recovery recovery.img
2) fastboot boot recovery recovery.img
All u need is a cwr recovery image. And the files on ur PC to use fastboot.
1) flashes a new recovery
2) just boots up the new recovery without flashing it
Sent from my Nexus S using xda premium

Luxferro said:
If recovery doesn't work u have 2 options from fastboot to try to get into recovery:
1) fastboot flash recovery recovery.img
2) fastboot boot recovery recovery.img
All u need is a cwr recovery image. And the files on ur PC to use fastboot.
1) flashes a new recovery
2) just boots up the new recovery without flashing it
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
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"
}

Another interesting note (i don't know if this will help me at all) is that if I boot up into download mode (holding both vol buttons when plugging in the usb cord) it gets stuck at the "unlock bootloader?" screen but in windows under the device manager instead of showing it as an android device with adb it is now under the usb controllers as "samsung usb composite device".
If I could get this thing to mount to my computer that would be fantastic and I could just drag and drop files out of the phone.
Any ideas?

If you flash clockwork recovery, you can boot into recovery and then use cwm to mount USB storage.
Sent from my Nexus S using XDA App

If I flash clockwork I need to unlock the bootloader, if I unlock the bootloader I have to wipe all my data.
So by nature of getting clockwork on the phone is useless to me since i'll have no data to backup by that stage =/

I do have access to fastboot now and is recognized via command prompt; is there a way to extract data via fastboot?

sj_martin said:
I do have access to fastboot now and is recognized via command prompt; is there a way to extract data via fastboot?
Click to expand...
Click to collapse
No and its rather preferred you not start two threads about the same issue.
Sent from my Nexus S MV from the XDA Premium app.

help me
can i use adb to change build.prop...
i hav changed build.prop and aftrr i reboot it ends with a boot loop.
i hav to change the build.prop .so does adb help me to do that .

mfmohamedbilal said:
can i use adb to change build.prop...
i hav changed build.prop and aftrr i reboot it ends with a boot loop.
i hav to change the build.prop .so does adb help me to do that .
Click to expand...
Click to collapse
Yes you can, boot to recovery and use adb to overwrite existing and put the original build.prop back in place

[Q] Fastboot Problems

I am trying to flash a custom recovery with fastboot but it is not working. When i put the device in fastboot mode it says"Starting Fastboot USB download protocol" but the screen doesn't change. When I flash it in CMD it says it finished but the device still does nothing. Then the same when I try to reboot it via flashboot. It says it is done but the device does nothing and I still have no custom recovery.

charger04 said:
I am trying to flash a custom recovery with fastboot but it is not working. When i put the device in fastboot mode it says"Starting Fastboot USB download protocol" but the screen doesn't change. When I flash it in CMD it says it finished but the device still does nothing. Then the same when I try to reboot it via flashboot. It says it is done but the device does nothing and I still have no custom recovery.
Click to expand...
Click to collapse
If fastboot is not working you need to look at 2 things: 1)Android SDK is not installed or 2)driver is not installed correctly. BTW, is your device rooted and unlocked and what version of firmware?
Edit: Also make sure usb debugging is checked in settings.

buhohitr said:
If fastboot is not working you need to look at 2 things: 1)Android SDK is not installed or 2)driver is not installed correctly. BTW, is your device rooted and unlocked and what version of firmware?
Edit: Also make sure usb debugging is checked in settings.
Click to expand...
Click to collapse
I second what buhohitr says...an unlocked tab is imperative to the process.

My device is unlocked but not rooted( I am trying to root it right now). I think it might be the SDK. I'm not sure if I installed it so I will do that now. Thanks
Sent from my Nexus 4 using xda app-developers app

Are you saying it says finished on the cmd prompt? Then it is done :cyclops:
I think you are missing the point.
It won't immediately take you into recovery.
You need to send the reboot command, then power off, power on again with vol down held down until the 4 icons appear, then volume up on RCK which should be default and now you should be in a custom recovery

sbdags said:
Are you saying it says finished on the cmd prompt? Then it is done :cyclops:
I think you are missing the point.
It won't immediately take you into recovery.
You need to send the reboot command, then power off, power on again with vol down held down until the 4 icons appear, then volume up on RCK which should be default and now you should be in a custom recovery
Click to expand...
Click to collapse
Yes I tried that and it just shows a dead android.
Sent from my Nexus 4 using xda app-developers app

charger04 said:
Yes I tried that and it just shows a dead android.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ah ok it wasn't clear. Are you sure you are unlocked?

sbdags said:
Ah ok it wasn't clear. Are you sure you are unlocked?
Click to expand...
Click to collapse
Yeah... When I boot it says "this device is unlocked"
Sent from my Nexus 4 using xda app-developers app

charger04 said:
Yeah... When I boot it says "this device is unlocked"
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
OK, so everything is clear, you're unlocked. Now back to my previous post:
1. SDK installation (check step 1 (jre java, you probably already have this...everyone does and step 3: SDK)
http://forum.xda-developers.com/showthread.php?t=1842969
2. USB driver:
http://forum.xda-developers.com/showthread.php?t=1706588
Make sure your usb debugging and unknow sources are both checked in settings. (if they are not, please try first before proceed to step 1).

[Q] Ways to get files into phone

Hi, I am having a very very newbie problem. I tried going for F2FS but mistakenly flashed a ROM that is meant for F2FS-all while I only have /DATA formatted as f2fs. I ended up with a ROM that won't get past google logo and since I formatted /data, I have no ROM zips on the device.
I tried to adb push files in and adb flash google stock image but to no avail because I couldn't get the google drivers and the adb to work. I have tried Google USB Driver, Universal Driver, Naked Driver etc. And yes, I have removed previous driver before testing the new one. I already have Android SDK installed but no matter what I do, Windows could not recognize my n5. It keeps saying that the device is unrecognizable and it shows up as "unknown device" in Device Manager. Also yes, I connect to PC while it is in fastboot mode. Tried another pc, same result.
Tried to have recovery (i have TWRP 2.7.1.1) to mount USB otg but I couldn't get it to mount. Tried a cable I made myself and also one I bought from ebay. The cables both worked when the phone isnt screwed.
So now I am wondering if there is any other way to get files into the phone? Also I have an idea of moving the system files that are meant for f2fs to /data temporarily, then format /system and cache as f2fs and move the files back to /system. Would that work? Thanks in advance.

Just to confirm, you are booted into recovery when trying to use adb right?

You can use sideload function to flash your zip files in recovery, don't you?

rootSU said:
Just to confirm, you are booted into recovery when trying to use adb right?
Click to expand...
Click to collapse
No, the fastboot mode. The one with the android bot lying down and guts exposed. Recovery mode works with adb?
Rip95 said:
You can use sideload function to flash your zip files in recovery, don't you?
Click to expand...
Click to collapse
I tried adb sideload, couldn't do it because windoze doesn't recognize my n5. It kept saying "one of the device connected is malfunctioning".

hawktalon said:
No, the fastboot mode. The one with the android bot lying down and guts exposed. Recovery mode works with adb?
I tried adb sideload, couldn't do it because windoze doesn't recognize my n5. It kept saying "one of the device connected is malfunctioning".
Click to expand...
Click to collapse
Flash the factory image and get rid of f2fs. It's not ready for prime time and you're not ready for it.
The android with it's guts is recovery, push vol up
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the factory image and get rid of f2fs. It's not ready for prime time and you're not ready for it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I know. I made a silly mistake. The problem now is that I can't get any ROM files into the phone bcs adb and usb-otg isnt working. Any ideas how to get files into the phone?

hawktalon said:
No, the fastboot mode. The one with the android bot lying down and guts exposed. Recovery mode works with adb?
I tried adb sideload, couldn't do it because windoze doesn't recognize my n5. It kept saying "one of the device connected is malfunctioning".
Click to expand...
Click to collapse
You can't use adb in fastboot mode.. Flash a custom recovery and boot into it to perform sideload commands.. Not sure whether stock recovery supports it or not.
hawktalon said:
I know. I made a silly mistake. The problem now is that I can't get any ROM files into the phone bcs adb and usb-otg isnt working. Any ideas how to get files into the phone?
Click to expand...
Click to collapse
You don't need to transfer the factory images to your device to flash them.. They are flashed via fastboot.

vin4yak said:
You can't use adb in fastboot mode.. Flash a custom recovery and boot into it to perform sideload commands.. Not sure whether stock recovery supports it or not.
You don't need to transfer the factory images to your device to flash them.. They are flashed via fastboot.
Click to expand...
Click to collapse
I already have a custom recovery. TWRP 2.7.1.1. I've tried sideload commands and adb commands, the problem is that windows won't recognize the phone when connected via usb. Also, I've tried using adb in both fastboot and twrp. Neither of them worked.
I know I don't have to actually get the files into the device, and I should be using adb to flash but adb isn't working for me since Windoze decided that my device is malfunctioning and ignores all the driver I tried.

hawktalon said:
I already have a custom recovery. TWRP 2.7.1.1. I've tried sideload commands and adb commands, the problem is that windows won't recognize the phone when connected via usb. Also, I've tried using adb in both fastboot and twrp. Neither of them worked.
I know I don't have to actually get the files into the device, and I should be using adb to flash but adb isn't working for me since Windoze decided that my device is malfunctioning and ignores all the driver I tried.
Click to expand...
Click to collapse
Might be a driver issue as well?? Have you downloaded the usb_driver from SDK manager and updated the Nexus drivers from the device manager?
If you can't get adb to work then see whether "fastboot devices" returns your phone in cmd? Fire this command when the phone is in bootloader/fastboot mode. If it does, then you can go ahead with flashing the factory images.

Has to be a driver issue
You have no choice but to get the drivers working on a computer. You have to be able to push files to your phone with adb or use fastboot and the stock files to get your phone back up and rolling.
Keep on trying. I had to mess with mine a bunch as I had multiple old drivers from old phones...
You could try something like un-installing the drivers then running a registry cleaner (assuming Windows). I like Ccleaner. Give your computer a reboot and try again.
You can message me if you want computer help.

flyboy_9 said:
You have no choice but to get the drivers working on a computer. You have to be able to push files to your phone with adb or use fastboot and the stock files to get your phone back up and rolling.
Keep on trying. I had to mess with mine a bunch as I had multiple old drivers from old phones...
You could try something like un-installing the drivers then running a registry cleaner (assuming Windows). I like Ccleaner. Give your computer a reboot and try again.
You can message me if you want computer help.
Click to expand...
Click to collapse
This
And remember fastboot in bootloader and adb in recovery
Sent from my Nexus 5 using Tapatalk

I already have a custom recovery. TWRP 2.7.1.1. I've tried sideload commands and adb commands, the problem is that windows won't recognize the phone when connected via usb. Also, I've tried using adb in both fastboot and twrp. Neither of them worked.
Click to expand...
Click to collapse
Use this guide to install adb driver for your nexus (just yesterday i had the same problem) run sideload in recovery and then do this:
http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
On step 5 you will be prompted to choose device type, and driver itself. You must click google adb driver, and choose android adb interface. But you should install google adb drivers first in order to choose this driver for your nexus.
UPD. Same guide in this forum: http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

flyboy_9 said:
You have no choice but to get the drivers working on a computer. You have to be able to push files to your phone with adb or use fastboot and the stock files to get your phone back up and rolling.
Keep on trying. I had to mess with mine a bunch as I had multiple old drivers from old phones...
You could try something like un-installing the drivers then running a registry cleaner (assuming Windows). I like Ccleaner. Give your computer a reboot and try again.
You can message me if you want computer help.
Click to expand...
Click to collapse
Tried all the drivers and toolkits I can find. It still says "one of the device has malfunctioned..." and device manager shows my n5 as unknown device. I did ccleaner on registry everytime I tried new solutions. I also uninstalled the previous drivers.
rootSU said:
This
And remember fastboot in bootloader and adb in recovery
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was afraid to be wrong so I tried both.. no difference, still couldn't get it to work.
Rip95 said:
Use this guide to install adb driver for your nexus (just yesterday i had the same problem) run sideload in recovery and then do this:
http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
On step 5 you will be prompted to choose device type, and driver itself. You must click google adb driver, and choose android adb interface. But you should install google adb drivers first in order to choose this driver for your nexus.
UPD. Same guide in this forum: http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
On my pc it doesn't show google adb driver, it only shows unknown device. I already have adb installed and is properly working since I can issue adb commands but my phone is not connected somehow.

On my pc it doesn't show google adb driver, it only shows unknown device. I already have adb installed and is properly working since I can issue adb commands but my phone is not connected somehow.
Click to expand...
Click to collapse
.
You didn't get it. I tried to tell you how to fix this:
Tried all the drivers and toolkits I can find. It still says "one of the device has malfunctioned..." and device manager shows my n5 as unknown device.
Click to expand...
Click to collapse
Since windows can't install driver for your nexus you should choose your device in device manager and install it by yourself (follow the guide i linked). When you fix your device driver you'll be able to use adb commands in recovery.

Rip95 said:
.
You didn't get it. I tried to tell you how to fix this:
Since windows can't install driver for your nexus you should choose your device in device manager and install it by yourself (follow the guide i linked). When you fix your device driver you'll be able to use adb commands in recovery.
Click to expand...
Click to collapse
Yes, I tried the steps in the url. It only shows my phone as unknown device, there was no adb devices listed. Also, I have tried using the manually upgrade driver method, windoze gave me the response saying "windows has determined that the best driver is installed" even though I pointed it to the driver directory. I also tried the "have disk" method, pointing to the google driver directory and on a seperate attempt pointed to naked driver and universal driver directory. It picked up the .inf file but too gave me the response "no suitable driver found... make sure it is meant to work with x64....'. Again I tried on another pc which is 32 bits, it gave me "no suitable driver found...".
This is where I am at. I am starting to suspect that the usb on my n5 is the faulty one. But then, it was working before all of this happened.

Try changing USB ports and cables on computer
Sent from my Nexus 5 using Tapatalk

Oh, well...
*uninstalling driver*
Your device looks like that?
{
"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"
}

rootSU said:
Try changing USB ports and cables on computer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes... I tried that. Used original cables for my galaxy s2 and n5, also tried some nokia and china cables. Ports I've used them all, even gone to the extend of trying USB hubs lol..
Rip95 said:
Oh, well...
*uninstalling driver*
Your device looks like that?
View attachment 2798388
Click to expand...
Click to collapse
No, it doesn't show nexus 5. It shows unknown devices. I'll attach a picture.

No, it doesn't show nexus 5. It shows unknown devices. I'll attach a picture.
Click to expand...
Click to collapse
Looks like TWRP have adbd or device issue. You can try install Philz touch recovery via fastboot.

Sorry guys, had a big finals exam i the past months. Am back now yay! Thanks for the attemps so far guys.
Rip95 said:
Looks like TWRP have adbd or device issue. You can try install Philz touch recovery via fastboot.
Click to expand...
Click to collapse
I can't install anything right now since the phone is basically empty due to formatting /data to f2fs and I can't adb in nor sideload. It's a really big mess.
One thing I wanted to point out is that does USB gets disabled if fast charge is enabled in the kernel? I remembered turning on fast charge in elementalX when I installed it. I really don't want to send this in for warranty since this device is actually not available in my country, had to buy it from Australia and now if I have to warranty it, I ahve to send it to Australia. Plus, I'm sure this isn't covered in warranty either.

[Q] Softbricked Nexus 5, can't enable USB Debugging -> adb doesn't work

Hi guys
I accidently wiped my whole phone (Caches, Data, Internal Storage & System).
After reading trough the forum I found out that I need to flash the Stock image via adb/fastboot.
The problem is that adb won't recognize my phone due the lack of enabled USB Debugging (no OS installed).
I already tried it, on both, Mac and Windows.
I have no idea what I should do now. I would really appreciate it, if you could help me guys.
Thanks in advance.
YM

1) you do not flash stock images using adb. Adb is not fastboot. They are different things
2) you can only use adb in android or recovery. USB debugging is an android only setting. It is NOT needed to use adb in recovery. Adb will not work in the bootloader
3) fastboot only works in the bootloader. It is fastboot to flash stock images.
Sent from my Nexus 5 using Tapatalk

rootSU said:
1) you do not flash stock images using adb. Adb is not fastboot. They are different things
2) you can only use adb in android or recovery. USB debugging is an android only setting. It is NOT needed to use adb in recovery. Adb will not work in the bootloader
3) fastboot only works in the bootloader. It is fastboot to flash stock images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you for your fast answer.
But ./adb devices doesn't shows any devices.
And neither does ./fastboot devices.

Let's stick with Windows for now
So boot into bootloader. Adb devices won't work here as explained. Fastboot devices should. If it doesn't you need to read the adb and fastboot drivers thread
Sent from my Nexus 5 using Tapatalk

rootSU said:
Let's stick with Windows for now
So boot into bootloader. Adb devices won't work here as explained. Fastboot devices should. If it doesn't you need to read the adb and fastboot drivers thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It doesn't work.
I read this thread http://forum.xda-developers.com/showthread.php?t=2588979 and installed the drivers.
I also found out that my Nexus doesn't even show up in the Windows Device Manager.
What could be the reason for that?

Windows, drivers, cables.. It have to keep trying. It's the only way
Sent from my Nexus 5 using Tapatalk

rootSU said:
Windows, drivers, cables.. It have to keep trying. It's the only way
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do you ever get sick of saying this?? I'm amazed at how many times you are willing to say it. Good on ya.
Let me know if I can help you out at all.

Have you tried using external micro usb flash drive with a rom + apps? I'm assuming your recovery is intact. If you're trying via win8 it's a pain #drivers.
Sent from my X9006 using XDA Premium 4 mobile app

Bronyr said:
Have you tried using external micro usb flash drive with a rom + apps? I'm assuming your recovery is intact. If you're trying via win8 it's a pain #drivers.
Sent from my X9006 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not everyone has a Micro USB flash drive or OTG cable.
I didn't have to try anything to get drivers working after I clean installed Windows 8.1U1, it worked as soon as I installed the Google USB driver lol. If you can't get it to work, you're doing it wrong.

Lack of ROM, S-ON

Hi. I have problem with my Desire S. There was no mobile signal after root so I decided to bring back stock rom. I firstly installed S-ON hboot (it deleted my rom) and after this I tried to install original RUU, but it requires to turn on phone. How to do this in bootloader or fastboot?

You can extract the RUU zip from the RUU exe and flash it as follows:
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
(note that it may tell you to "please flush image again immediately!", in that case simply run fastboot flash zip rom.zip again)
When it's complete you can reboot into your new rom via fastboot reboot

luki30210 said:
Hi. I have problem with my Desire S. There was no mobile signal after root so I decided to bring back stock rom. I firstly installed S-ON hboot (it deleted my rom) and after this I tried to install original RUU, but it requires to turn on phone. How to do this in bootloader or fastboot?
Click to expand...
Click to collapse
Just boot ur phone into fastboot, plug it into pc and run the ruu.exe file.

jmcclue said:
Just boot ur phone into fastboot, plug it into pc and run the ruu.exe file.
Click to expand...
Click to collapse
It doesn't work - can't see my phone.
Aquous said:
You can extract the RUU zip from the RUU exe and flash it as follows:
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
(note that it may tell you to "please flush image again immediately!", in that case simply run fastboot flash zip rom.zip again)
When it's complete you can reboot into your new rom via fastboot reboot
Click to expand...
Click to collapse
I've tried, but there is an error:
{
"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"
}

Put the Rom.zip on sdcard

Should I change the name of file?

luki30210 said:
Should I change the name of file?
Click to expand...
Click to collapse
What's the name of the file?
Sent from my HTC Desire S using XDA Free mobile app

rom.zip

luki30210 said:
rom.zip
Click to expand...
Click to collapse
Yh then do it.
Sent from my HTC Desire S using XDA Free mobile app

lilsafbig said:
Yh then do it.
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
And how I should name it?

luki30210 said:
And how I should name it?
Click to expand...
Click to collapse
Don't name it, leave it as Rom.zip
Sent from my HTC Desire S using XDA Free mobile app

lilsafbig said:
Don't name it, leave it as Rom.zip
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
Nothing happens when I turning on bootloader.

luki30210 said:
Nothing happens when I turning on bootloader.
Click to expand...
Click to collapse
Make sure in settings on ur phone I think in power untick fastboot and an dev options tick USB debugging and turn phone off, take battery out and in and hold power + vol down at same time until bootloader comes up and then fastboot connect ur phone to pc and u should see on screen fastboot USB and then do the commands.
Sent from my HTC Desire S using XDA Free mobile app

lilsafbig said:
Make sure in settings on ur phone I think in power untick fastboot and an dev options tick USB debugging and turn phone off, take battery out and in and hold power + vol down at same time until bootloader comes up and then fastboot connect ur phone to pc and u should see on screen fastboot USB and then do the commands.
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
The problem is that I can't turn on phone - there isn't any rom and I want to install some.

luki30210 said:
The problem is that I can't turn on phone - there isn't any rom and I want to install some.
Click to expand...
Click to collapse
It might be your vol down button like its hard to press so u have to find a workaround so press vol down but near to the middle and power and see if the bootloader appears.
Sent from my HTC Desire S using XDA Free mobile app

lilsafbig said:
It might be your vol down button like its hard to press so u have to find a workaround so press vol down but near to the middle and power and see if the bootloader appears.
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
I can run bootloader but nothing is happening. I remember that bootloader is looking for some names of files and installing them automatically.

luki30210 said:
I can run bootloader but nothing is happening. I remember that bootloader is looking for some names of files and installing them automatically.
Click to expand...
Click to collapse
Make sure u havnt got an pb88img.zip in the root if ur sd card if u do delete it and see if the names files come and disappear and use vol keys to goto fastboot and power button to select.
Sent from my HTC Desire S using XDA Free mobile app

lilsafbig said:
Make sure u havnt got an pb88img.zip in the root if ur sd card if u do delete it and see if the names files come and disappear and use vol keys to goto fastboot and power button to select.
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
I'm in fastboot. There aren't any new positions or messages.

luki30210 said:
I'm in fastboot. There aren't any new positions or messages.
Click to expand...
Click to collapse
Only in bootloader you will see messages in fastboot it won't so connect to the pc now with USB cable and do the rest in previous post.
Sent from my HTC Desire S using XDA Free mobile app

Rename the rom.zip to PG88IMG.zip put that on the root of ur sdcard (not in a folder) then boot into bootloader, it should find it and ask to update.
---------- Post added at 09:31 PM ---------- Previous post was at 09:30 PM ----------
lilsafbig said:
Make sure u havnt got an pb88img.zip in the root if ur sd card if u do delete it and see if the names files come and disappear and use vol keys to goto fastboot and power button to select.
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
PB88IMG is the desire NOT the desire s. If u dont know then dont post..