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?

..

Xoom bricked seen as APX in devices need drivers

Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?

Have you downloaded drivers from motodev?
Prior to the bricking, could you connect to your computer?

It will connect but it just shows up as APX in the devices and says its missing drivers. I went to moto and downloaded USB drivers but still does the same thing. The xoom does nothing when plugged in.

Windows 7 or XP?
Sent from my MB860 using xda premium

Windows 7. I did manage to get some drivers to install. Don't know if their the rite ones though. I clicked on let me choose such drivers, found some in SDK for htc,Samsung,and Motorola. Chose Motorola and it had several adb drivers clicked next and they installed. So now it just shows it as APX in the devices but no longer has the missing drive issue. Still no sign of life when trying adb or fastboot.

What mode is it in when you are attempting to connect it to your computer?
Sent from my MB860 using xda premium

It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.

ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?

Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?

ericman77 said:
Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Click to expand...
Click to collapse
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
darchiuk said:
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Click to expand...
Click to collapse
qoole33 said:
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
Click to expand...
Click to collapse
Dear all,
I got the same thing.
I installed the driver from nvflash drivers. And I ran several commands to try, it showed no bootloader was specified. I guess maybe I damaged my bootloader. Does any of you unbricked your xoom?
Here is a link to my post, which showed my tries.
http://forum.xda-developers.com/showthread.php?t=1838002
Anyone could help us? Thanks a lot.

Wow, i've been on that Wagon for a long time. http://forum.xda-developers.com/showthread.php?t=1838002 Now I just gave up cause I don't think anyone has gone past installing the drives after it detecting as APX.

Thanks for your kindly reply.
So, you mean there is no hope.
Actually, I sent it to another MOTO local service center again. After one week, they told me they tried to restore the software in two steps, but only the first could be done, and then went back to brick again. And they thought there might be some damage on “the kit” of motherboard, and if I want to repair, the whole motherboard must be replaced totally.
If you still have the bricked XOOM, would you please try to draw the BCT and config.cfg from your device?
Again, I did another search. Although there is no available bootloader.bin, BCT and config.cfg for XOOM, I guess there might be possible to use SAMSUNG P7510's files, because the hardwares are almost same, and it's heard that P7510 could use XOOM's ROM.
Sent from my ZTE U970 using xda app-developers app

Help about the phone booting

I compiled ROM and flash it into the mobile phone, The phone screen is black after starting
Connect the computer with USB. I can see the two devices in the Device manager.
SAMSUNG Mobile USB Composite Device
SAMSUNG Mobile USB Modem
It is not same with the fastboot mode in the equipment . Is it right? Kernel has started?
run ADB devices, display 4dXXXXXXXXXXXX offline
What is the problem? Why show black screen? Kernel has launched?

No, the kernel hasn't booted yet.
Seems like not even the primary OS bootloader was hit yet, something went wrong and it probably fallback to download mode.
Try using ODIN, if neither ODIN recognizes this you could be stuck in something like Qualcomm Emergency Download Mode and variations for other brands.
One of my thoughts is that you flashed an unsigned kernel with SecureBoot on.

greenboxal said:
No, the kernel hasn't booted yet.
Seems like not even the primary OS bootloader was hit yet, something went wrong and it probably fallback to download mode.
Try using ODIN, if neither ODIN recognizes this you could be stuck in something like Qualcomm Emergency Download Mode and variations for other brands.
One of my thoughts is that you flashed an unsigned kernel with SecureBoot on.
Click to expand...
Click to collapse
+1

[Q] Need Debug on, but screen and power button broken, device still on and working

Hi guys!
I brooke the screen and touch of my razr hd, as well its power button.
I'm trying to acess its screen trough the pc using a tool from the forum. BUT I need to have the usb debbuging enabled, wich I don't have.
So, I need to enable it from de pc somehow.
The device is working properly, the pc recognizes it and allows me to deal with its files, the device is turned on and is rooted already.
Someone have any idea of how to enable the usb debugging with the touch and without entering in recovery or fastbootmode?
The only two things I know I can do with it for now is to reset or turn it off trough a command in cerberus.

Sant Mark said:
Hi guys!
I brooke the screen and touch of my razr hd, as well its power button.
I'm trying to acess its screen trough the pc using a tool from the forum. BUT I need to have the usb debbuging enabled, wich I don't have.
So, I need to enable it from de pc somehow.
The device is working properly, the pc recognizes it and allows me to deal with its files, the device is turned on and is rooted already.
Someone have any idea of how to enable the usb debugging with the touch and without entering in recovery or fastbootmode?
The only two things I know I can do with it for now is to reset or turn it off trough a command in cerberus.
Click to expand...
Click to collapse
There's a lot of info out there on this. Various way to recover. Maybe try this:
http://android.stackexchange.com/qu...bug-mode-was-disabled-how-can-i-re-enable-adb
http://android.stackexchange.com/qu...-sg3-with-broken-screen-digitizer/69600#69600

CWGSM3VO said:
There's a lot of info out there on this. Various way to recover. Maybe try this:
http://android.stackexchange.com/qu...bug-mode-was-disabled-how-can-i-re-enable-adb
http://android.stackexchange.com/qu...-sg3-with-broken-screen-digitizer/69600#69600
Click to expand...
Click to collapse
All the info in this 2 tutorials and in other I've found, in some how, ask me to use the buttons to acess fastboot mode or recovery mode, but as I said, they are broken.
I was hoping to find some comand lines via pc and with the device still on to put it to recovery or fastboot mode, cause then I can use adb or fastboot to enable usb debugging.... But, I still don't know how...

No green android when using flash or fastboot mode

Hi,
First of all the bootloader is already unlocked.
Two problems:
1. - I was trying to flash twrp.img on my mobile but I am not getting that green android to show up in my screen all I get a black screen with blue led light, I usually power off the mobile, hold volume up and then connect the USB cable to my mobile.
2. - Can't find mobile device while using flash or fastboot, my mobile Developer option and USB debugging are turn on, mobile drivers and adb-setup-1.4.3 are installed, I have access to my mobile on my PC , when I do the process of flashing or fastboot I turn off the mobile and I unplug USB cable from my mobile, I press the keys to do flash or fastboot (I don't see no green android just a led light turn on) and connect the USB cable, problem is my PC can't find the mobile device, I use adb function eg. adb devices or fastboot devices I get nothing no device no info.
Is this problem with Win 10?
Was my problem understood in 2. - ?

Sa9aX said:
Is this problem with Win 10? Was my problem understood in 2. - ?
Click to expand...
Click to collapse
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers

Didgesteve said:
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Click to expand...
Click to collapse
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip

Sa9aX said:
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Click to expand...
Click to collapse
Back again...
I figured all out:-
twrp-3.2.1-0-maple.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img (latest firmware)
Magisk Manager