Database Develop

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!!!

Help With Nandroid Backup Errors

Hello, I am using WCX Illuminati Series by GINM and I receive this error whenever I try to make a nandroid back up
"Create Nandroid backup?
Press Power to confirm,
any other key to abort.
Preforming backup : ...
Oops. . . something went wrong!
Please check the recovery log!"
If anyone could please tell me what I am doing wrong I would appreciate it. I have used a regular version of CWM on a Motorola Triumph hundreds of times. Usually I would...
Boot into Recovery
Scroll to "Backup/Restore" and select
Select "Preform Nandroid Backup"
Then it usually just preformed the backup.
Thank you very much for reading this and I hope you can help me and anyone else who is having this problem

Where are you backing up to? The internal Sd-card or External and have you tried re-flashing the recovery?

Something doesn't sound right, maybe like the other poster said try flashing the recovery again. If that doesn't work may want to register here:
http://www.wcxxperia-nce.com/index.php
Post your question on the vivid forums since it is wild child's recovery.

tanner4137 said:
Hello, I am using WCX Illuminati Series by GINM and I receive this error whenever I try to make a nandroid back up
"Create Nandroid backup?
Press Power to confirm,
any other key to abort.
Preforming backup : ...
Oops. . . something went wrong!
Please check the recovery log!"
If anyone could please tell me what I am doing wrong I would appreciate it. I have used a regular version of CWM on a Motorola Triumph hundreds of times. Usually I would...
Boot into Recovery
Scroll to "Backup/Restore" and select
Select "Preform Nandroid Backup"
Then it usually just preformed the backup.
Thank you very much for reading this and I hope you can help me and anyone else who is having this problem
Click to expand...
Click to collapse
I have created and restored backups with WC's recovery.... but if we could have more info like if you are doing it to external or internal that would help
Also its always good to register in WC's forum and ask about his recovery there Because idk if he checks around here anymore

I am backing up to my internal micro sd card!
Sent from my HTC PH39100 using XDA

Have you tried re-flashing the recovery? Posting the recovery log would probably help us understand what exactly is happening.

Sure, I can try to do that in about an hour! I'll be back shortly
Sent from my HTC PH39100 using XDA

Also, what do you mean by recovery log. You mean the text that displays on the screen whenever I attempt to backup right? In that case, that was all that came up except a little bit before but it was just prompting me what to do. When I get home ill try to take a picture of everything on the screen and maybe that'll help!
Sent from my HTC PH39100 using XDA

tanner4137 said:
Also, what do you mean by recovery log. You mean the text that displays on the screen whenever I attempt to backup right? In that case, that was all that came up except a little bit before but it was just prompting me what to do. When I get home ill try to take a picture of everything on the screen and maybe that'll help!
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
No you have to go into recovery and choose other>Move recovery.log to SD. Then post it here.

Thank you so much!
Sent from my HTC PH39100 using XDA

*If it helps, I am running stock w/ root
Starting recovery on Thu Apr 5 00:10:55 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
RA Revamped
Build : Made for WCX ILLUMINATI SERIES by GINM
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.ril.oem.ecclist=911
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.dtm=0
ro.ril.gprsclass=10
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.def.agps.mode=1
ro.ril.att.feature=1
ro.ril.radio.svn=3
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.gea3=1
ro.ril.enable.ucsq=2
ro.ril.set.mtusize=1410
ro.ril.disable.cpc=1
persist.pdn.profile=pta
ro.ril.multirab.throttling=1
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-att-us
ro.product.model=HTC PH39100
ro.monkey=0
ro.sllowmock.location=0
ro.ril.ciq=1
ro.aa.customizationid=253678
ro.aa.romver=1.63.502.4
ro.aa.project=Holiday
ro.aa.mainsku=502
ro.aa.maincid=CWS__001
ro.aa.modelid=PH3910000
ro.aa.cidlist=CWS__001
ro.aa.rid=313
ro.aa.taskid=221238
ro.aa.skulist=502
ro.build.id=GRJ22
ro.build.display.id=GRJ22
ro.build.version.incremental=172546.4
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=五 10月 14 20:04:58 CST 2011
ro.build.date.utc=1318593898
ro.build.type=user
ro.build.user=
ro.build.host=ABM020
ro.build.tags=release-keys
ro.product.brand=cingular_us
ro.product.name=htc_holiday
ro.product.device=holiday
ro.product.board=holiday
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm8660
ro.build.product=holiday
ro.build.description=1.63.502.4 CL172546 release-keys
ro.product.processor=1.2 GHz dualcore
ro.build.changelist=172546
ro.product.ua=
ro.build.fingerprint=cingular_us/htc_holiday/holiday:2.3.4/GRJ22/172546.4:user/release-keys
ro.build.project=<CupcakeSKU.SKUInfo instance at 0x26fd1b8>:221238
ro.product.version=1.63.502.4
ro.build.languageremove=0
ro.build.sense.version=3.0
keyguard.no_require_sim=1
ro.sf.lcd_density=240
debug.fb.rgb565=0
debug.composition.type=c2d
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
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.rild.ril.ltedr=0
persist.rild.ril.ltedrtable=max_retries=infinite,10000
DEVICE_PROVISIONED=1
persist.cne.UseCne=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.be.ge.sqi.min=0
persist.cne.be.ge.sqi.max=100
persist.cne.be.umts.sqi.min=0
persist.cne.be.umts.sqi.max=100
persist.cne.be.hspa.sqi.min=0
persist.cne.be.hspa.sqi.max=100
persist.cne.be.1x.sqi.min=0
persist.cne.be.1x.sqi.max=100
persist.cne.be.do.sqi.min=0
persist.cne.be.do.sqi.max=100
persist.cne.be.wlan.sqi.min=0
persist.cne.be.wlan.sqi.max=100
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=11
ro.config.lte=true
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
ro.telephony.default_network=0
wifi.interface=eth0
wifi.supplicant_scan_interval=30
ro.opengles.version=131072
dalvik.vm.heapsize=32m
ro.ril.disable.power.collapse=1
ro.ril.enable.prl.recognition=1
ro.phone_storage=0
ro.ext4fs=1
ro.htc.checkin.url=http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl=http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN=http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN=http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url=http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN=http://fotamsg.htccomm.com.cn/android/extra/
ro.htc.appupdate.url=http://apu-chin.htc.com/check-in/rws/and-app/update
ro.htc.appupdate.url_CN=http://apu-chin.htccomm.com.cn/check-in/rws/and-app/update
ro.htc.appupdate.exmsg.url=http://apu-msg.htc.com/extra-msg/rws/and-app/msg
ro.htc.appupdate.exmsg.url_CN=http://apu-msg.htccomm.com.cn/extra-msg/rws/and-app/msg
ro.bt.chipset=Broadcom BCM4329-B1
ro.bt.stack=Broadcom BTL-A
ro.bt.stack.version=2.0.50.032
ro.bt.profiles=4270339
service.brcm.bt.activation=0
service.brcm.bt.srv_active=0
service.brcm.bt.hcid_active=0
service.brcm.bt.btld=0
service.brcm.bt.btld_pid=0
service.brcm.bt.avrcp_pass_thru=0
service.brcm.bt.avrcp_toggle=1
service.brcm.bt.local_name=
persist.sys.shutdown.mode=hibernate
ro.htc.common.version=2.0.0.0
ro.product.ram=1GB
ro.product.display_resolution=4.5 inch QHD resolution
ro.product.main_camera=8M
ro.product.front_camera=1.3M
ro.product.bluetooth=3.0
ro.product.wifi=802.11 b/g/n
ro.htc.framework.screencapture=true
ro.sdcard2=1
keydispatchtimeout=15000
profiler.anr_dump_native_uid=9999
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.networklocation=1
ro.setupwizard.mode=DISABLED
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
ro.com.google.gmsversion=2.3_r7
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=0
htc.audio.hac.enable=1
ro.setupwizard.enterprise_mode=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=Made for WCX ILLUMINATI SERIES by GINM
ro.factorytest=0
ro.qwerty_color=GenericColor
dev.silent_reboot=0
ro.serialno=HT1APVJ04544
ro.bootmode=recovery
ro.baseband=N/A
ro.carrier=ATT
ro.bootloader=1.85.0024
dev.bootreason=
ro.hardware=holiday
ro.revision=0
ro.devicerev=0
ro.engineerid=0
ro.lb=1
ro.cid=CWS__001
ro.mid=PH3910000
ro.emmc=1
ro.pagesize=2048
init.svc.choice_fn=stopped
init.svc.htcbatt=running
init.svc.adbd=running
init.svc.rmt_storage=running
ro.9kramdump=0
init.svc.recovery=running
ro.boot.block=/dev/block/mmcblk0p22
ro.recovery.block=/dev/block/mmcblk0p23
ro.misc.block=/dev/block/mmcblk0p24
ro.sdcard.block=/dev/block/mmcblk1p1
ro.sd-ext.block=/dev/block/mmcblk1p2
ro.internal_sdcard.block=/dev/block/mmcblk0p36
ro.ums.path=/sys/devices/platform/usb_mass_storage/lun0/file
ro.htcmodelid=PH3910000
*** WARNING ***
Nandroid backups require minimum
700mb SDcard space and may take a few
minutes to back up!
Compressed backups may take 30+ minutes!!
Use Other/recoverylog2sd for errors.
Create Nandroid backup?
Press Power to confirm,
any other key to abort.
Performing backup : .
nandroid-mobile v2.2.3
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default: Accepting default.
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
.checking free space on sdcard
Error: not enough free space available on sdcard (need 700mb), aborting.
.
Oops... something went wrong!
Please check the recovery log!
Create Nandroid backup?
Press Power to confirm,
any other key to abort.
Performing backup : .
nandroid-mobile v2.2.3
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default: Accepting default.
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
Error: not enough free space available on sdcard (need 700mb), aborting.
Oops... something went wrong!
Please check the recovery log!
Move recovery.log to SD
Press Power to confirm,
any other key to abort.
Moving : .unmounting /devlog
unmounting /cache

Does anyone know what the problem is?
Sent from my HTC PH39100 using XDA

Not enough space, tells you the problem...please removed the 5000 word post...lol...not needed
mounting system and data read-only, sdcard read-write
checking free space on sdcard
Error: not enough free space available on sdcard (need 700mb), aborting.
tanner4137 said:
Does anyone know what the problem is?
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse

How stupid of me very sorry!
Sent from my HTC PH39100 using XDA

Please rename thread as solved...
tanner4137 said:
How stupid of me very sorry!
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse

New Ubuntu port!

I want to run this on Samsung galaxy s4 i9505 jfltexx.
Anyone want to work on this?
Im willing to help in anyway i can
Sent from my GT-I9505 using xda app-developers app

Update: port is almost ready
Trying to sort a few compile errors

I would like to see this happen.

Relys said:
I would like to see this happen.
Click to expand...
Click to collapse
Me too
Sent from my GT-I9505G using Tapatalk

Awesome, can you dualboot it? And how big is the port rom?
Sent from my GT-I9505 using Tapatalk

JustSueMe said:
Update: port is almost ready
Trying to sort a few compile errors
Click to expand...
Click to collapse
Need any help?
Sent from my GT-I9505 using Tapatalk

Download link ! Alpha !
http://www.datafilehost.com/d/44a25a60
link is to download phablet
instructions:
reboot to recovery
wipe all partitions
flash phablet in above link
flash trusty-preinstalled-touch-armhf.zip [u can find on cdimages.ubuntu.com]
reboot phone to system
--
at this point youll have a black screen and no activity
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ reboot
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
no conectivity
no sound
edge swipe is small but works without case
camera
frame jumps to the right for some apps occasionally (unsure if thats on purpose of buggy... i vote buggy)
app crashing (maybe reason for camera crash?)
doesnt show imei
no sdcard mounted
terminal app doesnt even work so need to use adb to run commands
enjoy lol ... note alpha in title if anyone wants to complain ... also note only you are responsible for what happens to your device.

now have connectivity via reverse tether
adb root
adb shell setprop sys.usb.config rndis,adb
if you get permission error use adb server as root
ubuntu network manager will show that samsung android is connecting.
open network settings edit that connection and change auto DHCP to shared
adb shell
run this command (logged into phone)
dhclient usb0 -v
now on phone open webbrowser and you should be able to connect

just got WIFI !
haha progress
adb shell
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
now wifi will turn on
make it auto load at boot
touch /data/local/userinit.sh
add to the file :
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
make it run
chmod +x /data/local/userinit.sh

help !
im trying to fix the gsm
here is my output
[email protected]:/# nmcli dev
DEVICE TYPE STATE
/ril_0 gsm disconnected
wlan0 802-11-wireless connected
[email protected]:/etc/NetworkManager/system-connections# ls
TALKTALK-FCF354 Three
TalkTalk--* is my WIFI
Three is my mobile 3g data
so ill try to load Three
[email protected]:/etc/NetworkManager/system-connections# nmcli con up id Three
Error: Connection activation failed: The connection was not supported by oFono.
here is the contents of Three :
[connection]
id=Three
uuid=39a02ed3-d946-45f8-9abb-81ef997add03
type=gsm
autoconnect=false
[ppp]
refuse-eap=true
refuse-chap=true
refuse-mschap=true
refuse-mschapv2=true
nobsdcomp=true
nodeflate=true
no-vj-comp=true
[ipv4]
method=auto
[serial]
baud=115200
[gsm]
number=*99#
username=three
apn=3internet
contents of TalkTalk
[connection]
id=TALKTALK-FCF354
uuid=1bcf8cdf-9152-49de-b279-7770e94e5006
type=802-11-wireless
[802-11-wireless]
ssid=TALKTALK-FCF354
mode=infrastructure
mac-address=5C:F8:A1:90:2F:FB
security=802-11-wireless-security
[802-11-wireless-security]
key-mgmt=wpa-psk
auth-alg=open
psk=Password1
[ipv4]
method=auto
[ipv6]
method=auto
Why is TalkTalk supported and Three is not ?
as i understand it it uses https://github.com/rilmodem/ofono
AND if fixed this configuration may only give 3g data connection on the THREE 3 UK newtork not calls or sms but one step at a time/

JustSueMe said:
http://www.datafilehost.com/d/44a25a60
link is to download phablet
instructions:
reboot to recovery
wipe all partitions
flash phablet in above link
flash trusty-preinstalled-touch-armhf.zip [u can find on cdimages.ubuntu.com]
reboot phone to system
--
at this point youll have a black screen and no activity
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ reboot
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
no conectivity
no sound
edge swipe is small but works without case
camera
frame jumps to the right for some apps occasionally (unsure if thats on purpose of buggy... i vote buggy)
app crashing (maybe reason for camera crash?)
doesnt show imei
no sdcard mounted
terminal app doesnt even work so need to use adb to run commands
enjoy lol ... note alpha in title if anyone wants to complain ... also note only you are responsible for what happens to your device.
Click to expand...
Click to collapse
Will this work with an ATT that has a locked bootloader that needs loki file for the kernel?

toxicpaulution said:
Will this work with an ATT that has a locked bootloader that needs loki file for the kernel?
Click to expand...
Click to collapse
well for one this is for jfltexx, and secondly if the boot loader is locked i doubt that could flash it as u need a new the boot.img.
if you want it on att model you ill prob need to buid depreciated ubuntu touch.
depreciaed UT boots android then ubuntu in a container
this boots ubuntu then andriod in container.

JustSueMe said:
well for one this is for jfltexx, and secondly if the boot loader is locked i doubt that could flash it as u need a new the boot.img.
if you want it on att model you ill prob need to buid depreciated ubuntu touch.
depreciaed UT boots android then ubuntu in a container
this boots ubuntu then andriod in container.
Click to expand...
Click to collapse
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
---------- Post added at 01:49 PM ---------- Previous post was at 01:03 PM ----------
toxicpaulution said:
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
Click to expand...
Click to collapse
Didn't work, Getting status 7 which would mean I would have to edit the update script so it doesn't just look for the inital phone. I will do that now and try again.

toxicpaulution said:
Well see with ATT we can boot custom roms(MDL users) as long as the kernel is already lokidokied, or you can flash the loki zip and it will bypass the ATT check and allow you to boot a custom rom, Now seeing how this is based of CM10.2(thats what the file is saying so i am just taking a guess) if I flashed the Loki zip after flashing the rom would it work? But I am doing a backup as of now and I am going to test and see if it works :3 I will report back lol
---------- Post added at 01:49 PM ---------- Previous post was at 01:03 PM ----------
Didn't work, Getting status 7 which would mean I would have to edit the update script so it doesn't just look for the inital phone. I will do that now and try again.
Click to expand...
Click to collapse
the base may be cm10 but it doesnt boot cm10. the boot.img gets flashed and it boots ubuntu , the cm part is in a container within ubuntu
i dont think att will be able to use this is the bootloader cant be flashed

JustSueMe said:
the base may be cm10 but it doesnt boot cm10. the boot.img gets flashed and it boots ubuntu , the cm part is in a container within ubuntu
i dont think att will be able to use this is the bootloader cant be flashed
Click to expand...
Click to collapse
Yeah changing the updater script didnt do the job :/ lame lol well it was work the try, I will follow this htread though seems promising.

toxicpaulution said:
Yeah changing the updater script didnt do the job :/ lame lol well it was work the try, I will follow this htread though seems promising.
Click to expand...
Click to collapse
okay it wont let me adb push the file says bash: adb: command not found
edit: im running now but the connectivity through reverse thether isnt working. btw im on the att s4

JustSueMe said:
haha progress
adb shell
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
now wifi will turn on
make it auto load at boot
touch /data/local/userinit.sh
add to the file :
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
make it run
chmod +x /data/local/userinit.sh
Click to expand...
Click to collapse
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
---------- Post added at 02:34 AM ---------- Previous post was at 01:59 AM ----------
Joeyxc said:
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
Click to expand...
Click to collapse
link for att or tmobile http://www.androidfilehost.com/?fid=23252070760974893
Enjoy
This is just the cm, still follow the other instructions for everything else
http://www.youtube.com/watch?v=mJLKX_QWSpc&feature=youtu.be

Joeyxc said:
I have successfully ported the zip to the SGH-I337 AT&T model same as yours wifi no data after fixes. Are you having trouble with the roms sliding from the lockscreen to home trouble?
---------- Post added at 02:34 AM ---------- Previous post was at 01:59 AM ----------
link for att or tmobile http://www.androidfilehost.com/?fid=23252070760974893
Enjoy
This is just the cm, still follow the other instructions for everything else
http://www.youtube.com/watch?v=mJLKX_QWSpc&feature=youtu.be
Click to expand...
Click to collapse
So I should flash that first and then the others as stated?

toxicpaulution said:
So I should flash that first and then the others as stated?
Click to expand...
Click to collapse
Yup! Let me know if you run into any issues don't forget to thank if it worked!
Sent from my SGH-I337 using Tapatalk

Joeyxc said:
Yup! Let me know if you run into any issues don't forget to thank if it worked!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Forgot you need to use the Loki file for att, I'm doing adb on my other lappy haha xD then I'll boot it
Sent from my SGH-I337 using Tapatalk