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] nexus s 4g cant flash stock plz help!!!!

I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?

KJOM said:
I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?
Click to expand...
Click to collapse
Hi,
What are coming from? rooted with what ROM.. what recovery?
And are you trying to flash the newest ICS from stock recovery?
I guess Im just trying to see what you did and what you had before it all happened.
Thanks

Im currently running the [AOSP][4.0.4]Codename Android 2.0.0RC|Fully Open Source+Nightly Builds Rom and I have CWM Recovery and I am trying to flash the OTA ICS Update.

http://forum.xda-developers.com/showthread.php?p=24297394
[OFFICIAL][ROM][CWM] NS4G IMM76D 4.0.4 | Rooted | Zipalign | ETC
This is what u want if ur already rooted
Good luck
Vs Nexus S 4G

I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.

I had an issue where fastboot wouldn't recognize my device when I was in bootloader. For whatever reason it worked if I hooked up my phone via usb then rebooted into bootloader.
Anyway you can use this method
http://forum.xda-developers.com/showthread.php?t=1575502
Sent from my Nexus S 4G using Tapatalk 2

Did you install the wrong bootloader by any chance?

KJOM said:
I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.
Click to expand...
Click to collapse
That's why I asked for some clarity on ur post.
U want to Unroot and return to stock.
Its a big difference when someone reads and tried to help.
What root method did u use?
Vs Nexus S 4G

@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.

KJOM said:
@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.
Click to expand...
Click to collapse
Boot into the bootloader (volume up + power button) and tell me what it says for bootloader version.

It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End

KJOM said:
It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
Click to expand...
Click to collapse
Well, that's good that you have the right bootloader. Mine had the same problem, but I accidentally flashed the wrong bootloader. Pretty sure that's why I had no fastboot or USB mount. I had to send mine into Samsung for repairs.

So what's wrong with it?

KJOM said:
So what's wrong with it?
Click to expand...
Click to collapse
With yours? I don't know.
With mine? I don't know.

lol dam

KJOM said:
lol dam
Click to expand...
Click to collapse
Sent my jacked up phone into Samsung. It was unlocked and had TWRP on it (like I said before, no fastboot and none of my computers with any combination of OS/USB cable would recognize the phone). Samsung either repaired or replaced it and it is shipping back to me today.

Thats good for u. But I still can't flash stock, other than that, I'm doing great with mine.

RESOLUTION: Assuming you've installed the correct Samsung ADB drivers, you will have had to go to Device Manager, and tell it which driver to use. Good job at getting to to the fastboot screen! You're almost done.
At this point, (on fast boot) open up Device Manager again on your computer. Now your phone is being recognized as something completely different: Android 1.0 was what mine said. Right click on it, 'update driver software', 'browse my computer for...', 'let me select from a list of...", then choose "ADB Interface" from the list. If ADB interface is missing from the list, you haven't installed the drivers.
It will then give you a list of ADB Samsung phone drivers to choose from. I just chose the most updated ones (2012 was at the end of the strand of information about it, as opposed to 2010 which was further down). The second you click next, your phone (assuming you still have the command prompt up on your computer, saying its searching or waiting for your phone) will start to fly through the process of returning you back to stock.
DONE!
Good luck.

Thanks jackharvest. I didn't know Samsung had their own ADB drivers. That was the key! After I configured Windows Device Manager, as you indicated, to use the Samsung driver, all I had to do was run the windows batch file "flash-all.bat" which I had downloaded from google's "Factory Images for Nexus Devices." Unfortunately, their instructions don't tell use about the steps you identified!

Feiteng H7100 Bricked

Hello,
I managed to brick my new Feiteng H7100 phone, i flashed wrong rom to it and got a greenish screen when trying to start the phone.
So i formatted the phone in SPFT tool "Format whole flash" and from then it stopped responding, i cant start the phone anymore, and the charging indicator wont light up when charging.
When connecting the phone to try and reflash it the computer recognizes that i have connected the phone to the computer, but flashing doesnt work.
It is the S7180 with 1GB ram.
I hope there is a solution to it and it can be fixed, iam not sure if this can be called had brick or soft brick.
Was very close to throw it out of the window yesterday, but then thought i can give it a chance
Thanks

Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks

Mine is dead also
jemmars said:
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Click to expand...
Click to collapse
Same mine is completely dead after I flash it - Its not recognized by the originally drivers in windows 7. Showing up as an Unknown Device.

if it is showing up as an device, it isn`t bricked. you need to get the right firmware and flash it again. force install the drivers for the unknown device or take the drivers for Rom you flashed. (e.g. flashed wrong preloader from ZTE to a Star device, need to install ZTE drivers)

While I don't know the specifics of the Feiteng H7100, I've "bricked" many an android phone and tablet. Fortunately it's usually easy to fix.
1) Reboot the device into CWM Recovery Mode (usually by holding power and volume buttons at the same time)
2) Plug it into your computer & run "adb devices" - if you device comes up as a Recovery device, then you're probably home free
3) Run an "adb push newly_downloaded_cyanogenmod_rom.zip /sdcard/" - the data location (/sdcard/ in this example) might vary depending on your device
4) Wipe Cache
5) Install Zip from sdcard and choose your new_rom.zip

[Q] LG-P506 Fastboot Can See My Device But Won't Show The Serial Number

So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.

baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.

damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.

baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.

shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.

ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.

baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk

ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.

LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >

Help Please Please with my bricked Alcatel Ot 5020 (Evolve)

This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????

you found any solution i have the same problem ?

:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me

So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.

any luck with a solution? How close to one have you got to...

ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.

Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.

Alcatel 5020t T-Mobile plis help flshe file

please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks