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
Related
there're some troubles while data2sd, and it doesn't work.....
please help me！
my G7's infomation:
S-OFF, AlphaRev N1Table HBOOT, SdCard:6.8G+1.2G FATA32
Process：
E:\android-sdk\tools>adb shell
/ # mount /system
mount /system
/ # mount /data
mount /data
/ # mount /sdcard
mount /sdcard
/ # exit
exit
E:\android-sdk\tools>adb push c:\01data /system/etc/init.d
32 KB/s (394 bytes in 0.011s)
E:\android-sdk\tools>adb push c:\busybox-armv6l /system/xbin/busybox
1771 KB/s (1062992 bytes in 0.585s)
E:\android-sdk\tools>adb shell
/ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
/ # chmod 777 /system/xbin/busybox
chmod 777 /system/xbin/busybox
/ # cd /
cd /
/ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
/ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: writing '/sd-ext/ext2': No space left on device
1199+0 records in
1197+1 records out
/ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
Filesystem label=userdata
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
76800 inodes, 306639 blocks
15331 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
10 block groups
32768 blocks per group, 32768 fragments per group
7680 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
/ # mkdir /sd
mkdir /sd
/ # /system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/ # cd /data
cd /data
/data # cp -a * /sd
cp -a * /sd
/data # cd /
cd /
/ # /system/xbin/busybox umount /sd
/system/xbin/busybox umount /sd
/ # exit
exit
E:\android-sdk\tools>adb reboot
error: closed
BTW,when i reboot the phone,i found the second partition on sdcard is 100% full,why?where is the mistake?
help！help！help！help！help！
This is a question and belongs in q&a, not development.
Sent from my Evil Lair using Doomsday Device
It actually belongs in the Data2SD thread, which in turn IS in ROM Development
Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future
thx，i'll try
Btw I suggest to use the default mtd structure.
sent from the future
E:\android-sdk\tools>adb reboot
error: closed
this problem may cause by usb drives or recovery?
the drives are all installed ok...
mattiadj said:
Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future
Click to expand...
Click to collapse
i have a question,in your tutorial, don't need this file busybox?
Busibox may be included in ROM.
Try to install recovery driver from root thread.
sent from the future
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...
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.
hi had to restore everything and going through stages have installed busybox and unblocked bootloader but cant get rbox boot menu to install i follow all the stages but on last stage i get cannot open for read: No such file or directory any ideas? here is full commands and response:
is is possible to ubgrade without boot menu or install twrp instead or must i go through the stages
adb push c:\users\paul\desktop\bootmenu.img /sdcard
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
cannot stat 'c:userspauldesktopbootmenu.img': No such file or directory
1|[email protected]:/ # adb shell
adb shell
[email protected]:/ # su
su
[email protected]:/ # su
su
[email protected]:/ # /system/xbin/busybox md5sum /sdcard/bootmenu.img
/system/xbin/busybox md5sum /sdcard/bootmenu.img
a8a3c28baafe43f354d92e6cc8b392d3 /sdcard/bootmenu.img
[email protected]:/ # rm -f /sdcard/bootmenu.img
rm -f /sdcard/bootmenu.img
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # mkdir /system/boot
mkdir /system/boot
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
dcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.422 secs (24847772 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
/sdcard/bootmenu.img: cannot open for read: No such file or directory
paulsavo said:
hi had to restore everything and going through stages have installed busybox and unblocked bootloader but cant get rbox boot menu to install i follow all the stages but on last stage i get cannot open for read: No such file or directory any ideas? here is full commands and response:
is is possible to ubgrade without boot menu or install twrp instead or must i go through the stages
adb push c:\users\paul\desktop\bootmenu.img /sdcard
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
cannot stat 'c:userspauldesktopbootmenu.img': No such file or directory
1|[email protected]:/ # adb shell
adb shell
[email protected]:/ # su
su
[email protected]:/ # su
su
[email protected]:/ # /system/xbin/busybox md5sum /sdcard/bootmenu.img
/system/xbin/busybox md5sum /sdcard/bootmenu.img
a8a3c28baafe43f354d92e6cc8b392d3 /sdcard/bootmenu.img
[email protected]:/ # rm -f /sdcard/bootmenu.img
rm -f /sdcard/bootmenu.img
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # mkdir /system/boot
mkdir /system/boot
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
dcc.1/by-name/boot of=/system/boot/boot.img <
20480+0 records in
20480+0 records out
10485760 bytes transferred in 0.422 secs (24847772 bytes/sec)
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ # dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dev/block/platform/msm_sdcc.1/by-name/boot <
/sdcard/bootmenu.img: cannot open for read: No such file or directory
Click to expand...
Click to collapse
You deleted the file you're trying to dd. might want to double check the instructions.
Lol seen that cheers
How can I extract the recovery image from my phone over adb?
I was thinking something like
Code:
adb pull /dev/block/mmcblkXXX recovery.img
However, I can't work out which is the recovery.
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
[email protected]:/ #
Note: I'm only interested in adb and not via custom recovery or other apps on the phone.
It seems like I wasn't searching hard enough!
The "by-name" file was a level down further than expected and I didn't spot it initially when browsing.
Code:
1|[email protected]:/ # find /dev/block/ -name by-name
/dev/block/platform/omap/omap_hsmmc.0/by-name
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name|grep recovery
lrwxrwxrwx root root 2017-01-20 04:46 recovery -> /dev/block/mmcblk0p8
[email protected]:/ # exit
~ $ adb pull /dev/block/mmcblk0p8 recovery.img