Database Develop

Custom android for Sciphone N19?

Hello, I've a Sciphone N19 which uses android 1.5. I think it's a out of the box rooted device because i can see with adb shell:
Code:
# id
id
uid=0(root) gid=0(root)
I read about get recovery and boot image from HTC devices, but N19 reports different MTD info:
Code:
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00004000 "Bootloader"
mtd1: 00200000 00004000 "Kernel"
mtd2: 00100000 00004000 "initramfs"
mtd3: 03c00000 00004000 "system"
mtd4: 04000000 00004000 "userdata"
How easy or difficult is get Android 2.0 to this device?
I can provide all info that you request.
Thanks for answers and sorry for my english

sinman said:
Hello, I've a Sciphone N19 which uses android 1.5. I think it's a out of the box rooted device because i can see with adb shell:
Code:
# id
id
uid=0(root) gid=0(root)
I read about get recovery and boot image from HTC devices, but N19 reports different MTD info:
Code:
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00004000 "Bootloader"
mtd1: 00200000 00004000 "Kernel"
mtd2: 00100000 00004000 "initramfs"
mtd3: 03c00000 00004000 "system"
mtd4: 04000000 00004000 "userdata"
How easy or difficult is get Android 2.0 to this device?
I can provide all info that you request.
Thanks for answers and sorry for my english
Click to expand...
Click to collapse
errr, im not familiar with that device but it doesnt sound like a htc soo...it might be hard for devs to help you out pal

Wow..
Usualy Sci phones are Iphone clone based.
Now weve got Google phone clones lol.
It runs Android 1.5...
So if its updateable, start with the usual. Plus its a quad band so Im not sure about updating the radio.
But if its already running 1.6, then going to a new rom SHOULD be just like doing it on a Ny touch or G1.

I'm not sure if you can install any updates on this device.
First - it has two sim cards, so if you try to apply a normal android build it probably won't work.
Second - it probably hasn't got a hard spl or a recovery mode of any kind, so chances are that you could brick it.
It's best if you could contact the manufactirer and ask if they are planning for any updates. I think it's the DSTL1 phone you are talking about, or is it the smaller one with 2 mp camera. I was very tempted by the n21 when I saw the price, but after I watched the reviews - not so much...
How much did you pay for this one, if it's not a secret?

yes, it's the smaller one, the N19. I tried to power on holding down different buttons, but nothing happens, so perhaps don't have bootloader or recovery mode

If you have access to adb shell try typing "adb shell reboot recovery" and see what happens.
It should manually load up recovery mode regardless of shortcut key bindings.

I almost forgot. There's also "adb shell reboot bootloader" For access to SPL mode.

Oh
It reboots normally .

wow, for some reason, I want one.
It's only got 128 mb ram/rom, so I wonder about partitioning (I can't read what was posted), so could you run adb shell df?
I was reading about the phone, and apparently it's single sim, so it wouldn't be a problem.
I'm thinking that, if you have adb root access, you could probably do an on-handset port (though, again, I don't know that there'd be enough space for it on the device) by just deleting the framework, etc, and app folders, plus the libs that aren't specific to your device, and pushing the 1.6 equivalents back, but then again, the lack of 1.6 proprietary files for your device could be a problem. Maybe building 1.6 (or even waiting for 2.0) and making your own build around the 1.5 drivers could work, maybe

sorry i cannot provide you this info because i've not installed adb drivers in this PC at the moment.
With "on-handset port", do you mean i can overwrite system libs and files without flashing?
Actual N19 kernel is: 2.6.25
Build: N19-eng 1.5 CUPCAKE eng robinlaw.20090926.121057 test-keys
Build info i suppose is from sciphone engineer. Any way this afternoon i can provide build.prop, i think there are the hardware module names.

Except that it is *NOT A CLONE*.
It is a *genuine* android device.
If it is a clone of anything, it is a clone of a RIM 9500, since that is clearly what it is physically styled after.
crypysmoker said:
Wow..
Usualy Sci phones are Iphone clone based.
Now weve got Google phone clones lol.
It runs Android 1.5...
So if its updateable, start with the usual. Plus its a quad band so Im not sure about updating the radio.
But if its already running 1.6, then going to a new rom SHOULD be just like doing it on a Ny touch or G1.
Click to expand...
Click to collapse

jubeh said:
It's only got 128 mb ram/rom, so I wonder about partitioning (I can't read what was posted), so could you run adb shell df?
Click to expand...
Click to collapse
This is the output:
Code:
D:\Downloads\N19\android-sdk-windows\tools>adb shell df
* daemon not running. starting it now *
* daemon started successfully *
/dev: 60800K total, 0K used, 60800K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/system: 61440K total, 57252K used, 4188K available (block size 4096)
/data: 65536K total, 49788K used, 15748K available (block size 4096)
/sdcard: 994432K total, 131024K used, 863408K available (block size 16384)
And build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=CUPCAKE
ro.build.display.id=N19-eng 1.5 CUPCAKE eng.robinlaw.20090926.121057 test-keys
ro.build.version.incremental=eng.robinlaw.20090926.121057
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Sat Sep 26 12:12:54 HKT 2009
ro.build.date.utc=1253938374
ro.build.type=eng
ro.build.user=robinlaw
ro.build.host=robinlaw-dell-laptop
ro.build.tags=test-keys
ro.product.model=N19
ro.product.brand=SCIPHONE
ro.product.name=N19
ro.product.device=N19
ro.product.board=TA1
ro.product.manufacturer=Triones
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=N19
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=N19-eng 1.5 CUPCAKE eng.robinlaw.20090926.121057 test-keys
ro.build.fingerprint=SCIPHONE/N19/N19/TA1:1.5/CUPCAKE/eng.robinlaw.20090926.121057:eng/test-keys
# end build properties
# RIL Interface
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/mux1
# WiFi Interface
wifi.interface=eth0
wifi.module_name=gspi2480
wifi.module_path=/system/etc/modules/wifi/gspi2480.ko
# Bluetooth Interface
#bluetooth.power_on=/sys/bus/platform/devices/neo1973-pm-bt.0/power_on
# GPS Interface
ro.kernel.android.gps=s3c2410_serial2
# GPRS Interface
ro.radio.use-ppp=yes
# LEDs (vibrator is an led device)
#led.red=gta02-aux:red
#led.green=gta02-power:orange
#led.blue=gta02-power:blue
#led.vibrator=neo1973:vibrator
# Backlights
backlight.lcd=/sys/class/backlight/toybox-bl
backlight.button=
backlight.keyboard=
# Headset switch
headset.switch.name=headset
# Use PacketVideo software codecs
pv.codecs.software=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.kernel.android.checkjni=1
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

similar to the DSTL1 / N21 ?
Your device seems to be similar to the DSTL1 / N21
I recommend you check out my thread here.

Well, when i try to test Gmail, calendar and setupwizard into my N19 keys conf has changed for any reason, can anyone provide me original N19 files?
Code:
# pwd
pwd
/system/usr/keylayout
# ls -l
ls -l
-rw-r--r-- system system 1699 2009-08-18 21:18 qwerty.kl
-rw-r--r-- system system 2167 2009-09-23 05:25 keypad.kl
-rw-r--r-- system system 210 2009-08-18 21:18 AVRCP.klr
Thanks

Read the fine print on the Chinese clones. They usually say Non-android OS. This is a clone and not really android.

raptoro07 said:
Read the fine print on the Chinese clones. They usually say Non-android OS. This is a clone and not really android.
Click to expand...
Click to collapse
why would someone copy android if it's open source already? and why would he be able to connect via adb then? why does it have a build.prop and same partition table formatting as any other android phone?
-----
anyways, are you sure it doesn't have recovery? no reboot recovery or something like that? guess it has been designed to only work via console on that device, since it would still be able to do OTA updates then. can't believe it has no recovery

This IS an android device, you're probably thinking of the G2, which is a Nucleus OS device skinned to look like Android (hint: almost all chinese phones are Nucleus OS skinned).
The reason behind using another OS instead of Android, which is open source, is the cost of memory chips and pre-built boards. The boards that almost all chinese phones sport cost about $10 and have very little onboard memory and ram (last one I owned was an HTC diamond clone and had 48 MB storage and 32 MB RAM) and Android, even on a very shrinked down state, wouldn't fit or run properly (they seem to care about user experience more than Motorola does).
The device the OP has is a tad different, though. I've been reading and examining and it doesn't follow the traditional -recovery -boot -system -userdata and -cache partitioning that HTC devices use (and even the sciphone n21), instead, this device, dues to storage limitations (only 128 mb) seems to drop -recovery and -cache (cache is not necessary since it won't be receiving OTA updates, though I don't know how the other apps that use /cache would handle that) and also -boot and boot components (kernel and ramdisk) are mounted as mount points along with /system but both under the same partition (as oposed to having kernel and ramdisk be on the spl's -boot. This would have the advantage of /data having more access to more space in the rather skimpy confinements of the 128 MB nand, but then traditional flashing methods won't work, as the update wouldn't flash a -boot or -recovery, and instead flash a kernel, ramdisk, and a /system under the same partition and use different mount points (much, much like an emulator build does).
This makes the device more and more interesting to me. I might get one just for the sake of having one.

Hello,
I'm really interested by this smartphone only because it's the cheapest smartphone with Android.
But I don't understand one thing: it seems that the user is root by default, Android is Open-Sources with Linux Kernel and this phone isn't locked I think. So why isn't it possible to upgrade Android? The latest stable release is the 2.0 and we can't use it? I don't use Android (yet) but it seems that it's a good OS.
@sinman: Is it really a good smartphone?
Thanks for your support.

Well, i resolved buttons issue, it seems when i push setupwizard and some google apps directly into /system/app the button functions change for some reason but config file doesn't. Now works normally and i can't google apps get to work, mainly because into setupwizard app i can't sign into google account i get the "can contact server SIM provider" problem
matths said:
@sinman: Is it really a good smartphone?
Click to expand...
Click to collapse
What do you want to ask?
Is it really a good smartphone?
or
Is it really a good smartphone for 135$?
For the first question i can answer NO. But for the second, oh! yes, baby. I like touching and haking devices, so i like much this smartphone. Touch-screen works very well, navigation works well, sound playing works well, and you have a lot of application that works on this device, in other words this phone is better than other normal phone, but you can't think it will be better than HTC or iPhone (+400$)

Thanks for your answer
An I hope that it will be possible to upgrade Android to the latest stable release.

Recovery Mod - HELP!!!

First off, I am not sure if I am posting this in the correct forum or not. If it is the wrong forum, I do apologies.
Now on to the problem...
I have a T-Mobile G1 running on Rogers (currently running CyanogenMod-4.0.1 with Firmware version 1.5). The problem I am having is that my G1 got soaked a while ago and the Send/Call and Home buttons no longer work whatsoever. I have mapped my send/call button to the camera button, so I can still answer calls. However, I am unable to install any new ROMS (updates) through any of the current bootloaders since they all require you to confirm the install/update with the send/call button.
I have now since been informed by Rogers that since I am running 1.5, my data will be cut off if I do not update to 1.6. Normally this would be no problem, but since my send/call and home buttons do not work, I am unable to do this (I know how to boot into recovery using terminal I just am unable to confirm anything once there).
I was wondering if anyone out there is able to make a new recovery or customize either Cyanogen's or Amon_RA's recovery so that I can confirm a installation/update by using either the Menu, trackball, back, End, or camera button INSTEAD of the Send/Call button?
Any help would be GREATLY appreciated.
Thanks,
Thomas

definetly the wrong section
if you have the relevant .img files you can flash through adb (in theory, never done it for a full rom, just boot.img and recovery.img)
adb flash_image boot /sdcard/boot.img
for example
or get the source to the recovery images and try and edit it manually
or....suck up amon_ras ass and try and get him to make you one
good luck
you might want to think about buying a junker off of ebay for spare parts tho...

Dude go on the Market. Download Quickboot.
It lets you reboot into recovery and more.
Then you can do everything like before
if its possible to install ROM's through the Recovery Screen Console then do it that way. idk how just a suggestion.

the problem is that he needs to hit home to confirm - which he cant

wrong section. But they are just checking the build.prop so make another one and adb push it that will tell them your running 1.6
but also get your phone fix when your phone goes into water you gotta take it apart right away and use a blow dryer

garok89 said:
the problem is that he needs to hit home to confirm - which he cant
Click to expand...
Click to collapse
is there a way to flash a ROM via Recovery Console though? jc
and hmm maybe you should just wait until your fone is fully dried. Thats happened to me with my old fones where they get wet and some didnt even turn back on until they fully dried.
how long ago was this?

The phone is fully dried... this happened in the summer (couple of months ago). It was in my backpack while biking home, got caught in a sudden down pour. When I got home, I found my phone in a pool of water on the home screen fully frozen. I took out the battery right away (this was about 30min later after I got caught in the down pour) and put the phone in some rice for 24hours. I then let it air dry some more under some fans for another 24hours. Sadly, I think water got into the circuit board through the SD slot and fried those 2 connections (the send and home buttons).
How do I pull the build.prop from my phone and then push it back? That should fix the problem, but it would still be nice to have the option to install other ROMS or even have the ability to wipe my phone.

szuba said:
The phone is fully dried... this happened in the summer (couple of months ago). It was in my backpack while biking home, got caught in a sudden down pour. When I got home, I found my phone in a pool of water on the home screen fully frozen. I took out the battery right away (this was about 30min later after I got caught in the down pour) and put the phone in some rice for 24hours. I then let it air dry some more under some fans for another 24hours. Sadly, I think water got into the circuit board through the SD slot and fried those 2 connections (the send and home buttons).
How do I pull the build.prop from my phone and then push it back? That should fix the problem, but it would still be nice to have the option to install other ROMS or even have the ability to wipe my phone.
Click to expand...
Click to collapse
You put it in rice? hmm never would have thought of that one lol
to pull and push respectively:
Code:
adb pull /system/build.prop \<the location that you want to put it in>
adb push \<the location that you put build.prop in> /system/
i usually just copy it to the android-sdk-windows\tools directory on my computer because its easier to get to it.

Macrophage001 said:
You put it in rice? hmm never would have thought of that one lol
to pull and push respectively:
Code:
adb pull /system/build.prop \<the location that you want to put it in>
adb push \<the location that you put build.prop in> /system/
i usually just copy it to the android-sdk-windows\tools directory on my computer because its easier to get to it.
Click to expand...
Click to collapse
Done, but when I try to push the file back, I get the follow error;
Code:
adb push desktop/build.prop /system
failed to copy 'desktop/build.prop' to '/system/build.prop': Read-only file system

szuba said:
Done, but when I try to push the file back, I get the follow error;
Code:
adb push desktop/build.prop /system
failed to copy 'desktop/build.prop' to '/system/build.prop': Read-only file system
Click to expand...
Click to collapse
Sorry forgot to tell you to type in:
adb remount
before you do it.
so do this:
Code:
adb remount
adb push desktop/build.prop /system
should work. just tried and it did for me.

Thanks Macrophage001... I edited and the pushed the build.prop successfully. Here is how my build.prop now looks;
Code:
# begin build properties
ro.build.version.release=1.6
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
keyguard.no_require_sim=true
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Google's checkin service. I don't like it, but it's required for the SetupWizard -cm
#ro.config.nocheckin=1
ro.modversion=CyanogenMod-4.0.1
When I go into Menu, Settings, About Phone it still shows my Firmware as 1.5, is that ok?

szuba said:
Thanks Macrophage001... I edited and the pushed the build.prop successfully. Here is how my build.prop now looks;
Code:
# begin build properties
ro.build.version.release=1.6
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
keyguard.no_require_sim=true
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Google's checkin service. I don't like it, but it's required for the SetupWizard -cm
#ro.config.nocheckin=1
ro.modversion=CyanogenMod-4.0.1
When I go into Menu, Settings, About Phone it still shows my Firmware as 1.5, is that ok?
Click to expand...
Click to collapse
Its most likely because you are running an old version of Cyanogen. If that's the case then yeah your ok
Glad to be of Help

old school recoveries...
I dont think you have to press home in JF recovery or the first cyan recovery... just the trackball but i dont remember, its been so long... search for those recoveries and try them out... you gotta name the file update.zip to flash... it cant hurt right?

junkdruggler said:
I dont think you have to press home in JF recovery or the first cyan recovery... just the trackball but i dont remember, its been so long... search for those recoveries and try them out... you gotta name the file update.zip to flash... it cant hurt right?
Click to expand...
Click to collapse
I thought it was the Call button? but yeah I cant remember anymore either =/
@szuba
if everything's working now, you should totally get the latest ROM from Cyanogen lol or Super D or whichever you want....just you know...Get a more recent ROM lol

Macrophage001 said:
I thought it was the Call button? but yeah I cant remember anymore either =/
@szuba
if everything's working now, you should totally get the latest ROM from Cyanogen lol or Super D or whichever you want....just you know...Get a more recent ROM lol
Click to expand...
Click to collapse
I would LOVE a more recent ROM, however I still have not found a work around to install a ROM without using the Send/Call key to confirm the install...
I will try to find JF's or Cyanogen's previous recovery and maybe that will let me.

szuba said:
I would LOVE a more recent ROM, however I still have not found a work around to install a ROM without using the Send/Call key to confirm the install...
I will try to find JF's or Cyanogen's previous recovery and maybe that will let me.
Click to expand...
Click to collapse
ok well hope you find a way good luck =)

Found JF's original recovery, downloaded Super D's latest ROM and renamed it to update.zip, rebooted into recovery, hit Alt-S and what do you know... WORKED LIKE A CHARM!!!
Thanks a lot guys, it is greatly appreciated!

Great and np.

beautiful... Glad I could help... I made a 1.o theme a while back.. that would be cool to have with JF's original Recovery..
mad props to JF and Cyangen for such great work...

[Q] DjangoManouche 0.5 and adb's root access

Hello,
Can't ask in the Rom's thread because of the 10-post restriction, so I have to ask here.
I have just installed the DjangoManouche 0.5 rom and I can't connect to the phone as root with adb directly. If i do for example:
Code:
adb shell
then I'm logged as a normal user, not root. It's annoying because one can't do adb remount and adb push to /system.
I've seen in the default.prop file that carburano uses those values:
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
If I'm not mistaken, it should be:
Code:
ro.debuggable=1
@carburano: maybe you restricted adb's root access on purpose? If so, why? No other 2X roms I used do this (Paul's ones, topogigi, blazingdragon).

Hello maybe a an error try to change to see if change anything

It would be quickier if the rom author could answer, otherwise I will have to install the softwares needed to unpack/repack boot images as this parameter can only be changed in the boot.img. And I wouldn't know if it is done intentionnaly or not.

I ask in Rom's thread, as you perhaps can't post there. Confirmed here also but sometimes a bit more tricky than that, normally only ro.secure=0 is needed, and we had same problem in Topogigi's ROM, he had to tweak some other files to enalbe it.

Thank you, I'm indeed stuck in the non-development sections until I get 10 posts.
Let's wait if carburano figures out the problem then.

Hi Guys, I didn't notice this thread until now... sorry... I will solve this... thanks for the feedback!

[Q] Restore back to stock 2.1

I am currently having a unlocked bootloader using nAa kernel 11 and minicm 2.1.9. I want to restore back to the stock W8.
Now I first download and try to use the PC Companion, but it keeps on showing that there is no software available for my phone yet.
Then I try to use the Update Service, it says my phone is already up-to-date. And believe me, there is no repair button in any of the stage of update service.
I try flash tool. But I all I get is a clean X8 Rom. I can use xRecovery and get back to stock W8 back up which I already have. But my phone will be rooted.
I want a CLEAN stock ROM. Un-rooted. Just as it came.
Earlier, PCC and US used to solve my problem, but they no longer do it for me.
What am I suppose to do? Please help!

clean rom
If you can restore your stock w8 rom then restore it
flash the stock kernel
then use superoneclick to unroot your phone if you dont want that..
ypu can remove xrecovery from system directory by deleting xrecovery.tar
also i think there is an option to relock your bootloader in flashtool
check out the bootloader tutorials in forum
after flashing stock kernel you can use sony's software updater for a official clean rom.........

But there is no Un-Root button in superoneclick! Can you attach the version which has it? I think I have the latest one. But still!

UNROOT
look I UPLOAD THE VERSION WITH UNROOT! cLICK THANKS IF I HELPED YOU!

The PCC is still giving me the same error.. "There is no software available for your ROM yet". Currently I have un-rooted backup of W8 and I am using it!

I isn't sure at 100% but PPC should have a function to fix the phone.
In my italian version, when I try to check for upload, is available also a link-text to enter in repair of firmware.
Is necessary to power on the phone with some button sequence (I don't remember but are wroten). The program download original firmware from SE servers.
How I wrote uppon I don't sure about that so take care before begin any operation.
I'm not responsable for damages, OBVIOUSLY !

virajt said:
I am currently having a unlocked bootloader using nAa kernel 11 and minicm 2.1.9. I want to restore back to the stock W8.
Now I first download and try to use the PC Companion, but it keeps on showing that there is no software available for my phone yet.
Then I try to use the Update Service, it says my phone is already up-to-date. And believe me, there is no repair button in any of the stage of update service.
I try flash tool. But I all I get is a clean X8 Rom. I can use xRecovery and get back to stock W8 back up which I already have. But my phone will be rooted.
I want a CLEAN stock ROM. Un-rooted. Just as it came.
Earlier, PCC and US used to solve my problem, but they no longer do it for me.
What am I suppose to do? Please help!
Click to expand...
Click to collapse
You cannot use PCC and SEUS with a custom kernel because it doesnt recognise your phone. Go back to a stock kernel then use PCC or SEUS

bahmonkeys said:
You cannot use PCC and SEUS with a custom kernel because it doesnt recognise your phone. Go back to a stock kernel then use PCC or SEUS
Click to expand...
Click to collapse
Correct. I have done that. I am on stock kernel, stock rom, rooted phone. Still PCC says there is no update available for my phone yet and SEUS says my phone is up-to-date!

Pc Companion send me this too... and I Solve This Problem! You Need change build.prop with the original serial of the x8 with root explorer.. only change theese lines in with text editor with root explorer!
ro.product.name=E15i_XXXX-XXXX
ro.build.fingerprint=SEMC/E15i_XXXX-XXXX/sonyEricssonE15i/
ro.semc.version.cust=XXXX-XXXX
Replace xxxx-xxxx for "1243-9502"
before this, pc companion restore my x8

Thanks. Can you provide me the same for a W8 ?

Here's a copy of the build.prop out of a W8 2.1.1.A.0.46 xRecovery image
Code:
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Mon Mar 21 18:06:23 2011
ro.build.date.utc=1300701983
ro.build.user=SEMCUser
ro.build.host=SEMCHost
##### Final patch of properties #####
ro.build.product=E16i
ro.build.description=E16i-user 2.1-update1 2.1.1.A.0.46 268 test-keys
ro.product.brand=SEMC
ro.product.name=E16i_1250-8813
ro.product.device=E16i
ro.product.board=delta
ro.build.version.incremental=0X_d
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/E16i_1250-8813/E16i/delta:2.1-update1/2.1.1.A.0.46/0X_d:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1250-8813
ro.semc.version.cust_revision=R2B
persist.ro.ril.sms_sync_sending=1
#########################################################################
ro.config.ringtone=sony_ericsson.ogg
ro.config.notification_sound=notification.ogg
ro.semc.content.number=PA2
################# Updating of the SW Version #################
ro.semc.version.fs_revision=2.1.1.A.0.46
ro.build.id=2.1.1.A.0.46
ro.build.display.id=2.1.1.A.0.46
##### Values from product package metadata #####
ro.product.model=E16i
ro.semc.ms_type_id=AAD-3880091-BV
ro.semc.version.fs=WORLDW-1-8
ro.semc.product.name=W8
ro.semc.product.device=E16
# begin build properties
# autogenerated by buildinfo.sh
#ro.build.id=2.1.1.A.0.46
#ro.build.display.id=2.1.1.A.0.46
#ro.build.version.incremental=268
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
#ro.build.date=Fri Apr 1 22:58:41 CST 2011
#ro.build.date.utc=1301669921
ro.build.type=user
#ro.build.user=hudsonslave
#ro.build.host=cnbjlx2355
#ro.build.tags=test-keys
#ro.product.model=shakira
#ro.product.brand=Sony-Ericsson
#ro.product.name=shakira
#ro.product.device=shakira
#ro.product.board=delta
ro.product.cpu.abi=armeabi
ro.product.manufacturer=Sony Ericsson
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
#ro.build.product=shakira
# Do not try to parse ro.build.description or .fingerprint
#ro.build.description=shakira-user 2.1-update1 2.1.1.A.0.46 268 test-keys
#ro.build.fingerprint=Sony-Ericsson/shakira/shakira/delta:2.1-update1/2.1.1.A.0.46/268:user/test-keys
# end build properties
#
# system.prop for shakira
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
wifi.interface = wlan0
ro.sf.lcd_density=160
ro.semc.def_screen_orientation=sensor
ro.semc.timescape_keys=X8_key
ro.semc.timescape_model=1_handed
ro.semc.sound_effects_enabled=false
ro.workaround.noautofocus=1
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
#persist.ro.ril.sms_sync_sending=1
DEVICE_PROVISIONED=1
# Constant values for Battery test in Service menu.
ro.semc.batt.capacity=950
ro.semc.batt.test.consumption=150
ro.semc.batt.test.z_threshold=30
dalvik.vm.heapsize=24m
kernel.log=default
ro.telephony.call_ring.multiple=false
debug.sf.hw=1
keyguard.no_require_sim=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
#ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.1_r11
ro.com.google.clientidbase=android-sonyericsson
net.bt.name=Android
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.drm.active.num=4
ro.drm.active.0=semc,1
ro.drm.active.1=cmla,0
ro.drm.active.2=viaccess,0
ro.drm.active.3=marlin,1
By the way, virajt ... if you manage to restore the Stock ROM through PCC/SEUS there's a way to create a FTF bundle out of the "blob_fs" parts the Sony Software will cache.
While this thread isn't about the X8/W8 in particular it should give you the idea.
EDIT: If you can't get it done pass me the encrypted W8 binary blob firmware files and I'll try my luck.

Thanks. Giving it a try now!

Same error. Doesnt work still...
"No software available for my phone yet!"

download wotan client. register for free. use it to flash to stock. after that pcc and seus will now work. thats what i do. dont forget to flash stock e15i kernel and relock bootloader then use wotan to restore to e16i
Sent from my E15i using xda premium

virajt said:
Thanks. Can you provide me the same for a W8 ?
Click to expand...
Click to collapse
Try these Numers! or search the build.prop of the stock rom of your phone!
xcuse me 4 the bad english..
Press The Thanks Button if I Help You!

I tried today with the values and the build.pro given by B.Jay.
None seem to work!

virajt said:
I tried today with the values and the build.pro given by B.Jay.
None seem to work!
Click to expand...
Click to collapse
Two possible problems:
1. Did you edit build.prop to identify itself as 2.1.1.A.0.46?
That's actually one release version below the last ROM ever published by SEMC, which is 2.1.1.A.0.53.
2. You see the "1250-8813" values (either stand-alone or combined with the "E16i_")?
That's actually a Region-ID. If you're using a ID that's not matching India and where no W8 ROM update is available you won't get any update. Either try to figure out the ID through Google and edit build.prop accordingly or ask a friend who has a W8 with Stock ROM to look into build.prop and tell you the value.

the latest available software version in India is '.053' only....
i have updated to that before i change the kernel..
and bro if your backup stock rom has the same version then you are not going to get the same version again via PCC
funny sol: MAKE UR PHONE DEAD AND TRY...lol

Just 10 mins ago I tried the method by B.Jay. A cousin of mine has the same phone. I just did a quick root. Copy his build.prop and paste it over mine. But its still a issue.
I guess the only way it to attempt a half murder on my phone and rush to Sony Ericsson Emergency Center!

Is your cousin's phone rooted?
If yes - pull a xRecovery backup of 2.1.1.A.0.53 and restore it back into your phone (don't forget to erase possible personal data and/or uninstall unwanted apps - once you cleaned out the ROM you then can pull a xRecovery backup of your "clean" ROM).
Alternatively - if your cousin's phone once got updated through PCC and hasn't been touched ever since you may want to look into the PCC cache directory and grab the directory containing all the "blob_fs" files onto a USB Stick (to make a FTF).
EDIT: In Windows Vista/7 the cache should reside at...
C:\ProgramData\Sony Ericsson\SEMC OMSI Module\db
In Windows XP you find it at...
C:\Documents and Settings\All Users\Application Data\Sony Ericsson\SEMC OMSI Module\db
In short, copy the whole "db" directory as that contains the needed files to create a FTF bundle.
IF ANYONE ELSE AROUND HERE HAS THAT DIRECTORY WITH 2.1.1.A.0.53 SITTING ON THE HARD DRIVE PLEASE ZIP IT UP AND PUT IT UP FOR DOWNLOAD SO WE CAN MAKE A FTF!!!

stock build.prop needed

Hi all,
I got my nexus 7 today and I used an app to change the LCD dpi to enable tablet ui, and because I am an idiot I didn't take a manual backup of the build.prop.
It looks like the program I was using as actually removed the build prob rather than editing it.
the tablet boots up and i see the google logo but after that its just a black screen.
I can still access the tablet using adb and i looked in the system folder and there is no build.prop file now.
I am sure that if some one could provide me a build.prop file I can get the tablet back to normal again.
if anyone has it I would be very grateful.
Thanks, Mark.

Sure, I'll see if I can make a copy and UL it for you.
What build are you on though? Did you upgrade to the latest "D" build yet? That will impact what your build.prop file should look like.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Here are the contents of the JRO03D build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03D
ro.build.display.id=JRO03D
ro.build.version.incremental=402395
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Jul 13 01:03:41 UTC 2012
ro.build.date.utc=1342141421
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpba30.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus 7
ro.product.brand=google
ro.product.name=nakasi
ro.product.device=grouper
ro.product.board=grouper
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=grouper
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nakasi-user 4.1.1 JRO03D 402395 release-keys
ro.build.fingerprint=google/nakasi/grouper:4.1.1/JRO03D/402395:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libril-icera.so
rild.libargs=-e wwan0
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
# set default lcd density to TVDPI
ro.sf.lcd_density=213
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
tf.enable=y
drm.service.enabled=true
ro.carrier=wifi-only
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
ro.facelock.black_timeout=1250
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=1000
ro.facelock.use_intro_anim=true
ro.media.effect.bgdropper.adj=0.2
camera.flash_off=0
ro.setupwizard.wifi_required=true
ro.setupwizard.gservices_wait=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
You can also download it here:
http://core.routed.com/build.prop

I did the same thing, I didn't think anything of it since it has worked flawlessly on every other device I have had. In my case it removed the build prop as well. I do however, have a nandroid backup on my device. Can I fastboot out of the bootloader into recovery and restore my backup or will I get stuck on the Google screen with the padlock just like I do when I try to manually access it?

chrisjm00 said:
I did the same thing, I didn't think anything of it since it has worked flawlessly on every other device I have had. In my case it removed the build prop as well. I do however, have a nandroid backup on my device. Can I fastboot out of the bootloader into recovery and restore my backup or will I get stuck on the Google screen with the padlock just like I do when I try to manually access it?
Click to expand...
Click to collapse
You should be able to get into recovery one of two ways:
1) Connected to a computer, using adb reboot recovery (or fastboot method).
2) If you can get into your tablet, open up a command shell and enter the commands "su" then "reboot recovery".

It's possible you'll find recovery doesn't work (I had same issues as you and couldn't get in, tablet just booted to a blank screen after the Google logo).
Following the steps http://forum.xda-developers.com/showthread.php?t=1781250
worked (didn't bother with the bootloader image) got things back up and running.
If you can get into recovery and/or ADB is working (with SU) you can recover by replacing the file.
Good luck!

Highland3r said:
It's possible you'll find recovery doesn't work (I had same issues as you and couldn't get in, tablet just booted to a blank screen after the Google logo).
Following the steps http://forum.xda-developers.com/showthread.php?t=1781250
worked (didn't bother with the bootloader image) got things back up and running.
If you can get into recovery and/or ADB is working (with SU) you can recover by replacing the file.
Good luck!
Click to expand...
Click to collapse
The OP said he can still get into the tablet with adb. So he can either use 'adb shell' to manually edit the file, or use 'adb push' to overwrite the one on the tablet. Either way should work.

phonic said:
The OP said he can still get into the tablet with adb. So he can either use 'adb shell' to manually edit the file, or use 'adb push' to overwrite the one on the tablet. Either way should work.
Click to expand...
Click to collapse
That'll teach me to only 1/2 read a post!

One of the problems with a custom build.prop is that it will break updates from Google. Granted using CWM/TERP will do so as well (unless you turn off signature verification, but you will wind up losing custom recovery and root (unless you backed root up)). The updater-script in the update verifies the checksum of build.prop to make sure that it's running the correct version prior to installing the patches/new files/etc. Any modifications will break it, though you could force it manually - not a good idea unless you know what you are doing.

Its all good now. With the tablet connected to the computer, it let me get into recovery. Restored a backup and all is good. The tablet ui is kind of cool, but really feels cramped.
Sent from my Nexus 7 using xda premium

Thanks for the build prop, that got my tablet working again!
lesson learned, just because an app that advises a backup has worked every time on your phone dont assume it will do the same on a different device.
I have also stuck with the stock "Hybrid UI" I do think google made the right choice the full tablet UI is a bit strange feeling on a 7" screen

I usually don't make backups because I'm an idiot and things usually work out for me, so I was stunned when I suddenly had a blank build.prop file after trying to edit it
thanks for this, all is working now

phonic said:
Sure, I'll see if I can make a copy and UL it for you.
What build are you on though? Did you upgrade to the latest "D" build yet? That will impact what your build.prop file should look like.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Here are the contents of the JRO03D build.prop:
You can also download it here:
http://core.routed.com/build.prop
Click to expand...
Click to collapse
Your upload Saved me frustration! Thank you so much! I can update to 4.1.2 now!!

phonic said:
Sure, I'll see if I can make a copy and UL it for you.
What build are you on though? Did you upgrade to the latest "D" build yet? That will impact what your build.prop file should look like.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Here are the contents of the JRO03D build.prop:
You can also download it here:
http://core.routed.com/build.prop
Click to expand...
Click to collapse
wow, thanks for that! i've been downloading various build.prop backups and versions from all over the place and yours was the only one that worked! :good:
you saved my (nexus 7) skin!

drpepe said:
wow, thanks for that! i've been downloading various build.prop backups and versions from all over the place and yours was the only one that worked! :good:
you saved my (nexus 7) skin!
Click to expand...
Click to collapse
Could you please share the JRO03D build prop again. The original link is dead and I was stupid enough not to make a backup, before editing mine. The copy paste is not working for me either. Thanks a lot.