Database Info

[Released][ROM][ODIN] ICS Stock firmware XXLQ9 repacked with CWM 6

Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)

Now I am stuck @ finding a proper file host to upload the files.

waiting for this!

Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2

Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.

coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.

Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2

UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.

xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.

Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.

So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.

Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.

UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??

vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.

Nice work! Thanks!
Sent from my GT-I9103

nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.

This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts

So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.

pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....

pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app

Get your own CWM recovery for newer devices and dont beg anywhere - 2 simple steps

Those who struggle to get CWM recovery for thier newer devices and who are facing problem on romdump your stock rom to get stock recovery.img here you have 2 simple steps to get your CWM recovery for your new device
Step -1
Creating A Dump\Backup
Note: Root Required
1. Set "Settings" -> "Display" -> "Sleep" -> "10 minutes"
2. Install or update "Busybox" from play store
3. Set your phone to "Airplane" mode
4. Make sure that the card is not less than 2Gb of free space
5. Use any one of the following:
BakupTool_sdcard.zip saves a backup copy on the path: /mnt/sdcard/backup_v2
BakupTool_sdcard2.zip saves a backup copy on the path: /mnt/sdcard2/backup_v2
6. Extract the BakupTool_* to sdcard. Full path to the file should be: / sdcard / gscript
7. Install program: /sdcard /gscript /"GScriptLite.apk"
8. Open the program "GScriptLite". Press "Menu button" -> "Add Script"
9. Set tick "Needs SU"
10. Click "Load file" and select "back_mt657x.sh"
11. Click the button "Save"
12. Tap on a new script, "back_mt657x.sh". After that give the program root permissions if asked and wait for 5- 10 minutes. Do not use the phone during the process.
A sign of a normal shutdown of the script is:
Message in the terminal:
100% Backup Complite!!!
Saved to / sdcard/backup_v2/GGGGMMDD-ChChmm
Star Time: hh: mm: ss; End Time: hh: mm: ss
The appearance at the root of SD-card phone the following structure of folders and files:
backup_v2
YYYYMMDD-hhmm
* BDRS-YYYYMMDD-hhmm
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
* misk
cache.img
cmdline.info
config.info
cpu.info
nvram.img
nvram.tar
ram.info
rom.info
* over
expdb.raw
full_preloader_part.raw
misc.raw
pmt.raw
sec_ro.raw
seccfg.raw
unknown.raw
boot.img
dsp_bl.img
ebr1.img
firmware.info
MT6577_a4_v2c.info
logo.img
mbr.img
preloader.img
recovery.img
system.img
uboot.img
data.img
step - 2
upload your stock recovery.img to get cwm recovery
kaushik Dutta has developed a clockworkmod recovery builder on the official site....
http://builder.clockworkmod.com/
so upload your stock recovery.img and get exact cwm recovery.img of ur device....and flash it.
if yours is a new devicw please select new device column.
thanks for this awesome build.
- after u upload your stock recovery.img on clicking fro new device just click on Build icon on the last of the page.....
- then u will be qued and u will gwt build number please save it for further refference...
- click proceed to that server and find ur build number,,,if it finished successfully u will see green icon on the left
- then click on your build number then click status there u will get something like this
Project recovery
Last Successful Artifacts
android_device_lge_cayman.zip 5.12 MB
inputrecovery.img 16.00 MB
manifest.xml 53.95 KB
recovery.img 6.92 MB
finally download recovery.img which is ur cwm recovery and flash it via Mobileuncle MTK tools which can be downloaded from playstore
If something goes wrong u can revert back ur rom or stock recovery itself by flashing ur stock recovery.img from the back up folder...or u can flash ur rom back using SP FLASH tools
IF i helped u please press thanks :victory::victory::victory:

anybody tried???
meanwhile how to extract stock recovery.img from stock ICS

I did test it. The image build does boot for me. But the build recovery i got this way did miss some *.ko files my device needed
The site is not new by the way..
Read here how to dump you're recovery...
http://forum.xda-developers.com/showthread.php?t=1935162

Re: clockworkmod for newer devices - now get CWM recovery for every android
[email protected] said:
I did test it. The image build does boot for me. But the build recovery i got this way did miss some *.ko files my device needed
The site is not new by the way..
Read here how to dump you're recovery...
http://forum.xda-developers.com/showthread.php?t=1935162
Click to expand...
Click to collapse
Dumping rom is bit confusing....because I'm a dentist...
Can u please explain in simple steps to get stock recovery.img
I'm having intex aqua flash which is new in the market but it has all the feature of high devices...
One more thing can I do this in windows? Or should I need linux?
Sent from my Aqua flash using xda premium

Trying this right now. Hope the recovery.img from a stock nandroid works.

Re: clockworkmod for newer devices - now get CWM recovery for every android
McJesus15 said:
Trying this right now. Hope the recovery.img from a stock nandroid works.
Click to expand...
Click to collapse
Share in simple steps to extract stock recovery.img after u successfully get ur cwm
Sent from my Aqua flash using xda premium

Re: clockworkmod for newer devices - now get CWM recovery for every android
drganbds said:
Share in simple steps to extract stock recovery.img after u successfully get ur cwm
Sent from my Aqua flash using xda premium
Click to expand...
Click to collapse
My device is different. Technically I have cwm recovery already. It's just only accessible through a fast boot command. This allows me to have a nandroid back up already so I just took the recovery.img from a stock back up
Sent from my Zio using xda app-developers app

check this thread is updated...

I tried this for a Lenovo IdeaTab A2109 to try and build a touch recovery. It already has a unofficial cwm recovery non touch, so I used that as the recovery.img. It put out 2 recovery.img's. One was a recovery.img and the other inputreovery.img. I'm not sure what one I should flash or if I'm supposed to flash both. Would it put out errors if it didn't work?
Thanks for this post and any help you can give.

linsalata28 said:
I tried this for a Lenovo IdeaTab A2109 to try and build a touch recovery. It already has a unofficial cwm recovery non touch, so I used that as the recovery.img. It put out 2 recovery.img's. One was a recovery.img and the other inputreovery.img. I'm not sure what one I should flash or if I'm supposed to flash both. Would it put out errors if it didn't work?
Thanks for this post and any help you can give.
Click to expand...
Click to collapse
Inputrecovery.img is wat u uploaded and recovery.img is wat u get as cwm recovery.
Sent from my Aqua flash using xda premium

drganbds said:
Inputrecovery.img is wat u uploaded and recovery.img is wat u get as cwm recovery.
Sent from my Aqua flash using xda premium
Click to expand...
Click to collapse
Oh OK. What about the question I asked about errors? Will it give any errors if the recovery wont work?
Thanks for the quick reply.

linsalata28 said:
Oh OK. What about the question I asked about errors? Will it give any errors if the recovery wont work?
Thanks for the quick reply.
Click to expand...
Click to collapse
If it gives error like black screen or volume key unfunction means it is not compiled properly but don't worry your device won't brick and u can revert back ur recovery by placing original.img on the root of phone storage and flash through mobileuncle tool..all the best
Sent from my Aqua flash using xda premium

Three Questions and I'm gonna try this out:
1. If the CWM recovery I build from CWM builder doesn't work, can I flash back the stock recovery by Mobile Uncle Tools, I mean won't it brick the device, can I still boot? I have a MT6577 device.
2. Does the script provided here backups up the stock recovery on Ice Cream Sandwich?
3. What else does this script do? Backup the whole phone?

ApplePriest said:
Three Questions and I'm gonna try this out:
1. If the CWM recovery I build from CWM builder doesn't work, can I flash back the stock recovery by Mobile Uncle Tools, I mean won't it brick the device, can I still boot? I have a MT6577 device.
2. Does the script provided here backups up the stock recovery on Ice Cream Sandwich?
3. What else does this script do? Backup the whole phone?
Click to expand...
Click to collapse
1. Yes u can reflash you stock recovery back via mobile uncle tool
2. Yes it will work on ICS
3. I have shown that wat the backup folder will have...it does full backup of your phone....
Sent from my Aqua flash using xda premium

Okay, Thank you.
I will try and update you on this.
Edit: After flashing recovery, I got blank screen in recovery mode.

thanx mate , really a helpfu guide i have Xtouch x714 with Allwinner A13 chip
before i tried many A13 CWM none of them worked not even boot , they nearly damage my tablet
thank god there is Phoneixcard i was able to revive it .
Anyway , your methode of getting the recovery.img from [gscript] did not work for me , it kept give me errors
even though it shows 100% complete
so i used another method to get my recovery.img , hence my tablet is an Allwinner A13 chip, so
i used [ Rom Dump ] which a small and powerful tool run it in Windows from [ http://www.techknow.me ]
it uses ADB so u have to be rooted and enable developer mode in your device and have ADB drivers in your PC
it backup image of your system and boot.img , recovery.img and data
so i used the extracted recovery.img in the site you provide me and i got my new recovery.img and flash it to my tablet via NovoTools 1.0
and i test it , it works like charm , thanx again mate really helpful

step 2 no working....website down?

Black Screen
When I flashed recovery made through it, it gave me a black screen Is there any way to fix this??

the online one is not working
i tried twice for micromax a84... i got the CWM recovery and flashed it via mobile uncle tools...but it didnt work

?
after hitting "build" it states
your build has been queued.The
build id is
9b42b141e21a35c4007c250f45ab2039
continue to the build sever
view the current build output
when i hit either option i get "HTTP ERROR 404.
can anyone else see my build id and if so can you download it and link it to me via PM.
or what can i do to get my image

Flashing kernel

can i flash custom kernel??? if yes , how to flash thunderzap kernel???

Firstly you have to have unlocked bootloader via flashtool (here's how to do it)
http://www.modaco.com/topic/364335-...sh-tool-unlockingrelockingflashing-stock-rom/
Then download Thunderzap zip file so put it into internal storage. From that zip extract .img file which you need (kk - kitkat, jb - jelly bean) and type of recovery - TWRP or CWM. That file flash via fastboot mode in flashtool. Then boot into recovery and install that zip which you have in internal storage.. follow instalation progress instructions. That's all.
If youre complete beginner and absolutely don't know what to do do not flash custom kernel you can damage your phone.

Kosa02 said:
Firstly you have to have unlocked bootloader via flashtool (here's how to do it)
http://www.modaco.com/topic/364335-...sh-tool-unlockingrelockingflashing-stock-rom/
Then download Thunderzap zip file so put it into internal storage. From that zip extract .img file which you need (kk - kitkat, jb - jelly bean) and type of recovery - TWRP or CWM. That file flash via fastboot mode in flashtool. Then boot into recovery and install that zip which you have in internal storage.. follow instalation progress instructions. That's all.
If youre complete beginner and absolutely don't know what to do do not flash custom kernel you can damage your phone.
Click to expand...
Click to collapse
can u give me extracted .img for jb????

Here is it

Kosa02 said:
Here is it
Click to expand...
Click to collapse
thanks, can u give me thunderzap kernel???

RootLord said:
thanks, can u give me thunderzap kernel???
Click to expand...
Click to collapse
It's included in the post above, flash it via flashtool & install the zip file in recovery.

Joery360 said:
It's included in the post above, flash it via flashtool & install the zip file in recovery.
Click to expand...
Click to collapse
zip file is included in it.I should extract it???

First copy that zip file copy to internal storage in phone. Then flash the kernel as @Joery360 said. Then boot into CWM and install that zip. You have to install it because of wifi modules. Without this install you wouldn't have working wifi.

Joery360 said:
It's included in the post above, flash it via flashtool & install the zip file in recovery.
Click to expand...
Click to collapse
Kosa02 said:
First copy that zip file copy to internal storage in phone. Then flash the kernel as @Joery360 said. Then boot into CWM and install that zip. You have to install it because of wifi modules. Without this install you wouldn't have working wifi.
Click to expand...
Click to collapse
In brief??? its a img file??
But u didn't give me zip file??? I don't know much about it so asking plz help
Sent from my C2104 using xda app-developers app

Here is link to zip file. http://forum.xda-developers.com/devdb/project/dl/?id=4856 download it and the rest is above.

I'm just browsing thru here trying to become more educated in all this.
I'm just saying, none of the explanations make sense in this post.
Really?
Flash this, install that, extract, etc etc.
Please rephrase.
Sent from my GT-N7105 using xda app-developers app

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]

Question I need to go back to stock kernel

Anyone have vendor_boot, dtbo and boot.img from 11.2.9.9 le25aa ?. Install a custom kernel and I need to go back to stock

Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.

gorilla p said:
Just use oxygen updtaer to download full zip and do a local install. Flash magisk to alternate partition and reboot.
Click to expand...
Click to collapse
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?

Partigiano0105 said:
Install the Arter kernel. And now I get an error when I want to update that way. So I need to go back to stock rom.
Do you know any way to do that?
Click to expand...
Click to collapse
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot

mattie_49 said:
Shouldn't be flashing a kernel without proper backups first. You need stock untouched boot.img and vendor_boot
Click to expand...
Click to collapse
how can I do that?

You can download the zip file containing th full update of your version in a thread here, them using the payload dumper tool you extract all img files inside

I don't know how to edit so more details about this process:
1. Go to sticked thread Repo of oos builds
2. Download the zip file of the firmware you are using
3. Download the payload dumper here: https://androidfilehost.com/?fid=818070582850510260
4. Once extracted extract the payload.bin from firmware zip into payload_input directory
5. Launch payload_dumper.exe
6. Process take few minutes depending on your computer, result img files are stored in payload_output directory
7. Have fun with your img file