Database Users

Magic not booting

Installed a hero rom, Maxisma's, didn't like the speed so I went for MghtyMax rom instead. After reading on a few threads, I decided to update the SPL, but accidentally flashed a 32A SPL, mine is a 32B. Have now installed 1.33.2004, for the 32B, and can access recovery and fastboot. I can install roms, and different recovery programs, I am currently running Amon RA's recovery. Now, the problem, I have tried this with about 5 different roms, and every one gets stuck on the splash screen (Which is custom btw). I have attached the logcat log from cmd:
C:\SDK\tools>adb logcat
- waiting for device -
I//system/xbin/busybox( 47): +++ "In a world of deceit, open your eyes. Don't
be afraid and you realize......"
I//system/xbin/busybox( 47): +++ Welcome to Android 1.6 / CyanogenMod-4.2.9.1
I//system/xbin/busybox( 47): --- Executing firstboot.sh
I//system/xbin/busybox( 47): --- Checking filesystems
I//system/xbin/busybox( 47): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/busybox( 47): /dev/block/mmcblk0p2: clean, 15/244320 files, 392
81/488281 blocks
I//system/xbin/busybox( 47): cp: cannot stat '/data/app-private/*': No such fi
le or directory
I//system/xbin/busybox( 47): cp: cannot stat '/data/dalvik-cache/*': No such f
ile or directory
I//system/xbin/busybox( 47): +++ Apps-to-SD successfully enabled
I/logwrapper( 47): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 132): debuggerd: Dec 17 2009 21:34:52
E/flash_image( 138): error opening /data/recovery.img: No such file or director
y
I/vold ( 131): Android Volume Daemon version 2.0
I/vold ( 131): New MMC card 'SD16G' (serial 3495231383) added @ /devices/pla
tform/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35
I/vold ( 131): Disk (blkdev 179:0), 31326208 secs (15296 MB) 3 partitions
I/vold ( 131): New blkdev 179.0 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 3
I/vold ( 131): Partition (blkdev 179:1), 30015625 secs (14656 MB) type 0xc
I/vold ( 131): New blkdev 179.1 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 2
I/vold ( 131): Partition (blkdev 179:2), 976562 secs (476 MB) type 0x83
I/vold ( 131): New blkdev 179.2 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 1
I/vold ( 131): Partition (blkdev 179:3), 318497 secs (155 MB) type 0x82
I/vold ( 131): New blkdev 179.3 on media SD16G, media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:9b35, Dpp 0
I/vold ( 131): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:9b35/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 131): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 131): Volmgr not ready to handle device
D/vold ( 131): Bootstrapping complete
Click to expand...
Click to collapse

No one knows any solutions? Or how much it could cost for a repair? All I'm looking for is to get my phone usable again but I've tried undoing everything I've done so far, but I can't find the stock SPL for a Vodafone UK Magic or any nandroid backups that might fit my phone (I did have one but my laptop hard drive stopped working so I update the SLIC and installed Windows 7). I would be willing to pay for any help that would get my phone working again. Thanks.

update the spl to a higher number i'm using update.SPL_Crios_1.33.2004 (you might already be on this one)which thinks its 2005 also is you card partitioned with 3 partitions and make sure you wipe everything with wipe from recovery

Thanks for the help, no I'm not on the Crios SPL, I'm on the normal 1.33.2004. I have now sorted the problem, I wiped and partitioned many times, and downloaded a previous CyanogenMod. I don't know which one of these solved the problems but now my phone boots. I am having a problem with the phone still though, as every time I try to open a message, the app force closes, the home button will not work, and the contacts app will not open.

jULY 2010 MR4 logcat

W/SystemUpdateHelper( 74): !!! REBOOTING TO INSTALL /cache/8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip !!!
D/ ( 74): unable to unlink '/cache/recovery/command': No such file or directory (errno=2)
D/ ( 74): unable to unlink '/cache/recovery/log': No such file or directory (errno=2)

[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).

Droid RAZR M: Qflash Utility Help

QFLASH Problem
What the hell .. squint emoticon
"No data read from USB. This may not be an error. Trying again..."
if anyone knw about it so Guide me .i am very close :|
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>python 8960_blankflash.py
Emergency download enumeration detected on port - com3
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
Blank flashing successful
Device will now enumerate in fastboot mode
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>pause
Press any key to continue . .

Shield TV 16 GB, bootloop, usb debugging not enabled

Hi guys,
I have a Shield TV 16gb and I updated it couple days ago to Marshmallow. The shield was previously rooted and I re-rooted it successfully again. After a while I realized, that however Google Cast was missing and I decided to flash my shield back with the nv-recovery-image-shield-atv-upgrade2_1.zip from that page: http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv/.
Flashing went well, but when I try to reboot now, I'm stucked with the NvidiaShield logo. I'm able to access the fastboot mode manually on the shield, but under adb devices, no device is listed.
I was checking the hardware manager on my computer, and the shield is listed under usb devices.
Could it be, that when I did the recovery image flash, that my usb debugging is not enabled anymore and that's way it's not listed under adb devices, and is there a way to somehow restore my shield?
Thanks very much for everybody who try to help me with my problem.

The command while in bootloader is 'fastboot devices'.
Restore using the recovery images here for your device https://developer.nvidia.com/gameworksdownload using fastboot not twrp. Although they may have removed the 2.1 images now that 3.0 is out.

gffmac said:
The command while in bootloader is 'fastboot devices'.
Restore using the recovery images here for your device
using fastboot not twrp. Although they may have removed the 2.1 images now that 3.0 is out.
Click to expand...
Click to collapse
As 3.0 images are out, they have removed old image.
I downloaded 1.3 source from shield-open-source built and flash.
The bootup stuck in a loop "nVidia" followed by "android" screen and reboots.
Here is the adb error log:
E/sdcard ( 251): missing packages.list; retrying
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/default/use_optimistic: No such file or directory
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/dummy0/use_optimistic: No such file or directory
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/eth0/use_optimistic: No such file or directory
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/ip6tnl0/use_optimistic: No such file or directory
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/Netd ( 227): Failed to open /proc/sys/net/ipv6/conf/wlan0/use_optimistic: No such file or directory
E/gralloc ( 201): NvGrAllocExt: formats - internal 0x1, external 0x1 usage 0x1a00
E/gralloc ( 201): NvGrAllocExt: formats with color space - internal 0x1, external 0x1 usage 0x1a00
E/HAL ( 231): load: module=/vendor/lib/hw/camera.tegra.so
E/HAL ( 231): dlopen failed: library "libnvavp.so" not found

Try this: http://forum.xda-developers.com/shield-tv/general/guide-how-to-flash-recovery-image-t3321404

Yeah, it worked, you guys are awsome!!
Thanks so much for all your help and advice :good: