Related
I would like to try flashing the stock bell rom back on my phone but I never backed it up initially.
I've been having Bluetooth music issues with both kernelpanics and ho!no!s roms so I have to get stock to test if its the phone or just the roms while its still in warranty.
Thanks guys!!
Sent from my LG-P930 using XDA
EDIT:
Found stock system.img
What are the ADB commands to flash the file to my phone?
Bump for new topic. Found System.img of stock bell canada rom
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
Epyoch said:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
Click to expand...
Click to collapse
when I type SU in, it says /sbin/sh: su: not found
and if i try dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
it gives me dd: can't open '/sdcard/system.img': No such file or directory
Okay, first, in CWM, you don't need to su for root permissions, your ADB shell has them. Second, if you haven't copied your file to the root level of your sdcard and if your file isn't named "system.img" exactly, that command will fail. I'll leave it to you to figure out how to move/rename your system.img file accordingly lol
Edit, it just occurred to me you might be having the garbled sdcard problem where it will spit out garbage if you type in the "ls" command in ADB. The solution has been posted by kernelpan1c, but first let us know what the output of ls is if you're sure your system.img is in the root level of your sdcard.
Malnilion said:
Okay, first, in CWM, you don't need to su for root permissions, your ADB shell has them. Second, if you haven't copied your file to the root level of your sdcard and if your file isn't named "system.img" exactly, that command will fail. I'll leave it to you to figure out how to move/rename your system.img file accordingly lol
Edit, it just occurred to me you might be having the garbled sdcard problem where it will spit out garbage if you type in the "ls" command in ADB. The solution has been posted by kernelpan1c, but first let us know what the output of ls is if you're sure your system.img is in the root level of your sdcard.
Click to expand...
Click to collapse
I already used ADB to push system.img to my phone's SDCard root directory.
Are you suggesting that I reformat my SDCard through windows?
I just realized that I am lacking the boot.img of the stock bell ROM. system and boot are the two that are absolutely necessary to get the phone working correct?
Which rom are you coming from? If it's a Nitro rom/kernelpan1c's rom, you shouldn't have to flash boot.img.
Yeah, according to kernelpan1c, there is something weird going on with the way our sdcard is formatted. After formatting it in Windows he says it should work just fine in the CWM flashed by Rom Manager (I haven't tested it myself, but I'm sure he's correct). I really want to know what is making the Rom Manager CWM unable to read it where bytecode64's CWM can read it just fine...
Malnilion said:
Which rom are you coming from? If it's a Nitro rom/kernelpan1c's rom, you shouldn't have to flash boot.img.
Yeah, according to kernelpan1c, there is something weird going on with the way our sdcard is formatted. After formatting it in Windows he says it should work just fine in the CWM flashed by Rom Manager (I haven't tested it myself, but I'm sure he's correct). I really want to know what is making the Rom Manager CWM unable to read it where bytecode64's CWM can read it just fine...
Click to expand...
Click to collapse
I think I'll be using HO!NO!'s rom as a base for the boot.img, since he has a bell optimus LTE, not the AT&T phone. I'm assuming that he hasn't made any changes to the boot partition, since no custom kernel development has occurred for this phone yet.
I found a so called legit CWM backup of the BELL rom, in one of the lu6200 threads, http://forum.xda-developers.com/showthread.php?t=1472501
but recovering the backup only hangs on the LG logo. I did a "advanced restore" and restored only the system and boot files but that didn't get past the logo either...
It booted after an advanced restore with the "stock" system(from that thread) and the boot (from HONO's), but the WIFI wouldn't start, it said error.
Where did you get your stock bell system.img? and can you provide it?
hereric said:
when I type SU in, it says /sbin/sh: su: not found
and if i try dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
it gives me dd: can't open '/sdcard/system.img': No such file or directory
Click to expand...
Click to collapse
Mount sdcard in recovery.
After you enter adb shell
"mount /sdcard" (without quotations)
Then use the command "dd if=/sdcard/system.img of=/dev/block/mmcblk0p27"
I'm using the U.S. Glide running dmans cm10.1 with the Aquethys touch CWM recovery and I have messed up my USB Port and cannot transfer any data what so ever. I decided to explore alternatives to update the recovery and I found the flash_image command to be the best option as I was unable generate a cwm flashable zip from the Odin tar file (a bit too complexed for me (I have a windows pc)) and while attempting the command flash_image recovery /sdcard/recovery. Img in the phones terminal (image extracted from the new cwm built from source (great job guys!!!!)) and got a partition error and after more research found this to be a common error with people with phones containing the Emmc layout. But of course no solutions presented themselves without needing a solid USB connection. Any help or troublshooting would be appreciated! Other routes included fastboot interface but I don't think this phone uses it (correct me if I'm wrong )
Sent from my SGH-I927
wat about twrp recovery... u can find it on the goomanager app
You should try the nontouch version of cwmr. I've heard several people running into similar problems as you with the touch version.
Sent form my SGH-i927 running dman's cm10.1
Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium
Cprager said:
Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
Now follow this http://forum.xda-developers.com/showthread.php?t=1630519 . Replce the .img file with the glide verison of recovery.
The above should work for you, though i've not tried it myself.
awesome, I will attempt this today and report back.
Cprager said:
awesome, I will attempt this today and report back.
Click to expand...
Click to collapse
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)
greeneyez15o said:
wat about twrp recovery... u can find it on the goomanager app
Click to expand...
Click to collapse
And what version of twrp did you flash and for what device to work on the glide? Without smashing your partitions..
Sent from my SGH-I927 using xda premium
Cprager said:
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)
Click to expand...
Click to collapse
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app
ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal
Cprager said:
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal
Click to expand...
Click to collapse
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.
ninthsense said:
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.
Click to expand...
Click to collapse
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx
Cprager said:
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx
Click to expand...
Click to collapse
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img
ninthsense said:
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Same error, "failed with error: -1"
ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.
roothorick said:
ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.
Click to expand...
Click to collapse
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.
ninthsense said:
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.
Click to expand...
Click to collapse
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
edit** don't know if this helps
cat /proc/partitions
major minor #blocks name
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
179 24 7786496 mmcblk1
179 25 7785472 mmcblk1p1
Cprager said:
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
Click to expand...
Click to collapse
Nothing really, besides just ls /dev/block/mmcblk0p*
Phone partitions are quite a bit different from computer partitions -- about half the partitions don't even have filesystems; the entire partition is dedicated to some image that is important to one thing or the other.
I've got a pretty good overview of the CGlide ICS partitions here: http://forum.xda-developers.com/showthread.php?t=2051327
From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state
ninthsense said:
From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state
Click to expand...
Click to collapse
YOU GUYS ROCK !!!!!
I understand the procedure for replacing the previous recovery with the new recovery.img through the DD command,
but am unsure how to backup the current one. I will do more research and run my procedure by you guys before attempting anything
**edit**
to backup:
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
to flash new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
there was an attribute listed bs=4096 (maybe bit size??)
please let me know if my commands are correct, and I will give it a go (fingers crossed lol)
When I first got SGS3 I made efs backup as suggested by xda. I didn't backup it as a folder, only as a dd block copy.
So if you are good today - make block copy of EFS and tar copy using adb:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.sbn
cd /sdcard
tar cvf efs.tar /efs
Also there is a way of saving NVRam into recovery. Do it now if you haven't yet:
adb reboot nvbackup
Then if you still don't feel safe download QPST tools from IMEI thread and backup your NVRam to PC.
My earpiece died and I got a replacement SGS3.
Something (CWM6?) caused IMEI corruption. I didn't know that, so I tried reflashing modems and ROMs. I was trying everything to restore my connectivity. It somehow didn't help that there are seversal guides on how to do IMEI restore.
While I was waiting for another tool download I decided to restore efs from my previous SGS3 on to current SGS3 (I was at my wits end). And I didn't backup current EFS - my huge mistake! But I already almost give up on the phone at that point.
QPST+Peoplearmy tool was able to restore my IMEI. But EFS is now corrupt (why? I cannot even mount it!). And I can only use one modem - the one I used when backing up EFS (UCALG1 modem).
On the good side - after formatting EFS and making it clean, I can run CM10.1 without any issues. My serial number is 000000, but who cares.
Here's how to format EFS:
1. Reboot into recovery (CWM 5.8.0.5 touch is my preferred)
2. You should be able to see phone connected to PC in adb (recovery mode)
3. Issue following commands:
adb shell
mke2fs -T ext4 /dev/block/mmcblk0p11
mkdir /efs
mount -w -t ext4 /dev/block/mmcblk0p11 /efs
Lesson learned - try not to mess with EFS at all. Do IMEI restore using QPST and Peoplearmy. I'll keep you posted on EFS restore efforts.
Assuming I made a block copy of my EFS partition using "dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.sbn".
How would I restore it should I corrupt my EFS?
Like this?
dd if=/sdcard/efs.sbn of=/dev/block/mmcblk0p11
HiKsFiles said:
Assuming I made a block copy of my EFS partition using "dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.sbn".
How would I restore it should I corrupt my EFS?
Like this?
dd if=/sdcard/efs.sbn of=/dev/block/mmcblk0p11
Click to expand...
Click to collapse
Correct.
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Or you can do the backup in one nice command:
dd if=/dev/block/mmcblk0p11 | gzip -9 > /sdcard/efs.gz
And to restore:
gunzip /sdcard/efs.gz - | dd of=/dev/block/mmcblk0p11
Oh, and you don't need to reformat the partition before restoring, that happens during the restore, because every bit gets overwritten.
Sent from my SAMSUNG-SGH-I747 using xda premium
bravomail said:
...make block copy of EFS and tar copy using adb:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.sbn
cd /sdcard
tar cvf efs.tar /efs
Click to expand...
Click to collapse
The TAR command failed for me on my i747, TAR not found.
d3athsd00r said:
Or you can do the backup in one nice command:
dd if=/dev/block/mmcblk0p11 | gzip -9 > /sdcard/efs.gz
Click to expand...
Click to collapse
This worked like a charm for me, thanks.
Hello. I was bricked my sm-p605, so I played enough. Can someone make full backup, I mean full - dd if=/dev/block/mmcblk0pxx /sdcard or so, I think I need all partitions, it doesn't mater what version of ROM, Please help me to fix it, Odin does not work, usb does't work to, I think I can flash it via twrp using "send terminal command" function with dd if=system.img of /dev/block/mmcblk0p23. And if you can please make files as partition names like dd if=/dev/block/mmcblk0p23 of=/sdcard(or so)/mmcblk0p23 or jus 0p23. Actually Odin does work, but I can't flash original firmware, I getting errors with sbl1.mbn. Sorry for my bad english and thanks.
I think I need repartition my device using right pit file, so do anyone know where can I get it?
Tautvaldas said:
Hello. I was bricked my sm-p605, so I played enough. Can someone make full backup, I mean full - dd if=/dev/block/mmcblk0pxx /sdcard or so, I think I need all partitions, it doesn't mater what version of ROM, Please help me to fix it, Odin does not work, usb does't work to, I think I can flash it via twrp using "send terminal command" function with dd if=system.img of /dev/block/mmcblk0p23. And if you can please make files as partition names like dd if=/dev/block/mmcblk0p23 of=/sdcard(or so)/mmcblk0p23 or jus 0p23. Actually Odin does work, but I can't flash original firmware, I getting errors with sbl1.mbn. Sorry for my bad english and thanks.
I think I need repartition my device using right pit file, so do anyone know where can I get it?
Click to expand...
Click to collapse
I need all packages except:
/dev/block/mmcblk0p23 \system
/dev/block/mmcblk0p26 \data
/dev/block/mmcblk0p14 \recovery
/dev/block/mmcblk0p15 /boot
So I think I need:
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21
/dev/block/mmcblk0p22
Please anyone help.
Can you not get your P605 to show up when you connect to Odin? Here is what I would do:
1. Try a different USB port
2. Try a different USB cable
3. Try a different pc
I see no reason why you should not be able to recover your tablet.
Download your firmware from here:
You just need to register to be able to download.
http://www.sammobile.com/firmwares/
Hi all.
Need some help with backup of
mmcblk0p2
mmcblk0p18
mmcblk0p25
mmcblk0p26
mmcblk0p33
mmcblk0p37
From T-mobile m8
For backup them need:
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2.img;
dd if=/dev/block/mmcblk0p18 of=/sdcard/radio_config.img;
dd if=/dev/block/mmcblk0p25 of=/sdcard/modem_st1.img;
dd if=/dev/block/mmcblk0p26 of=/sdcard/modem_st2.img;
dd if=/dev/block/mmcblk0p33 of=/sdcard/mmcblk0p33.img;
dd if=/dev/block/mmcblk0p37 of=/sdcard/mmcblk0p37.img;
Thanks.
PS: Its need for me, as I make gsm dead (no imei and unknown Radio in OS, in bootloader all present fine)
For this needed only terminal, not even root, and I realy apreciate any response.
To check which block causes this need backup from 2 M8 T-Mobile on 4.x.x.x FW (last)