Is my Orange San Francisco bricked?

[Guest iconware]

Dear Forum,

I have an Orange San Francisco/ZTE Blade (UK) that powers onto a green android, but remains stuck there. I think I installed "Orange San Francisco Debraded ROM for OLED and TFT" following this guide on my phone: http://sanfranciscoandroid.co.uk/android/h...isco-zte-blade/ - it was a few months ago.

I have confirmed it is a GEN1 phone back when it was able to boot.

Everything was fine for a couple months, until suddenly one day when I started my phone, it was stuck on the green android screen. I didn't install any new roms or anything like that.

Here's my current symptoms:

- It often doesn't respond to the power button when I try to power it on. I have to take out the battery and put it back in a few times. I've borrowed a battery from an identical phone that works, doesn't help.

- It never gets past the green android screen. (http://developeraspirations.files.wordpress.com/2010/06/android_logo.gif - This guy, but with a black background and smaller)

- Holding the power button for 10 seconds doesn't help.

- It will not get into recovery mode. Tried holding volume up, tried holding volume down (4 seconds, 10+ seconds, tried it all). I tried holding all the buttons. I tried holding just the menu button. Same result (the only way I can even try this is to take the battery out, put it in, then power it on.)

Here's what I've tried:

- Tried getting into recovery mode several different ways:

x Tried powering on the phone with volume up button.

x Tried powering up the phone with volume down button.

x Tried powering up the phone with both volume buttons.

x Tried powering up the phone with menu button.

x Tried powering up the phone with back button.

x Tried powering up the phone with home button.

x Tried powering up the phone with menu + volume buttons.

x Tried powering up the phone with all buttons pressed.

(All attempts were tested by taking out the battery for 15 seconds, putting it back in, and holding said buttons for 10 seconds. The result is either the phone not turning on, where I'd take out the battery and try again and again until it works, or it continues to be stuck at the android screen)

- Tried waiting half a hour after the volume up/down for 30 seconds to see if it would enter recovery.

- Tried hooking it up to a linux machine. See below for results.

- Tried hooking it up to a windows machine. Windows always says there's a problem with the USB device and won't let me install a driver.

- Tried installing 5 different drivers intended for the ZTE blade on Windows, uninstalling and rebooting each time. I'm guessing from the linux error though and what I've read online, it sounds like it's not a driver problem. But I tried anyway.

- Tried both operating systems above by unplugging the phone from my PC, replacing the battery and turning on the phone with volume up held. The green android screen appears.

- Tried different USB cables

- Tried Total Phone Transfer (TPT) with a few different roms intended for GEN1 phones. Procedure is successful when the phone does turn on.

- Tried charging the phone for 8+ hours

- Tried multimeter testing the battery. Comes up as ~3.9v.

- After trying the above, tried leaving it in 'rice' trick for absorbing moisture. Phone hasn't been exposed to any wet conditions, but figured it couldn't hurt to try.

TPT Details:

Roms I have tried:

1. TPT Image of CyanogenMod 7 stable + ClockWorkMod Recovery on ZTE Blade Base Lutetia (http://android.modaco.com/content/zte-blade-roms-rom-customisation/337412/gen1-rom-tpt-image-to-install-cm7-0-0stable-in-easy-way/#entry1671850)

2. Tried all the TPT roms on this page marked GEN1 (http://android.modaco.com/content/zte-blade-roms-rom-customisation/329856/02-may-roms-current-known-available-roms-for-the-zte-blade-gen1/)

The TPT procedure works, and is successful, but after taking out the SD card and rebooting, it still remains stuck at the exact same spot and not being able to enter recovery.

Linux Details:

[268695.440042] usb 1-5: new high speed USB device using ehci_hcd and address 2

[268710.560018] usb 1-5: device descriptor read/64, error -110

[268725.790036] usb 1-5: device descriptor read/64, error -110

[268726.020020] usb 1-5: new high speed USB device using ehci_hcd and address 3

[268741.140036] usb 1-5: device descriptor read/64, error -110

[268756.370046] usb 1-5: device descriptor read/64, error -110

[268756.600047] usb 1-5: new high speed USB device using ehci_hcd and address 4

[268762.030017] usb 1-5: device not accepting address 4, error -71

[268762.150082] usb 1-5: new high speed USB device using ehci_hcd and address 5

[268772.570026] usb 1-5: device not accepting address 5, error -110

[268772.570053] hub 1-0:1.0: unable to enumerate USB device on port 5

[268772.990034] usb 4-2: new full speed USB device using ohci_hcd and address 2

[268778.160031] usb 4-2: device descriptor read/64, error -62

[268783.450028] usb 4-2: device descriptor read/64, error -62

[268783.730036] usb 4-2: new full speed USB device using ohci_hcd and address 3

[268788.910044] usb 4-2: device descriptor read/64, error -62

[268794.200052] usb 4-2: device descriptor read/64, error -62

[268794.500046] usb 4-2: new full speed USB device using ohci_hcd and address 4

[268799.920015] usb 4-2: device not accepting address 4, error -62

[268800.080011] usb 4-2: new full speed USB device using ohci_hcd and address 5

[268805.500034] usb 4-2: device not accepting address 5, error -62

[268805.500084] hub 4-0:1.0: unable to enumerate USB device on port 2

This happens no matter how I try to connect the phone. Fastboot/ADB is unable to see my phone on linux. Windows is unable to see my phone.

Is my phone bricked? Is there anything left I can do?

Thanks

Edited June 24, 2011 by iconware

[Guest t0mm13b]

Dear Forum,

I have an Orange San Francisco/ZTE Blade (UK) that powers onto a green android, but remains stuck there. I think I installed "Orange San Francisco Debraded ROM for OLED and TFT" following this guide on my phone: http://sanfranciscoandroid.co.uk/android/h...isco-zte-blade/ - it was a few months ago.

I have confirmed it is a GEN1 phone back when it was able to boot.

Everything was fine for a couple months, until suddenly one day when I started my phone, it was stuck on the green android screen. I didn't install any new roms or anything like that.

Here's my current symptoms:

- It often doesn't respond to the power button when I try to power it on. I have to take out the battery and put it back in a few times. I've borrowed a battery from an identical phone that works, doesn't help.

- It never gets past the green android screen. (http://developeraspirations.files.wordpress.com/2010/06/android_logo.gif - This guy, but with a black background and smaller)

- Holding the power button for 10 seconds doesn't help.

- It will not get into recovery mode. Tried holding volume up, tried holding volume down (4 seconds, 10+ seconds, tried it all). I tried holding all the buttons. I tried holding just the menu button. Same result (the only way I can even try this is to take the battery out, put it in, then power it on.)

Here's what I've tried:

- Tried getting into recovery mode several different ways:

x Tried powering on the phone with volume up button.

x Tried powering up the phone with volume down button.

x Tried powering up the phone with both volume buttons.

x Tried powering up the phone with menu button.

x Tried powering up the phone with back button.

x Tried powering up the phone with home button.

x Tried powering up the phone with menu + volume buttons.

x Tried powering up the phone with all buttons pressed.

(All attempts were tested by taking out the battery for 15 seconds, putting it back in, and holding said buttons for 10 seconds. The result is either the phone not turning on, where I'd take out the battery and try again and again until it works, or it continues to be stuck at the android screen)

- Tried waiting half a hour after the volume up/down for 30 seconds to see if it would enter recovery.

- Tried hooking it up to a linux machine. See below for results.

- Tried hooking it up to a windows machine. Windows always says there's a problem with the USB device and won't let me install a driver.

- Tried installing 5 different drivers intended for the ZTE blade on Windows, uninstalling and rebooting each time. I'm guessing from the linux error though and what I've read online, it sounds like it's not a driver problem. But I tried anyway.

- Tried both operating systems above by unplugging the phone from my PC, replacing the battery and turning on the phone with volume up held. The green android screen appears.

- Tried different USB cables

- Tried Total Phone Transfer (TPT) with a few different roms intended for GEN1 phones. Procedure is successful when the phone does turn on.

- Tried charging the phone for 8+ hours

- Tried multimeter testing the battery. Comes up as ~3.9v.

- After trying the above, tried leaving it in 'rice' trick for absorbing moisture. Phone hasn't been exposed to any wet conditions, but figured it couldn't hurt to try.

TPT Details:

Roms I have tried:

1. TPT Image of CyanogenMod 7 stable + ClockWorkMod Recovery on ZTE Blade Base Lutetia (http://android.modaco.com/content/zte-blade-roms-rom-customisation/337412/gen1-rom-tpt-image-to-install-cm7-0-0stable-in-easy-way/#entry1671850)

2. Tried all the TPT roms on this page marked GEN1 (http://android.modaco.com/content/zte-blade-roms-rom-customisation/329856/02-may-roms-current-known-available-roms-for-the-zte-blade-gen1/)

The TPT procedure works, and is successful, but after taking out the SD card and rebooting, it still remains stuck at the exact same spot and not being able to enter recovery.

Linux Details:

[268695.440042] usb 1-5: new high speed USB device using ehci_hcd and address 2

[268710.560018] usb 1-5: device descriptor read/64, error -110

[268725.790036] usb 1-5: device descriptor read/64, error -110

[268726.020020] usb 1-5: new high speed USB device using ehci_hcd and address 3

[268741.140036] usb 1-5: device descriptor read/64, error -110

[268756.370046] usb 1-5: device descriptor read/64, error -110

[268756.600047] usb 1-5: new high speed USB device using ehci_hcd and address 4

[268762.030017] usb 1-5: device not accepting address 4, error -71

[268762.150082] usb 1-5: new high speed USB device using ehci_hcd and address 5

[268772.570026] usb 1-5: device not accepting address 5, error -110

[268772.570053] hub 1-0:1.0: unable to enumerate USB device on port 5

[268772.990034] usb 4-2: new full speed USB device using ohci_hcd and address 2

[268778.160031] usb 4-2: device descriptor read/64, error -62

[268783.450028] usb 4-2: device descriptor read/64, error -62

[268783.730036] usb 4-2: new full speed USB device using ohci_hcd and address 3

[268788.910044] usb 4-2: device descriptor read/64, error -62

[268794.200052] usb 4-2: device descriptor read/64, error -62

[268794.500046] usb 4-2: new full speed USB device using ohci_hcd and address 4

[268799.920015] usb 4-2: device not accepting address 4, error -62

[268800.080011] usb 4-2: new full speed USB device using ohci_hcd and address 5

[268805.500034] usb 4-2: device not accepting address 5, error -62

[268805.500084] hub 4-0:1.0: unable to enumerate USB device on port 2

This happens no matter how I try to connect the phone. Fastboot/ADB is unable to see my phone on linux. Windows is unable to see my phone.

Is my phone bricked? Is there anything left I can do?

Thanks

You have not stated what ROMS did you use *AFTER* TPT'ing it?

TPT transfer is for upgrading to gen2 handset, so you must have carried out TPT how many times? It is a one-shot to the handset....

That guide in the linky is about rooting the handset!

As for the linux output - that is definitely bad kernel - perhaps you installed a gen2 kernel on your gen1 device or installed a gen1 kernel on your gen2 device... all in all, it sounds like you need to follow this guide elsewhere, by wbaw. Try that and see how you fare! :) Read the instructions carefully!!! :D

P.S: Would not be inclined to think its bricked - if it was - you wouldn't be seeing the green man! B)

Edited June 24, 2011 by t0mm13b

[Guest hedgepigdaniel]

Well I don't know... you said nothing in particular prompted it to stop booting, and that it often doesn't respond to the power button. that sounds like something more physical to me - I'd say its probably broken.

Besides that, you can try reflashing firmware with this thread - hopefully you can boot into download mode, if nothing else. I doubt it will help you but you never know. Do it as a last resort, because it will cause you to lose your IMEI. Flash one of the European firmwares in the download. It's like flashing with TPT, but it flashes the entire firmware (TPT only flashes a subset). If you try initially with the same gen firmware as what is on your phone, and with the flash CEFS box unticked, it might retain your IMEI.

By the way, congratulations for starting the most detailed and useful brick post I have ever seen.

Edited June 24, 2011 by hedgepigdaniel

[Guest The Soup Thief]

Would not be inclined to think its bricked - if it was - you wouldn't be seeing the green man! :)

FWIW, my sister-in-law's blade showed the green android after its run-in with the microwave - that was pretty impervious to attempts to unbrick it, appearing (given the context) to be a hardware problem

I'd be inclined to agree with hedgepigdaniel

It's a bit of a cop-out, but have you thought of ringing Orange? From the way you describe it you didn't do anything to produce this problem - everytime I've (temporarily) screwed my phone it's usually a result of my having done something stupid to it

Phones rarely fail spontaneously, but they do sometimes...

EDIT - By contacting Orange, I mean ringing their customer care and describing what happened - that your phone was working fine (as I gather it was) then it stopped working and has since failed to work. If (as seems quite likely) this is a hardware fault they should be happy to replace it with a reconditioned blade (probably TFT, but certainly working, which would be progress)

Edited June 24, 2011 by The Soup Thief

[Guest iconware]

You have not stated what ROMS did you use *AFTER* TPT'ing it?

TPT transfer is for upgrading to gen2 handset, so you must have carried out TPT how many times? It is a one-shot to the handset....

That guide in the linky is about rooting the handset!

As for the linux output - that is definitely bad kernel - perhaps you installed a gen2 kernel on your gen1 device or installed a gen1 kernel on your gen2 device... all in all, it sounds like you need to follow this guide elsewhere, by wbaw. Try that and see how you fare! B) Read the instructions carefully!!! ;)

P.S: Would not be inclined to think its bricked - if it was - you wouldn't be seeing the green man! :D

I tried the guide you mentioned in the post. Instead of booting into clockwork, it booted into the green man. And it was stuck again.

So I turned it off, was about to try the second one on the page, but before I even got a chance, the power now refuses to power on at all anymore. :)

Any ideas?

[Guest Joshua-]

I tried the guide you mentioned in the post. Instead of booting into clockwork, it booted into the green man. And it was stuck again.

So I turned it off, was about to try the second one on the page, but before I even got a chance, the power now refuses to power on at all anymore. :)

Any ideas?

Pull out the battery and plug the usb cable

Should wake up the blade B)

[Guest iconware]

Pull out the battery and plug the usb cable

Should wake up the blade :)

Just tried it B) Still doesn't wake up.

EDIT - By contacting Orange, I mean ringing their customer care and describing what happened - that your phone was working fine (as I gather it was) then it stopped working and has since failed to work. If (as seems quite likely) this is a hardware fault they should be happy to replace it with a reconditioned blade (probably TFT, but certainly working, which would be progress)

The reason I'm trying to fix it instead of calling is that I'm actually from North America, I purchased the phone from the UK.

[Guest hedgepigdaniel]

I tried the guide you mentioned in the post. Instead of booting into clockwork, it booted into the green man. And it was stuck again.

So I turned it off, was about to try the second one on the page, but before I even got a chance, the power now refuses to power on at all anymore. :)

Any ideas?

Turn on the phone with both volume buttons held down. If the notification LED flashes briefly when you do that, you can flash firmware from that thread I linked. If that doesn't work, you can completely discount a software problem.

[Guest iconware]

Turn on the phone with both volume buttons held down. If the notification LED flashes briefly when you do that, you can flash firmware from that thread I linked. If that doesn't work, you can completely discount a software problem.

Thanks for the response. i just tried this, nothing happens. Is there anything else I can try?

[Guest hedgepigdaniel]

Thanks for the response. i just tried this, nothing happens. Is there anything else I can try?

Not to my knowledge I'm afraid.

[Guest curl66]

apply the GEN1 to GEN2 CM7 TPT.

maybe your phone is stuck with some messed up versions.

the GEN1->GEN2 TPT will flash the phone internal firmware,too.

also format the SD-Card before applying the image folder. so that it is completly empty. remove the sim.

if this doenst help i guess your phone has a hardware defekt. sorry.

[Guest iconware]

apply the GEN1 to GEN2 CM7 TPT.

maybe your phone is stuck with some messed up versions.

the GEN1->GEN2 TPT will flash the phone internal firmware,too.

also format the SD-Card before applying the image folder. so that it is completly empty. remove the sim.

if this doenst help i guess your phone has a hardware defekt. sorry.

Tried it before, it still got stuck on an android screen.

Curious, now it has a new symptom. It didn't power on for a day, it was completely dead, but I tried now and whenever I turn it on, it 'vibrates' and does nothing else, does that mean anything?

[Guest hedgepigdaniel]

Tried it before, it still got stuck on an android screen.

Curious, now it has a new symptom. It didn't power on for a day, it was completely dead, but I tried now and whenever I turn it on, it 'vibrates' and does nothing else, does that mean anything?

That is what usually happens when the battery is too flat for it to turn on.

[Guest q123456]

i think that your motherboard is dead. Does your phone charging battery?

[Guest iconware]

i think that your motherboard is dead. Does your phone charging battery?

Not really sure. I think so, but right now it's not powering on.

Anyone know what could cause a phone to sometimes power on, but sometimes not?

Sometimes I could take out the battery 10 times in a row, plug it in and out of an usb cable 10 times in a row, and have absolutely nothing change and feel pretty stupid about doing it.

Then sometimes I just plug in the usb cable once, and it instantly turns on. I don't do anything in between.

Right now it's in it's 'dead' mode so I can't do anything with it.

I did manage to reflash the firmware as linked by hedgepigdaniel and get clockwork recovery finally on the phone (using USB cable only, it didn't seem to want to work with the battery). I wiped it down (basically deleted every option I could wipe, cache, system, data, etc.) installed a mod, but it didn't work (froze on the android screen). I tried a few different mods, even managed to get a TPT, but generally the same result, stuck on android screen or just goes back to the recovery screen.

I've tried different USB cables, I'm using a different one right now just in case (one that I know works).

Anyway, right now it won't even turn on at all. Nothing on the screen, no light, nothing, acting like it's completely dead. Just randomly. The last time it did this, I just kept trying every few hours and eventually it turned on and I managed to flash the firmware.

Is there something causing this that I could fix? Right now it doesn't respond to anything, I would plug in the usb cable as I usually do, try both volume buttons, no volume button, just the top one or bottom one, try TPT mode, it responds to nothing, like it has absolutely no power.

Edited June 27, 2011 by iconware