Jump to content

OrangeSanFrancisco.co.uk - UPDATED June 2013


Guest

Recommended Posts

The "List of ROMs (updated regularly)" on orangesanfrancisco.co.uk needs to be updated a little moe regularly :(

Updated...I've been really busy lately so I haven't had an awful lot of time to work on the site.

Link to comment
Share on other sites

Guest anotherbob

Newbie question....

I've used your guide to root my Orange San Francisco and install the debranded ROM. Thanks for the simple explanation, there's too many experts who seem determined to keep their knowledge to themselves by using specialist jargon we laymen can't follow. However.... now I've succeeded I presume I can delete the original ZIP of the ROM from my SD card and free up some space, is that right?

Link to comment
Share on other sites

.... now I've succeeded I presume I can delete the original ZIP of the ROM from my SD card and free up some space, is that right?

Yes, you can delete the ZIP to free up space.

Link to comment
Share on other sites

Guest Society

0B10 build and having problems getting past step 31 on page 3 of the guide despite following instructions precisely (allowing for some mismatches between wording in guide and actual display on OSF screen). Rooted more than once, clearing Recovery Manager's Cache and so on as instructions require but that error message appears each time I cycle around.

Is this build known to be problematic? If so, are there workarounds or alternative techniques that are known to be OK with 0B10? I looked to the pinned guide on this forum but was deterred by the warning on the UniversalAndroot page so thought I'd seek expert advice rather than plough on regardless.

Link to comment
Share on other sites

Guest Fou-lu
0B10 build and having problems getting past step 31 on page 3 of the guide despite following instructions precisely (allowing for some mismatches between wording in guide and actual display on OSF screen). Rooted more than once, clearing Recovery Manager's Cache and so on as instructions require but that error message appears each time I cycle around.

Is this build known to be problematic? If so, are there workarounds or alternative techniques that are known to be OK with 0B10? I looked to the pinned guide on this forum but was deterred by the warning on the UniversalAndroot page so thought I'd seek expert advice rather than plough on regardless.

you root it with androot and get Superuser permissions?

do that and the app should work, the warning is norm on root/flash forums the app works perfectly on the blade and doesn't void warranty..

what clockwork/rom you flashing?

Edited by Fou-lu
Link to comment
Share on other sites

0B10 build and having problems getting past step 31 on page 3 of the guide despite following instructions precisely (allowing for some mismatches between wording in guide and actual display on OSF screen). Rooted more than once, clearing Recovery Manager's Cache and so on as instructions require but that error message appears each time I cycle around.

Is this build known to be problematic? If so, are there workarounds or alternative techniques that are known to be OK with 0B10? I looked to the pinned guide on this forum but was deterred by the warning on the UniversalAndroot page so thought I'd seek expert advice rather than plough on regardless.

you could try uninstalling and then installing the app again

Link to comment
Share on other sites

Guest Society
you root it with androot and get Superuser permissions?

do that and the app should work, ...

I stepped back from following the simple external guide "by the numbers" and read around here a bit more so as to get a slightly better handle on the whole process.

I realised that I already had Superuser v2.3.1 and UniversalAndroot on the device by the time it all went wrong. I've since (re)downloaded other required files and plodded along to a reportedly successful conclusion using guides found here.

It actually ended in a boot loop but I could pull the battery and restart into Clockwork such that reading-around lead me to wiping cache and factory reset and then rebooting. All appears to now be well.

My thanks to the contributors who have taken the time to explain the basics so that we noobs don't immediately sink when arriving here fearing we're in at the deep end.

Link to comment
Share on other sites

Guest irishpancake
Hi, I keep getting the following message "The application Recovery Manager (process com.podtwo.RecoveryManager) has stopped unexpectedly. Please try again."

I have unlocked, and have rooted several times and still get the same, I would be very grateful if some one could advise me further, thank you.

Orange San Francisco

OUK_P729BV1.0.0B10

Hi there.....OSF with OUK_P729BV1.0.0B10

like what kracatoa said up there....

I have followed the guide as far as 3-31/32......but no joy with Recovery Manager, I get the message above, which is mentioned in the troubleshooting also.

However, as above also, I have rooted numerous times, and uninstalled/reinstalled Recovery Manager, etc. still no joy??

Where to from here, bearing in mind that I am a complete newbie here.

BTW, I also had to go to the Market for Apps ES File Explorer and ManD5 as both tinyurl links produced nothing.....see below.

http://tinyurl.com/esfile and http://tinyurl.com/clockmd5

However both are installed and the clock.img MD5 hash checks out OK...

But, now I am stuck, apparently, with a dodgy?? Recovery Manager, and can go no further.

Also, starting phone with vol+ has no effect, normal start. Starting with vol- I get freeze, with White Box saying FTM????

Can anyone help please??

Where to from here? :D :(

Edited by irishpancake
Link to comment
Share on other sites

Is this normal: in device manager and my computer I have three entries each of which I must safely remove :

USB mass storage device drive O, Android Composite ADB interface and Android ADB Interface. Just that it's a pain to have to safely remove each one when for most USB connected devices, it's just one to remove. Thanks.

Link to comment
Share on other sites

Guest cheezydee

I am stuck at step 34/35 Tap /sdcard/download/clock.img and press OK.

When I've done this it does the install bar and then says it's unrecognized. The MD5 hash check is the same as stated on the site.

I'd been quite chuffed it was all going nicely until that point.

After this, I also got the error message "The application Recovery Manager (process com.podtwo.RecoveryManager) has stopped unexpectedly. Please try again." when I went to go back in to the recovery manager. I'd read somewhere else to clear it's cache the apps menu and reboot and worked for me

Edited by cheezydee
Link to comment
Share on other sites

Guest MrsGeek

Great, thanks for this. Spent hours last night playing around to no avail and I MUST get rid of the Orange stuff cluttering up my phone!

Link to comment
Share on other sites

Guest Skip Tracer
Hi, great site but some of the links are dead, clockmd5 and esfile :D

Problems with the download from these links were being reported last month when I up graded my OSF to JJ r9 but they all worked fine for me.

I did the downloads via my home WiFi and not the more un-reliable 3G network way.

Could be just the servers busy or, they really are dead now.

Link to comment
Share on other sites

Guest The Soup Thief

Rotmann makes a very good point you know

I've read a lot of really positive feedback of your site and the guides therein from new owners of this phone, but it is getting a bit out of date and actually given recent developments this may lead to new owners bricking their phones on the basis of your advice

If you've not seen it, you should check out the threads about the new Generation 2 handsets that are coming into the supply chain

Kallt kaffe has put together a smashing app (the curiously titled Mr Pigfish) that determines whether people have Gen1 or Gen2 phones

In essence, putting a Gen1 ROM on a blade set up as Gen2 is going to end badly (StevenHarper, Flibblesan, Kallt Kaffe and many others explain this much more fully elsewhere)

Given that your guides are for new owners you've kind of assumed a bit of responsibility to keep abreast of this

Don't mean to sound chippy, I just think you could be leading some new owners into very choppy waters if you don't keep it up to date

Link to comment
Share on other sites

Guest Society
...

Don't mean to sound chippy, I just think you could be leading some new owners into very choppy waters if you don't keep it up to date

The omission of any mention of taking a back-up prior to flashing is, to say the least, unfortunate.

Several threads here indicate that there are now some OSF devices in the supply chain on which the touch capability of the screen is totally or intermittently lost after flashing so having a backup (and an explanation of how to restore) seems wise.

Link to comment
Share on other sites

Guest Phoenix Silver

V

Hi, great site but some of the links are dead, clockmd5 and esfile :D

Download astro manager from market it does the 2 functions

Link to comment
Share on other sites

Guest ronc2000

Yes I agree there is something new everyday.

A site like this needs dedication and constant house keeping.

If begin does not have time he should make a note saying that the information was as February 2011.

Having said that, I used root, recovery, clockwork, JJ9 mentioned on the site and I have not changed even on the light of the updated cloakwork/roms.

I have actually flashed a few phones with the same and will probably do some more. New is not inevitably better.

Link to comment
Share on other sites

Guest The Soup Thief
New is not inevitably better.

Unless the phone and memory structure happens to be new, and more importantly different, when if you don't use an appropriately different approach your fancy phone might become a fancy paperweight (sorry - I realise that this sounds like scaremongering, but my basic point is valid, that if you're setting out to write a beginners' guide, it's gotta be safety first, second and third)

Link to comment
Share on other sites

Unless the phone and memory structure happens to be new, and more importantly different, when if you don't use an appropriately different approach your fancy phone might become a fancy paperweight (sorry - I realise that this sounds like scaremongering, but my basic point is valid, that if you're setting out to write a beginners' guide, it's gotta be safety first, second and third)

Sorry guys, I have been having a lot of trouble lately so I haven't been able to work on the site at all or check here. I have updated the site to warn about the two generations of the phone on every page on our guide on how to install custom ROMs. Hopefully nobody has brick their phone yet.

As for JJ9 being outdated, I did have FLB as the recommended ROM on my site for a week. The amount of people who had trouble was enormous (some didn't have any trouble with the FLB ROM, like me). JJ9 is the most stable and compatible Android 2.2 ROM for the Orange San Francisco / ZTE Blade right now. The Sweedish Spring ROM will become the next recommended ROM as soon as it is fully stable like JJ9.

Edited by Guest
Link to comment
Share on other sites

Guest cheezydee
I am stuck at step 34/35 Tap /sdcard/download/clock.img and press OK.

When I've done this it does the install bar and then says it's unrecognized. The MD5 hash check is the same as stated on the site.

I'd been quite chuffed it was all going nicely until that point.

any feedback on this beggin (or anyone else?)

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

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