Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Lin1876

  • Rank
  • Birthday August 15

Profile Information

  • Location
    Glasgow, Scotland
  • Your Current Device(s)
    ZTE Crescent
  1. Hmm, that might actually be enough for me to buy one.
  2. You beauty! I was preparing to throw something when it wasn't working, before I discovered a tutorial for the original Blade which said that some models need you to press Power, Volume up and Home at the same time. Tried that and it worked! Yes, it's the stock firmware, but my phone works again. Thanks everyone for all the help over the past few days. Problem solved! We (read: you) did it.
  3. I did a quick Google search and it seems ZTE have something like this on their website. Downloading it now. Thanks for the suggestion, I didn't even know what a TPT was until 10 minutes ago!
  4. Well when I turn it on the LED turns itself off quite quickly. If the best change to catch ADB is early on, how am I supposed to flash ClockworkMod back on?
  5. What happens if your regular boot up has failed? Does it keep trying or does it just stick at a certain point? Perhaps more to the point, does it particularly affect whether the device would be recognised by ADB?
  6. Am I right in assuming that the Android logo screen means you're in the bootloader? What I'm doing is booting the phone while it's connected to the computer by USB. It hangs on the Android screen, and I enter commands from there. I know people are having joy from putting their device into USB Development mode, but I obviously can't get that far. However, I would assume that being stuck in the bootloader (I assume) would be enough, but apparently not. For the sake of trying I also tried everything in FTM mode (without success). I'll keep poking around in hope of a solution, but I'm getting into obscure results now.
  7. No luck I'm afraid. I've read online I might have to fiddle around in udev. It's something I'd rather not do, but if needs must...
  8. Did some digging on the internet which told me to install the ia32-libs package which fixed my previous problem. However, ADB is now not recognising my device. When I run ./adb devices there's nothing listed. How do I get ADB to recognise the device, bearing in mind I can't get past the Android screen.
  9. The ZTE Crescent/Orange San Francisco II is a true successor to the original San Francisco/ZTE Blade, and I would say it's the best phone for the money. The ZTE Skate is very similar inside, but you get a notably bigger screen. It's about £50 more than the Crescent, so it depends how much you value the extra size. I personally find 3.5 inches to be perfectly sufficient for my needs.
  10. Never used one, but I've heard that Archos tablets are great cheap choices. They seem to be good value and easily hackable, which is an irresistable combination for many would-be hackers. Having said that, there are any number of sub-£200 tablets. You can find them from places like Maplin, Amazon, Carphone Warehouse and others. They vary greatly in quality, but if you do your research there's no reason you can't get a perfectly servicable tablet for little money. Make sure you get Android Market pre-installed, as it can be a pain to add later.
  11. I've had another issue. I ran ./adb reboot bootloader and got an error message. ./adb reboot bootloader ./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
  12. Sorry for being a noob, but how do I that? I've got the SDK and the Eclipse plugin installed, but I don't even know where to start from there. edit: Hang on, I've found something on the CyanogenMod Wiki, so I'll try that. edit 2: No joy. I'll need to ask for help.
  13. There is one other thing which I forgot to mention. My computer doesn't recognise the phone (not to my knowledge anyway) when I connect it by USB, so is there a way of forcing that to happen. When I do lsusb I can't see anything that screams out "phone" to me. I'll show what does come up in case I'm missing it... Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 0bda:0181 Realtek Semiconductor Corp. Bus 002 Device 003: ID 04f3:0103 Elan Microelectronics Corp. Bus 002 Device 004: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58) Bus 001 Device 006: ID 19d2:0112 ZTE WCDMA Technologies MSM edit: D'oh I see it. Forget what I just said.
  14. I've got a pretty serious problem with my San Francisco II. Basically, I was trying to restore the stock ROM following the instructions here (the way you'd install any other ROM from ClockworkMod), but something has gone wrong and the phone will not go past the Android boot logo. Worse, instead of Clockwork Mod, pressing the Volume down button when booting only brings up the FTM screen. I'm led to believe that the phone hasn't been bricked per se, but the solutions I've seen here haven't come to anything yet. I don't have access to a Windows computer right now, so if the solution need that then I'm http://www.youtube.com/watch?v=DpnvS7kM4Fs, but I am running Ubuntu 12.04, if that helps.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.