Develop Bugs

[Request] How to flash system.img through ADB in CWM

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"

[ROOTED]Bell v20f .img files

Here is a link to the .img files. You can flash them using adb, but you will lose CWM. I am posting these in the hope that it will help someone who knows a little bit more about bootloader security and whatnot to make a CWM-compatible version.
The stock files are Here
Extract files to root of SD card, enable USB debugging and PC Software mode (if on LG rom)
Run the following from windows command prompt:
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/baseband.img of=/dev/block/mmcblk0p14
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
Restart,
Congrats, you've got the latest Bell release for the P930.
Got it rooted using this guide: http://forum.xda-developers.com/showthread.php?t=1835946
Used Rom Manager to install CWM.
Whenever I try to boot into CWM, i get the following error:
-------------------------------------------
Secure Booting Error
Cause : boot certification verify
-------------------------------------------
---------------------------------------------------
Enter the fastboot...
Enter the fastboot...
Long time no see!
---------------------------------------------------
Click to expand...
Click to collapse
The ROM boots though, and has root access. Superuser works, and I am currently using titanium backup to delete the massive amounts of bloatware present in the rom.
I have attempted to flash recovery.img with CWM on it, but the error persists.
Anyone have any ideas as to how we can get around this error?
Click to expand...
Click to collapse

hereric said:
Anyone have any ideas as to how we can get around this error?
Click to expand...
Click to collapse
You must downgrade to GB before you can install CWM properly.

I just wonder if it works if you just load boot.img and system.img with adb.

abc001 said:
I just wonder if it works if you just load boot.img and system.img with adb.
Click to expand...
Click to collapse
You're welcome to try. I am too busy today, and I have started getting random reboots, so I'm switching back to Liquid Nitro.

[Q] Cannot flash stock boot.img from fastboot

[EDIT] - adb commands work fine..
I am rooted and bootloader unlocked, trying to flash back to the stock kernel. I can boot into bootloader (fastboot mode), however when I issue the fastboot command from my pc, nothing happens like the usb connection is not recognized.
"fastboot devices" does nothing.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash boot boot.img
< waiting for device >
Is fastboot supposed to work?
Alternatively is there a recovery package somewhere that includes only the current stock kernel?
Thank you for your help.

You can actually use my all in one in the dev section to do it for you.
Sent from my LG-LS970 using xda app-developers app

TheShadow1 said:
You can actually use my all in one in the dev section to do it for you.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Shadow, thank you for your work! I jumped into your github to check out the code because I am not sure if the boot.img your app is downloading is the latest zv9 release kernel.
It looks like I can
1) drop boot.img into /sdcard/
2)issue the following from terminal on device (or from adb):
su -c dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
su -c dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
3) rm /sdcard/boot.img
4) reboot
EDIT: This worked great issuing commands in adb shell (grant su on the phone when it pops up)
THANKS!
Now I need to figure out how to get fastboot communicating

[TUT][HOW TO] Flash Recovey without use bootloader

Hi guyz! With this small guide I hope i'll explain to you how to flash a recovery without bootloader. C'mon!
1) Download the recovery
2) Extract the recovery image in the zip (normally the folder is named "pg76img.zip" and the recovery "recovery.img")
4) Download terminal emulator
5) Open Terminal Emulator
6) Write su and accept superuser request
7) write flash_image recovery /sdcard/recovery.img
8) if you'd like to try if recovery work write reboot recovery
9) enjoy!
-EDIT-
This script doesn't work with stock rom (sense roms)
Sent from my Wildfire S using xda app-developers app

This method won't work on Sense ROMs unless you install the flash_image script (Else you'll get not found or something similar).
Assuming you've already downloaded and installed Android SDK and that stuff, we can start:
1. Extract the script. Let's say you extracted it to your Desktop.
2. Connect your WFS with android debugging on.
3. Type the following:
Code:
adb root (enter)
adb remount (enter)
adb push Desktop\flash_image /system/bin (enter)
adb shell chmod 0755 /system/bin/flash_image (enter)
4. Flash your recovery. (In this case, your recovery.img is on /sdcard/)
Code:
adb shell flash_image recovery /sdcard/recovery.img
That's all. And there's no need to do this on CM-based ROMs as they already have this command script.

ScardracS said:
Hi guyz! With this small guide I hope i'll explain to you how to flash a recovery without bootloader. C'mon!
1) Download the recovery
2) Extract the recovery image in the zip (normally the folder is named "pg76img.zip" and the recovery "recovery.img")
4) Download terminal emulator
5) Open Terminal Emulator
6) Write su and accept superuser request
7) write flash_image recovery /sdcard/recovery.img
8) if you'd like to try if recovery work write reboot recovery
9) enjoy!
Sent from my Wildfire S using xda app-developers app
Click to expand...
Click to collapse
this won't work on stock roms....as stock doesn't have flash_image script....so mention in OP only for cm based roms....& ofcourse for stock based roms djoliver has already posted a tut

XT1635-03 Power On Straight Away Go To Bootloader Mode

Hi, I have a XT1635-03 and have an issue of power on button go to bootloader mode instead of go to system. Phone is unlocked and on modified logo.bin. Any idea how to fix this symptom?
Thank you.

Hi,
First boot to twrp recovery menu and connect your phone via usb. And in your computer open the adb fastboot command And type the following:
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
#but do a backup before! (just in case)
adb pull /dev/block/platform/msm_sdcc.1/by-name/misc misc.img
Sent from my VTR-L29 using Tapatalk

pocko said:
Hi,
First boot to twrp recovery menu and connect your phone via usb. And in your computer open the adb fastboot command And type the following:
adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
#but do a backup before! (just in case)
adb pull /dev/block/platform/msm_sdcc.1/by-name/misc misc.img
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Thank you, but I'm currently on stock ROM (retcn).
So I have to flash TWRP, perform the 'dd' command and flash back the stock ROM and the issue will be gone?
Update: Flashed the TWRP and tried the 'dd', it returned error of no such file or directory.
dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc': No such file or directory
Cheers.