Database Info

[Q] No way of upgrading the phone - Please Help

hi there.
maybe I am using wrong words but I cannot find any post similar to my subject.
I am on stock ICS but it is not working well - I wanted to downgrade, but it looks like it is not possible to downgrade on stock recovery. I know I have to change the recovery to sth else like ClockWork.
I know about fastboot way - and here my problems starts.
I have all the drivers, phone is visible in Device Manager while it is booten into Android. I can go into Fastboot mode BUT
when phone is in fastboot mode it is not visible in Windows Device Manager at all.
It is not a driver problem. There is no new device I can use the driver for.
I tried different computers. Win7 64bit and 32bit and WinXP 32bit
My phone does not show up on any of them.
I think it ia a problem with the bootloader - my current version is XXKL1 - as when I am in the fastboot mode my volume keys are not working, while they work perfectly well in recovery or in the OS.
Any ideas appreciated.
Cheers

My phone wasn't showing in w7 i had turn on usb debugging in settings -> developer options. I m not sure if this helps but might be worth a try
Sent from my Nexus S using Tapatalk

Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway

..

vstar said:
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
Click to expand...
Click to collapse
Know what u mean.
Windows finds u phone but not in recovery mode.
Download pdanet for android and this will solve ur problem buddy.
http://junefabrics.com
I just realize that what I done a while ago.
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk

XXK1 sounds like the baseband/radio to me. Granted I never actually looked in the bootloader for a model number. You sure that's not the radio?
What rom is on the phone now? Does it work? Are you rooted? If you got working phone with root you can flash custom recovery from inside the os. Boot directly into it via terminal or adb or any app that does it.
The volume buttons not working sounds odd and does worry me though

did you try to boot into bootloader/fastboot without being connected to any machine (holding vol up + power) to check if your volume keys work or not?
your issue might not be driver related, but you can always try if the test above was ok.
http://forum.xda-developers.com/showthread.php?t=1138755
best of luck

OK guys. I am on 4.0.3 stock. Works almost fine. This phone is unlocked but not rooted. So no chance for any other recovery but the stock one as far as I know. So I am not able to downgrade easily. Yes I can boot into fast boot without being attached to USB. Volume keys still not working here. But working in recovery mode no problem. GM no drivers will help if phone does not show in windows device menadzer at all. I have tried Linux approach but it looks phone is not being discovered there in fast boot mode as well. I have tried unbrick software - does not discover the phone.
And yes it says on fast boot screen boot loader : I9020XXK1
I have run out of ideas.
Downgrade would be best but how to put any recovery manager without root privileges
Sent from my Nexus S using XDA App

you can use ROM manager to jump back to 2.3.x

..

I am not rooted so I cannot use from manager and I do have stock recovery not clockwork so I cannot install superuser.zip
Sent from my Nexus S using XDA App

And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App

vstar said:
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
for SuperOneClick phone needs to be visible in usb debugging mode.

Sorry mate but it only starts in USB Debug/Android mode - then it reboots the phone to fastboot shell and then same issue - phone is not discovered by windows hence nothing else happens.
Is there no other way of gaining root access instead of fastboot option - this would solve all my pains
Thx everyone for input

..

i suggest just follow zedomax tutorial on how to root your ics phone. He also have the download links for all the files that you will need. once your phone is rooted then you can download the old stock version of your phone.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/

Looks like a driver issue, when phone isn't discovered by windows in fast boot mode. (You are booting with vol up+power, right?)
Forget about any one-click-stuff etc - unlocking and cwm is the way to go. Everything else just makes troubles.
What I don't get is how you unlocked your phone without fastboot working?! That's not possible... for the moment forget about rooting - superuser isn't needed to flash stuff via fastboot/cwm.
Concentrate on getting fastboot to work. After that it's a piece of cake. Check you have drivers and fastboot set up properly on your PC.
Edit:
By this I mean following the sticky-guides, using the sdk from Google (not any downloads pretending to make it quick'n'easy. Go the official way!)
You should also give the 4.0.4-stockrom (ported from ns4g-leak) a try - it's way better than 4.0.3!
Edit: talking about this one: http://forum.xda-developers.com/showthread.php?t=1474878

OK guys - I have no idea how should I say it in different way - this is not a matter of a driver - the phone is physically not visible to the computer. There is no unknown device of anykind so I have nothing to use a driver for. It is not that fastboot command does not recognize the phone - the phone does not exists in Windows Device Manager. Looks like when phone is in fastboot mode the usb port is dead. So no chance of rooting in standard way.
And I have unlocked it as it was working before. I did realize it is not working when I tried to downgrade recently.
Election Day: I have tried 3 different cables, couple of computers and 3 different operating systems - ubuntu included. How this trick with hairdrier works? If it is a flash why does it work for everything else but not fastboot mode? Should I heat it up without cover and battery? Any specific area? Should I plug in while hot?
Thx guys.

usb working with sys booted up, but broken on bootloader?! makes no sense at all, i hope you can see that for yourself. can't be a hw-failure (then it would be broken everywhere).
have you reinstalled the driver from the sdk? the problem is on your pc, not the phone...
and forget about rooting for the moment, you don't need that to flash a rom. or are you mixing things up?!
that nonsense about heating up the phone with a hair drier was a joke, right?

..

[Q] Recovery of files

Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
You don't need to boot in recovery, boot in bootloader only.

polobunny said:
You don't need to boot in recovery, boot in bootloader only.
Click to expand...
Click to collapse
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.

bahagiga said:
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
Click to expand...
Click to collapse
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
http://junefabrics.com/android/

polobunny said:
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
link
Click to expand...
Click to collapse
Hmm, on the third step where it says "installing pdanet to your phone" it just like freeze and on my phone in the bottom it says "FASTBOOT STATUS - FAILInvalid Command"
what should I do??

bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium

Bkadleck said:
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I tried but I dont think I can, when I try it just goes into that 'bootup screen, with the Google text and lock icon'. :/ Not sure what to do

Im still stuck and havent been able to get around this, any helpful information is appreciated. Thanks in advance

Hey guys, Im still stuck with this issue. Anyone who has some tips on what to do or has an idea of what it could be? I just formatted my PC yesterday Windows 7 32bit and everything should be up to date.
Kind regards,
baha

If there's anyone out there I would greatly appreciate your help! I have some pictures that are very valuable to me (pictures of my dog) and would really love to see if I could recover them.
I cannot start up my phone the "normal" way, I can only start up the Fastboot mode. I have the Samsung phone drivers installed along with the Google USB drivers. I have attached a picture that shows that there should be no problems with the drivers. I have tried to use the google usb drivers specifically but still the same. I have also attached a picture of the command prompt and as you can see nothing really happens. I have tried different tutorials and all kinds of ways trying to make it work but I have no clue what the problem is since I am not getting any other error message.
Any help is appreciated, please!
I typed fastboot devices in the cmd prompt and it actually listed a device serial number which matches then one stated on my phone in the fastbootmode. Any idea what to do or what this means?

Softbrick? some custom rom advice please

Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated

osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.

Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work

Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before

Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?

osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app

osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)

Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys

osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story

osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app

Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this

osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

TWRP cant find any of the files on my USB-OTG

with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?

osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app

Very sorry, Ive just re-read what Im looking for
Appologies

thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best

my phone doesnt recognized by pc if i start downloading mode

Hi guys .
i flashed "by mistake " the wrong cwm recovery by ( Rsher ) . after the device is restarted the screen just stopped on welcome screen .
now i have no access to recovery mode .
so i tried the other choice which was the download mode .
and here is my problem my pc doesnt recognize my android phone , when i connect the phone the pc displays these words
"usb is not recognized . the last device you connected to computer malfunctioned and windows does not recognized it "
also odin does not recognize it .
now i have no access neither to recovery mod nor to download mode and the device still freezing on welcome screen . so my device practically is DEAD!!
PLEASE IF YOU WANT TO HELP ME :
**KEEP IN MIND THE DEVICE " BEFORE THIS " WAS RECOGNIZED WHEN IT IS TURNED ON
** KEEP IN MIND OTHER PHONES LIKE GALAXY DOUS OR GALAXY BEAM IS WORKING ON THE SAME PC AND RECOGNIZED ON ODIN
** my phone is galaxy s II Plus working on android 4.2.2
**my pc is HP working on windows 10
**i have the latest Samsung kies and the latest drivers
** what i have tried
*update the driver on my pc
*uninstall and reinstall the driver
*using different usb cables
*uninstall the drivers and restarting pc
*updating other generic usb hub
*changing values in the registry
*I have tried all versions of odin
*pull the battery and entering download mode several times
PLEAAAAAAASE HELP :crying::crying::crying: ​

Try installing the google USB drivers.They are normally installed with the android SDK. Maybe they can help you detect the phone or you can try to manually update the driver.
Sent from my Moto E using Tapatalk

Cruzy12100 said:
Try installing the google USB drivers.They are normally installed with the android SDK. Maybe they can help you detect the phone or you can try to manually update the driver.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
thanks for replay but nothing happened still the same problem

abdanoo said:
thanks for replay but nothing happened still the same problem
Click to expand...
Click to collapse
Because in most cases this would have fixed the problem.Try some other forum maybe to get a different set of answers.
Sent from my Moto E using Tapatalk
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Cruzy12100 said:
Because in most cases this would have fixed the problem.Try some other forum maybe to get a different set of answers.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Or could also try to repeat the same steps in a different system.
Sent from my Moto E using Tapatalk

Cruzy12100 said:
Because in most cases this would have fixed the problem.Try some other forum maybe to get a different set of answers.
Sent from my Moto E using Tapatalk
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Or could also try to repeat the same steps in a different system.
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
as i mentioned above sir , the phone is recognized when it is ON but the problem occurs when i go to download mode . i think it is not concerned with the drivers

Have a look at this soft-brick help guide. If your phone is not even able to enter the Recovery Mode, you may have a case of NAND rw corruption and recovery may not even be possible (you may have to look at hard unbrick scenarios).
Having said that, these are a few things I might have still tried if I were you:
1. If you have access to a Linux PC or a bootable Ubuntu drive, start it and see whether it recognizes your phone using the lsusb command. It will help you to rule out any driver issues.
2. Try to drain the battery (by keeping a long time in that welcome screen) and then do a fresh recharge and then try again.

prahladyeri said:
Have a look at this soft-brick help guide. If your phone is not even able to enter the Recovery Mode, you may have a case of NAND rw corruption and recovery may not even be possible (you may have to look at hard unbrick scenarios).
Having said that, these are a few things I might have still tried if I were you:
1. If you have access to a Linux PC or a bootable Ubuntu drive, start it and see whether it recognizes your phone using the lsusb command. It will help you to rule out any driver issues.
2. Try to drain the battery (by keeping a long time in that welcome screen) and then do a fresh recharge and then try again.
Click to expand...
Click to collapse
Well. , I have to say this is new solution . thank you brother I'll try and give you feedback ??

Moto G7 Power won't boot. Bricked?

So after I installed the Official Android 10 GSI just out of curiousity, it worked and the only reason I didn't stay with it was because it didnt have the new gestures and no lockscreen options. Everything else worked amazingly.
At this point I just wanted to install LineageOS and root but the phone kept rebooting to TWRP over and over no matter what I'd flash and no matter how many times I wiped it kept rebooting until it eventually got no response at all.
I tried everything restoring back up nothing, when I tried just flashing the zip file the recovery screen just kept flashing then rebooted back. I cannot save this for life of me I am left with a paperweight.
Ive tried the classic Moto G force restart trick but no luck in anything. No matter what I tried now it wont respond to any button presses. Am I just screwed? I'm waiting 24 hours before trying again while plugged in. What am i to do?
Metro By T-Mobile Variant if that helps at all

uHeash said:
So after I installed the Official Android 10 GSI just out of curiousity, it worked and the only reason I didn't stay with it was because it didnt have the new gestures and no lockscreen options. Everything else worked amazingly.
At this point I just wanted to install LineageOS and root but the phone kept rebooting to TWRP over and over no matter what I'd flash and no matter how many times I wiped it kept rebooting until it eventually got no response at all.
I tried everything restoring back up nothing, when I tried just flashing the zip file the recovery screen just kept flashing then rebooted back. I cannot save this for life of me I am left with a paperweight.
Ive tried the classic Moto G force restart trick but no luck in anything. No matter what I tried now it wont respond to any button presses. Am I just screwed? I'm waiting 24 hours before trying again while plugged in. What am i to do?
Metro By T-Mobile Variant if that helps at all
Click to expand...
Click to collapse
Connect to a PC
In Device Manage
If phone is shown as
QHSUSB_Bulk or qloader
It's in emergency download mode
You will need a Blankflash file or a mmcblk0.img

sd_shadow said:
Connect to a PC
In Device Manage
If phone is shown as
QHSUSB_Bulk or qloader
It's in emergency download mode
You will need a Blankflash file or a mmcblk0.img
Click to expand...
Click to collapse
Hi my phone stay in bootloader but dont work, fbank flash say waiting for devices, and qhusb or qloader dont appear in my pc, help me

iFelipe97 said:
Hi my phone stay in bootloader but dont work, fbank flash say waiting for devices, and qhusb or qloader dont appear in my pc, help me
Click to expand...
Click to collapse
You cannot use a blankflash if device is in fastboot mode
Sent from my ali using XDA Labs
---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Sent from my ali using XDA Labs

sd_shadow said:
You cannot use a blankflash if device is in fastboot mode
Sent from my ali using XDA Labs
---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Please help me flash stock firmware not work for me error remote failured