Jump to content

New Orange UK ROM - OUK_P729BV1.0.0B08

Guest Arr Too

By Guest Arr Too
in ZTE Blade / Libra - Blade.MoDaCo.com

 Share

Recommended Posts

Guest Winston69

Guest Winston69

Posted
Posted
Could be that it just hadn't turned the backlight back on? (Of course, on the OLED version there is no backlight to remember to turn on.)

No idea but i couldn't see anything either way ;)

Link to comment
Share on other sites
  • Replies 60
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Winston69

Guest Winston69

Posted
Posted
Hmnmnm, why are you flashing the superboot image?

You going to cause problems for yourself there, since the kernel from that is based on the old OUK one,,, leave the stock one on, and use clockwork to install ROMS n' stuff

Oh I see as i'd be using the boot image from the OUK_P729BV1.0.0B05 build and using it with the newer OUK_P729BV1.0.0B08 based ROM, that's what could of caused the troubles???

I just remember from when I first got my grey San Fran right at the start that the first step was to root it as shown in pauls installation videos that are still on this forum

Link to comment
Share on other sites
Guest Winston69

Guest Winston69

Posted
Posted

From what i've just been reading some ROMs come including the root access now?

I'm worried that any ROM won't work as it won't be able to wake the backlight from sleep if it's not included in the older ROMs

Link to comment
Share on other sites
Guest rjm2k

Guest rjm2k

Posted
Posted

Hmm, I wonder if this is the rumoured new version of 2.1 that Orange have been working on, so maybe we wont officially get it on our older phones, it's just for the newer TFT phones?

Link to comment
Share on other sites
Guest Kthulhu

Guest Kthulhu

Posted
Posted
use androot, or one of the other exploits... mixing the old kernal with the new OS will cause you problems...

Try this one....

http://android.podtwo.com/roms/beta/OUK_P7...ggable_boot.zip

Does any one has succefully rooted a white SF? - I tried this link and executed Androot, it said that pnohe is rooted but Tittanium+busybox or Superusser app does not work.

Link to comment
Share on other sites
Guest Kthulhu

Guest Kthulhu

Posted
Posted (edited)
I had an issue with rooting, so I've updated the install script for the .zip file (for ClockworkMod) to better mirror the permissions that were set in .img: OUK_P729BV1.0.0B08.R2 (ROM).

Sorry If I do not understand it, so this is like the stock rom that can be installed with clockworkMod and allow rooting or is already rooted. Thanks mate. ;)

Edited by Kthulhu
Link to comment
Share on other sites
Guest oh!dougal

Guest oh!dougal

Posted
Posted (edited)
Sorry If I do not understand it, so this is like the stock rom that can be installed with clockworkMod and allow rooting or is already rooted. Thanks mate. ;)

This is to put a new-style San Francisco back as close as possible to the way it came out of the box.

And it can be installed with Clockwork.

Edited by oh!dougal
Link to comment
Share on other sites
Guest Arr Too

Guest Arr Too

Posted
Posted
Sorry If I do not understand it, so this is like the stock rom that can be installed with clockworkMod and allow rooting or is already rooted.

This is the same ROM that jchamier dumped for us. When you repackage as a ClockworkMod zip the special permissions fall off files and are updated by a script during the installation. I tried to run AdFree and it complained about lack of Superuser permissions, so the ROM isn't rooted (or not in the way AdFree wants). I tried to use Universal AndRoot to root it and got all sorts of problems (including my wifi breaking until a reboot!). So I checked the original image permissions and found that the script needing updating a bit to be more accurate. After this, AndRoot and AdFree worked fine for me.

Link to comment
Share on other sites
Guest Arr Too

Guest Arr Too

Posted
Posted (edited)

Hmm... any experts out there help me understand why the following files look like they were added sometime after this ROM was booted?

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/su

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/iptables

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/Tgetmem

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/busybox

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/getlogtofile.sh

file: 0100550 1010 1000 - Fri Dec  3 19:07:06 - etc/init.athwlan.sh

file: 0100660 1010 1010 - Fri Dec  3 19:07:06 - etc/wifi/wpa_supplicant.conf

file: 0100750 1010 1000 - Fri Dec  3 19:07:06 - wifi/wpa_supplicant.sh

file: 0100777	0	0 - Fri Dec  3 19:07:32 - wifi/reg_code

file: 0100750 1010 1000 - Fri Dec  3 19:07:06 - wifi/dhcpcd.sh

All other files are dated "Wed Oct 20". This ROM appears to have been dumped at 19:37 on Fri Dec 3, so these files appeared half an hour before. If it were just down to jchamier rooting and preparing for ClockworkMod then why would the WiFi stuff be changed? And if it's something Orange did, why did they do it? (And how?! It'd explain the presence of "su", though, wouldn't it?)

Edited by Arr Too
Link to comment
Share on other sites
Guest Kthulhu

Guest Kthulhu

Posted
Posted
I had an issue with rooting, so I've updated the install script for the .zip file (for ClockworkMod) to better mirror the permissions that were set in .img: OUK_P729BV1.0.0B08.R2 (ROM).

I installed your room, Androot said it is rooted but I can not use Titanium ;)

I also found that clockworkMod 2.5.1.3 does not work propely in my white - actually after installing the rom teh phone was stuck in green Android boot (and I was pretty scared!!)... but finally I could flash clockworkMod 2.5.0.9, install the rom and boot the phone :P

Link to comment
Share on other sites
Guest Arr Too

Guest Arr Too

Posted
Posted
I installed your room, Androot said it is rooted but I can not use Titanium ;)

Probably need to install busybox. Do as Titanium Backup suggests when you first started it and press the Problems button to download and install busybox.

Link to comment
Share on other sites
Guest Kthulhu

Guest Kthulhu

Posted
Posted
Probably need to install busybox. Do as Titanium Backup suggests when you first started it and press the Problems button to download and install busybox.

I did it but that was not the problem. The thing that after running Androot, it seems to work but then any application that need root access does not work ?? Maybe I am not using he latest version of Androot or I am doing something wrong

Link to comment
Share on other sites
Guest Arr Too

Guest Arr Too

Posted
Posted

Using the R2 ROM (with updated script) and AndRoot 1.6.2 beta 5 (the last one I could find), I successfully got AdFree working, which requires root access. Did you get a popup asking for root access when first starting Titanium Backup? It seems to work fine for me. At precisely what point are you getting an error/problem?

Link to comment
Share on other sites
Guest rjm2k

Guest rjm2k

Posted
Posted

I think that this ROM is a good example of why there should be a warning on the threads for all other ROMS suggesting that the person checks the version on their sf before flashing anything over it, so we don't lose the chance to gain an update and they don't brick their phone.

Link to comment
Share on other sites
Guest Sebastian404

Guest Sebastian404

Posted
Posted (edited)
Hmm... any experts out there help me understand why the following files look like they were added sometime after this ROM was booted?

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/su

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/iptables

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/Tgetmem

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/busybox

file: 0104550	0 1000 - Fri Dec  3 19:07:05 - bin/getlogtofile.sh

file: 0100550 1010 1000 - Fri Dec  3 19:07:06 - etc/init.athwlan.sh

file: 0100660 1010 1010 - Fri Dec  3 19:07:06 - etc/wifi/wpa_supplicant.conf

file: 0100750 1010 1000 - Fri Dec  3 19:07:06 - wifi/wpa_supplicant.sh

file: 0100777	0	0 - Fri Dec  3 19:07:32 - wifi/reg_code

file: 0100750 1010 1000 - Fri Dec  3 19:07:06 - wifi/dhcpcd.sh[/code]






Have you looked at init.rc....



line 125:


[code]	chown root system /system/bin/su

	chmod 4550 /system/bin/su

	chown root system /system/bin/iptables

	chmod 4550 /system/bin/iptables
Line 136: 
	# ZTE_LOG_CXH_001,set root right

	chown root system /system/bin/getlogtofile.sh

	chmod 4550 /system/bin/getlogtofile.sh

	chown root system /system/bin/Tgetmem

	chmod 4550 /system/bin/Tgetmem

	chown root system /system/bin/busybox

	chmod 4550 /system/bin/busybox[/code]




line 184:


[code]	mkdir /data/misc/wifi/wapi_certificate 0777 wifi wifi

	chown wifi wifi /system/etc/wifi/wpa_supplicant.conf

	chmod 0660 /system/etc/wifi/wpa_supplicant.conf

	chmod 0550 /system/etc/init.athwlan.sh

	chmod 0550 /system/wifi/wpa_supplicant.sh

	chmod 0550 /system/wifi/dhcpcd.sh

	chmod 0777 /system/wifi/reg_code

	chown wifi system /system/wifi/wpa_supplicant.sh

	chown wifi system /system/etc/init.athwlan.sh

Edited by Sebastian404
Link to comment
Share on other sites
Guest Sebastian404

Guest Sebastian404

Posted
Posted
I installed your room, Androot said it is rooted but I can not use Titanium ;)

I also found that clockworkMod 2.5.1.3 does not work propely in my white - actually after installing the rom teh phone was stuck in green Android boot (and I was pretty scared!!)... but finally I could flash clockworkMod 2.5.0.9, install the rom and boot the phone :P

Paul's version of ClockworkMod 2.5.1.3 does not work properly, there is a big in it, for the time being use 2.5.0.9

Link to comment
Share on other sites
Guest Sebastian404

Guest Sebastian404

Posted
Posted (edited)
I had an issue with rooting, so I've updated the install script for the .zip file

So I did a diff on the two, and you have added the follwing:

set_perm 0 1000 04555 SYSTEM:bin/su

set_perm 0 1000 04555 SYSTEM:bin/busybox

set_perm 0 1000 04555 SYSTEM:bin/Tgetmem

set_perm 0 1000 04555 SYSTEM:bin/iptables

set_perm 0 1000 04555 SYSTEM:bin/getlogtofile.sh[/code]




not really needed, since init.rc does that.






[code]set_perm 1010 2000 0550 SYSTEM:etc/init.athwlan.sh

set_perm 1010 1010 0550 SYSTEM:etc/init.qcom.sdio.sh

set_perm 0 0 0555 SYSTEM:etc/ppp/ip-up-vpn
init.rc will fix the first one for you Line 187: 
	chmod 0550 /system/etc/init.athwlan.sh

that second line seems interesting, but I'm interested in why you changed the permissions on ip-up-vpn to 0555 from 04755 ?

Edited by Sebastian404
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
 Share
Go to topic listing
×
×
  • Create New...

Important Information

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

  I accept