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"

[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

I need you help guys! I need d855 laf.img

Guys please help me, i need laf.img, i lost my download mode
just do this for me:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of =/storage/external_SD/laf.img # backup the stock recovery to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-recovery.img . # backup the recovery image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
EDIT: SOLVED! I manage to pull it out, i dont know how i did it, my hearts pumping like hell. GOSH! ALMOST A BRICK, GOODTHING I FIXED It.

Please help me!

Hey ehm.. just wanna ask if you still have the laf file ? Would be nice if u can send it to me.
I have the same problem... ^^ lost my dl-mode too

Guys!
Stop flashing ROMs if u dont know what you are doing....

niko626 said:
Guys please help me, i need laf.img, i lost my download mode
just do this for me:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of =/storage/external_SD/laf.img # backup the stock recovery to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-recovery.img . # backup the recovery image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
EDIT: SOLVED! I manage to pull it out, i dont know how i did it, my hearts pumping like hell. GOSH! ALMOST A BRICK, GOODTHING I FIXED It.
Click to expand...
Click to collapse
download fastboot&adb
download rom 10l kdz
extract kdz rom
rename laf.bin tu laf.img
copy laf.img tu sd memory&fastboot folder
run.bat in fastboot folder select
tipe: fastboot boot laf.img
run download mod
flash kdz rom
enjoy

I have the same problem. you can tell me how to fix, i lost download mode
with "adb shell", i have "error: device not found"
with "fastboot boot laf.img", i have "waiting for device"

Flash TWRP
IMANX2 said:
download fastboot&adb
download rom 10l kdz
extract kdz rom
rename laf.bin tu laf.img
copy laf.img tu sd memory&fastboot folder
run.bat in fastboot folder select
tipe: fastboot boot laf.img
run download mod
flash kdz rom
enjoy
Click to expand...
Click to collapse
I have the same problem. Can you tell me how to fix, i lost download mode
you can flash TWRP? or alternatively by the terminal always TWRP?
If you could write the commands?
thank you

hello
its very simple
just install AUTOREC.apk to uor phone & flash stock recovery
after that enter to recovery mod & do factory reset
your phone now have download mod

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.

[HowTO] Get rid of annoying "Kernel is not seandroid enforcing" message....

Hi,
I started to play with kernel hacking/configuration and I found the annoying red message
After a lot of research i found that we can get rid of it by adding at the end of boot.img file the SEANDROIDENFORCE text string, as following
echo SEANDROIDENFORCE >> boot.img
Best regards,
Marc

serdeliuk said:
Hi,
I started to play with kernel hacking/configuration and I found the annoying red message
After a lot of research i found that we can get rid of it by adding at the end of boot.img file the SEANDROIDENFORCE text string, as following
echo SEANDROIDENFORCE >> boot.img
Best regards,
Marc
Click to expand...
Click to collapse
Thanks.. Work bro..

diphons said:
Thanks.. Work bro..
Click to expand...
Click to collapse
Yeah, I'd like recommend to find a solution to get also rid of "set warranty bit kernel/recovery", the yellow warning is really annoying!

I was able to append the boot.img file with SEANDROIDENFORCE text string.
But how do you exactly write it back?
I'm on samsung note 4.
Code:
adb reboot recovery
adb shell
dd if=/dev/block/bootdevice/by-name/BOOT of=/sdcard/boot.img
echo SEANDROIDENFORCE >> /sdcard/boot.img
If i try to switch if and of path, I get an error
Code:
dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/BOOT
dd: writing '/dev/block/bootdevice/by-name/BOOT': No space left on device

UnknownPlanet said:
I was able to append the boot.img file with SEANDROIDENFORCE text string.
But how do you exactly write it back?
Code:
adb reboot recovery
adb shell
dd if=/dev/block/bootdevice/by-name/BOOT of=/sdcard/boot.img
echo SEANDROIDENFORCE >> /sdcard/boot.img
If i try to switch if and of path, I get an error
Code:
dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/BOOT
dd: writing '/dev/block/bootdevice/by-name/BOOT': No space left on device
Click to expand...
Click to collapse
In order to write the boot.img you need to use fastboot/bootloader mode of your device, adb reboot bootloader, then use `fastboot flash boot boot.img`
Alternatively, you can put the boot.img on your /sdcard boot to twrp then `cat boot.img > /dev/your/boot/partition`
The no space left on the device means that your file is bigger than the destination which is unusual if you built that boot img, from your example it seems that you save your partition and do not use a built boot.img

serdeliuk said:
In order to write the boot.img you need to use fastboot/bootloader mode of your device, adb reboot bootloader, then use `fastboot flash boot boot.img`
Alternatively, you can put the boot.img on your /sdcard boot to twrp then `cat boot.img > /dev/your/boot/partition`
Click to expand...
Click to collapse
It doesn't work, I'm on samsung note 4. I also have latest TWRP installed.
fastboot device keep saying:
< waiting for any device >

UnknownPlanet said:
It doesn't work, I'm on samsung note 4. I also have latest TWRP installed.
fastboot device keep saying:
< waiting for any device >
Click to expand...
Click to collapse
you need to find how to boot your device in bootloader mode, usually volDOWN+power together

serdeliuk said:
Alternatively, you can put the boot.img on your /sdcard boot to twrp then `cat boot.img > /dev/your/boot/partition`
Click to expand...
Click to collapse
Still error
Code:
~ # cat /sdcard/boot.img > /dev/block/bootdevice/by-name/BOOT
cat: write error: No space left on device
serdeliuk said:
The no space left on the device means that your file is bigger than the destination which is unusual if you built that boot img, from your example it seems that you save your partition and do not use a built boot.img
Click to expand...
Click to collapse
I use Custom ROM of Hani Base v1.01 here:
[ROM][6.0.1][TW][N910C/H/U] Hani Base v1.01 [18-04-2016][Deodexed][PreRooted]
Welcome to Hani Base ROM thread! Samsung Galaxy Note 4 SM-N910C N910CXXU2DPCB TW 6.0.1 THREAD INDEX: I. INTRODUCTION II. FEATURES III. DOWNLOADS IV. HOW TO FLASH #_____________________________# #include ...
forum.xda-developers.com
I have succcessfuly get and edit the boot.img but I don't know how to flash it back. Forking to make another whole custom ROM is not an option. I won't learn anything.
It's just a tiny append why so difficult.
serdeliuk said:
you need to find how to boot your device in bootloader mode, usually volDOWN+power together
Click to expand...
Click to collapse
There's no bootloader in my samsung note 4, adb reboot bootloader goes to system instead.
Home+Power+VolumeDown enters the download mode, but even then fastboot device still doesn't respond.
Do I need to use Odin or what?

You may need to ask questions about your boot options on the dedicated channel for your device, i do not own such device, but download mode is the fastboot mode as far as can remember, "fastboot devices" should show your device listed when in download mode.
Your steps to flash the boot.img fail because the file is bigger than your boot partition, does not fit there, you may need to seek for help form the img developers to see what to do. You can try to flash the boot.img on recovery partitions which is usually bigger and reboot to recovery, but pay attention, if you don't know how to go back to fastboot mode you are stuck with a bricked device

I was able to flash it without any change in the boot partition size by editing it manually using hex editor.
These are my steps
Code:
adb reboot recovery
adb shell "dd if=/dev/block/bootdevice/by-name/BOOT of=/sdcard/boot.img"
adb pull /sdcard/boot.img
I use Frhed hex editor to edit the last 16 bytes of boot.img into SEANDROIDENFORCE
Code:
adb push boot.img /sdcard/boot.img
adb shell "dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/BOOT"
The problem right now is that, the red text is still there. What should be my next step?

UnknownPlanet said:
I was able to flash it without any change in the boot partition size by editing it manually using hex editor.
These are my steps
Code:
adb reboot recovery
adb shell "dd if=/dev/block/bootdevice/by-name/BOOT of=/sdcard/boot.img"
adb pull /sdcard/boot.img
I use Frhed hex editor to edit the last 16 bytes of boot.img into SEANDROIDENFORCE
Code:
adb push boot.img /sdcard/boot.img
adb shell "dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/BOOT"
The problem right now is that, the red text is still there. What should be my next step?
Click to expand...
Click to collapse
I don't know if editing the boot.img works, probably should do, however, i found this solution poking around with third party device trees and worked for my samsung galaxy tab, if do not work on your phone then you may need to dig a bit deeper, however, if you use a third party image maybe you ask them why you have that on your screen, maybe they have another fix. Probably a bit of more info can be found here https://github.com/osm0sis/dhtbsign but i didn't spent time to read it. You can ask the developer about more info.

Your solution of device tree / dhtb is impressive on it's own, that's another big learning curve.
But I think I know the problem, because the Custom ROM Hani Base above is using H-Vitamin Kernal which is SELinux Permissive. No matter how I edit the boot.img file the red text message will always appears, unless I flash it with another kernel which is SELinux Enforcing.
UPDATE
This is even weirder.
By updating SuperSU into the latest version, the red text is missing from system mode. It still persist in recovery mode tough, because, well twrp need full access to begin with.
No Magisk here, it was an old custom ROM.
All official app from playstore is now gone but the official xda thread still remain:
[STABLE][2017.05.27] SuperSU v2.82
*** Urgent Update Notice *** We are deeply sorry about the installation errors and failures happened in v2.80. The new update v2.81 has rolled out on XDA and Play Store to fix the problem occured in v2.80. Chainfire has also...
forum.xda-developers.com
From reading the last pages of the thread, I got the official site of chainfire to download it.
SuperSU Download
The file name is
sr5-supersu-v2.82-sr5-20171001224502.zip
Just flash it with latest TWRP and you're done.
I still don't understand how could updating SuperSU could fix the problem.
But what a long journey, thank you so much @serdiluk , I learn so much things.