Database Users

Flash any kernel or modem on CWM

- I made some ZIPs with scripts for you to flash any kernel or modem on CWM.
- It's simple, just drag and drop your file to the correct ZIP.
#Put zImage on the "Flash Kernel [zImage]"
#Put boot.img on the "Flash Kernel [boot.img]"
#Put modem.bin on the "Flash Modem [modem.bin]"
1. Extract the ZIPs from the 7z file first.
2. Just open your ROM file [Cyanogenmod {Also other AOSP, AOKP, etc...}, Samsung Stock, Samsung-based], extract the file, and drag and drop to the ZIP, then you install on CWM Recovery, very simple,
Download

in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?

Good work Marcello
Enviado do GalaxyS2 usando Tapatalk 2.1.3

LogeshMenon said:
in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?
Click to expand...
Click to collapse
There are just binary and script, no need for certs. Just drag and drop or extract and compress the file you want to flash,

Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412

stone_ship said:
Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412
Click to expand...
Click to collapse
No. Never had any problems. And maybe those libs are already inclued in the ROM, don't know. And all I know is that boot.img = zImage. I've seen a thread saying that you can rename boot.img to zImage.

Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.

jjcoolaus said:
Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.
Click to expand...
Click to collapse
This is very old. If you tried on your S3 lte, of course it won't work. Be more careful next time,
Sent from my GT-I9300 using xda premium

[GUIDE][18th Dec][4Noobs] Flashing a Custom Rom & Kernel Using Fastboot

Installing Custom Rom and Custom Kernel
Pre-Requisites
Download Any Custom Rom For Your Device From XDA.
Download Any Custom Kernel For Your Device.
Have a device with a unlocked bootloader.
Download this fastboot package.
We will refer to the downloaded custom kernel as [highlight]CKernel[/highlight] and the Custom Rom as [highlight]CRom[/highlight].
Flashing the Custom Kernel
Copy the [highlight]CROM.zip[/highlight] file to your sd card
Extract the Fastboot package to a folder and copy the [highlight]CKernel.img[/highlight] file to the same location.
Shift + Right Click the folder and press "Open Command Window Here".
Reboot your phone in to fastboot (Press search and connect USB cable , may be different for some 2011 devices).
Blue LED should be switched on. This means your in fastboot. Now you need to type.
Code:
fastboot flash boot CKernel.img
After a few seconds it should be done and say "Completed" or something similiar.
Installing A Custom Rom
Reboot your phone in to recovery (Keep Tapping Vol Down or Back or Another key when device is booting).
Format the phone "Factory Reset".
Next press "Install Any Zip From SD Card".
Select the [highlight]CRom.zip[/highlight] file that we copied over earlier and press yes/accept/apply.
After a few minutes it should be done and say "Installed or Applied or Success".
Now reboot your phone and wait patiently.
If everything is done correctly then you should now be running your [highlight]CRom [/highlight]​e.g. AOKP, CM, MIUI, Etc.
Installing Google Apps (may not be needed depending on the ROM)
Download the latest google apps that corresponds with your android version from goo.im/gapps.
Copy the download zip to your SD Card.
Reboot your phone in to recovery (Press the button you pressed earlier while phone is at the logo again).
Next press "Install Any Zip From SD Card".
Select the GoogleApps*.zip or GApps.*.zip file and press yes.
After a few minutes it should be done and say "Installed or Applied or Success".
Now reboot your phone and wait patiently.
You now should be running your custom kernel, custom rom and have the latest gapps installed.
[no longer linking tutorials to my site as currently messing around with my site so links may break, to prevent this i will post them here since i found a html to vbcode converter aswell ]

Thanks... But you need to change
Copy the CKernel.zip file to your sd card
Click to expand...
Click to collapse
to
Copy the CRom.zip file to your sd card

Could you please include an example?
Because Lupus Kernel + Cyanogenmod doesn't work for me.
Error Status 7 (tried both latest 7 and 9)
Lupus recovery itself works(and since it still boots i guess so does the kernel itself), but flashing Cyanogenmod doesn't.

What lupus kernel are you using? If youre using lups v8 then choose aosp ics under boot menu of whatever slot your using. If your using lupus v10 or lupus ics/gb those dont work with cm9 so those could be your problems
Sent from my Xperia Play (r800x)

LuPuS_zeus_ICS-GB_v3-ram(2) is the one i'm using.
I got it from here: http://forum.xda-developers.com/showthread.php?p=38988056
and choose it because it was the only still supported one for android 4 without beta in the name.
So i have no idea.
btw: cm7 doesn't work either, same error.

Beta means it supports the stock ics beta rom not the kenels a beta. Lol use lupus jb v8 or turbo kernel 3.1. Both support cm9. You just have to choose it under rom type when going into recovery
Sent from my Xperia Play (r800x)

turbo: can't use it because it requires the flashtool that doesn't work
v8: tested, nice but unusable with cm9 because of graphic glitch and doesn't find the sd card (and bootloop + graphic glitch with CM7)
ALso another problem:
The phone doesn't enter fastboot anymore, lupus goes into recovery instead...

543563465643534 said:
turbo: can't use it because it requires the flashtool that doesn't work
v8: tested, nice but unusable with cm9 because of graphic glitch and doesn't find the sd card (and bootloop + graphic glitch with CM7)
ALso another problem:
The phone doesn't enter fastboot anymore, lupus goes into recovery instead...
Click to expand...
Click to collapse
Try the fxp kernel. Just extract it from the rom zip and flash. Also to get the kernel to stop booting remove the battery and wait 30 seconds. Then put it back and quickly enter fastboot by plugging in and holding search button.
Sent from my Xperia Play (r800x)

Since when does turbo kernel REQUIRE flashtool?
Sent from my R800i using Tapatalk 2

@fma965
this guide:
http://forum.xda-developers.com/showthread.php?t=1817548
Step 1 GSM (Germany)
requires an ftf file which i thought requires the flashtool for using.
@abdel12345
Freexperia?
Is it the boot.img?
I'm new to this flashing thing, last time i did it(on my magic) there was just the romand no manual Kernel messing.
btw, fastboot works now, seemed to be a problem with the cheap micro USB cable. I also really appreciate your help, thank you guys.
Everything works now with CM9 and FXP Kernel!

543563465643534 said:
@fma965
this guide:
http://forum.xda-developers.com/showthread.php?t=1817548
Step 1 GSM (Germany)
requires an ftf file which i thought requires the flashtool for using.
@abdel12345
Freexperia?
Is it the boot.img?
I'm new to this flashing thing, last time i did it(on my magic) there was just the romand no manual Kernel messing.
btw, fastboot works now, seemed to be a problem with the cheap micro USB cable. I also really appreciate your help, thank you guys.
Everything works now with CM9 and FXP Kernel!
Click to expand...
Click to collapse
Wrong link? that is turbo kernel thread and no mention of "Germany" ???
Yh the boot.img, Recovery is on the kernel partition so you can't flash a kernel from the recovery aka the kernel partition, i think this is correct??? if not then any 1 feel free to correct me

That's correct, but Germany is one of the countries using "GSM" not "CDMA", that's what i meant.
But thanks for the help and the short guide(but is still think a total newb tutorial should include an example if 2 or more components are needed).

Thank You. This worked for me today.

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.

*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this

*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.

Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?

Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847

Thanks for the guide
Appreciate the work. What gapps are you using.

Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.

ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)

Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app

@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus

oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app

can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx

cos 12.1 firmware corrupt every time i download

i just wanna revert back to cos 12.1...so downloaded cos 12.1 fastboot file from cyanogen support...
this link - http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS7DF-ham-signed-fastboot-fb41353cf8.zip
but the file corrupted every time i download even tried i my friends pc but the result is same... it says file is corrupt in the middle of extraction...tired winrar, 7zip, universal extractor none of then worked giving same error...
iam using cm13 nightlies right now....
need help...

Kounjula Rahul said:
i just wanna revert back to cos 12.1...so downloaded cos 12.1 fastboot file from cyanogen support...
this link - http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS7DF-ham-signed-fastboot-fb41353cf8.zip
but the file corrupted every time i download even tried i my friends pc but the result is same... it says file is corrupt in the middle of extraction...tired winrar, 7zip, universal extractor none of then worked giving same error...
iam using cm13 nightlies right now....
need help...
Click to expand...
Click to collapse
Try the non-fastboot version and flash it using TWRP. It worked for me.

Flashing stock rom gives Treble Compatibility error

Hello.
I'm trying to get my phone back to stock rom.
I'm using the TWRP from the [All In One] post: https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
And I'm trying to install the file I got from: http://en.miui.com/download-360.html
But when I flash the file (miui_LAVENDERGlobal_V10.3.5.0.PFGMIXM_a5cabeca22_ 9.0.zip) I get the error attached.
Can anyone help me with this error?

Download the zip file again from miui.com, if you’re using a custom rom go to ‘Wipe’ -> ‘Advanced Wipe’ and wipe the ‘Cache’, ‘Dalvik/ART Cache’, ‘Data’ and ‘System’ partitions.
Once you are done, go back and tap on the ‘Install’ button and browse the rom file.
If this doesn't work, try the fastboot method with the miui flash tool.

delete compatibility.zip in rom file and flash normally

Thanks for the replies. I already formatted and wiped, and tried redownloading the stock rom file, but got the same error. I also tried the MIUI flash tool but got an error after doing the last step.
However... I did end up fixing the problem moments ago.
As I was leaving work, a nerd directed to a wepage that had instructions that worked:
https://www.androidexplained.com/redmi-note-7-unbrick

16. May 2020: the tip: unzipping - deleting - zipping and flash that new file worked for me also. Redmi Note 7 Lavender; Rom Lineage 17.1 20200215. Very nice. Ernest from Germany

FligMupple said:
Hello.
I'm trying to get my phone back to stock rom.
I'm using the TWRP from the [All In One] post: https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
And I'm trying to install the file I got from: http://en.miui.com/download-360.html
But when I flash the file (miui_LAVENDERGlobal_V10.3.5.0.PFGMIXM_a5cabeca22_ 9.0.zip) I get the error attached.
Can anyone help me with this error?
Click to expand...
Click to collapse
Why not orangefox?