Hi,
so far I had an xrecovery with an older cm version installed on my xperia x10 mini pro, now i wanted to install a more current rom, so i needed to go from xrecovery to clockworkmod.
i used the linux tool linked in the clockworkmod thread. unfortunately something must've happened during the installation, since the phone suddenly rebooted.
It happened sometime after pushing the files, i guess during or before setting the right permissions.
Now at some point the bootanimation just stops and nothing happens anymore, I can't adb in, I can't get to the recovery. dmesg on the connected pc is giving me
Code:
Nov 17 16:24:05 catscrash-desktop kernel: [24429.860116] usb 1-2.1: new high speed USB device using ehci_hcd and address 37
Nov 17 16:24:06 catscrash-desktop kernel: [24431.344730] scsi23 : usb-storage 1-2.1:1.0
Nov 17 16:24:07 catscrash-desktop kernel: [24432.341629] scsi 23:0:0:0: Direct-Access SEMC Mass Storage 0001 PQ: 0 ANSI: 2
Nov 17 16:24:07 catscrash-desktop kernel: [24432.342002] scsi 23:0:0:1: CD-ROM SEMC CD-ROM 0001 PQ: 0 ANSI: 2
Nov 17 16:24:07 catscrash-desktop kernel: [24432.342726] sd 23:0:0:0: Attached scsi generic sg13 type 0
Nov 17 16:24:07 catscrash-desktop kernel: [24432.346618] sd 23:0:0:0: [sdk] Attached SCSI removable disk
Nov 17 16:24:07 catscrash-desktop kernel: [24432.351127] sr3: scsi3-mmc drive: 0x/0x caddy
Nov 17 16:24:07 catscrash-desktop kernel: [24432.351290] sr 23:0:0:1: Attached scsi CD-ROM sr3
Nov 17 16:24:07 catscrash-desktop kernel: [24432.351411] sr 23:0:0:1: Attached scsi generic sg14 type 5
Any idea what might have happened and how to undo that?
try to reinstall stock via SEUS repair option then go back and reinstall CWM and the rom you want.
do you have a link to this "SEUS" for me?
thank you!
@Catscrash honestly i can't find SE PC companion for linux i got the link for windows you can download it and install it then go to support and set to repair the phone without connecting your phone until it request that from you.
http://dl-www.sonyericsson.com/cws/...4/Sony_Ericsson_PC_Companion_2.01.231_Web.exe
try it it will be fixed...
thats alright, i just didn't know the pc companion was what you meant, I'll try that with windows.
I tried the flasher tool already, that found my phone, but told me to activate usb debugger mode... very funny ;-)
I'll try the pc companion, thx for the tip
thank you, it took two attemps, but worked in the end
for nothing glad i helped
Related
Hallo,
I followed the instructions in the original thread, everything works fine since
"UrukDroid 0.7 installation framework" - "Transfer now ..."
The A70H enumerate at USB but no storage device is available:
/var/log/messages:
Mar 14 21:29:25 knut-core2duo kernel: [12387.188024] usb 1-5: new high speed USB device using ehci_hcd and address 15
Mar 14 21:29:25 knut-core2duo kernel: [12387.321667] usb 1-5: New USB device found, idVendor=0e79, idProduct=1422
Mar 14 21:29:25 knut-core2duo kernel: [12387.321672] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 14 21:29:25 knut-core2duo kernel: [12387.321677] usb 1-5: Product: A70H
Mar 14 21:29:25 knut-core2duo kernel: [12387.321680] usb 1-5: Manufacturer: Archos
Mar 14 21:29:25 knut-core2duo kernel: [12387.321684] usb 1-5: SerialNumber: A70-XXXXXX-...
Mar 14 21:29:25 knut-core2duo kernel: [12387.321825] usb 1-5: configuration #1 chosen from 1 choice
Mar 14 21:29:25 knut-core2duo kernel: [12387.323677] scsi18 : SCSI emulation for USB Mass Storage devices
Mar 14 21:29:30 knut-core2duo kernel: [12392.326531] scsi 18:0:0:0: Direct-Access ARCHOS A70H 0000 PQ: 0 ANSI: 2
Mar 14 21:29:30 knut-core2duo kernel: [12392.327613] sd 18:0:0:0: Attached scsi generic sg4 type 0
Mar 14 21:29:30 knut-core2duo kernel: [12392.329761] sd 18:0:0:0: [sdi] Attached SCSI removable disk
What I am doing wrong?
Thanks for any answer.
der.knut
If your Archos is not showing up on your computer so that you can transfer the file, you may want to try installing UrukDroid 0.6 and upgrading to 0.7. I was having the same issue and installing 0.6 and upgrading using the 0.7 upgrade file worked for me. Good luck.
As stated in the Dev Forum, $auron is trying now for weeks to get the help of some A70H 250G owners to fix that issue, but all the people do is ignore this.
So if you want a working version for your device, help the "inventor" of Uruk.
Thanks for fast reply. Will try at weekend when home again.
I have a little experience with Embedded Linux and try to help. Any special questions or hints where to look for problems/solutions?
Thanks again
derknut
Hello,
I installed Uruk Droid 0.6 and update to 0.7.
Thanks a lot for the tip and the Uruk Droid. Great work!
Now I can ssh and its a real linux =;-)
Is there any link for kernel/initramfs creation/source?
fzelle said:
As stated in the Dev Forum, $auron is trying now for weeks to get the help of some A70H 250G owners to fix that issue, but all the people do is ignore this.
So if you want a working version for your device, help the "inventor" of Uruk.
Click to expand...
Click to collapse
Huh, I would have helped but I can't post in that thread since I dont have 10 posts. I had to do what other people were doing and start at 0.6 and upgrade to 0.7
There is a new Easy Install: http://sauron.pourix.com/UrukDroid/UrukDroid-1.0/EI/
You can use this to install UrukDroid 0.7. It works for me!
Dear list,
Since last two days I tried to root my lenevo A60 aka spice Mi-350 in India ( android - 2.3.3 ) without any success and now searching for help. I have first tried with the following
1. A60-tools-v2 in winxp (http://forum.hotmid.com/discussion/...60-install-google-market-and-gmail-account/p1)
2. http://lephone-a60.ominis.net/how-to-root-lephone-a60-and-install-android-market-and-gmail/
with winxp
3. gingerbreak (http://www.addictivetips.com/mobile/how-to-root-android-2-3-gingerbread-using-gingerbreak/)
No luck :-( I have attempted the guides many times to confirm..... seems driver problem.
Now within linux I am trying SuperOneClick (http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537) and during the process I have found actually the adb can't communicate with the phone. If I run "adblinux discover" as root it shows as following
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
And due to this the superoneclick is not progressing.
obviously at phone I have usb debugging on. I have also added the following udev rules found at http://www.idroidproject.org/wiki/ADB
Code:
SUBSYSTEM=="usb" ID_VENDOR_ID=="0bb4", MODE="0666"
SUBSYSTEM=="usb" ID_VENDOR_ID=="18d1", MODE="0666"
SUBSYSTEM=="usb" ID_VENDOR_ID=="05ac", MODE="0666"
but no luck. Could any one kindly show me the way to activate adb so that I can run superoneclick .. Or any other way to root it ....PLEASE
DEBUG within Linux
================
lsusb
Code:
Bus 002 Device 116: ID 2006:0c03
/var/log/messages
Code:
Nov 20 15:38:56 shiva kernel: [320568.881611] usb 2-1.2: new high speed USB device number 117 using ehci_hcd
Nov 20 15:38:56 shiva kernel: [320568.975012] usb 2-1.2: New USB device found, idVendor=2006, idProduct=0c03
Nov 20 15:38:56 shiva kernel: [320568.975019] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 20 15:38:56 shiva kernel: [320568.975025] usb 2-1.2: Product: Mi-350
Nov 20 15:38:56 shiva kernel: [320568.975028] usb 2-1.2: Manufacturer: Spice
Nov 20 15:38:56 shiva kernel: [320568.975032] usb 2-1.2: SerialNumber: 0123456789ABCDEF
Nov 20 15:38:56 shiva kernel: [320568.976814] scsi116 : usb-storage 2-1.2:1.0
Nov 20 15:38:57 shiva kernel: [320569.973037] scsi 116:0:0:0: Direct-Access Spice Mi-350 0100 PQ: 0 ANSI: 2
Nov 20 15:38:57 shiva kernel: [320569.974216] sd 116:0:0:0: Attached scsi generic sg3 type 0
Nov 20 15:38:57 shiva kernel: [320569.977437] sd 116:0:0:0: [sdc] Attached SCSI removable disk
1.Search for unlock root on google.
2.Install it on your PC.
3.Connect your phone to PC while USB debugging is on.
4.Open/run unlock root.
5.It will search the connected device, let it complete.
6.Confirm your phone when the search is complete.
7.Click root and it is done.
Your device is rooted.
Dear list,
I have found the adb can't communicate with my phone (spice Mi-350, actually lenevo-A60)
If I run "adblinux discover" as root it shows as following
` ` `
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
` ` `
obviously at phone I have usb debugging on. I have also added the following udev rules found at idroidproject.org/wiki/ADB
SUBSYSTEM=="usb" ID_VENDOR_ID=="0bb4", MODE="0666"
SUBSYSTEM=="usb" ID_VENDOR_ID=="18d1", MODE="0666"
SUBSYSTEM=="usb" ID_VENDOR_ID=="05ac", MODE="0666"
but no luck. Could anyone kindly show me the way to activate adb so that I can run superoneclick .. Or any other way to root it ....PLEASE
DEBUG within Linux
================
lsusb
``
Bus 002 Device 116: ID 2006:0c03
` `
/var/log/messages
------------------
Nov 20 15:38:56 shiva kernel: [320568.881611] usb 2-1.2: new high speed USB device number 117 using ehci_hcd
Nov 20 15:38:56 shiva kernel: [320568.975012] usb 2-1.2: New USB device found, idVendor=2006, idProduct=0c03
Nov 20 15:38:56 shiva kernel: [320568.975019] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 20 15:38:56 shiva kernel: [320568.975025] usb 2-1.2: Product: Mi-350
Nov 20 15:38:56 shiva kernel: [320568.975028] usb 2-1.2: Manufacturer: Spice
Nov 20 15:38:56 shiva kernel: [320568.975032] usb 2-1.2: SerialNumber: 0123456789ABCDEF
Nov 20 15:38:56 shiva kernel: [320568.976814] scsi116 : usb-storage 2-1.2:1.0
Nov 20 15:38:57 shiva kernel: [320569.973037] scsi 116:0:0:0: Direct-Access Spice Mi-350 0100 PQ: 0 ANSI: 2
Nov 20 15:38:57 shiva kernel: [320569.974216] sd 116:0:0:0: Attached scsi generic sg3 type 0
Nov 20 15:38:57 shiva kernel: [320569.977437] sd 116:0:0:0: [sdc] Attached SCSI removable disk
-- with best wishes
Is there any way whatsoever to put this in msc mode?
I did root it.
The only options for USB are MTP mode and PTP mode. There is no MSC selection.
Trying "/system/bin/setprop persist.sys.usb.config mass_storage,adb" is the closest I can get--it seems to work halfway. It causes the connection message on the tablet to change to "Connected as an installer". On my machine (Mageia Linux 2.0) it seems to partly recognize this as a removable disk:
Code:
Jan 5 02:12:49 localhost kernel: [ 8870.360079] usb 6-6: new high-speed USB device number 21 using ehci_hcd
Jan 5 02:12:49 localhost kernel: [ 8870.511203] usb 6-6: New USB device found, idVendor=16d5, idProduct=8001
Jan 5 02:12:49 localhost kernel: [ 8870.511214] usb 6-6: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jan 5 02:12:49 localhost kernel: [ 8870.511222] usb 6-6: Product: NS-13T001
Jan 5 02:12:49 localhost kernel: [ 8870.511227] usb 6-6: Manufacturer: Matsunichi
Jan 5 02:12:49 localhost kernel: [ 8870.511232] usb 6-6: SerialNumber: 091184990501600A
Jan 5 02:12:49 localhost kernel: [ 8870.518457] scsi13 : usb-storage 6-6:1.0
Jan 5 02:12:49 localhost mtp-probe: checking bus 6, device 21: "/sys/devices/pci0000:00/0000:00:12.2/usb6/6-6"
Jan 5 02:12:49 localhost mtp-probe: bus: 6, device: 21 was not an MTP device
Jan 5 02:12:50 localhost kernel: [ 8871.511967] scsi 13:0:0:0: Direct-Access Android File-CD Gadget 0000 PQ: 0 ANSI: 2
Jan 5 02:12:50 localhost kernel: [ 8871.518940] sd 13:0:0:0: [sdb] Attached SCSI removable disk
Normally, connecting an android device would bring up a screen with a green android image and a "turn on USB storage" box. Once I turn it on, I would get a sdb1 as well as a sdb and I would be able to mount it. However, with this tablet, the "Connected as an installer" message is all I get. I never get a green android image or a "turn on USB storage" box, and it never produces a /dev/sdb1 or anything else that I can actually mount on my PC.
I tried an app "USB Mass Storage Watcher", which supposedly allows MSC mode on devices that have it disabled, but that didn't work either. It said I need the proper kernel, which I guess I don't have.
While we're at it, if anyone else has one of these, how much RAM and storage do you have? Mine apparently has 660M RAM and around under 6G of storage. Both of these numbers are too small to be explainable by the difference between different kinds of megabytes--they should be 1G and 8G.
Device information:
BB Chip: MT6572
MS Board: Mpie
Modem View:. Moly.wr8.w1315.md.wg.mp.v43, 09/17/2014 10:10
Bar code: 10
Build Time: 2015 05 06 15:01:35 CST
Kernel View:. 04/03/67 (root @ zy-190-d) (gcc version 4.7 (GCC)) # 2 SMP PREEMPT Thu May 7 15:33:36 CST 2015
Android View: 4.2.2
SW View:. ALPS.KK1.MP7.V1
Custom Build Verno. : 1430895545
Problem: I edited the file build.prop and something went wrong and got stuck in a loop boot. I did a wipe and then that things got worse since left the unit root. In recovery mode can not access the SD card, the invez to access the SD card the phone accesses the internal memory (no file). The only way I can access it by sideload (adb).
I have to send into the unit back up the build.prop more'm not getting.
When I try permição root in adb (adb root) returns me a "closed". I've tried installing several update.zip more without success. I've been reading about update.zip and saw the need to create for each appliance. (I do not know how to do it)
I ask you to please help me!
I thank you!
up!
Need help!
Edit:
I got a rom for testing.
However I need help.
When I connect the phone, the windows makes sound by connecting, however soon after begins to charge the battery, makes the sound of disconnecting.