Database Users

Unable to Haz Root (log attached)

I got a new x10 from Best Buy Mobile as a loaner phone, running 1.6 on AT&T fresh out of the box. followed the ATT thread to go to 2.1 using flash tool.
I have tried nearly everything to root it, flash tool tells me phone should be rooted after reboot, it isnt, X10root.apk fails, superoneclick fails (maybe adb related & not sure why.. had adb path set up properly and shows device id, but says protocol error?), z4root doesnt even get temp root.
Im on generic 2.1 x10a , this wall all done on my win 7 64 bit laptop. I will try via adb on my computer at work running win xp later today, but the root .apks should have rooted, I dont understand why.
I will post a log for you guys to check out, Im not a n00b, but not an expert either.
I may have the phone for a week or a month, while my other LCD is repaired.
Thanks everyone!
Go for root !
Version: Universal Androot - v1.6.2 beta 5
Detected OS version:7
ls -l /system/etc
-rw-r--r-- root root 461 2011-01-07 06:11 pvextensions.cfg
-rw-r--r-- root root 418 2011-01-07 06:11 iddd.conf
-rw-r--r-- root root 684 2011-01-07 06:11 wiperconfig.xml
-rw-r--r-- root root 1853914 2010-12-15 20:46 dop.iso
drwxr-xr-x root root 2011-01-26 05:16 wifi
-rw-r--r-- root root 1358 2011-01-07 06:11 hw_config.sh
drwxr-xr-x root root 2011-01-26 05:16 firmware
-rw-r--r-- root root 2046 2011-01-07 06:11 bookmarks.xml
drwxr-xr-x root root 2011-01-26 05:16 ppp
-rw-r--r-- root root 8319 2011-01-07 06:11 event-log-tags
-r-xr-x--- root shell 1176 2011-01-07 06:11 init.goldfish.sh
-rw-r--r-- root root 85623 2011-01-07 06:11 NOTICE.html.gz
-rw-r--r-- root root 438 2010-10-08 04:40 apns-conf.xml
-rw-r--r-- root root 8858 2010-11-30 20:14 default-capability.xml
drwxr-xr-x root root 2011-01-26 05:16 semc
-rw-r--r-- root root 197 2011-01-07 06:11 pvasfstreaming.cfg
drwxr-xr-x root root 2011-01-26 05:16 dhcpcd
-rw-r--r-- root root 3396 2011-01-07 06:11 init.es209ra.bt.sh
-rw-r--r-- root root 2 2011-01-07 06:11 DualMicControl.txt
-rw-r--r-- root root 177 2011-01-07 06:11 pvasflocal.cfg
drwxr-xr-x root root 2011-01-26 05:16 security
-r--r----- bluetooth bluetooth 935 2011-01-07 06:11 dbus.conf
drwxr-xr-x root root 2011-01-26 05:16 customization
drwxr-xr-x root root 2011-01-26 05:16 permissions
-rw-r--r-- root root 935 2011-01-07 06:11 gps.conf
-rw-r--r-- root root 458 2011-01-07 06:11 pvplayer.cfg
drwxr-xr-x root root 2011-01-26 05:16 bluez
-rw-r--r-- root root 85 2011-01-07 06:11 01_qcomm_omx.cfg
-rw-r--r-- root root 1462 2011-01-07 06:11 vold.conf
-rw-r--r-- root root 285 2011-01-07 06:11 sensors.conf
-rw-r--r-- root root 25 2011-01-07 06:11 hosts
-rw-r--r-- root root 1804 2011-01-07 06:11 loc_parameter.ini
ls -l /system/bin/reboot
lrwxr-xr-x root shell 2011-01-26 05:17 reboot -> toolbox
cat /proc/sys/kernel/osrelease
2.6.29
getprop ro.product.model
X10a
getprop ro.product.brand
SEMC
getprop ro.product.name
X10a_1234-4820
getprop ro.product.manufacturer
Sony Ericsson
getprop ro.build.product
X10a
ls -l /sqlite_stmt_journals
-rw------- app_96 app_96 1 2011-05-02 08:41 persist.service.adb.enable
-rw------- app_96 app_96 158741 2011-05-02 08:41 Superuser.apk
-rw------- app_96 app_96 26256 2011-05-02 08:41 su
-rw------- app_96 app_96 1001388 2011-05-02 08:41 busybox
-rwxr-xr-x app_96 app_96 19114 2011-05-02 08:40 exploid
lrwxrwxrwx app_96 app_96 2011-05-01 23:35 data -> /proc/sys/kernel/hotplug
-rw-r--r-- app_96 app_96 29 2011-05-02 08:41 hotplug
-rw-rw-rw- app_96 app_96 0 2011-05-02 08:41 loading
-rw------- app_96 app_96 164788 2011-05-01 23:30 com.noshufou.android.su.apk
ls -l /data/local/tmp
opendir failed, Permission denied
ls -l /app-cache
/app-cache: No such file or directory
run mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,group_id=0,allow_other 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
run df
/dev: 143500K total, 12K used, 143488K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 1388K used, 2708K available (block size 4096)
/system: 361088K total, 248980K used, 112108K available (block size 4096)
/data: 476160K total, 96052K used, 380108K available (block size 4096)
/cache: 113920K total, 3316K used, 110604K available (block size 4096)
/sdcard: 1913216K total, 368864K used, 1544352K available (block size 16384)
/data/DxDrm/fuse: Permission denied
Preparing Exploit ... :true
Preparing busybox binary ... :true
User selected: Eclair
Preparing Su binary ... :true
Preparing Superuser apk ... :true, resid:2131034118
Preparing root toolkit script ... :true
Trying to get mount point:/data
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
Trying to get mount point:/system
/dev/block/mtdblock2 /system yaffs2 ro 0 0
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mkdir /system/xbin
cat su > /system/xbin/su
chmod 04755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw,nosuid,nodev -t yaffs2 /dev/block/mtdblock3 /data
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
rm /system/bin/su
rm /system/xbin/su
Preparing to execute exploit, do chmod
Executing exploit..
cmd: /data/data/com.corner23.android.universalandroot/files/getroot /dev/block/mtdblock3 yaffs2
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by shakalaca for various devices
[+] Using basedir=/sqlite_stmt_journals, path=/data/data/com.corner23.android.universalandroot/files/getroot
[+] opening NETLINK_KOBJECT_UEVENT socket
[-] creat: Permission denied
Wifi enabled ...
/sqlite_stmt_journals/rootshell missing ..
/app-cache/rootshell missing ..
/data/local/tmp/rootshell missing ..
Install/Uninstall rootkit: false
ls -l /sqlite_stmt_journals
-rw------- app_96 app_96 1 2011-05-02 08:41 persist.service.adb.enable
-rw------- app_96 app_96 158741 2011-05-02 08:41 Superuser.apk
-rw------- app_96 app_96 26256 2011-05-02 08:41 su
-rw------- app_96 app_96 1001388 2011-05-02 08:41 busybox
-rwxr-xr-x app_96 app_96 19114 2011-05-02 08:40 exploid
lrwxrwxrwx app_96 app_96 2011-05-01 23:35 data -> /proc/sys/kernel/hotplug
-rw-r--r-- app_96 app_96 29 2011-05-02 08:41 hotplug
-rw-rw-rw- app_96 app_96 0 2011-05-02 08:41 loading
-rw------- app_96 app_96 164788 2011-05-01 23:30 com.noshufou.android.su.apk
ls -l /data/local/tmp
opendir failed, Permission denied
ls -l /app-cache
/app-cache: No such file or directory
run mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,group_id=0,allow_other 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
run df
/dev: 143500K total, 12K used, 143488K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 1388K used, 2708K available (block size 4096)
/system: 361088K total, 248980K used, 112108K available (block size 4096)
/data: 476160K total, 96044K used, 380116K available (block size 4096)
/cache: 113920K total, 3316K used, 110604K available (block size 4096)
/sdcard: 1913216K total, 368864K used, 1544352K available (block size 16384)
/data/DxDrm/fuse: Permission denied

I just want to flash a gingerbread ROM of course, but I will need xrecovery right? which isnt installing without root.
Unless its possible for me to flash a new rooted rom without xrecovery, I uppose that will work although it might be dangerous.
I'll post back as soon as I can.

use the latest version of superoneclick and make sure you have USB debugging enabled
if you have rooted with flash tool you do not need to do anything else it will be rooted you dont need x10root or other one click apk apps as flash tool rooted your phone
test it with a tool that requires root such as adfree or terminal emulator

flash tool says success with root, but its not rooted, as i cant install busybox, says not rooted and entering su in terminal says permission denied
please help!

chrisrotolo said:
flash tool says success with root, but its not rooted, as i cant install busybox, says not rooted and entering su in terminal says permission denied
please help!
Click to expand...
Click to collapse
try using SuperOneClick here
failing that use SuperOneClickv1.5.5 here

i already tried the newest SOC, no dice.
ill try the older one too.
I think it may have to do with the drivers, it looks like regular drivers dont work, Im installing the SE developer ones.
but that doesnt really explain why z4root didnt work, and universal androot fails too.
thanks guys. this is killing me.

chrisrotolo said:
i already tried the newest SOC, no dice.
ill try the older one too.
I think it may have to do with the drivers, it looks like regular drivers dont work, Im installing the SE developer ones.
but that doesnt really explain why z4root didnt work, and universal androot fails too.
thanks guys. this is killing me.
Click to expand...
Click to collapse
what firmware are you using on your phone(under about phone) !?
and try the 1.5.5 version make sure when you run it you have USB debugging enabled! (under settings /applications/development ) you may also want to make sure you have UNKNOWN SOURCES checked!
z4 and universal will no longer work after the first version of 2.1! so dont bother with those!
you could also try the root tool that comes with the lastest flashtool
make sure when you root you choose 'connect phone' and not mount for usb storage mode!

2.1-update 1
build 2.1.a.0.435
2.6.29 [email protected] #1
x10a
this is beginning to p1ss me off, I think it must be a driver/adb issue, i did the fix for 64 bit, and now Im on xp and still cant connect to daemon when i say adb devices in cmd. I have the latests drivers, maybe i need to install older ones, maybe these have security?
also what are the signfiles.bat ,etc on my sdcard, they look SE signing tools , like they verify signature, etc.
also tried downloading the new rooting method for 2.1, rootme.tar, but server is unavailable.
yahhhhh! this is nuts!

adb kill-server and start-server work, so I know my adb is ok, I have android sdk installed. path>adb devices **daemon still not runningerror: cannot connect to daemon, so it has to be the phone or the drivers Im guessing. arrghhh!

i have tried different usb ports, still nothing!

Best way to root, install Xrecovery and JIT enable your phone is via Flash Tool. I'm on AT&T too, and found it rather simple.
Follow the guide found here:
http://forum.xda-developers.com/showthread.php?t=1012380
Make sure you have installed java on your computer.
Also, do not mount your SD card. While your phone is on, connect your phone via usb and hit root once your phone is recognized.
I'm not sure if this is necessary for rooting but for flashing purposes you need to connect your phone via pc companion or SEUS. Check to see if you have the latest firmware and set your phone up to flash new firmware. The computer will install flash drivers onto your computer. You don't have to install the latest AT&T firmware if there is one. You just want to have those flash drivers on your PC.
Hope this helps!

ok, so i was trying to follow the AT&T giude from 1.6 -2.1, which says update then root, should I go back to 1.6 and try universalandroot or z4root, root first, then update? or will I lose root when I update? Thanks guys.
installed PC companion update my driver, but still no adb devices cannot connect to daemon, and SOC 1.5.5 failed
I installed SEUS on my other PC too, didnt seem to change much, drivers were the same.
this is crazy, what should i do guys? use pc companion to repair? go back to 1.6 and try rooting then update??

Just use flash tool and press root if you just want to root. You don't have to sideload any apps which is blocked by AT&T anyways.
Update to 2.1 in order to install xrecovery. Once done updating, root it afterwards by pressing the root button on flash tool. No need to go back to 1.6 just to root. Just follow the guide and then you can install any rom you want. The Agent got your back.

Ok, so I re-read your thread. Let me summarize what I know.
1. Flash tool says you have root after your phone rebooted
2. You can not install busybox via flash tool
It might be that your phone is already rooted. If you tried to install busybox or xrecovery through flash tool and have seen that the advanced options are greyed out, it is because you need to press "ask root permissions" and then accept on your phone.
Also check to see if superuser is working correctly, Install Titanium backup to check. Install it from the marketplace open it up. A box should pop up saying "Allow Root Access"?
If so, then you have done it correctly.
I'm not keen with all the coding so I don't know how to read those logs you have noted.
Try pressing root again on flash tool and let it reboot, let me know what you see afterwards.

TYhanks for the help , I appreciate it guys.
im at my home laptop with win7 64 bit and adb devices shows serial number connected. adb push gives me cannot connect to daemon error, and super one click fails. I have busybox and superuser .apks installed from astro but both not "fully" installed without root. I know how to check for root, and I do not have it even when flashtool tells me I should. Really strange. what is going on??
ok, didnt want to do it, but im going to try the old way, with the 3 .bat files, is this a good idea? wish me luck! (if i can find clearer instructions)
cant go to sony ericsson unlock bootlloader online with IMEI, becuase its a loaner and says invalid IMEI... *double facepalm*!

I had those same issues with my 64bit windows 7 too. I think it has to do with Java and how adb tools works better with 32 bit. Troubleshooting your computer and phone might be the way to go.
Make sure on your phone you have usb debugging clicked via Settings>applications>Development. Also, just for the hell of it, click unknown sources.
Make sure on your computer, UAC/User Access Controls is turned off. If you recently installed java, reboot your computer.
After reboot, restart cmd and get into your adb folder. Type adb devices. Should show if you have your phone connected/computer recognizes your phone.

chrisrotolo said:
TYhanks for the help , I appreciate it guys.
im at my home laptop with win7 64 bit and adb devices shows serial number connected. adb push gives me cannot connect to daemon error, and super one click fails. I have busybox and superuser .apks installed from astro but both not "fully" installed without root. I know how to check for root, and I do not have it even when flashtool tells me I should. Really strange. what is going on??
ok, didnt want to do it, but im going to try the old way, with the 3 .bat files, is this a good idea? wish me luck!
Click to expand...
Click to collapse
Start over with new download of Flash Tool and 2.1.A.0.435 ftf firmware.

this is terrible!
will try to reflash the 2.1 update again.
relashed fine, without rebooting, ran Root option from flashtool, says should be rooted after reboot, havent rebooted yet, but definetly no root.
F%ck! after flash tool finishes and reboot still zilch! I dont think flashtool is installing superuser, here's a log, man this is awful!
02/022/2011 20:22:40 - INFO - <- This level is successfully initialized
02/022/2011 20:22:54 - ERROR - Cannot identify your device. Found while expecting X10, E10, U20 or E15 (read from ro.product.model from build.prop)
02/022/2011 20:22:54 - INFO - Selecting from user input
02/023/2011 20:23:17 - INFO - Connected device : X10
02/023/2011 20:23:23 - INFO - Installed version of busybox : * daemon not running. starting it now on port 5037 *
02/023/2011 20:23:29 - INFO - Pushing .\custom\root\busyboxX10 to /data/local/tmp/busybox
02/023/2011 20:23:40 - INFO - Running busyhelper
02/023/2011 20:23:45 - INFO - Pushing .\custom\root\givmeroot.tar to /data/local/tmp/
02/023/2011 20:23:51 - INFO - Running part1 of Root Exploit, please wait
02/023/2011 20:23:55 - INFO - Running rootit
02/024/2011 20:24:07 - INFO - Running part2 of Root Exploit
02/024/2011 20:24:08 - INFO - Running rootit2
02/024/2011 20:24:10 - INFO - Finished!.
02/024/2011 20:24:10 - INFO - Root should be available after reboot!
02/025/2011 20:25:06 - ERROR - Cannot identify your device. Found while expecting X10, E10, U20 or E15 (read from ro.product.model from build.prop)
02/025/2011 20:25:06 - INFO - Selecting from user input
02/025/2011 20:25:10 - INFO - Connected device : X10
02/025/2011 20:25:10 - INFO - Installed version of busybox : /system/bin/busybox: not found
strange.. now i cant seem to get adb devices, with the latest drivers, to show anything.. cant connect to daemon... give me a break.

24 hour bump! hopeless

Hate to say it, but it sounds like a isolated issue. Thousands of people used the flash tool and superoneclick successfully. Are you sure you selected the next tab, "root permissions" after root? You need to do that to install SuperUser and Busybox.
Also, antivirus should be disabled.

[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush

A few days ago Koush published his new CWM recovery v.5.5.0.4 for TF101.
Many (most?) of those who flashed it are experiencing trouble booting normally:
the device goes straight into CWM recovery unless you cold-boot by holding the Vol(-) key at boot time.
This thread is meant to support those who are in this situation.
Also, this thread is to warn others not to flash CWM 5.5.0.4 for the time being.
Also, also, this thread is to gather information that will help devs to fix our problem.
Note:
The previous thread found here got locked (I was told) because of FUD and general lack of clarity.
Please keep it clean and flame-free.
If you are new to Android and TF101, please refer to good guides such as this one:
http://forum.xda-developers.com/showthread.php?t=1494230
You can save yourself from much trouble by educating yourself a little.
UPDATE:
If you have 5.5.0.4 installed and have not used any apps for booting into recovery you likely don't have the problem described above.
We now have two reports of being able to successfully flash an alternate recovery and escape 5.5.0.4
See posts #3 and #67.
UPDATE2:
See post #3 for continuing contributions from @gee one (thanks!):
http://forum.xda-developers.com/showpost.php?p=23257966&postcount=3
UPDATE3:
There is some progress. More testing to be done ...
Money post: http://forum.xda-developers.com/showpost.php?p=23301594&postcount=105
UPDATE4:
We have a solution courtesy of @gee one and @leetlikeawping and the fearless tester @trtk.
This solution does NOT involve NVFlash or has anything to do with the boodloader, so it should apply to all SBK versions (and SN's).
There are comments from people with B70 and B80 (as well as below) reporting success.
The repair can be done in several ways. I have tested the scenario of when you cannot cold-boot into the system, but have a correctly set-up adb access.
while booted into CWM 5.5.0.4 ...
step 1: use adb to push a good recovery [I used Rogue XM v1.3.0 (CWM-based v5.0.2.7)]***
step 2: flash the zip
step 3: use the adb shell to execute the following command
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
*** Do not flash stock recovery. There is no good reason to do it (stock recoveries are generally pretty useless) and you are flirting with trouble if there are signature checks that your custom components might fail. Use trusted custom recoveries
Click to expand...
Click to collapse
(If you entered the shell, don't forget to exit at the end.)
Now you should "Reboot system".
When rebooting, you will notice the ASUS splash screen with a blue progress line. This indicates that the /staging partition got picked up and is being processed (i.e. your payload is being flashed to the recovery partition).
When you next boot into recovery, you should NOT see the 5.5.0.4 screen.
Continue by flashing your ROM if you need to.
Word of the day: teamwork. Peace!
UPDATE 5: Roach2010 published a fixed version of CWM v5.5.0.4
You may find it here. You still need to clear the boot-recovery flag by following the procedure described above or using the command line, as explained by Roach2010 here.

My personal observations so far are that, after flashing Koush's CWM 5.5.0.4, I cannot replace it with any other CWM's I've tried (roach, solarnz, using the RecoveryInstaller app).
The available recovery blobs get written to the staging partition (mmvblk0p4) but appear to not be touched on boot.
I have the 9.2.1.11 bootloader on B70 with SBK v.2

I flashed both ways and got stuck not being able to flash using the staging partition, which is the typical way to reflash recovery. So if you flash this, there is no way to unflash it. I think it also uses a different sdcard mount, so it makes it a little tougher to get a fresh zip to flash onto there.
When it's working normally, cwm will flash to the staging partition on reboot. When it's recovery bootlooping, the flash to staging will be skipped, which makes it difficult to flash a new recovery. I looked at the init.rc files and noted that the cwm 5.5.04 version doesn't even touch the staging partition, so it will be ignored completely.
I did have success reflashing a full rom- EBT, LNX, SOS, and APP or bootloader, boot.img, recovery, and system. This might work for others too, although I never had a problem of always booting into recovery. If it boots into recovery after flashing a full rom, then it might not work since we'll be stuck with the same init.rc.
I don't know all the inner workings of what happens at the boot process, so does anyone have any ideas about what is causing this.
Some things I found out:
to mount the internal sdcard so that you can push a new rom- use adb shell
mount /dev/block/mmcblk0p7 /data/
ls /sdcard/
exit
then from your pc, type:
adb push /path/to/your/rom.zip /data/media
There are other ways too- I think cwm will mount data when you try to flash a zip from the sdcard.
Here's the init.rc's
part of 92111 stock recovery init.rc
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mkdir /btmac
mount /tmp /tmp tmpfs
mount ext4 /dev/block/mmcblk0p1 /system wait
# mount ext4 /dev/block/mmcblk0p1 /system ro remount
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache
mount ext3 /dev/block/mmcblk0p4 /staging wait nosuid nodev
chown system staging /staging
chmod 0770 /staging
mount ext4 /dev/block/mmcblk0p7 /data wait nosuid nodev
chown system system /data
chmod 0771 /data
part of cwm init.rc
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache
---------- Post added at 01:53 PM ---------- Previous post was at 01:18 PM ----------
Does mounting and clearing/formatting cache do anything for anyone stuck in the recovery loop?
I thought this issue popped up before too- are we reinventing fire?

feisty_noodle said:
I have the 9.2.1.11 bootloader on B70 with SBK v.2
Click to expand...
Click to collapse
Same specs here, installed ROM Manager via market, purchased premium ROM Manager, installed recovery via ROM Manager.
I have attempted to restore to previous ROM using recovery and it restores system but fails data.
I have attempted the restore to stock and unrooted using the methods listed in XDA, and because it will not allow a reboot after flashing the factory unrooted firmware it does not work. I had actually seen mention of a soft brick if unable to reboot and thought that is what had happened. After flashing the factory unrooted firmware I was unable to cold boot.
Sent from my Transformer TF101 using xda premium

sandiegopaneraiguy said:
Same specs here, installed ROM Manager via market, purchased premium ROM Manager, installed recovery via ROM Manager.
I have attempted to restore to previous ROM using recovery and it restores system but fails data.
I have attempted the restore to stock and unrooted using the methods listed in XDA, and because it will not allow a reboot after flashing the factory unrooted firmware it does not work. I had actually seen mention of a soft brick if unable to reboot and thought that is what had happened. After flashing the factory unrooted firmware I was unable to cold boot.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I used the free version and I don't get the bootloops. Can you check something for me- in /sdcard/clockworkmod/download/ there will be a file there maybe something like -210115432
look around and see if you can find something like this:
Code:
{
"name": "Asus Transformer",
"flash_recovery": "dd if=%s of=/dev/block/mmcblk0p4 ;",
"version": "5.5.0.4",
"init": "init.ventana.rc",
"key": "tf101",
"lunch": "cm_tf101-userdebug"
}
These seem to be the parameters that cwm uses to flash the recovery. See if they are any different.

Add me to the forced recovery boot list, but I have a twist to add. I flashed via Rom Manager and I'm running Revolver 4.0 beta 1.2.
Reboot #1 after flashing the new CWM 5.5.0.4 went as usual - no forced recovery
Reboot #2 also worked fine
Reboot #3 - I forced a shutdown, then rebooted fine
Reboot #4 - this time I forced a reboot into recovery, and now I'm stuck in the recovery loop unless I hold down the volume button.
So...until I booted INTO recovery, everything was working fine.

pooh-bah said:
Add me to the forced recovery boot list, but I have a twist to add. I flashed via Rom Manager and I'm running Revolver 4.0 beta 1.2.
Reboot #1 after flashing the new CWM 5.5.0.4 went as usual - no forced recovery
Reboot #2 also worked fine
Reboot #3 - I forced a shutdown, then rebooted fine
Reboot #4 - this time I forced a reboot into recovery, and now I'm stuck in the recovery loop unless I hold down the volume button.
So...until I booted INTO recovery, everything was working fine.
Click to expand...
Click to collapse
are there any recovery commands in your /cache or /cache/recovery folders?

gee one said:
are there any recovery commands in your /cache or /cache/recovery folders?
Click to expand...
Click to collapse
/cache is empty
/cache/recovery has one file, "last_log" - this appears to be a log of when I first entered the recovery about 30 min ago.
Regarding your question about /sdcard/clockworkmod/download/ - I see the same as you posted above.

I got the same thing as Poo-Bah.
Everything was fine until I booted into recovery, now that's all I can boot into unless I cold boot into android.
I'm on bootloader 9.2.1.11 on a B90.
I was wondering if there are any files that tell the system what to boot into and if those are something we can edit. Sorry, I don't have a lot of experience with android, but I'm willing to help as much as I can.

Here is what is in my cache file...
Starting recovery on Sun Mar 4 19:12:16 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /staging ext3 /dev/block/mmcblk0p4 (null) 0
4 /data ext4 /dev/block/mmcblk0p7 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IML74K
ro.build.display.id=IML74K
ro.build.version.incremental=eng.koush.20120226.195010
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Sun Feb 26 19:50:53 PST 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Transformer
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=tf101
ro.product.board=ventana
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=tf101
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.2.1.11-20120221 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.2.1.11-20120221:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=tf101
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-tf101-KANG
ro.modversion=9.0.0-RC0-tf101-KANG
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=0388924343df52d7
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=unknown
ro.hardware=ventana
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=stopping
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Sent from my Transformer TF101 using xda premium
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
gee one said:
I used the free version and I don't get the bootloops. Can you check something for me- in /sdcard/clockworkmod/download/ there will be a file there maybe something like -210115432
look around and see if you can find something like this:
Code:
{
"name": "Asus Transformer",
"flash_recovery": "dd if=%s of=/dev/block/mmcblk0p4 ;",
"version": "5.5.0.4",
"init": "init.ventana.rc",
"key": "tf101",
"lunch": "cm_tf101-userdebug"
}
These seem to be the parameters that cwm uses to flash the recovery. See if they are any different.
Click to expand...
Click to collapse
I have seven files in that folder, none of which match the one you mention.
I opened each of them with the text viewer and found nothing like what you are seeing. I posted the contents of my recovery log above.

OK- I have recovery bootloops now. Does any one have them and isn't running on Revolver4? I did not get them with stock or team eos, but those roms don't have a reboot to recovery that works, as far as I could tell. I had to flash to Revolver4 to get them.

gee one said:
OK- I have recovery bootloops now. Does any one have them and isn't running on Revolver4? I did not get them with stock or team eos, but those roms don't have a reboot to recovery that works, as far as I could tell. I had to flash to Revolver4 to get them.
Click to expand...
Click to collapse
I'm running stock rooted.

AlcoholicDoc said:
I'm running stock rooted.
Click to expand...
Click to collapse
Do you have any mods that allow you to reboot into recovery from the power menu?

gee one said:
Do you have any mods that allow you to reboot into recovery from the power menu?
Click to expand...
Click to collapse
Nothing. With the exception of being rooted and having CWM installed, I'm bone-stock.

Thanks, that helps. I had a stock-ish rom and I couldn't get the recovery bootloops. Very curious.

Anyone think NVFlash CWM will work? I have a B50 model that can take NVFlash, I just don't know the exact steps of getting it done. I downloaded the NVFlash CWM. Do I just throw that into the nvflash folder and go from there?

kxs783kms said:
Anyone think NVFlash CWM will work? I have a B50 model that can take NVFlash, I just don't know the exact steps of getting it done. I downloaded the NVFlash CWM. Do I just throw that into the nvflash folder and go from there?
Click to expand...
Click to collapse
NVFlash should be able to fix this issue. Use one of the tutorials to unbrick to stock with NVFlash. Then re-root. You'll be fine
I wish I had a B50, I'd be done with this crap already.

The good news is that there is just the recovery.img nvflash, so I don't have start from stratch with my rom. The bad news is that the link to download the NVFlash folder keeps telling me to check back later. :/

kxs783kms said:
The good news is that there is just the recovery.img nvflash, so I don't have start from stratch with my rom. The bad news is that the link to download the NVFlash folder keeps telling me to check back later. :/
Click to expand...
Click to collapse
I'm in the same predicament and want to try the same thing as you. Could you provide a link to the Recovery only NVFlash thread please? I've tried to search but cannot find the one you are talking about.

Can anyone link me to another NVFlash download for the Transformer, other than the one going through the AndroidRoot.mobi website. That one leads me to a FileFactory link that download it, but it appears to not be working at the moment. Thanks.
---------- Post added at 06:06 PM ---------- Previous post was at 06:04 PM ----------
ShadowZephyr said:
I'm in the same predicament and want to try the same thing as you. Could you provide a link to the Recovery only NVFlash thread please? I've tried to search but cannot find the one you are talking about.
Click to expand...
Click to collapse
Here you go buddy, but it's not working for me(the files download link that is.) http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/

[nvflash] A very powerfull tool

Here I will post some information regarding using nvlash tool with ThinkPad Tablet.
NVflash tool is a tool for tegra devices which allows different low level operations such as:
1. reading device partition table
2. partitioning device memory
3. reading a device partition
4. writing a device partition
1 and 3 are usefull for backing up device partitions
2 and 4 are usefull for restoring everything back
After backing up a partition you can split the image to a lot of usefull components and information using your PC. You can even edit or add some files to a partition image, i.e. this tool could help you to root your device at any time you want.
Everything here is just for educational puproses. I'm not resposible for any damage which may occur to your device. Use it at your own risk.
Here's small tutorial. Put attached file 04.EBT.img on your hard disk (/space/android/_tpt/device in my case).
Booting to bootloader
1. Turn off your device and disconnect it from PC
2. Hold Rotation button and press Power button for approx 2 seconds
3. Start nvflash:
Code:
$ nvflash -w --bl /space/android/_tpt/device/04.EBT.img --go
4. Connect device via USB. After that you should able to see the following:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x043c6246433f44d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 2
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: /space/android/_tpt/device/04.EBT.img
/ 6291456/6291456 bytes sent
/space/android/_tpt/device/04.EBT.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
5. The device screen should display "Entering NvFlash recovery mode / Nv3p Server" message at the top with Lenovo logo at the backroung.
If everything worked fine you have started a bootloader for futher low level communication with your tablet.
Getting partition table information
1. Boot your device with a bootloader as described above.
2. Run the following command
Code:
$ nvflash -r --getpartitiontable ptable.txt
3. The following output will be displayed on PC console:
Code:
Nvflash started
[resume mode]
Succesfully updated partition table information to ptable.txt
4. This means you have successfully downloaded partition table information to ptable.txt file. You can view it. Here's some useful information from it:
Code:
....
PartitionId=4
Name=EBT
DeviceId=18
StartSector=1536
NumSectors=1536
BytesPerSector=4096
....
PartitionId=6
Name=SOS
DeviceId=18
StartSector=3584
NumSectors=1536
BytesPerSector=4096
PartitionId=7
Name=LNX
DeviceId=18
StartSector=5120
NumSectors=2048
BytesPerSector=4096
PartitionId=8
Name=APP
DeviceId=18
StartSector=7168
NumSectors=196608
BytesPerSector=4096
....
PartitionId=15
Name=UDA
DeviceId=18
StartSector=611840
NumSectors=7202816
BytesPerSector=4096
Here I'll try to give some more information:
PartitionId=4 -- is a number of partition
Name=EBT -- is a name of partition. This partition holds a bootloader image. The same you used to boot your device!
StartSector, NumSectors, BytesPerSector -- these parameters determine a location and size of partition in the internal device memory.
Partition 6 is a recovery partition which holds recovery image (kernel + ramdisk). You can use split_bootimg.pl to split it.
Partition 7 is a bootable partition which holds bootable image (kernel + ramdisk). You can use split_bootimg.pl to split it.
Partition 8 is an ext4 image of /system partition. You can mount it using mount linux utility.
Partition 15 is an ext4 image of /data partition. You can also mount it using mount linux utility.
Reading partition images from device
This method can be used to backup your device. I will show you how to backup a recovery partition (6) but you can do it with any partition you want.
1. Boot your device with a bootloader as described above.
2. Read partition number 6 to file 06.SOS.img with the following command
Code:
$ nvflash -r --read 6 06.SOS.img
3. The following output will indicate a successfull read
Code:
Nvflash started
[resume mode]
receiving file: 06.SOS.img, expected size: 6291456 bytes
/ 6291456/6291456 bytes received
file received successfully
Using split_bootimg.pl you can split you to kernel and ramdisk image:
Code:
$ split_bootimg.pl 06.SOS.img
Page size: 2048 (0x00000800)
Kernel size: 3659716 (0x0037d7c4)
Ramdisk size: 1496705 (0x0016d681)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing 06.SOS.img-kernel ... complete.
Writing 06.SOS.img-ramdisk.gz ... complete.
Now you can get ramdisk contents:
Code:
$ mkdir ramdisk
$ cd ramdisk
ramdisk$ gzip -dc ../06.SOS.img-ramdisk.gz | cpio -im
4405 blocks
ramdisk$ ls
data dev init proc sbin system ueventd.goldfish.rc
default.prop etc init.rc res sys tmp ueventd.rc
Writing an image to device partition
Be very carefull! This operation can brick you device. If you are unsure of result you'd better don't use it
1. Boot your device with a bootloader as described above.
2. Write file recovery.img to partition number 6 (recovery) with the following command:
Code:
$ nvflash -r --download 6 recovery.img
3. Here's a sample output of successfull operation:
Code:
Nvflash started
[resume mode]
sending file: recovery.img
/ 6291456/6291456 bytes sent
recovery.img sent successfully
4. You will also note a large message PASS on your device screen following with the message "Success to update the system, please reboot your system to leave the recovery mode"
5. Now you can easily reboot your system and test your new recovery.
Conclusion
You can use nvflash for deep exploration of your device software, backing up software before any critical updates, flash modified software.
Thank you
P.S. Sorry for any mistakes as English is not my native language.

I thought the bootloader was locked and we can't access nvflash without the proper keys. Has the ics bootloader been unlocked or are the keys not needed? Sorry I'm a bit confused here

darkhandsome18 said:
I thought the bootloader was locked and we can't access nvflash without the proper keys. Has the ics bootloader been unlocked or are the keys not needed? Sorry I'm a bit confused here
Click to expand...
Click to collapse
AFAIK bootloader is locked for Ideapad (but the key has been already disclosed). Thinkpad comes with unlocked bootloader.

It's very interesting. Thank you.
Does this mean that we can make a backup of partitions, and do not need more in CWR?

horsse said:
It's very interesting. Thank you.
Does this mean that we can make a backup of partitions, and do not need more in CWR?
Click to expand...
Click to collapse
We need CWR for different other actions, i.e. for applying unsigned patches in case we had modified our system and normal update fails with consistency check error.
Sent from my ThinkPad Tablet using XDA Premium HD app

Not working for me:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Edit:
Maybe you are lucky and have one of the first relased TPT. I heard they have open bootloader but it was closed in later produced ones.

In my case it does not work. Holding rotation (or any other hardbutton) prevents TPT from powering on.

jaba_cz said:
In my case it does not work. Holding rotation (or any other hardbutton) prevents TPT from powering on.
Click to expand...
Click to collapse
I need more help with this in order to try I believe my will work if I only knew how I don't know where to put that .IMG file were I have adb setup?
Sent from my Galaxy Nexus using Tapatalk 2

jaba_cz said:
In my case it does not work. Holding rotation (or any other hardbutton) prevents TPT from powering on.
Click to expand...
Click to collapse
That's normal. Holding rotation and power on will bring the TPT to APX-Mode.
If you plugin to USB while in APX-Mode it will request new drivers.

Exe557 said:
Not working for me:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
Please verify that you have write permissions for usb device:
Code:
$ cat /etc/udev/rules.d/95-nvflash.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", ATTR{idProduct}=="7820", MODE="0660", OWNER="suntechnic"
You can adjust idVendor and idProduct corresponding values you see with lsusb command, i.e.:
Code:
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 005 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 001 Device 045: ID 0955:7820 NVidia Corp.

Is it possible to fix my unit through Nvflash?
Hi,
Just wondering if it would be possible to fix my unit from nvflash. ?
I by mistake applied the wrong cwm file to my device, and now it's stuck at "Booting recovery kernel image"
Regards
Anders

This is what I need to fix my /system partition it looks like :good: Has to be run in Linux i'm guessing?

I only get error 04 as well.
I have European model 1838.
Mine got bricked trying to install ics. Now it is just in a boot loop and won't even go into recovery.
If this doesn't work I guess I'll have to send it in for service.

AFAIK rcm version 0X4 means the bootloader is locked. Just google for it.
Without SBK which is not leaked for TPT yet we have no chance to use it!

Was worth a shot but mine is version 0x4 as well

Damn, guy where you were when my tablet was just a big 10' brick?
You are perfectly know what a service quality is in Russia ;[
alright sorry, I shouldn't.. great finding even too late, maybe we'll have an unlock key for it, call me when its done, I don't want to brick my tablet anymore.. but do want to be a part of a custom rom development.

Where can I find the nvflash to use?
/Anders

osse said:
Where can I find the nvflash to use?
/Anders
Click to expand...
Click to collapse
I ended up finding it googling around...it was for the asus transformer but it seemed to work(as far as I could get with my locked bootloader)

I ended up using this simple guide from modaco, here.
For the people that "can't" get into APX mode, the screen at least mine gave NO indication that it was in APX mode. After trying a few times I flipped the tablet over and noticed the red LED was on. I then proceeded to connect it to my PC and install the drivers and follow the guide.
Unfortunately, I believe my bootloader is also locked because I typed nvflash --sync and received the output:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Now, granted this is within windows. I haven't tried it on my Linux machine yet. So who knows what the actual issue is, but I am fairly certain the bootloader is locked. It also took me a few minutes to get my device out of APX-mode and boot normally again (or maybe my power button is on the verge of DEATH).
Edit: I have a US TPT 16GB (WiFi only) 183822U, that I bought practically a year ago.

Same here
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Device : 1838-2CG

[Q] adb cannot see my defy, please help

Hello guys,
can any of you help me, please? I tried flashing CM 10.1 or ParanoidAndroid on my Defy (it's quite a long time, so I'm not exactly sure which was the last one). The result was that my phone couldn't boot anymore or even charge a battery. Now I have a new battery and here is the state I'm in:
I try to flash fixed sbf of Android 2.2 which I know is OK. I'm trying to do it in Ubuntu 13.10 x64 but I cannot see the device (I have also tried Ubuntu 12.04 x32, Win7 x64). I boot the defy into bootloader and connect it to my PC and I get:
Code:
Bootloader 09.10
Battery OK
OK to Program
Transfer Mode:
USB
then in linux:
Code:
[B]$ ll /etc/udev/rules.d/[/B]
celkem 32
drwxr-xr-x 2 root root 4096 úno 25 19:38 ./
drwxr-xr-x 4 root root 4096 led 25 11:08 ../
-rw-r--r-- 1 root root 1157 říj 12 13:01 README
-rw-r--r-- 1 root root 897 úno 25 19:38 51-android.rules
-rw-r--r-- 1 root root 769 úno 25 19:36 51-android.rules~
-rw-r--r-- 1 root root 340 úno 23 01:10 51-android.rules.backup
-rw-r--r-- 1 root root 56 úno 23 16:35 70-android.rules.backup
-rw-r--r-- 1 root root 631 led 25 01:43 70-persistent-net.rules
[B]$ cat /etc/udev/rules.d/51-android.rules[/B]
# Motorola
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41d9", MODE="0660", OWNER="jiri" # normalni rezim
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0660", OWNER="jiri" # Debug mode a Recovery
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0660", OWNER="jiri" # Bootloader
# SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666" [I]<-- I have also tried this - no good[/I]
# SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev" [I]<-- I have also tried this - no good[/I]
# SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0660", OWNER="jiri" # Bootloader [I]<-- I have also tried this - no good[/I]
###################################
# GIGABYTE AKU A1 <-- my second android phone
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0414", ATTRS{idProduct}=="0001", MODE="0660", OWNER="jiri" # Normalni rezim bez ladeni
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0414", ATTRS{idProduct}=="0c03", MODE="0660", OWNER="jiri" # Normalni rezim s ladenim
[B]$ lsusb[/B]
..
Bus 003 Device 004: ID 22b8:4280 Motorola PCS
.. [I](I deleted other devices from the list)[/I]
[B]$ adb devices[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[I](nothing here)[/I]
#######################################################################################################################
when I connect Gigabyte Aku A1 I can see it without problem:
Code:
[B]$ lsusb[/B]
..
Bus 003 Device 005: ID 0414:0c03 Giga-Byte Technology Co., Ltd
.. [I](I deleted other devices from the list)[/I]
[B]$ adb devices[/B]
List of devices attached
0123456789ABCDEF device
[B]$ adb version[/B]
Android Debug Bridge version 1.0.31
$
=======================================================================================
I can also boot the defy into custom recovery but I get this:
Code:
Android system recovery <3e>
Android system recovery utility
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
E:Can't mount CACHE:recovery/command
E:Can't mount CACHE:recovery/caller
E:Can't mount CACHE:recovery/log
I have also tried adding 0x22b8 in the adb_usb.ini file (in /home/user/.android folder) but that didn't change anything.
I don't know what I can do to save my defy... Any advice will be very appreciated. I can try solutions both for Ubuntu or Windows.

Update
Hoorrah! Hooray! rah-rah! rah! hurray! :laugh: Now I connected defy in Windows XP, and I see it! But I'm not sure if everything is OK, so here is what i see (see attachment). In RSD Lite it writes
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1e60001391b963010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: c238d606b58692223f266533ecc0f336f1ad5012
BP Public ID: 0000000000000000000000000000000000000000
So I guess I'm ready to flash fixed sbf. Do you think, that errors in recovery (E:Can't mount CACHE:recovery/command; E:Can't mount CACHE:recovery/caller; E:Can't mount CACHE:recovery/log) may cause any trouble? What may be wrong, that I see the mobile only on WinXP x32 and not in Ubuntu 12.04 x32, Ubuntu 13.10 x64, Win7 x64? It's not beacuse of an USB cable neither because of drivers or admin rights.
So the main question is: Do you think the phone is ready for flashing or is there any problem you can see (and I don't) which could cause more trouble?
Thanks fory any advice / comment.

google-the_big_brother said:
Hoorrah! Hooray! rah-rah! rah! hurray! :laugh: Now I connected defy in Windows XP, and I see it! But I'm not sure if everything is OK, so here is what i see (see attachment). In RSD Lite it writes
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1e60001391b963010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: c238d606b58692223f266533ecc0f336f1ad5012
BP Public ID: 0000000000000000000000000000000000000000
So I guess I'm ready to flash fixed sbf. Do you think, that errors in recovery (E:Can't mount CACHE:recovery/command; E:Can't mount CACHE:recovery/caller; E:Can't mount CACHE:recovery/log) may cause any trouble? What may be wrong, that I see the mobile only on WinXP x32 and not in Ubuntu 12.04 x32, Ubuntu 13.10 x64, Win7 x64? It's not beacuse of an USB cable neither because of drivers or admin rights.
So the main question is: Do you think the phone is ready for flashing or is there any problem you can see (and I don't) which could cause more trouble?
Thanks fory any advice / comment.
Click to expand...
Click to collapse
For future reference: if you have your phone in boot loader mode, adb can't be used to connect to it: you need to use sbf_flash on Linux or its Windows equivalent (RSD Lite, I think).
Code:
sbf_flash -v -r
should produce some (lots of) output.
I think you're fine to flash an SBF, but no guarantees.

update
To PhilipCetero:
thank you for your advice.:good: I didn't know that.
Current situation is:
I managed to flash stock ROM (Eclair 2.1-update 1, JRDNEM_U3_2.51.1) using RSDLite 6.1.6 (I had previously used recommended version 4.9 and that was the problem, I guess). Now "sbf_flash -v -r" gives me info about CG files contained in the flashed ROM.
I rooted the phone using Framaroot and installed 2nd init version 2.3. But something is wrong cause after reboot there is no blue light and I can't get into custom recovery. So now I'm trying to solve that...
Update (21:33):
2nd Init version 2.0 worked OK. Now I have Android BootMenu v0.6.1 and ClockworkMod Recovery v2.5.1.8. So my goal is now to instal CWM or ParanoidAndroid (if there is a working version).

Rooting LG V20 and installing TWRP

Question for everyone,
So I have followed the steps to root my LG V20 before I installed TWRP, however I am stuck at the moment. Here is a copy of my log. It keeps coming up with an error saying no file or directory when I try to put this in " dd if=/sdcard/twrp-3.0.2-0-beta4-h918.img of=/dev/block/bootdevice/by-name/recovery.
Here is a copy of the log:
--------
Updating boot image hash
Writing modified boot image to block device '/dev/block/bootdevice/by-name/boot'...
Done!
------------
Permissive boot has been has been flashed to /dev/block/bootdevice/by-name/boot successfully!
You may use 'reboot' now to enter a permissive system.
***********************************************
* give jcadduono a hug, will ya? *
***********************************************
elsa:/data/local/tmp $ run-as su
Welcome to recowvery! (run-as)
------------
Current uid: 2000
Setting capabilities
Attempting to escalate to root
Current uid: 0
We have root access!
------------
Starting root shell
elsa:/data/local/tmp # dd if=/sdcard/twrp-3.0.2-0-beta4-h918.img of=/dev/block/bootdevice/by-name/recovery
dd: /sdcard/twrp-3.0.2-0-beta4-h918.img: No such file or directory
1|elsa:/data/local/tmp # dd if=/sdcard/twrp-3.0.2-1-h918.img of=/dev/block/bootdevice/by-name/recovery
dd: /sdcard/twrp-3.0.2-1-h918.img: No such file or directory
1|elsa:/data/local/tmp #
---------------------------------------------------------------------
Thanks