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.

Help for unbrick ZTE Nubia Z7 Mini....:(

After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......

i flash manually the files from recovery so now im ok.
Steps
1)Download this file (has everything you need) http://d-h.st/RLS
2)Unzip it
3)Boot Into recovery
4)Open a command promt on the unziped folder
5)Copy paste one by one these commands into command promt
Code:
adb shell mkdir /storage/sdcard1
adb shell mount /dev/block/mmcblk1p1 /storage/sdcard1 -t vfat
adb push part1.sh /tmp/part1.sh
adb shell chmod 0777 /tmp/part1.sh
adb shell /tmp/part1.sh
adb push persist /storage/sdcard1/persist
adb push customfs /storage/sdcard1/customfs
adb push fsg /storage/sdcard1/fsg
adb push fsc /storage/sdcard1/fsc
adb push ssd /storage/sdcard1/ssd
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/persist if=/storage/sdcard1/persist
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/customfs if=/storage/sdcard1/customfs
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsg if=/storage/sdcard1/fsg
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsc if=/storage/sdcard1/fsc
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/ssd if=/storage/sdcard1/ssd
You are ready

i have same problem with z7 max but in mine situation i cant see sim cards
can i use the same?

Petros_tigra said:
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
Click to expand...
Click to collapse
hi ,
i have zte nubia z7 mini and i was installing z5s mini miui rom in my phone. when the process done phone went to off and hard to turn it on. when i connect to pc it doesn't even detect the phone usb and asking for installing phones usb drivers... please help me if its possible

Thank you Sir!
Your intelligence has saved my Z7 Max running stock ROM v1.59. Now the WiFi and Bluetooth is working as usual....

Can you please help me about this, i tried to repartiton the phone and i got the same situation phone works but wifi and bluetooth doesnt work, i try to download that link but it says link doesnt work any more files are missing. can you please help me about this.

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.