Database Info

How To flash [ SYSTEM.IMG ] using TWRP

Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _

vinay durva said:
Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
Click to expand...
Click to collapse
TWRP can flash .img files without having to do anything special.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
TWRP can flash .img files without having to do anything special.
Click to expand...
Click to collapse
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img

vinay durva said:
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
Click to expand...
Click to collapse
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Click to expand...
Click to collapse
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img

vinay durva said:
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
Click to expand...
Click to collapse
I remember now that TWRP doesn't flash system.img correctly, system.img isn't a standard .img, you need PC and use fastboot.
Sent from my SM-S903VL using Tapatalk

Thanks Sir.. Any Another way to flash system , i don't have A PC

vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I wouldn't try it without PC
Sent from my SM-S903VL using Tapatalk

vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.

Aex12 said:
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Click to expand...
Click to collapse
hi aex, I have the same problem but I dont have the folder
/bootdevice/by-name............
can you help me?

it will not work.
try to make a folder and "mount -o loop file in it.
and it will be not mounted also if you specify file system type.
(if it work probably you can use the file)
so ,i don't know how fastboot write in partition or probably
in to file system.
however if you do a dd of your current system partition in a file , after will be correctly mounted , or rewrited correctly in the original partition if you need.
then probably you cannot use fastboot system.img directly in twrp shell (using dd)
this is my experience (e2303 sony / pexorom 3.0 twrp 3.1.1)
if you are searching a fast way to know system partition device block
cat /etc/fstab
and look for system
or just mount system in twrp , then in a terminal do a
df -h
and search for system
for e2303 was /dev/block/mmcblk0p30
(example)
twrp have busybox and light kernel.
so , is linux.
for better support try to ask
tonystark88

u need to use simg2img
(sparse file format compression)
system partition device name can be different on other phones.
done.
img can be write by twrp whitout pc/fastboot.
c'ya
giuseppe

just go to file manager and search for system partition, and on first part type your system.img location and 2 part type just system location

I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?

chr2002 said:
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
Click to expand...
Click to collapse
Why not just use the settings in Kingroot to remove root? Or convert from Kingroot to SuperSu then use SuperSu app settings to remove root?
You don't have to flash the stock system to remove root.
Sent from my LGL84VL using Tapatalk

Kingroots uninstall leaves traces in /system/xbin and Safetynet wont work. Why i did not try Supersu ? :-/
But i managed to flash the system.img without problems.
First i tryed an extracted system.img from the Huawei Firmware extractor and Sim2img reported an invalid sparse image. So i thought it must be a raw image.....And this was my mistake. It is a useless image for TWRP.
So i created a flashable zip (TWRP cant flash this, too and the /system partition is not mountable after flashing / installing this zip.
BUT, the system.img INSIDE this zip is a spase image, which sim2img can handle. It gave me a nice raw image which i just dd´d to /system and BINGO, my phone starts up normally
The Short Version :
- Create a FLASHABLE ZIP with the Huawei Firmware Extractor
- use SIM2IMG in TWRP Terminal to get a RAW Image.
- dd´it to the /system partition

System img
You use the restore in twrp to flash your system img, you just until the other boxes

Edit: Sorry wrong thread

Lenovo K5 Pro ROM img
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?

Help u
Hi u can download a deodexed rom because ais doesn't support some stock roms for ex ch Samsung roms. then decompile it.then decompile it with rar or zarchiver or etc. Then install android image studio (ais) from google
Then open it and tap unpack/mount and select system.img or system.img.ext4 file in decompiled rom . After mounting, copy all files to a directory for ex emulated/0/system/system or another. Attention if you copy it in another directory, rename it as (system) now copy the boot.img from decompiled rom into emulated/0/system .then download this file
https://forum.xda-developers.com/an...oid-o-beta-redesigned-emoji-set-t3608280/amp/
Extract meta-inf file into emulated/0/system using winrar or zarchiver or etc. Now you need to have a system folder,boot.img file and a Meta-inf in diractory emulated/0/system. Now compress system,boot.img and meta-inf into one archive and after completing, turn of your device and boot it into twrp recovery and wipe data and cache without wipping internal storage then select install. Then tap select storage and select internal storage.then go to the file and select it and turn off zip singuature verification and install it after installing tis rom, install root zip file and wipe cache/dalvik art and then reboot your device. It may take between 5-25 minutes to boot. Enjoy your new rom
#issues
Sometimes your device maybe take bootloop so you need to install your stock boot.img file and after installing your root zip file choose wipe cache/dalvik art and then reboot your system.
#Alert
1.Don't install the recovery.img file which exists in the decompiled rom because it takes your device into recovery mod and not boot anymore and after you need to install the stock rom using PC
2.your device maybe take bootloop in this method so do it with your own risk
---------- Post added at 07:58 AM ---------- Previous post was at 07:53 AM ----------
ShmuelCohen said:
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Reboot your device and install twrp official app and open it and select flash image from a directory and select your own twrp and reboot your device [root]
Connect your phone to a PC and install stock rom using ADB or another app which was made for your smartphone [no root]

Note 3 neo boot loop. Nand erazed. No backup.

hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide

@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/

SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab

1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too

Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.

RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!

MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here

[Guide] How to unpack/repack diffrent img files easily without pc.

Hey, today in this post I've discussed on the topic
"How to unpack/repack img without PC or android tools (android tool is a little complicated and sometimes doesn't works)."
So let's get started
First of all download & install 'android image studio'
1: open it and click on repack/unpack
2: select the port ROMs boot or recovery img.
3: we get two folders
a.) Split_img --->> contains kernal zimage.
b.) Ramdisk----> contains init.rc recovery. Fstab etc..
4: to delete any file long press on it and click delete
5: to import any file click on import button in right panel & select the file
6: after making desired changes. Repack the img using repack button
7: a file will be created with the name image-new.img
8: export this file using export button and select the desired location.
Congratulations you have just ported an img without PC easily.
Link for the tool: https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
Link to my video toitorial for better understanding on this:
If you liked it just PRESS the THANKS button

I need more help, trying to open a .IMG boot file for Samsung s5, it gives the "No Image Supplied" error

Screenshot

Using AIS. Trying to port custom recovery but first thing I've tried is to just unpack and repack stock recovery. When repacking output of AIS is new IMG and new ramdisk. New IMG is smaller than original but from what I've read this should be okay. Flashed new IMG and attempted reboot recovery and all I got was black screen. Flashed stock recovery and it booted recovery fine. Not sure what I'm doing wrong. I used AIS to open the new image it created and then kept doing file/folder comparisons on the output. I narrowed down the difference being recovery.img-ramdisk.cpio. But when I unpack with cpio the contents of the archive are the same. Additionally, I repacked the contents with cpio but it still comes up as not matching the original recovery.img-ramdisk.cpio. My device can and does make replacement recovery images using applypatch with bonus files and boot img. Any help greatly appreciated!

[GUIDE] How to Change Boot Logo (Splash Screen) of Razer Phone (cheryl)

Note:
This is not bootanimation, this is the splash screen (the boot logo which is displayed when device is switched ON)
This is for Razer Phone Only.. (codename: cheryl)
(For other devices, please send me your splash.img so that I can create a tool for you too..)
Requirements:
1. Rooted Razer Phone (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Razer_Phone_Cheryl_Splash_Maker.zip
2. Make sure you have a picture with resolution 1440x2560px.
Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
3. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@game_guy who provided the stock splash.img of Razer Phone (cheryl)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..

You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.

RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Splash screen is different from boot animation. The one which appears before boot animation

Oops sorry, brain fart.
I guess I wasn't paying attention all that well.

@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?

linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed

eoghan2t7 said:
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
Click to expand...
Click to collapse
Nope, the splash screen is just a BMP picture (in RGB24 format) with an empty 16kB header before the picture.
You could see that in the batch file's code.
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
The warning message actually is from the bootloader itself.
Most probably, it will be present in the 'aboot' partition, but it's not as easy as changing splash screen.
The same issue was also present in Nextbit Robin. (a company acquired by Razer)
Because, the bootloader is just a raw file when dumped, which needs to be checked using hex editor or whatever tool to see if it has an image and find its offset and patch the image accordingly, or even, it might be possible to find the location of where the amount of warning time is present and make it 0.
But the problem is, since it's a raw dump and the bootloader is the code that brings up the kernel, it's highly possible that if we do something wrong, the device might be hard-bricked (even fastboot mode is from bootloader). Also, today's bootloaders might even be signed, so patching the bootloader for warning picture might not necessarily work since the device won't be able to verify the integrity of bootloader partition after its contents change.
So, if there's a tool with which you can flash and recover a hard-bricked phone, and if you're willing to test the modified bootloaders that I create, send me the bootloader partition dump. I'll take a look at it

@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)

linuxct said:
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
Click to expand...
Click to collapse
Lol I remember doing stuff with my Droid RAZR and Bionic for dhacker back in the day. It was worth it in the end, but took time for the recover from hard brick processes to come about.

RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Hi, can you please upload and share the default bootanimation here? I have deleted mine and would like to get it back.

Solve fastboot: error: the boot partition is too smaller

I am trying to root my tecno f1 pro with magisk manager soon i was flashing the magisk_patched.img renamed boot.img i got an error
code:
C:\Program Files\platform-tools>fastboot flash boot boot.img
fastboot: error: boot partition is smaller than boot image
How can I fix this?

Re-partition Android of your phone so the boot.img fits.

jwoegerbauer said:
Re-partition Android of your phone so the boot.img fits.
Click to expand...
Click to collapse
How do I do that? My boot partition is 233kb and my Magisk patched image is 32mb.

Beelzebub6 said:
How do I do that? My boot partition is 233kb and my Magisk patched image is 32mb.
Click to expand...
Click to collapse
You have a wrong file patched. Normally the patched file can with 10MB or more.
Since you wrote the patched file have ONLY 233KB so never you can flash that!

DragonPitbull said:
You have a wrong file patched. Normally the patched file can with 10MB or more.
Since you wrote the patched file have ONLY 233KB so never you can flash that!
Click to expand...
Click to collapse
lol, my phone has updated since then, your right.
But then I downloaded my new stock rom which is android 11 and tried to continue with that but it still says the boot partition is too small. How would I re-partition so then my patched file can fit?
And also the original boot file straight outta boot.img.lz4 is 32.0mb same as patched but inside the .lz4 file it says that it is 16 bytes, should I worry about that?

Beelzebub6 said:
lol, my phone has updated since then, your right.
But then I downloaded my new stock rom which is android 11 and tried to continue with that but it still says the boot partition is too small. How would I re-partition so then my patched file can fit?
And also the original boot file straight outta boot.img.lz4 is 32.0mb same as patched but inside the .lz4 file it says that it is 16 bytes, should I worry about that?
Click to expand...
Click to collapse
I think thats just compression saying that but if u need try backup the boot partition via another method