Was following this thread: http://forum.cyanogenmod.com/topic/15623-how-to-fix-a-semi-bricked-g2/#entry159320
And when I get to
adb shell(enter)
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17(enter)
Click to expand...
Click to collapse
I get this on the phone
c:\ANDROID-SDK\TOOLS>adb shell
~ # dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd: writing '/dev/block/mmcblk0p17': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 2.056183 seconds, 0B/s
Click to expand...
Click to collapse
Here is a transcript of the entire process to show what I was doing
C:\Users\Christopher>cd c:\android-sdk\tools
c:\ANDROID-SDK\TOOLS>adb devices
List of devices attached
SH0CXR200450 recovery
c:\ANDROID-SDK\TOOLS>adb push PC10IMG.zip /sdcard/PC10IMG.zip
1542 KB/s (129303247 bytes in 81.854s)
c:\ANDROID-SDK\TOOLS>adb push misc.img /sdcard/misc.img
1523 KB/s (262144 bytes in 0.168s)
c:\ANDROID-SDK\TOOLS>adb push misc_version /data/local/misc_version
1031 KB/s (15837 bytes in 0.015s)
c:\ANDROID-SDK\TOOLS>adb shell chmod 777 /data/local/misc_version
c:\ANDROID-SDK\TOOLS>adb shell
~ # dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd: writing '/dev/block/mmcblk0p17': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 2.056183 seconds, 0B/s
~ # reboot bootloader
reboot bootloader
c:\ANDROID-SDK\TOOLS>
Click to expand...
Click to collapse
My original problem is I am getting these errors when I go into Clockwork 3.0.0.5 and I can not format cache, data, or anything.
e:can't open /cache/recovery/log
e:can't open /cache/recovery/log
e:can't open /cache/recovery/last_log
e:can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Any resolution
I am getting similar errors. Did you ever resolve this issue? I could use some help.
Thanks!
Those recovery errors could be signs of a bad emmc, which would be why you can't flash p17.
Here is more info on the errors/bad emmc
-Nipqer
Related
Ok ariel_ on the irc channel has managed to get the right LTE radio and I was able to dd it back on, but we still need to get the cdma radio.
@ariel_> I used this command to take one of them out. adb shell dd bs=256 count=49153 if=/dev/block/platform/omap/omap_hsmmc.0/by-name/radio of=/sdcard/radio.img and this was for the other one: adb shell dd if=/dev/block/mmcblk0p9 of=/data/media/radio1.img
Click to expand...
Click to collapse
I then took those images and pushed them onto my device through the recovery shell using as follows.
C:\Galaxy Nexus ToolKit>adb-toolkit.exe shell
~ # ls
ls
boot etc sd-ext
cache init sdcard
data init.rc sys
datadata proc system
default.prop res tmp
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd sdcard
cd sdcard
/data/media # ls
ls
radio.img radio1.img
/data/media # dd if=/sdcard/radio.img of=/dev/block/platform/omap/omap_hsmmc.0/b
y-name/radio
dd if=/sdcard/radio.img of=/dev/block/platform/omap/omap_hsmmc.0/b
y-name/radio
24576+1 records in
24576+1 records out
12583168 bytes (12.0MB) copied, 3.677856 seconds, 3.3MB/s
/data/media # dd if=/sdcard/radio1.img of=/dev/block/mmcblk0p9
dd if=/sdcard/radio1.img of=/dev/block/mmcblk0p9
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 4.613159 seconds, 3.5MB/s
/data/media #
C:\Galaxy Nexus ToolKit>
Click to expand...
Click to collapse
My LTE baseband now reads correctly as L700.FC12 but my CDMA baseband isnt correct.
Please post questions in Q&A.
Development is for released products
Thanks
FNM
Please do this test:
write in terminal emulator, not also (...):
(Write file 64MB (8k * 8192) bigger file is better)
busybox dd if=/dev/zero of=/data/out.img bs=8000 count=8192
(Read)
busybox dd of=/dev/null if=/data/out.img bs=8000
(to Remove out.img)
rm /data/out.img
If you don't have int2sd and let /data the phone writes in nand.
If you change / data in /sdcard or /sd-ext you can test your sd-card speed.
Report in this thread your results.
If the test is positive we can ask to our developer to try to include this NativeSD script in roms.
http://forum.xda-developers.com/showthread.php?t=1869673
Edit: use androbench from market and try both /data and /system.
(I read this information from N1 jb evervolv thread)
a/local/bin:$PATH <
[email protected]:/ $ su
ev/zero of=/data/out.img bs=8000 count=8192 <
dd: writing '/data/out.img': No space left on device
4004+0 records in
4002+1 records out
32022528 bytes (30.5MB) copied, 30.591187 seconds, 1022.3KB/s
dev/null if=/data/out.img bs=8000 <
4002+1 records in
4002+1 records out
32022528 bytes (30.5MB) copied, 0.244355 seconds, 125.0MB/s
[email protected]:/ # rm /data/out.img
[email protected]:/ #
That's for nand.
Using nikez jb p0.9 with a2sd y/n/y.
Hope this helps as I ran out of space during the test
Below for sdcard . Using class 10 16GB Kingston (tested r/w speeds on PC they are of class 10).
a/local/bin:$PATH <
[email protected]:/ $ su
ev/zero of=/sd-ext/out.img bs=8000 count=8192 <
8192+0 records in
8192+0 records out
65536000 bytes (62.5MB) copied, 5.494354 seconds, 11.4MB/s
ev/zero of=/sd-ext/out.img bs=8000 count=8192 <
8192+0 records in
8192+0 records out
65536000 bytes (62.5MB) copied, 2.478820 seconds, 25.2MB/s
[email protected]:/ # rm /sd-ext/out.img
[email protected]:/ #
# busybox dd if=/dev/zero of=/data/out.img bs=8000 count=8192
busybox dd if=/dev/zero of=/data/out.img bs=8000 count=8192
8192+0 records in
8192+0 records out
65536000 bytes (62.5MB) copied, 18.992340 seconds, 3.3MB/s
# busybox dd of=/dev/null if=/data/out.img bs=8000
busybox dd of=/dev/null if=/data/out.img bs=8000
8192+0 records in
8192+0 records out
65536000 bytes (62.5MB) copied, 0.258057 seconds, 242.2MB/s
This was for NAND
---------- Post added at 10:33 AM ---------- Previous post was at 10:28 AM ----------
# busybox dd if=/dev/zero of=/sd-ext/out.img bs=8000 count=8192
busybox dd if=/dev/zero of=/sd-ext/out.img bs=8000 count=8192
8192+0 records in
8192+0 records out
65536000 bytes (62.5MB) copied, 0.590332 seconds, 105.9MB/s What ??
# busybox dd of=/dev/null if=/sd-ext/out.img bs=8000
busybox dd of=/dev/null if=/sd-ext/out.img bs=8000
8192+0 records in
8192+0 records out
65536000 bytes (62.5MB) copied, 0.256714 seconds, 243.5MB/s
# rm /sd-ext/out.img
rm /sd-ext/out.img
This was for sdcard
My class 4 sdcard is faster than NAND ????
Is nobody else interested in this to at least see how it works? Or it makes no sense on our desires.
I'm just wondering if our nands are faster than class 6/10 SD cards.
Sent from my HTC Desire using xda app-developers app
I am guessing the ext4 file system since it buffers returns immediately to write request. Therefore the wrong result in my test.
yes, this script test reports false results, it is better to use the app: ANDROBENCH.
you can try both sdcard and internal. When I will have time to try new Nikez's release (or another non-int2sd rom) I will write my results.
Unfortunately androbench crashes without completing the test. Will try to reinstall or fix permissions maybe that will help. I'm on nikez jb p0.9
Sent from my HTC Desire using xda app-developers app
Weird
Weird, Androbench crashes here also on Spazedog-ICS...
I have followed this guide twice now, but when I reboot the phone with Vol Down + Power, I still get the revolutionary screen:
http://forums.androidcentral.com/in...uide-unroot-revolutionary-incredible-2-a.html
Is this the hboot image that revolutionary is using? Why is it still on the phone after running these commands?
C:\Users\Bro\Desktop\unroot>adb push busybox /data/local/
2353 KB/s (1062992 bytes in 0.441s)
C:\Users\Bro\Desktop\unroot>adb push hboot_0.97.0000_336906.nb0 /data/local/
2250 KB/s (1048576 bytes in 0.455s)
C:\Users\Bro\Desktop\unroot>adb shell chmod 777 /data/local/psneuter
C:\Users\Bro\Desktop\unroot>adb shell chmod 777 /data/local/busybox
C:\Users\Bro\Desktop\unroot>adb shell /data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\Users\Bro\Desktop\unroot>adb shell /data/local/busybox md5sum /data/local
/hboot_0.97.0000_336906.nb0
adb server is out of date. killing...
* daemon started successfully *
affe3dc9abe9d3a8c8bb3ba0ee5176ac /data/local/hboot_0.97.0000_336906.nb0
C:\Users\Bro\Desktop\unroot>adb shell dd if=/data/local/hboot_0.97.0000_3369
06.nb0 of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.275 secs (3813003 bytes/sec)
C:\Users\Bro\Desktop\unroot>adb shell /data/local/busybox md5sum /dev/block/
mmcblk0p18
adb server is out of date. killing...
* daemon started successfully *
affe3dc9abe9d3a8c8bb3ba0ee5176ac /dev/block/mmcblk0p18
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.
These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:
Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]
[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
[email protected]:/ # exit
C:\u-boot-firefirefire-1.2>adb reboot
After the reboot statement the device shut down but never came back.
I fear I have killed the Kindle (my sons Kindle ). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
If there is to be a solution to your problem, it will get figured out here:
http://forum.xda-developers.com/showthread.php?t=2622218
Sent from my Nexus 7 using Tapatalk
Fly_Trap said:
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.
These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:
Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]
[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
[email protected]:/ # exit
C:\u-boot-firefirefire-1.2>adb reboot
After the reboot statement the device shut down but never came back.
I fear I have killed the Kindle (my sons Kindle ). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
Click to expand...
Click to collapse
Cause of the problem is that the above method does not work for the latest software version 6.3.2
androvista said:
Cause of the problem is that the above method does not work for the latest software version 6.3.2
Click to expand...
Click to collapse
So, @androvista, is there a solution?
Sent from my Nexus 7 using Tapatalk
jma9454 said:
So, @androvista, is there a solution?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
did you get it figured out? i have same prob
Fly_Trap said:
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.
These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:
Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]
[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
[email protected]:/ # exit
C:\u-boot-firefirefire-1.2>adb reboot
After the reboot statement the device shut down but never came back.
I fear I have killed the Kindle (my sons Kindle ). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
Click to expand...
Click to collapse
Hello
You can try doing the following
Install Minimal Fastboot and ADB, you can find a thread here on xda.
Type in when connected to kindle from pc, abd devices.
If you see any long serial number type in adb reboot recovery
Then adb reboot bootloader, either way the kindle should go into recovery after step one, and there you could get factory reset. It worked for me. Just check out the link, thanks to SnegovikRZN http://forum.xda-developers.com/showthread.php?t=2530623
Hello there,
I am attempting to downgrade my rooted (w/BusyBox) Fire TV 51.1.1.0_511070220 to 510058520, in order to eventually install pre-rooted firmware by rbox. However, I continue to get the "downgrade install failed" message upon reboot. I read all of the comments in the downgrade post at AFTVnews, and still can't figure it out. I know that some people have had this same problem going from 70220 to 58520. Can anyone please help?
Here is my log:
User-1s-MacBook-Pro:~ user1$ ./adb push /Users/user1/APK\ Files/recovery.img /sdcard/
940 KB/s (10485760 bytes in 10.886s)
User-1s-MacBook-Pro:~ user1$ ./adb shell
[email protected]:/ $ su
dev/block/platform/msm_sdcc.1/by-name/recovery <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.587 secs (6607284 bytes/sec)
[email protected]:/ # rm -f /cache/*.bin
[email protected]:/ # rm -f /cache/*.zip
[email protected]:/ # rm -f /cache/recovery/command
[email protected]:/ # rm -f /sdcard/recovery.img
[email protected]:/ # chmod 777 /cache
[email protected]:/ # chmod 777 /cache/recovery
[email protected]:/ # cd /cache/recovery
cache/update.zip > command <
[email protected]:/cache/recovery # exit
[email protected]:/ $ exit
User-1s-MacBook-Pro:~ user1$ ./adb push /Users/user1/APK\ Files/update.zip /cache
1017 KB/s (415956067 bytes in 399.180s)
User-1s-MacBook-Pro:~ user1$ ./adb reboot recovery
Do you see anything that I am doing wrong? I followed the instructions very carefully, including the steps where the install fails, and have attempted this like 5 times. I am using a Mac computer, so am I missing something in front of the "rm" lines? There is no visible response when I enter the rm lines. I'm at a loss! Thanks.