Related
Hi
Yesterday with SEUS my X10 is bicked, today i try all this ways and all the same result BRICKED.
1º Several times with SEUS, 2 pcs, and not installed.
2º pccompanion connect to X10 but not identifie.
3º flashupdate with step 1 of root way, several times, KO
Code:
INFO: <<<ERR_SEVERITY="MAJOR";ERR_CLASS="PROTOCOL_CLASS";ERR_STATIC="UNVALID_COMMAND";ERR_DYNAMIC="";
30-jun-2010 12:11:52 X10flash writeCmd
INFO: write(cmd=10) (finish)
30-jun-2010 12:11:52 X10flash readReply
INFO: <<< cmd=10,flags=0,length=0
30-jun-2010 12:11:52 X10flash writeCmd
INFO: write(cmd=4) (finish)
30-jun-2010 12:11:52 X10flash readReply
INFO: <<< cmd=4,flags=1,length=0
30-jun-2010 12:11:52 X10flash run
INFO: ###test end.
4º With special pack unbrick XIOFUB, the same result, KO
hotfile.com/dl/44983907/9d54b5e/XIOFUB.rar.html
5º With Omnius, the same result, KO
Code:
13:11:49 Flash
13:11:49 Allows to change languages supported by the phone and upgrade its firmware.
13:11:49 Operating system: Microsoft Windows XP Home Edition Service Pack 3 (build 2600)
13:11:49 Application version: 0.04.2151 (beta)
13:11:49 . The action name is 'Flash'
13:11:49 Selected phone type: Xperia™ X10
13:11:49 i Instructions
13:11:49 i 1. Make sure the phone battery is charged to at least 50%.
13:11:49 i 2. Switch off the phone!
13:11:49 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:11:49 i 4. Press and hold the return back button, then connect the cable to the phone!
13:11:49 . The action started waiting for the user
13:12:31 . The action finished waiting for the user
13:12:31 Conectado por medio de Dispositivo Flash USB SEMC (USB1)...
13:12:31 Version del controlador: 2.2.0.5
13:12:31 Cip detectado: QSD8250
13:12:31 Modo de Arranque: EROM
13:12:31 IMEI:
13:12:31 Enviando Cargador...
13:12:33 Establishing connection to the server...
13:12:38 Receiving news...
13:12:39 i No news
13:12:40 Actual credit: 0.00
13:12:46 Writing file R1FA016_APP_SW_RACHAEL_GENERIC_1227_4612_S1_SW_LIVE_AC12_0001_S1_PARTITION.zip...
13:13:16 e ¡Fallo!
13:13:16 . The action entered shutdown phase
13:13:16 . The action reported failure
Error code
# C882780696072EA7
Detalles del error
---
11 2C C9 F3 6E FE 3A DF 5C 3D FE F8 38 EA 82 99
EE D9 94 3C B0 8F 36 FB 3D B5 B1 B8 86 08 EE A7
44 5B AA 5E 60 2C A6 D1 86 58 4C 8A E8 79 A2 23
11 08 38 33 3E 30 EA 6F D4 29 2A D4 0A 7E 9C 18
DC B5 8A 47 D4 C6 F8 BF B2 4C C2 35 08 29 3E C9
14 65 FA E3 70 CF A4 62 F4 3D CE 0B 18 76 AE 99
04 EB 62 74 CE B3 9A 01 04 1D A2 D5 D8 C3 D6 3C
61 E8
---
6º With Davinci, the same result, KO
Code:
Getting Software List From Server For: X10 / 0001 / Red...
SELECTED: Flash / Debrand / Re-Brand [SonyEricsson] X10 / 0001 / Red / R2BA020 / O2 DE/LUSTER WHITE (1233-2794/R14A | GENERIC)
Script Execution Started...
Checking Files...
Downloading 85Kb...OK! (1 sec)
Downloading 16268Kb...OK! (47 sec)
Downloading 131984Kb...OK! (413 sec)
Starting up...
Script initialization. Please wait...
Loading S1 Loader... OK
20091222 15:39:00 S1_LOADER R4A024 1226-2250
Memory Stick: 8GB
Opening TA...OK
Reading TA Please Wait...OK
Closing TA...OK
Opening MiscTA...OK
Reading TA Please Wait...OK
Requesting Account Status...OK
User: 49574 / Credits: 0 / Counters: 10
Writing TA Data...OK
Writing APP-SW/amss_fs.sin...OK
Writing APP-SW/apps_log.sin...OK
Writing APP-SW/amss.sin...OK
Writing APP-SW/fota0.sin...OK
Writing APP-SW/fota1.sin...OK
Writing APP-SW/recovery.sin...
Error! SIN Body Block Not Accepted! Done 0x575000 of 0x575880
Writing APP-SW/dsp1.sin...
Error! APP-SW/dsp1.sin Header Is Not Accepted!
Writing APP-SW/boot.sin...
Error! APP-SW/boot.sin Header Is Not Accepted!
Writing APP-SW/cache.sin...
Error! FSP/cache.sin Header Is Not Accepted!
Writing APP-SW/preset.ta...FAILED
Error! SIN Body Block Not Accepted! Done 0x575000 of 0x575880
Writing APP-SW/dsp1.sin...
Error! APP-SW/dsp1.sin Header Is Not Accepted!
Writing APP-SW/boot.sin...
Error! APP-SW/boot.sin Header Is Not Accepted!
Writing APP-SW/cache.sin...
Error! FSP/cache.sin Header Is Not Accepted!
Writing APP-SW/preset.ta...FAILED
Failed To Write: 0x08FD Size 0x0010
Writing FSP/system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin...
Error! FSP/system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin Header Is Not Accepted!
Writing FSP/userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin...
Error! FSP/userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin Header Is Not Accepted!
Writing TA Data...FAILED
Starting Advanced Section...
Closing TA...FAILED
Shutting Down...OK
Your X10 Has Been Successfully Updated!
Execution Time - 00:10:07
Done!
Loading User Info...
User: / Credits: 0 / Counters: 10
You are, of course putting the device into flash mode each try right?
what do you mean by bricked? bricked usually means unable to do anything including flash roms....
x edude03, of course always put return key and x10 is in flash mode.
x dan-htc-touch, bricked is like you say, power on my x10 and in 30/40 seconds one phone with warning appear in the screen.
May be this problems is by status battery < than 50% ?
thanks a lot
alucine
alucine said:
x edude03, of course always put return key and x10 is in flash mode.
x dan-htc-touch, bricked is like you say, power on my x10 and in 30/40 seconds one phone with warning appear in the screen.
May be this problems is by status battery < than 50% ?
thanks a lot
alucine
Click to expand...
Click to collapse
I have a feeling that is has to do with an incompatible baseband (amss) currently on your phone, and the OS image...
the easy way: why don't you try the root method again?
rodrigofd said:
the easy way: why don't you try the root method again?
Click to expand...
Click to collapse
rodrigofd, if you look first post "way 3" is with root method of this forum, "way 4" is unbrick method of this forum, "way 5" is with Omnius server, and "way 6" is with Davinci server.
I think that is impossible, that 4 differents methods fail.
My last theory is battery status, it is possible to update firm with less than 50% battery ?
May be my X10 brick has less than 50% battery and ALL method fail buy this...
Anybody can updated x10 with less than 50% battery ?
Thanks agains.
alucine
P.D: Gracias amigo, desde Madrid
I updated yesterday, using Omnius, with 38% battery. Then I rooted it. No problems here.
when you tried with omnious , did you try to flash with software that was for your version of the x10, ie, did you use x10a software with an x10a or x10a software on a x10i?
my bricked phone came back to life only after flashing with the correct version of the software
instigator008 , sure that with 38% battery ? you are the first my friend
hondaguy, i sure that firmware is for X10i
by bricked you mean that you have a phone with a triangle on screen?
If so, I had the same problem.
what I did was to flash the latest firmware R2. This booted the phone for me.
Grab the flash tool, and download the Telenor R2 version from here
forum.xda-developers.com/showthread.php?t=683793
backup system.sin and userdata.sin from the flash folder, and rename the files that you got in the R2 rar to system.sin and userdata.sin (userdata.sin should be the file that is 5kb)
and then flashed it, this fixed the issue
stop what you are doing and start with the BASICS.
first of all if your phone goes to yellow triangle then it is not bricked so stop worrying
secondly re download an omnius firmware of your choice ( i suggest UK generic r1b0016 as it will prepare you for root )
i tell you to re-download because your old download may be corrupt
extract the file you downloaded so you get the 2 .zip files
try omnius again. large zip in top , small zip in bottom
if that fails then try from different a computer.
What version of Omnius are you using and where did you get the firmware that you are trying to flash through it from?
Also can you add how you "stuffed" it exactly.
Global Generic R1FA016 for Omnius:
http://www.2shared.com/file/rWZ3YeGm/X10i_GLOBAL_GGL_GENERIC_1232_9.html
http://www.megaupload.com/?d=0JMUI3I5
R1FA016_APP_SW_RACHAEL_GENERIC_1227_4612_S1_SW_LIVE_AC12_0001_S1_PARTITION in as the application file and
R7A_R1FA016_FSP_X10i_GENERICGLOBAL_GGL_GENERIC_1232_9897_S1_SW_LIVE_AC12_0001_S1_PARTITION_WITH_SPARE as the customised file.
and also have you tried emptying your blob_fs folder and getting SEUS to do a repair with its own files ? rather than with the 2 files you put in
andy8271 said:
and also have you tried emptying your blob_fs folder and getting SEUS to do a repair with its own files ? rather than with the 2 files you put in
Click to expand...
Click to collapse
Ok, bad thing what you have there. Seems like part of the erase/write procedure for the recovery image has crashed. What might mean you have a hardware problem (and seus crashed because of that) or some essential area has got corrupt.
First pick omnius and try to backup the Trim Area (TA). Just in case you might need it, and to check it still exists.
Pick Any of the rooting packages, and from step1 move all SIN files EXCEPT loader.sin to another folder.
Then, one by one, go flashing those files, in no particular order, but one by one:
amss first
dsp second
amss_fs
apps_log
boot
fota0
fota1
system
userdata
recovery
If any of them give any kind of error, the rest won't flash. If it always get stucked on recovery, you probably have a bad block on the flash chip, and you should go to a service center, tell them you were updating with SEUS and it crashed. See if you can get a swap.
alucine said:
My last theory is battery status, it is possible to update firm with less than 50% battery ?
May be my X10 brick has less than 50% battery and ALL method fail buy this...
Click to expand...
Click to collapse
Yes it might completely fail with less than 50% battery, I myself had one rooting routine where my battery dropped from 60% to less than 10% in a full ROM flashing. So the guy who did it with only 38% just had a lucky run period.
I can't remember where it was posted but I did see a post from somebody who failed flashing with 48% of battery power.
So before starting any recovery attemp I'd suggest you let your X10 load up to a full 100% (when the led turns off) before trying anything else. I also noticed that when loading the battery directly from a power outlet it loads faster than from powering from USB.
alucine said:
instigator008 , sure that with 38% battery ? you are the first my friend
hondaguy, i sure that firmware is for X10i
Click to expand...
Click to collapse
My impression is the 50% battery is a recommendation for safety, not a must have to proceed.
Hi guys, this morning my battery in another X10 say 30% left only...
My X10 with the battery of a friend, not work update firmware, pccompanion, SEUS and flashtool.
This afternoon i will go to oficial SE support of my city, i hope that will be revive
while rooting yesterday, i left my phone in flash mode for around 20 mins
and from 80% battery it dropped to 10%
if you try rooting or restoring firmware with only 30% battery you are asking for trouble!
I guess I was lucky then lol.. had around 35-40%
Sent from my X10i using XDA App
alucine said:
Hi
Yesterday with SEUS my X10 is bicked, today i try all this ways and all the same result BRICKED.
[/CODE]
Click to expand...
Click to collapse
You mean that its bricked while you used SEUS update?
If this is true and you cannot run X10flash or others again you have a nand failure (hw related).
Then please connect SE and let it fixed by them. I know exactly one person with the same problem, they replaced his device directly .
Regards
Bin4ry
Hi all,
Like many of us, I managed to kill a digitizer on my HTC Aria. Replaced the blasted thing, and now I find my proximity sensor is really sensitive. It's locked in proximity mode (Z-devicetest shows distance 0) in normal conditions.
If I pull off the digitizer, so the prox sensor has a clear path in front of it, it goes out of proximity state and Z-devicetest shows the distance as 1 (and the display works properly during calls, speakerphone works, etc) ...
If I slowly move the tip of my finger towards the prox. sensor, digitizer still removed, Z-devicetest shows it flip from 1 to 0 (out of prox to in prox) as my finger gets within ~2 inches.
So it seems the prox. sensor is working but is too sensitive.
Is this the normal failure mode of a CM3602 prox sensor (read: i dropped it, and not only broke the digizer, but took out the prox sensor too!) .. or, is there some sort of calibration i need to do?
Anyone have a USA source of the CM3602? My usual suppliers digikey and mouser don't carry this component..
*curses self* shoulda listened to my friend who warned me this phone is real easy to bust
There is a guy in the accessories board that is selling parts of his aria. I'd link ya but I don't know how from this app.
Sent from my Liberty using XDA App
Right on.
I didn't want to butcher this poor little POS more so I figured out how to turn the bloody sensor off in software.
append
gsm.proximity.enable=false
to /system/build.prop
or just uncomment the line if you have an editor.. but you can just cat >> build.prop in the shell and type in the line. No editor needed.
Must do this via adb shell with phone in clockwork, otherwise nand is lokt. boo. dev eng hardware doesn't have that problem... stupid consumer devices!
So do you just start Android sdk and then type the following.
append (enter)
gsm.proximity.enable=false (enter)
or is there more to it. I really need to get this disabled.
I tried to do it with ASTRO but it doesnt save my changes.
/system/build.prop is a standard text file.
Remember that stuff in /system is protected, I find the best way to deal with the /system partition is through clockworkmod recovery.
a. Disconnect USB, reboot into clockworkmod recovery
b. Mount the /system partition from the partitions menu
c. Connect USB to a system with adb
d. adb pull /system/build.prop
e. Edit file with your favorite text editor to append gsm.proximity.enable=false
f. adb push build.prop /system/build.prop
g. unmount /system from clockworkmod recovery partition menu
h. reboot phone, receive bacon
If you don't have clockworkmod recovery, just use unrevoked to install it
Oh, i should also say CM6 (and maybe all of Froyo images?) do not honor this setting.
Thank you I will try this when I get home..
I may have an issue because if I open build.prop with root explorer it says...
# try to disable proximity sensor in call by default
# gsm.proximity.enable=false
This is located almost at the bottom of the page does this mean I am sol. It is the liberated Rom and I haven't done anything to it.
Sent from my HTC Liberty using XDA App
Just remove the # ...
# gsm.proximity.enable=false
..to
gsm.proximity.enable=false
thank you so much..... you may be oh wait you are the FN man.
ok so if froyo images dont honor this does that mean when we get froyo I shouldn't upgrade.
anyway thank you so much now I can use my phone again, I didn't realize how much my Pure was dated till I had to use it for a few days.
Glad that helped
I didn't find a property in Froyo that disabled the proximity sensor. Maybe there is one, maybe there is not. I went another method..
Code:
# hexdump -C /system/lib/hw/sensors.liberty.so | grep -C3 dev/cm
00001b10 54 5f 54 46 4c 41 47 20 65 72 72 6f 72 20 28 25 |T_TFLAG error (%|
00001b20 73 29 00 45 43 53 5f 49 4f 43 54 4c 5f 41 50 50 |s).ECS_IOCTL_APP|
00001b30 5f 53 45 54 5f 4d 56 46 4c 41 47 20 65 72 72 6f |_SET_MVFLAG erro|
00001b40 72 20 28 25 73 29 00 2f 64 65 76 2f 63 6d 66 75 |r (%s)./dev/cmfu|
00001b50 6b 74 00 43 41 50 45 4c 4c 41 5f 43 4d 33 36 30 |kt.CAPELLA_CM360|
00001b60 32 5f 49 4f 43 54 4c 5f 45 4e 41 42 4c 45 20 65 |2_IOCTL_ENABLE e|
00001b70 72 72 6f 72 20 28 25 73 29 00 2f 64 65 76 2f 6c |rror (%s)./dev/l|
Offset 1b48 in /system/lib/hw/sensors.liberty.so defines the device name of the proximity sensor, normally /dev/cm3602.
Hexedit the file to change the name of the device to something that doesn't exist, and you will no longer use the proximity sensor.
Nasty and totally the wrong way to do this, but it worked for me. I suppose I could have dug through source code to check for a flag to disable the sensor, but that takes more time and is far less hacking fun than hex editing a system library If I didn't want to live dangerously I'd stick with the stock ROM lol.
Thanks again I will check back when group comes out if I can't figure it out. I am going to stick with the liberated Rom till we get the official Rom and it gets liberated.
Sent from my HTC Liberty using XDA App
Not a bad idea if you're happy with 2.1 and Sense
Yeah I really like the sense UI so I will stay with 2.1 until a 2.2 with sense is available.
Sent from my HTC Liberty using XDA App
Thanks for this info. Just changed CM3602 to XM3602 and it stopped.
I just upgraded to the new attn1 2.2 Rom with sense and I used the same fix you gave me for the 2.1 Rom and it worked so I guess that fix will work on all sence roms.
Sent from my HTC Liberty using XDA App
I just used hexeditor on my phone ( fr 2.2) and went to the location you noted 00001b48 but nothing there. I went on looking and found it on a few lines starting at 00002090. but which value do I change to get it to disable. If you could look at this for me it would help alot.
nrvate said:
/system/build.prop is a standard text file.
Remember that stuff in /system is protected, I find the best way to deal with the /system partition is through clockworkmod recovery.
a. Disconnect USB, reboot into clockworkmod recovery
b. Mount the /system partition from the partitions menu
c. Connect USB to a system with adb
d. adb pull /system/build.prop
e. Edit file with your favorite text editor to append gsm.proximity.enable=false
f. adb push build.prop /system/build.prop
g. unmount /system from clockworkmod recovery partition menu
h. reboot phone, receive bacon
If you don't have clockworkmod recovery, just use unrevoked to install it
Click to expand...
Click to collapse
I am trying to use these steps to disable the sensor, but I am having issues pulling build.prop.
In the command prompt, I enter in:
adb pull /system/build.prop c:\
And receive:
264 Kb/s (4695 bytes in .012s)
The issue I am having is that I cannot find where adb stores the file on my computer. It's not in the c:\ directory. It's not in platform-tools folder. I did a search, and nothing came up
Any suggests would be really appreciated.
Thanks!
I'm confused - why are you guys disabling the proximity sensor???
Is it because you improperly installed a new screen?
Might as well use duct tape to hold the new screen on and then JB Weld the back case. Seriously guys, do things right and take the screen back off and install it the right way.
kaschenberg,
I dropped my phone, shattering the screen; resulting in a lot of fractures in the glass where the sensor is located. The phone and screen works when I add pressure to the upper right corner, leaving me to believe the sensor is being interrupted by the fractures. I am hopeful, as a temporary fix, that if I can disable the sensor, the phone will work more optimally until I replace the screen.
- Thoughts?
Hi all,
I might have discovered a bug in the Android 2.2.1 for Galaxy S.
the following is the case:
My Galaxy S is running 2.2.1, and is completely standard, I have for 100% sure not messed with root access or lagfixes or whatssoever.
It Appears that when you de-install an app from the phone, it sometimes does not remove the preferences file.
The result is, when you reinstall the same app, it gets a new uid, and it can not save its preferences, because the apps preferences file is still on the phone, with a different uid.
in my case:
ps output:
USER PID PPID VSIZE RSS WCHAN PC NAME
app_17 19411 2366 223648 21104 ffffffff 00000000 S klwinkel.huiswerk
ls -l output:
-rw-rw---- app_107 app_107 292 2011-01-22 20:13 klwinkel.huiswerk_preferences.xml
Did more people see this problem?
does anyone how to report this to Samsung?
Hi
Firstly I apologise if I have put this into the wrong section within the forum.
I'm wanting to remove the secondary icon from a notification within a particular app. Also on some apps like WhatsApp it will also show a notification count (next to the secondary icon) Please see below link which gives an example.
//developer.android.com/design/patterns/notifications_k.html
Which line of code do I need to find and remove so the secondary icon and notification count no longer appears?
Thanks.
There will be called NotificationBuilder at some instance and there look for a method call to setSmallIcon(...)
---------------------------------
Phone : Nexus 4
OS :
- KitKat 4.4.4 stock
- Xposed: 58(app_process); 54(bridge)
- SU: SuperSU
- no custom recovery
---------------------------------
4d 61 73 72 65 70 75 73 20 66 74 77
Gesendet von Tapatalk
When searching through the code I found a few lines looking like this;
invoke-virtual {v1, v2, v3}, Landroid/app/Notification$Builder;->setSmallIcon(II)Landroid/app/Notification$Builder;
When I removed each line then the application crashed prior to the notification being displayed in the status bar. Meaning no notification was shown, however I was still able to open the app.
What would I need to change in this line to prevent the secondary icon from displaying?
Thanks.
hi,
since two month I am using the AOKP ROM on my Huawei P10 lite (WAS-LX1A):
https://forum.xda-developers.com/p1...m-aokp-7-1-2-p10-lite-hassanmirza01-t3746120/
Everything was working fine: TWRP for backups and flashing, SuperSU with some Apps that require root (titanium, ...).
But I only had one SIM and one SD card inside.
Now I want to use two SIM cards and no SD card. But when I insert two SIM cards and boot the phone, I am asked to enter both pin's. Nothing unusual.
But no sim will find a network. So no signal on both cards. And every two to four minutes, I am asked to enter both pin again. So it is like a SIM PIN loop. But between each request, I can use the rest of the system normally.
I read, that maybe my `phone.prop` file is not correct. So I tried some changes.
When I open `/sys/firmware/devicetree/base/hisi,modem_id` in hex editor app (from playstore), I get `3b 45 74 00 00 00 00 00` in the first line. So I assume my code must be `0X3B457400` (correct me, if I am wrong).
So originally I have a symlink `/system/vendor/phone.prop` that is pointing to `/hwvendor/phone.prop`. (is that normal?)
And in that file I have the following text somewhere in the middle:
Code:
[...]
[0X3B457400]:
rild.libpath1=/vendor/lib64/libbalong-ril-1.so
ro.config.hw_dsda=false
rild.libpath=/vendor/lib64/libbalong-ril.so
ro.config.is_start_commril=true
ro.multi.rild=false
ro.config.modem_number=2
ro.config.hw_save_pin=true
persist.dsds.enabled=true
ro.config.client_number=2
ro.config.dsds_mode=umts_gsm
persist.radio.multisim.config=dsds
rild.rild1_ready_to_start=false
rild.libargs1=-m modem1
persist.radio.nv_match_by_card=2
ro.pwroff_card_if_tray_out=true
rild.libargs=-m modem0
ro.telephony.default_network=9
persist.radio.modem.cap=09A9C
ro.config.default_commril_mode=ULG_MODE
[..]
And I changed it to:
Code:
[...]
[0X3B457400]:
rild.libpath1=/vendor/lib64/libbalong-ril-1.so
ro.config.hw_dsda=false
rild.libpath=/vendor/lib64/libbalong-ril.so
ro.config.is_start_commril=true
ro.multi.rild=false
ro.config.modem_number=2
ro.config.hw_save_pin=true
persist.dsds.enabled=false
ro.config.client_number=2
ro.config.dsds_mode=umts_gsm
persist.radio.multisim.config=single
rild.rild1_ready_to_start=false
rild.libargs1=-m modem1
rild.libargs=-m modem0
ro.telephony.default_network=9
persist.radio.modem.cap=09A9C
ro.config.default_commril_mode=ULG_MODE
[...]
But it did not help at all. still no signal and still a pin loop.
What can I do? am I missing something important? Is there something that I did not find yet?
greetings,
Christopher
PS.: When I enter a wrong pin, the pone tells me that I have 2 tries left. So that is working I guess.