i want to unlock my Tablets i do this steps:-
adb devices
adb shell recovery --wipe_data
and device was there.
then
adb reboot bootloader
after that the device restarted and stuck on boot screen showing the tab company name"crony"
fastboot reboot showing "waiting for the device"
now i get stuck on boot screen only and device not listed in
adb devices
fastboot devices
==================================
[email protected]:~$ lsusb
Code:
Bus 003 Device 005: ID 1bcf:2b8a Sunplus Innovation Technology Inc.
Bus 003 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 003: ID 8087:07dc Intel Corp.
Bus 003 Device 006: ID 1f3a:1010
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 006: ID 1f3a:1010
any one can help
Code:
[email protected]:~$ lsusb -D /dev/bus/usb/001/028
Device: ID 1f3a:1010
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x1f3a
idProduct 0x1010
bcdDevice 2.00
iManufacturer 5 Android Bootloader Interface
iProduct 1 USB Developer
iSerial 2 Android Fastboot
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3 20080411
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 3
iInterface 4 Android Fastboot
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0001
Self Powered
[email protected]:~$
A33 Tablet issue
Hello everyone,
I opened this thread becasue of forum rules...
So I have got a Chinese tablet that internal name is C-712 and Usb Vendor is 1F3A:1010.
I tried to install a custom rom and my device isn't open now I have got only a white screen.
At first I can see with adb devices as
adb devices
xxxxx recovery
and I tried the
adb reboot-bootloader command
and rebooted...
After reboot my device don't seem in the device manager as "Android composite ADB Interface" but showing as "USB Developer"
So I tried to search alternative driver of this device in my computer and I found another one now I can see as "Android Bootloader Interface" in Windows 7's device manager.
But this device don't recogize by adb devices nor fastboot devices.
Is there any tool or way to reinstall my original img file into this device.
Best regards
Tr Escape
tr_escape said:
Hello everyone,
I opened this thread becasue of forum rules...
So I have got a Chinese tablet that internal name is C-712 and Usb Vendor is 1F3A:1010.
I tried to install a custom rom and my device isn't open now I have got only a white screen.
At first I can see with adb devices as
adb devices
xxxxx recovery
and I tried the
adb reboot-bootloader command
and rebooted...
After reboot my device don't seem in the device manager as "Android composite ADB Interface" but showing as "USB Developer"
So I tried to search alternative driver of this device in my computer and I found another one now I can see as "Android Bootloader Interface" in Windows 7's device manager.
But this device don't recogize by adb devices nor fastboot devices.
Is there any tool or way to reinstall my original img file into this device.
Best regards
Tr Escape
Click to expand...
Click to collapse
Ok. I solved my self...
So you need PHOENIXCARD V3.09 software and a sdcard.
And follow the instructions for formating of sdcard as production.
You may find in the google
Thanks for reading.
Related
Hi!
I got OTA update to ICS today, and everything went smooth. The phone is working fine. I connect it to iMac, run adb devices, and there is see my device. I'm also using vmware fusion with Ubuntu, where I develop Android apps. Ubuntu does not see this device. Previously, it worked fine. Yes, the device is connected and configured to be available to guest machine.
dmesg and lsusb output follows:
[email protected]:~$ lsusb
Bus 002 Device 005: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ dmesg
[ 3751.650501] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 3763.141707] usb 1-1: new high speed USB device using ehci_hcd and address 46
[ 3778.252927] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 3778.936251] usb 1-1: new high speed USB device using ehci_hcd and address 47
[ 3794.048386] hub 1-0:1.0: unable to enumerate USB device on port 1
Does anybody know what is going on?
Thanks!
Regards,
Miha.
Am I the only one having this problem? Any other Ubuntu users with Galaxy S2 and ICS update?
On the phone. Go to setttings/Wireless and networks/USB utilities/connect storage to PC.
bored_stupid said:
On the phone. Go to setttings/Wireless and networks/USB utilities/connect storage to PC.
Click to expand...
Click to collapse
This disables USB debugging. I did it anyway, but it still does not show up. Unfortunately.
I solved this by editing Ubuntu.vmx file. I added the following lines (I believe the last line makes a difference):
Code:
usb.quirks.device0 = "0x4e8:0x681d skip-reset" # Mass Storage
usb.quirks.device1 = "0x4e8:0x68a9 skip-reset" # Media
usb.quirks.device2 = "0x4e8:0x6877 skip-reset" # Kies
usb.quirks.device3 = "0x4e8:0x6866 skip-reset" # SGS2 ICS
Hey guys,
I have a Lumia 800 with a "messed up" Qualcomm bootloader. Here's what's different about it:
- Power+Vol.UP button combination doesn't work. Every other combination works great (FTM, Hard Reset, etc.).
- Since that combination doesn't work, I can't get to OSBL mode without NSSPro.
- When in OSBL mode, it shows up as Qualcomm CDMA Technologies MSM on Windows, OS X and Ubuntu but doesn't show its NAND partitions.
- In the Device Manager on Windows, the device has a tiny yellow warning sign like it's not working properly or it doesn't have the correct drivers. I tried installing/uninstalling the Qualcomm drivers from the other thread but nothing changed.
Is there any way to "repair"/reset the bootloader or force it to show its partitions ? Obviously I'm very careful with it so it doesn't get replaced with a DLOAD one.
I can put the USB debug logs from any/all of the OS if it might help.
Please help if you have any idea. Thanks.
I have tried all kinds of things on Windows.
I tried forcing the generic USB Mass Storage Device driver but it said it couldn't "start" the device.
I also installed all kinds of Qualcomm drivers I could find. I found the correct one, Qualcomm HS-Diagnostics 9006 (COMx), though unsigned (and still showing the yellow warning sign). Lumia still doesn't show the partitions.
Installed QPST (had weird errors about not being able to register a lot of DLLs while installing) and the Lumia didn't even appear in the devices list. (might be because of the broken install, I don't know)
Any ideas ?
inket said:
I have tried all kinds of things on Windows.
I tried forcing the generic USB Mass Storage Device driver but it said it couldn't "start" the device.
I also installed all kinds of Qualcomm drivers I could find. I found the correct one, Qualcomm HS-Diagnostics 9006 (COMx), though unsigned (and still showing the yellow warning sign). Lumia still doesn't show the partitions.
Installed QPST (had weird errors about not being able to register a lot of DLLs while installing) and the Lumia didn't even appear in the devices list. (might be because of the broken install, I don't know)
Any ideas ?
Click to expand...
Click to collapse
Mine does the same thing... My guess is that it is a intermediate version between full dev qualcomm bootloader and nokia dload that they rushed out.
What's your phone info?
My Lumia's information (weird bootloader):
Firmware: 12070
Hardware revison: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
ROM Language: 0C0A (Spanish (Spain))
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU 238
Mobile Operator: 000-ES
IMEI: 35928904 67xxxxx
Friend's (Nokia DLOAD):
Firmware: 12070
Hardware revison: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
ROM Language: 0809 (English (United Kingdom))
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU NDT EURO1
Mobile Operator: 000-33
IMEI: 35928904 79xxxxx
I have thought to open the phone and remove the battery to see if it helps, but I haven't tried it yet.
At least, I'm not the only one.
Here's mine:
OS: 7.10.8107.79
Firmware: 1600.2489.8107.12072
Hardware revision: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
IMEI: 3592890464xxxxx
Product Code: 059L702
Basic Product Code: 059J2N6
Type Designator: RM-801
Production SN (PSN): 004370FAB (< copied this because it seemed interesting)
That's all I found on WP, NCS and NSSPro. Where did you find the other info ?
I know that mine came from Vodafone Spain and 11414 firmware. Interesting, right ? Both from Spain.
My phone is the Unlocked Spanish country version, came with 11412.
I got the information from the diagnostics app (dial ##634#). I don't know if the diagnostics from 12072 has all this data (it should), I haven't updated mine from 11500.
Where did you get the PSN?
The question is: it is related to the country variant or to the production run?
I found the PSN on both NSSPro and NCS. Look in the Extended Info in NCS, I think.
My Lumia's info from Diagnostics:
ROM Language: 0C0A (doesn't say "(Spanish(Spain))" or anything, just 0C0A)
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU 214
Mobile Operator: VOD-ES
So far the only similarity is that they're both from Spain.
Nothing new, I guess ?
I'm thinking of trying NCS' "Refurbish" or "Recovery".
Anyone care to explain how do they work or what do they do exactly ?
I still don't want to replace the bootloader with Nokia's; I'm looking if there's a way to "refresh" the bootloader or something like that.
just take the battery out and insert after 10 or more second..then press and hold the vol up and insert the usb cable while holding vol up ....usb should be connected to pc from other end...after u inserted usb in phone u feel a short vibration, then leave the vol button and u'll be in qpst mode..
@debbuger
Are you sure that would work ?
I mean, did you have the same problem and you fixed it by removing the battery ?
sorry bro i thought that u've lumia 710.. don't remove battery do as follows --
as u r on l800
force it off by pressing the power switch for about 10 to 15 sec ,
then press and hold vol up and insert the usb ..a short vibratin means u r in osbl mode...
Already tried that. Doesn't work. Thanks anyway.
can u tell me if ur lumia is shipped with qualcom boot or you have flashed it after ...
It shipped that way.
Can you post the USB ID of the phone in bootloader mode? (lsusb -n in Linux, or Details tab in the Windows device manager)
Oh my brothers lumia 710 was given for a repair ang was returned with dload
Sent from my MB865 using xda premium
lsusb:
Bus 001 Device 002: ID 05c6:9006 Qualcomm, Inc.
Ubuntu's lsusb doesn't have the option '-n' so I'll paste the verbose output:
Code:
Bus 001 Device 002: ID 05c6:9006 Qualcomm, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9006
bcdDevice 0.00
iManufacturer 3
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode. Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.
One thing to try is plug in the phone normally into your computer (while in Linux), and turning it on. Post the device IDs that show up in "dmesg" after doing that.
Thanks NetRoller.
.NetRolller 3D said:
Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode.
Click to expand...
Click to collapse
What's QHSUSB_DLOAD mode ? I looked all over the internet and found nothing answering that...
Please note that this mode isn't triggered with the Power+VolUp combination, but by selecting OSBL Mode in NSSPro. I don't know much about this but maybe selecting other modes in NSSPro could be more "useful" ?
.NetRolller 3D said:
Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.
Click to expand...
Click to collapse
I just realized, the "Couldn't open device" is because I ran lsusb as a user (without sudo)... I'll try it again and paste the output.
.NetRolller 3D said:
One thing to try is plug in the phone normally into your computer (while in Linux), and turning it on. Post the device IDs that show up in "dmesg" after doing that.
Click to expand...
Click to collapse
Doesn't seem to have anything important (I added comments):
Code:
[345141.576034] usb 1-6: new high-speed USB device number 3 using ehci_hcd
[345142.410405] generic-usb 0003:045E:041E.0001: hiddev0,hidraw0: USB HID v1.10 Device [Microsoft Windows Phone] on usb-0000:00:1d.7-6/input0
[345142.410441] usbcore: registered new interface driver usbhid
[345142.410445] usbhid: USB HID core driver
# vibration
# screen ON but black, stays like that for 15s
[345157.617055] usb 1-6: USB disconnect, device number 3
# shuts down
# vibration
# boots
[345178.864037] usb 1-6: new high-speed USB device number 4 using ehci_hcd
Does Power+VolUP put it into "mass storage" mode?
Power+VolUp does nothing. Long vibration and it just boots normally. Here's the `sudo lsusb -v` after switching to "OSBL Mode" through NSSPro:
Code:
Bus 001 Device 005: ID 05c6:9006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9006
bcdDevice 0.00
iManufacturer 3 Qualcomm, Incorporated
iProduct 2 Qualcomm CDMA Technologies MSM
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 Qualcomm Configuration
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
1st I'm a noob, so be kind. After getting the 4.0.4 update pushed from Verizon, my Motorola Bionic has disappeared from adb radar. terminal command "adb devices" returns nothing under list of devices attached, when its usb connected. (I've updated my android sdks. to latest platform tools).
I have tried each of the 3 usb settings 4.0.4 offers (Mass Storage, Media Device(MTP) and Camera (PTP), with debugging both on and off. Still no joy. I have killed and started adb server and rebooted both the macbook pro and the bionic. BTW - the original android os it started with had a "Charge Only" mode, which was the usb connection type that adb connection had previously required, but that's gone from this 4.0.4 upgrade for some reason. I have searched numerous forums and threads, but haven't found anything that seems to specifically apply to what i'm encountering. Those forums that did have posts about adb not finding connected device, mostly suggested rebooting and updated sdks. A couple suggested editing some config files, but I couldn't locate those. Any and all suggestions/solutions will be gratefully attempted. Thanks in advance for your analysis.
I'm running osx lion 10.7.5 on a MacBook Pro. I can provide phone system info if necessary. I've copied below the info I've gathered about the usb port the device is connected to from USB Prober.
Using usb prober the device appears as "Composit device: "XT875" in the bus probe. Port Info shows as: 0x1018, not captive, external device, connected, enabled. Device Descriptor shows as: Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x22B8/0x4353 (Motorola MDS)
Device Version Number: 0x0216
Number of Configurations: 1
Manufacturer String: 2 "Motorola"
Product String: 3 "XT875"
Serial Number String: 4 "0A3BAA470C01100C"
Interfaces show as: Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Device Qualifier Descriptor
Descriptor Version Number: 0x0200
Device Class 0 (Composite)
Device Subclass 0
Device Protocol 0
Device MaxPacketSize: 64
Number of Configurations: 1
bReserved: 0
Other Speed Configuration Descriptor
Length (and contents): 69
Number of Interfaces: 2
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 500 ma
Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Same issue
I am trying to root a Bionic running 4.0.4 and it is having the same issue with the ADB driver. Using the same computer and a rooted razr, the ADB drivers show up as soon as it is pluged in. Any help with this matter would be a big help.
Hi, this is my first post, so im not sure how to do this
I have adquired a Vexia Navlet 2 White version, managed to root it everything worked fine but i was fooling around with it (of course ¬_¬) and now im stuck on a bootloop with no adb shell (due to permissions).
It tries too boot but crash, or something, and then it reboot and spit me into the default recovery (Android System Recovery <e3>), before this happened i made a backup with nandroid online backup but ended with a tar stuff
Code:
Files Backed-up:
"
----rwxr-x 1 7519232 May 20 23:01 .android_secure.vfat.tar
----rwxr-x 1 10485760 May 20 22:59 boot.img
----rwxr-x 1 2560 May 20 23:01 cache.yaffs2.tar
----rwxr-x 1 404272640 May 20 23:01 data.yaffs2.tar
----rwxr-x 1 352 May 20 23:06 nandroid.md5
----rwxr-x 1 10485760 May 20 22:59 recovery.img
----rwxr-x 1 667948032 May 20 23:04 sd-ext.vfat.tar
----rwxr-x 1 222075392 May 20 23:00 system.yaffs2.tar
"
Device data:
Code:
ro.build.id=MID
ro.build.display.id=full_m805_892x_evm-userdebug 4.0.3 MID eng.zxp.20121031.161114 test-keys
ro.build.version.incremental=eng.zxp.20121031.161114
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Wed Oct 31 16:13:19 HKT 2012
ro.build.date.utc=1351671199
ro.build.type=userdebug
ro.build.user=zxp
ro.build.host=kf-mid
ro.build.tags=test-keys
ro.product.model=Vexia Tablet 780 GPS
ro.product.brand=Android
ro.product.name=full_m805_892x_evm
ro.product.device=m805_892x
ro.product.board=m805_892x_evm
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=es
ro.product.locale.region=ES
ro.wifi.channels=
ro.board.platform=tcc892x
# ro.build.product is obsolete; use ro.product.device
ro.build.product=m805_892x
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_m805_892x_evm-userdebug 4.0.3 MID eng.zxp.20121031.161114 test-keys
ro.build.fingerprint=Android/full_m805_892x_evm/m805_892x:4.0.3/MID/eng.zxp.20121031.161114:userdebug/test-keys
ro.build.characteristics=tablet,sdcard
and i dont know if i can or how i can flash system and data back with fastboot, this device dont have clockworkmod.
I have tried different things but im totally stuck, as a note using the builder.clockworkmod.com and providing the older recovery and/or recovery.fstab gave my back a non-working CMW, in wich only the sd card can be mounted (even mount usb storage dont work), all the other stuff fail.
I suppose that if i can mange to fix the mountings points for the CWM i can restore system and data, but i dont know how to do it.
I have windows 7 and linux Mint 14, so it dosent matter where to go, i can enter botloader, fasboot mode and adb on recovery.
Pls, help
I attach all files i have available, except the backup (its big) ill add it, or other files, if neccesary.
Thx.
Good Luck
glorer said:
Hi, this is my first post, so im not sure how to do this
I have adquired a Vexia Navlet 2 White version, managed to root it everything worked fine but i was fooling around with it (of course ¬_¬) and now im stuck on a bootloop with no adb shell (due to permissions).
It tries too boot but crash, or something, and then it reboot and spit me into the default recovery (Android System Recovery <e3>), before this happened i made a backup with nandroid online backup but ended with a tar stuff
Code:
Files Backed-up:
"
----rwxr-x 1 7519232 May 20 23:01 .android_secure.vfat.tar
----rwxr-x 1 10485760 May 20 22:59 boot.img
----rwxr-x 1 2560 May 20 23:01 cache.yaffs2.tar
----rwxr-x 1 404272640 May 20 23:01 data.yaffs2.tar
----rwxr-x 1 352 May 20 23:06 nandroid.md5
----rwxr-x 1 10485760 May 20 22:59 recovery.img
----rwxr-x 1 667948032 May 20 23:04 sd-ext.vfat.tar
----rwxr-x 1 222075392 May 20 23:00 system.yaffs2.tar
"
and i dont know if i can or how i can flash system and data back with fastboot, this device dont have clockworkmod.
I have tried different things but im totally stuck, as a note using the builder.clockworkmod.com and providing the older recovery and/or recovery.fstab gave my back a non-working CMW, in wich only the sd card can be mounted (even mount usb storage dont work), all the other stuff fail.
I suppose that if i can mange to fix the mountings points for the CWM i can restore system and data, but i dont know how to do it.
I have windows 7 and linux Mint 14, so it dosent matter where to go, i can enter botloader, fasboot mode and adb on recovery.
Pls, help
I attach all files i have available, except the backup (its big) ill add it, or other files, if neccesary.
Thx.
Click to expand...
Click to collapse
A common problem when using adb to access your Android phone via USB is:
$ adb devices
List of devices attached
???????????? no permissions
According to official Android Developers website:
If you’re developing on Ubuntu Linux, you need to add a rules file that contains a USB configuration for each type of device you want to use for development. Each device manufacturer uses a different vendor ID. The example rules files below show how to add an entry for a single vendor ID (the HTC vendor ID). In order to support more devices, you will need additional lines of the same format that provide a different value for the SYSFS{idVendor} property.
Quick fix:
sudo -s
adb kill-server
adb start-server
adb devices
Permanent fix:
$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Hama Optical Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 18ea:0004 Matrox Graphics, Inc. TripleHead2Go [Digital Edition]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 010: ID 0bb4:0c87 High Tech Computer Corp. <<<<<<<< my HTC phone
Bus 001 Device 008: ID 046d:0817 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note 0bb4 is the vendor ID. Next, create /etc/udev/rules.d/51-android.rules with the following lines:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Final steps:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo udevadm control --reload-rules
Done.
A list of popular vendor IDs:
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
ref. Android Developers
ken.okech.94 said:
A common problem when using adb to access your Android phone via USB is:
$ adb devices
List of devices attached
???????????? no permissions
According to official Android Developers website:
If you’re developing on Ubuntu Linux, you need to add a rules file that contains a USB configuration for each type of device you want to use for development. Each device manufacturer uses a different vendor ID. The example rules files below show how to add an entry for a single vendor ID (the HTC vendor ID). In order to support more devices, you will need additional lines of the same format that provide a different value for the SYSFS{idVendor} property.
Quick fix:
sudo -s
adb kill-server
adb start-server
adb devices
Permanent fix:
$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Hama Optical Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 18ea:0004 Matrox Graphics, Inc. TripleHead2Go [Digital Edition]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 010: ID 0bb4:0c87 High Tech Computer Corp. <<<<<<<< my HTC phone
Bus 001 Device 008: ID 046d:0817 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note 0bb4 is the vendor ID. Next, create /etc/udev/rules.d/51-android.rules with the following lines:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Final steps:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo udevadm control --reload-rules
Done.
A list of popular vendor IDs:
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
ref. Android Developers
Click to expand...
Click to collapse
no no i have connectivity
adb during bootloop process
Code:
List of devices attached
20120122800F32 device
adb when tablet is on recovery mode
Code:
List of devices attached
20120122800F32 recovery
fasboot on bootloader mode
Code:
???????????? fastboot
i can flash stuff and all, but "adb shell" return this on device mode
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
and this on recovery mode
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and i dont know what to do ><
Is there no way to turn the system.yasff2.tar into system.img, so that i can try to do a flashboot system system.img ?¿
truth to be told i will rather make CWM work
PD
forgot mention i dont know that much about linux, thought im more that willing to learn ^^, i wouldn't been using mint if that wasn't the case
glorer said:
no no i have connectivity
adb during bootloop process
Code:
List of devices attached
20120122800F32 device
adb when tablet is on recovery mode
Code:
List of devices attached
20120122800F32 recovery
fasboot on bootloader mode
Code:
???????????? fastboot
i can flash stuff and all, but "adb shell" return this on device mode
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
and this on recovery mode
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and i dont know what to do ><
Is there no way to turn the system.yasff2.tar into system.img, so that i can try to do a flashboot system system.img ?¿
truth to be told i will rather make CWM work
PD
forgot mention i dont know that much about linux, thought im more that willing to learn ^^, i wouldn't been using mint if that wasn't the case
Click to expand...
Click to collapse
try to flash goclever gps firmware
Hi
I have installed Arch Linux but cannot find suitable material on setting up drivers and utilities for flashing rom on Linux specifically arch linux.
I can setup arch even if instructions are available for other distro Linux Mint and Ubuntu so any link can come in handy.
I was using flashtool in windows but after shifting to Arch, I am not sure whats the right procedure to do it.
I have unlocked bootloader and rooted rom (FXP kernel + MIUI) installed as of now which I want to change asap.
Please help.
Regards
Hello,
You don't need any drivers,just install android-udev and android-sdk-platform-tools for adb and fastboot (both from aur).
Download latest flastool and run it from the terminal just like you do in windows (it requires jre and libusbx from official repos ).
Ok I have reinstalled fatsboot, android-sdk-platform-tools and openjre
Now I still cannot use fastboot devices , its list nothing.
Also since I should have adb available (from sdk-platform) when I run adb it says no command ?
Code:
[[email protected] fastboot]$ fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo adb
sudo: adb: command not found
[[email protected] fastboot]$ adb
bash: adb: command not found
I have also installed udev-android , previous I created 51-android.rules manually but still doesnt work.
fastboot won't list the devices nor it works.
Code:
[sha[email protected] fastboot]$ lsusb
Bus 002 Device 005: ID 413c:2107 Dell Computer Corp.
Bus 002 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0fce:5146 Sony Ericsson Mobile Communications AB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
First of all make sure you have enabled usb debugging on your phone.Adb and fastboot should be under /opt/android-sdk/platform-tools/ and also 51-android.rules file in /usr/lib/udev/rules.d/ (with -rw-r--r-- permissions).
With these things i have everything in my sytem to flash roms etc,maybe you're missing something with your installation.
Also for more information check wiki from archlinux wiki.archlinux.org/index.php/android