Database Develop

[Q] Unlock bootloader. no completed.

I do the whole process, but the error does not come out of this part, I waited 5 minutes. what can be? gingerdx tried the v19 and 2.1 (backup made ​​before installing the ROM).
I'am using Stock 2.1 and gingerdx v19...
error:
process requires standard 2.x android firmware.
Pressione qualquer tecla para continuar. . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
5 minutes...

new error........kkkkk
process requires standard 2.x android firmware.
Pressione qualquer tecla para continuar. . .
Getting ROOT rights.
1153 KB/s (585731 bytes in 0.496s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent.
Require ROOT rights
.
343 KB/s (3087 bytes in 0.008s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Waiting ...
Getting ROOT rights.
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
733 KB/s (8064 bytes in 0.010s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Second, we need to write semcboot
1289 KB/s (596916 bytes in 0.452s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Pressione qualquer tecla para continuar. . .

wlon said:
process requires standard 2.x android firmware.
Pressione qualquer tecla para continuar. . .
Getting ROOT rights.
1153 KB/s (585731 bytes in 0.496s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent.
Require ROOT rights
.
343 KB/s (3087 bytes in 0.008s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Waiting ...
Getting ROOT rights.
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
733 KB/s (8064 bytes in 0.010s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Second, we need to write semcboot
1289 KB/s (596916 bytes in 0.452s)
- exec '/system/bin/sh' failed: No such file or directory (2)
-
- exec '/system/bin/sh' failed: No such file or directory (2)
-
Pressione qualquer tecla para continuar. . .
Click to expand...
Click to collapse
i got same output. they say i should try with stock ROM
well i didnt try since then.

Make backup.
Use PC Companion to reset your device.
Use new Flashtool to root it.
Run unlock utility.

make sure PC Companion detect your device

worked, thanks for the help guys!!

i succesfuly unlocked bootloader too.
confirmed again
installed stock 2.1 version of software (with SEUS)
update flashtool to 0.5.3. ...
root
unlock bootloader
Code:
25/031/2011 10:31:24 - INFO - <- This level is successfully initialized
25/031/2011 10:31:26 - INFO - Device connected with USB debugging on
25/031/2011 10:31:27 - INFO - Connected device : E15
25/031/2011 10:31:27 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
25/031/2011 10:31:27 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
25/031/2011 10:31:27 - INFO - Root Access Allowed
25/031/2011 10:31:41 - INFO - Searching Xperia....
25/031/2011 10:31:41 - ERROR - Please plug you device in flash mode
25/031/2011 10:31:42 - INFO - Searching Xperia....
25/032/2011 10:32:06 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&DF2EE03&0&7
25/032/2011 10:32:06 - INFO - VER="R8A029";DATE="20100601";TIME="12:17:00";
25/032/2011 10:32:06 - INFO - Start Reading property
25/032/2011 10:32:06 - INFO - Reading property finished.
25/032/2011 10:32:06 - INFO - Found semcSL
25/032/2011 10:32:06 - INFO - You can now unplug and turn on device, then plug it again
25/032/2011 10:32:06 - INFO - Waiting for device
25/032/2011 10:32:06 - INFO - Device connected in flash mode
25/032/2011 10:32:34 - INFO - Device disconnected
25/033/2011 10:33:31 - INFO - Device connected with USB debugging on
25/033/2011 10:33:33 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\my7227bootwrite_semcSL to /data/local/tmp
25/033/2011 10:33:33 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\mapper_2.6.29.ko to /data/local/tmp
25/033/2011 10:33:33 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\fixPart to /data/local/tmp
25/033/2011 10:33:34 - INFO - Running runfixPart as root thru sysrun
25/033/2011 10:33:34 - INFO - Successfully applied fixPart. Rebooting
25/033/2011 10:33:35 - INFO - Waiting for device
25/033/2011 10:33:37 - INFO - Device disconnected
25/033/2011 10:33:47 - INFO - Device connected with USB debugging off
25/033/2011 10:33:57 - INFO - Device connected with USB debugging on
25/034/2011 10:34:20 - INFO - Running runbootwrite as root thru sysrun
25/034/2011 10:34:22 - INFO - Successfully applied unlock. Rebooting
25/034/2011 10:34:22 - INFO - Running runClean as root thru sysrun
25/034/2011 10:34:24 - INFO - Device disconnected
25/034/2011 10:34:34 - INFO - Device connected with USB debugging off
25/035/2011 10:35:37 - INFO - Device disconnected
25/035/2011 10:35:41 - INFO - Device connected with USB debugging off
-----------------------------------------------------------
s1tool log
-----------------------------------------------------------
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1241-4047_R2B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: BX902D6JL1
SEMC SIMLOCK CERTIFICATE
Elapsed:29 secs.
thaks developers

gferen said:
i succesfuly unlocked bootloader too.
confirmed again
installed stock 2.1 version of software (with SEUS)
update flashtool to 0.5.3. ...
root
unlock bootloader
Code:
25/031/2011 10:31:24 - INFO - <- This level is successfully initialized
25/031/2011 10:31:26 - INFO - Device connected with USB debugging on
25/031/2011 10:31:27 - INFO - Connected device : E15
25/031/2011 10:31:27 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
25/031/2011 10:31:27 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
25/031/2011 10:31:27 - INFO - Root Access Allowed
25/031/2011 10:31:41 - INFO - Searching Xperia....
25/031/2011 10:31:41 - ERROR - Please plug you device in flash mode
25/031/2011 10:31:42 - INFO - Searching Xperia....
25/032/2011 10:32:06 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&DF2EE03&0&7
25/032/2011 10:32:06 - INFO - VER="R8A029";DATE="20100601";TIME="12:17:00";
25/032/2011 10:32:06 - INFO - Start Reading property
25/032/2011 10:32:06 - INFO - Reading property finished.
25/032/2011 10:32:06 - INFO - Found semcSL
25/032/2011 10:32:06 - INFO - You can now unplug and turn on device, then plug it again
25/032/2011 10:32:06 - INFO - Waiting for device
25/032/2011 10:32:06 - INFO - Device connected in flash mode
25/032/2011 10:32:34 - INFO - Device disconnected
25/033/2011 10:33:31 - INFO - Device connected with USB debugging on
25/033/2011 10:33:33 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\my7227bootwrite_semcSL to /data/local/tmp
25/033/2011 10:33:33 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\mapper_2.6.29.ko to /data/local/tmp
25/033/2011 10:33:33 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\fixPart to /data/local/tmp
25/033/2011 10:33:34 - INFO - Running runfixPart as root thru sysrun
25/033/2011 10:33:34 - INFO - Successfully applied fixPart. Rebooting
25/033/2011 10:33:35 - INFO - Waiting for device
25/033/2011 10:33:37 - INFO - Device disconnected
25/033/2011 10:33:47 - INFO - Device connected with USB debugging off
25/033/2011 10:33:57 - INFO - Device connected with USB debugging on
25/034/2011 10:34:20 - INFO - Running runbootwrite as root thru sysrun
25/034/2011 10:34:22 - INFO - Successfully applied unlock. Rebooting
25/034/2011 10:34:22 - INFO - Running runClean as root thru sysrun
25/034/2011 10:34:24 - INFO - Device disconnected
25/034/2011 10:34:34 - INFO - Device connected with USB debugging off
25/035/2011 10:35:37 - INFO - Device disconnected
25/035/2011 10:35:41 - INFO - Device connected with USB debugging off
-----------------------------------------------------------
s1tool log
-----------------------------------------------------------
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1241-4047_R2B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: BX902D6JL1
SEMC SIMLOCK CERTIFICATE
Elapsed:29 secs.
thaks developers
Click to expand...
Click to collapse
This worked for me to!
I used msm7227_semc.cmd and my sim lock is not locked so,i bought it with sim lock locked but with this method it didn't locked it again.Tnx

maybe you must check from the earlier step man.
1. Root your phone, you can use flash tool or super one click
2. make sure unlock bootloader
3. follow the instruction from you flash tool
4. than you can flash your kernel
5. flash your rom
6. dont' forget to wipe
read this http://forum.xda-developers.com/showthread.php?t=1254225
hope it can help you...
take it easy man because I had bricked my phone 3 times..but it stilll okay

rav3n_pl said:
Make backup.
Use PC Companion to reset your device.
Use new Flashtool to root it.
Run unlock utility.
Click to expand...
Click to collapse
pc companion to reset , how ?
help here, still noob

phycro.sync said:
pc companion to reset , how ?
help here, still noob
Click to expand...
Click to collapse
just flash the X8 E15i 2.1.1.C.0.0._un.ftf to go back on 2.1 firmware
download from my signature
zzzzzzzzzzzzzzz thread from 2011

from ROM gingerdx v031 ,.stock kernel
can it still reset like normally ?
Sent from my GT-I8150 using xda app-developers app

phycro.sync said:
from ROM gingerdx v031 ,.stock kernel
can it still reset like normally ?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
U must go back to stock rom with help of pc companion or flashtool
Sent from my E15i

phycro.sync said:
pc companion to reset , how ?
help here, still noob
Click to expand...
Click to collapse
It was in PCC menu, "rescue device" or something. Look @ menu

[Q] novaterm executes novacom

whenever I type "novaterm" into terminal (on arch linux) It just executes novacom, and I can't get into my device.
here is that output:
usage: /opt/Palm/novacom/novacom [-a address] [-p port] [-t] [-l] [-d device] [-c cmd] [-r password] [-w] <command>
/opt/Palm/novacom/novacom [-V]
/opt/Palm/novacom/novacom [-a address] [-p port] -P[ [-f <localport:remoteport,...>] ]
options:
-a address: ip address of the novacomd server, default is 'localhost'
-p port: port of the novacomd server's device list port, default is 6968
-t: go into terminal mode, for interactive use
-s: pass signals to remote process
-l: list devices and then exit
-r: device password (must use with -c option)
-c: service command [login, add, remove, logout]
login: opens new session
add: adds device token to host
remove: remove device token from host
logout: closes active session
-d device: connect to specific device instead of first.
might be <nduid>, <connection type>, <device type>
-w: wait for device to show up before running command
-V: version information
-P: Port Forwarding Enabled
-f: ports to forward

bbm21 said:
whenever I type "novaterm" into terminal (on arch linux) It just executes novacom, and I can't get into my device.
here is that output:
usage: /opt/Palm/novacom/novacom [-a address] [-p port] [-t] [-l] [-d device] [-c cmd] [-r password] [-w] <command>
/opt/Palm/novacom/novacom [-V]
/opt/Palm/novacom/novacom [-a address] [-p port] -P[ [-f <localport:remoteport,...>] ]
options:
-a address: ip address of the novacomd server, default is 'localhost'
-p port: port of the novacomd server's device list port, default is 6968
-t: go into terminal mode, for interactive use
-s: pass signals to remote process
-l: list devices and then exit
-r: device password (must use with -c option)
-c: service command [login, add, remove, logout]
login: opens new session
add: adds device token to host
remove: remove device token from host
logout: closes active session
-d device: connect to specific device instead of first.
might be <nduid>, <connection type>, <device type>
-w: wait for device to show up before running command
-V: version information
-P: Port Forwarding Enabled
-f: ports to forward
Click to expand...
Click to collapse
Take a look at this thread : http://forum.xda-developers.com/showthread.php?t=1426244
On page 12 there's a good work around for novaterm problem. I've used it 3 times and it's been a life saver for me. It's a PITA, but it works.
As always, make a backup, just in case.
Edit : the commands are input using windows. This will repartition your tablet, so make sure that you have back up.

[Q] Flash Tool + Linux Mint Help

Hey All,
So today I've tried rooting the .253 by downgrading my firmware back to .434 but for some reason it just doesn't work I've inserted the log from the terminal and the log from Flash Tool (Latest Release), I'm running Linux Mint 14 xfce (Running Flash Tool as root of course) I took a risk by unplugging the device after 25 minutes and luckily it still works no brick so I'm happy but I'm a little stuck on how to actually get it to work because I had the same problem with it not downgrading on windows which I was stuck on because thats how I flashed the .253 firmware :S
Terminal Log
Code:
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre32
Error parsing gtk-icon-sizes string: ''
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (read) : No device
flashsystem.X10FlashException: S1 Header checksum Error
at flashsystem.S1Packet.<init>(S1Packet.java:55)
at flashsystem.io.USBFlashLinux.linuxReadS1Reply(USBFlashLinux.java:53)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:50)
at flashsystem.io.USBFlash.writeS1(USBFlash.java:33)
at flashsystem.Command.writeCommand(Command.java:123)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.uploadImage(X10flash.java:215)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
flashsystem.X10FlashException: Cannot read from device
at flashsystem.Command.writeCommand(Command.java:129)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.uploadImage(X10flash.java:215)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
flashsystem.X10FlashException: Cannot read from device
at flashsystem.X10flash.uploadImage(X10flash.java:222)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (read) : No device
flashsystem.X10FlashException: S1 Header checksum Error
at flashsystem.S1Packet.<init>(S1Packet.java:55)
at flashsystem.io.USBFlashLinux.linuxReadS1Reply(USBFlashLinux.java:53)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:50)
at flashsystem.io.USBFlash.writeS1(USBFlash.java:33)
at flashsystem.Command.writeCommand(Command.java:123)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.endSession(X10flash.java:398)
at flashsystem.X10flash.closeDevice(X10flash.java:408)
at flashsystem.X10flash.flashDevice(X10flash.java:373)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
release_interface : No device
release_interface : No device
Flash Tool Log
Code:
23/054/2013 08:54:04 - INFO - <- This level is successfully initialized
23/054/2013 08:54:04 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 22:29:21
23/054/2013 08:54:04 - INFO - You can drag and drop ftf files here to start flashing them
23/054/2013 08:54:08 - INFO - Device disconnected
23/054/2013 08:54:13 - INFO - List of connected devices (Device Id) :
23/054/2013 08:54:13 - INFO - List of ADB devices :
23/054/2013 08:54:13 - INFO - - none
23/054/2013 08:54:13 - INFO - List of fastboot devices :
23/054/2013 08:54:13 - INFO - - none
23/003/2013 09:03:28 - INFO - Flash canceled
23/004/2013 09:04:00 - INFO - Selected Xperia Z_10.1.A.1.434_Generic_WORLD.ftf
23/004/2013 09:04:00 - INFO - Preparing files for flashing
23/005/2013 09:05:32 - INFO - Please connect your device into flashmode.
23/005/2013 09:05:42 - INFO - Device connected in flash mode
23/005/2013 09:05:42 - INFO - Opening device for R/W
23/005/2013 09:05:42 - INFO - Device ready for R/W.
23/005/2013 09:05:42 - INFO - Reading device information
23/005/2013 09:05:43 - INFO - Phone ready for flashmode operations.
23/005/2013 09:05:43 - INFO - Current device : C6603 - CB5A1PQBU0 - 1270-4986_R7A - 1269-5309_10.1.1.A.1.253 - GLOBAL-LTE_10.1.1.A.1.253
23/005/2013 09:05:43 - INFO - Start Flashing
23/005/2013 09:05:43 - INFO - Processing loader
23/005/2013 09:05:43 - INFO - Checking header
23/005/2013 09:05:43 - INFO - Flashing data
23/023/2013 09:23:51 - INFO - Ending flash session <--- This is were I disconnected the device after 25 mins of waiting
23/023/2013 09:23:51 - ERROR - Cannot read from device
23/023/2013 09:23:51 - ERROR - Error flashing. Aborted
23/023/2013 09:23:52 - INFO - Device disconnected
23/025/2013 09:25:24 - INFO - Selected Xperia Z_10.1.A.1.434_Generic_WORLD.ftf
23/025/2013 09:25:24 - INFO - Preparing files for flashing
23/026/2013 09:26:48 - INFO - Please connect your device into flashmode.
23/027/2013 09:27:32 - INFO - Device connected in flash mode <--- This is me trying it again ...
23/027/2013 09:27:33 - INFO - Opening device for R/W
23/027/2013 09:27:33 - INFO - Device ready for R/W.http://forum.xda-developers.com/showthread.php?p=41741577#
23/027/2013 09:27:33 - INFO - Reading device information
23/027/2013 09:27:33 - INFO - Phone ready for flashmode operations.
23/027/2013 09:27:33 - INFO - Current device : C6603 - CB5A1PQBU0 - 1270-4986_R7A - 1269-5309_10.1.1.A.1.253 - GLOBAL-LTE_10.1.1.A.1.253
23/027/2013 09:27:33 - INFO - Start Flashing
23/027/2013 09:27:33 - INFO - Processing loader
23/027/2013 09:27:33 - INFO - Checking header
23/027/2013 09:27:33 - INFO - Flashing data <--- And this is me just giving up ... (got to get to work so :()

[DEV][ROM][ION][JB 4.1.2][Sense 5] Visionary Sense 5 [BUILD#3][WIP][13 Jan]

Hello Guys , This is my port of Sense 5 from Desire 300 to HTC Desire C.
This is a complete stock Rom ported from system dump of desire 300.
I will Specially Thanks To @cute_prince for his ION kernel.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
Installation Instruction :
1. Here Is a new boot.img flash this : LINK
2.Wipe Cache/dalvik cache(if you use TWRP, format system and data)
3.Install Test Build 2
4.Wipe cache/dalvik cache
5.Reboot
Download :
Testing Build#3
Testing Build#2
Testing Build#1
Please Guys test and report me through logcat.
Credits :
@cute_prince for UniFiedKerNel ( ION Kernel ) and without him it was not possible
@MameTozhio for Desire 300 Dump

reserved..

more

last

Thanks gonna flash it now

Rom doesnt boot
boot stop on htc logo(this build is for development purposes only...)

Ansanen said:
boot stop on htc logo(this build is for development purposes only...)
Click to expand...
Click to collapse
Yea same for me. Can't pull logcat because it stops so early

Wait problem in boot.img.. i will see
Take Logcat :
adb dmsg > dmsg.txt

xaak said:
Wait problem in boot.img.. i will see
Take Logcat :
adb dmsg > dmsg.txt
Click to expand...
Click to collapse
I don't know if I'm doing it right i get blank file. It seems that comman is not found in adb

doweeez said:
I don't know if I'm doing it right i get blank file
Click to expand...
Click to collapse
same for me

Ansanen said:
same for me
Click to expand...
Click to collapse
Take out battery and switch on take log immediately
Sent from my HTC Explorer A310e using Tapatalk

xaak said:
Take out battery and switch on take log immediately
Sent from my HTC Explorer A310e using Tapatalk
Click to expand...
Click to collapse
Doesn't seem to work either.
Code:
[email protected]:~/sdk/sdk/platform-tools$ adb dmsg > dmsg.txt
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.

doweeez said:
I don't know if I'm doing it right i get blank file. It seems that comman is not found in adb
Click to expand...
Click to collapse
Ansanen said:
same for me
Click to expand...
Click to collapse
Here Is a new boot.img flash this : LINK

xaak said:
Here Is a new boot.img flash this : LINK
Click to expand...
Click to collapse
Yay got booting. Now I'm past development build only window. Haven't booted to homescreen yet. But now when I'm trying to use logcat I get this message
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -

doweeez said:
Yay got booting. Now I'm past development build only window. Haven't booted to homescreen yet. But now when I'm trying to use logcat I get this message
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Can you see bootscreen and whenrom boots up please provide screenshots and tell me whats working and whats not.
Sent from my HTC Explorer A310e using Tapatalk

xaak said:
Can you see bootscreen and whenrom boots up please provide screenshots and tell me whats working and whats not.
Sent from my HTC Explorer A310e using Tapatalk
Click to expand...
Click to collapse
For last 10-15 mins I'm at boot animation. So don't know is it normal to take so much time

doweeez said:
For last 10-15 mins I'm at boot animation. So don't know is it normal to take so much time
Click to expand...
Click to collapse
It will take time as to load apps.
Sent from my HTC Explorer A310e using Tapatalk

xaak said:
It will take time as to load apps.
Sent from my HTC Explorer A310e using Tapatalk
Click to expand...
Click to collapse
bootloop and i can make logcat
exec '/system/bin/sh' failed: No such file or directory 2 2) -

Ansanen said:
bootloop and i can make logcat
exec '/system/bin/sh' failed: No such file or directory 2 2) -
Click to expand...
Click to collapse
Unzip rom take updaterscript from sense 4 now rezip and flash rom now provide me complete logcat on pastebin

xaak said:
Unzip rom take updaterscript from sense 4 now rezip and flash rom now provide me complete logcat on pastebin
Click to expand...
Click to collapse
Logcat

Unable to Launch Arm AVD on x86_64 Host

Hi,
I am trying to invoke arm based android emulator recent version(Android 11) on Linux. While doing so, facing "Device Manager: The emulator process for AVD Arm64 has terminated" -- details found on idea.log
2022-11-10 11:50:19,744 [ 611405] WARN - util.DeprecatedMethodException - Exception 'com.intellij.util.DeprecatedMethodException: The default implementation of method 'com.intellij.openapi.fileEditor.FileEditor.getFile' is deprecated, you need to override it in 'class com.android.tools.idea.mlkit.viewer.TfliteModelFileEditor'. A proper @NotNull implementation required' was reported 90 times
2022-11-10 11:50:20,006 [ 611667] INFO - Emulator: Arm64_Android11 - C:\Users\Devi\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -avd Arm64_Android11 -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-11-10 11:50:20,079 [ 611740] INFO - Emulator: Arm64_Android11 - PANIC: Avd's CPU Architecture 'arm64' is not supported by the QEMU2 emulator on x86_64 host.
2022-11-10 11:50:20,080 [ 611741] INFO - Emulator: Arm64_Android11 - Android emulator version 31.2.10.0 (build_id 8420304) (CL:N/A)
2022-11-10 11:50:20,084 [ 611745] INFO - Emulator: Arm64_Android11 - Process finished with exit code 1
2022-11-10 11:50:20,084 [ 611745] ERROR - Emulator: Arm64_Android11 - Emulator terminated with exit code 1
java.lang.Throwable: Emulator terminated with exit code 1
Click to expand...
Click to collapse
I am able to launch Android 7 on x86_64
Does this mean we can't launch Android arm emulator on x86_64 or am I missing any dependencies??