Related
while trying many cusOMS RomS ANd FLAshable ZiPS ,Came aCRoss TWo TERMS Flash BY cwm RecOVeRy or sTOck cwM Wats THE Difference betwen THE two Sorry FOR a A NOOB quESTion but WAS very Anxious to KNow tHE DiFereNCE......THANKS IN ADVANCE
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
hell_lock said:
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
Click to expand...
Click to collapse
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
talwarrokzz said:
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
Click to expand...
Click to collapse
cwm has more options than the stock one so using cwm is preferable
hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
CWM has more options and very simple to understand and use!
STOCK=less option.... hard to use... some times its cause a boot loop!
talwarrokzz said:
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
Click to expand...
Click to collapse
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
hell_lock said:
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
Click to expand...
Click to collapse
are you mad?
PwN.CraZyTagZ said:
are you mad?
Click to expand...
Click to collapse
Yes I am!!
its depends on scripting... stock recovery runs only amend scripting but cwm 3.0 or later edify scrpiting... and it has so many options then stock... one notable option and frequently using option is dalvik cache wipe... this is y most of em prefer cwm...
I GUESS THIS IS THE ANSWER... BUT IM NOT SURE ABOUT... GOOGLE IT FOR MORE INFO... I READ IT SOMEWHERE ONCE UPON A TIME... SO I FORGET SOME OF THE THINGS...
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
irfanbagus said:
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
Click to expand...
Click to collapse
Yes friend u r right............
Sent from my GT-S6102 using xda premium
Let's get to your qeury . . . Flashing via stock or CWM
With CWM Recovery you can:
Flash boot.img (kernel)
Flash Custom ROMS
Flash .zips without resinging packages
Choose what partition to be mounted during flash
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
Flash .zips but requires zips to be signed and resigned if there are modifications on the package
CarlDeanCatabay said:
...
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
...
Click to expand...
Click to collapse
that's not stock recovery problem, but custom rom problem. a lot of custom rom have poorly written (or generated) updater-script. rom dev put a lot of work on making his/her rom looks good, but give very small attention to installation process. some rom event try to mount /dev/stl19 to /system in instalation process. that partition not exist in sgy. and updater-script not depend to which recovery that you use. it's depend to updater-binary inside your zip file.
Hi guys,
First of all I don't know where thi thread should be. so, mods please spare me.
I have been compiling (Developing) kernel for a week now and I compiled 2 kernels from cm11 source and also from cm10.2 source using NDK toolchain4.6 (as 4.8 gives me some errors) .
I got zImage and also modules.I thought I will make a flashable zip but I don't have any other files and also I don't have source for any rom.so i pulled out boot.img from the AICP release 5.0 RC and packed my zImage in to a boot.img (renamed zImage to boot.img-kernel) and tried to put that boot.img and modules in to AICP zip folder and flash but everytime it gets stuck in LG logo.there could be many reasons for this as i am using a very crude method to put boot.img and modules files in to a rom zip and also it could be the kernel itself.I can't flash it in fastboot mode as my device won't stay in fastboot.
SO if anyone wants to try if this kernel works or not,please flash the provided boot.img in your device fastboot and let me know.If it works then i can go on making changes and adding OC ,governors and all.
BTW you know that normal XDA slogan so i won't repeat.
boot.img
Wat steps did u take as in making the image
Am making a kernel for stock KitKat sphinx
1. Unpacked boot.img (i pulled it from AICP release 5 RC.zip) using the script
2. Unpacked ramdisk.gz in to ramdisk folder
3. deleted boot.img-kernel file and renamed zImage to boot.img-kernel
4. repacked using the script
I used this script
I started looking at some videos to try and make a kernel also can you share a guide
sure.this is the best one i found,
[Tutorial] Building Your First Kernel
before this you need to install some things and you can follow this guide for that
How to Compile AOSPA from Source
follow this guide till installing android SDK then download android ndk and then follow the guide I provided above "building your first kernel" .
one more thing i wasn't able to install oracle jdk6 according to that guide so google it,you will find the installation procedure.
sukesh1090 said:
sure.this is the best one i found,
[Tutorial] Building Your First Kernel
before this you need to install some things and you can follow this guide for that
How to Compile AOSPA from Source
follow this guide till installing android SDK then download android ndk and then follow the guide I provided above "building your first kernel" .
one more thing i wasn't able to install oracle jdk6 according to that guide so google it,you will find the installation procedure.
Click to expand...
Click to collapse
Thanks we need some attention on this device, its still an invincible device, if it was on more carriers it would have gotten the attention of many
I want to prest my respect and thanks for youres work, both. The g pro still are a great device, I don't understand why aren't some quality and quantity of stock Base room's and kernel's! So, I hope we seen some of that from yours!
I don't have skills to help, only I can say... Good luck and keep on!
bountyman334 said:
Wat steps did u take as in making the image
Am making a kernel for stock KitKat sphinx
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Is it necessary to lokify the boot.img before flashing or will freegee will do it for us??
I don't understand why the stock unmodified CM 10.2 kernel get stuck in LG logo.I don't get any errors while compiling but still it won't boot.
sukesh1090 said:
Is it necessary to lokify the boot.img before flashing or will freegee will do it for us??
I don't understand why the stock unmodified CM 10.2 kernel get stuck in LG logo.I don't get any errors while compiling but still it won't boot.
Click to expand...
Click to collapse
What Recovery you use?
I believe the recoveries provided through FreeGee are already lokified.
Sent from my LG-E980 using XDA Free mobile app
I am using TWRP provided in freegee OG pro. I remember sometimes seeing the log while flashing it says lokifying.... .I think it does the job for us but then why the hell my kernel is not booting.
Atleast If fastboot was working it would have made my life much easier,I didn't have to flash then if it won't work then flash some other kernel,its pain in ........
guys is fastboot working for you??
sukesh1090 said:
I am using TWRP provided in freegee OG pro. I remember sometimes seeing the log while flashing it says lokifying.... .I think it does the job for us but then why the hell my kernel is not booting.
Atleast If fastboot was working it would have made my life much easier,I didn't have to flash then if it won't work then flash some other kernel,its pain in ........
guys is fastboot working for you??
Click to expand...
Click to collapse
Try CWM 6.0.4.4 [emoji15]
Mervingio said:
Try CWM 6.0.4.4 [emoji15]
Click to expand...
Click to collapse
Thought i would share this fount a twrp recovery 2.6.3.0 loki-fied and i made a simple swap and it works for all my flashing (am On Spihnx 1.6) <-- Flash this daily becuz am testing g3 & g flex apps and i dont have to switch over to cwm....
but Note when u wipe data,cache,dalvik u have 2 reboot 2 recovery
https://mega.co.nz/#!hhBHWb4I!NEgT5TIeEgZEvLKMG22sAB3m1i6Uzk3bXB2wElIEO7o
^^
does fastboot work in your recovery??
bountyman334 said:
Thought i would share this fount a twrp recovery 2.6.3.0 loki-fied and i made a simple swap and it works for all my flashing (am On Spihnx 1.6) <-- Flash this daily becuz am testing g3 & g flex apps and i dont have to switch over to cwm....
but Note when u wipe data,cache,dalvik u have 2 reboot 2 recovery
https://mega.co.nz/#!hhBHWb4I!NEgT5TIeEgZEvLKMG22sAB3m1i6Uzk3bXB2wElIEO7o
Click to expand...
Click to collapse
Not sure ladt time i tru use TWRP need back to LG Flash tool
this is legit am using it now between cm11 and sphinx...but i fiqured out that u have to be on 4.1.2 to use twrp tried it with the stock kitkat and it dosent wrk ...so beware dont use stock kitkat at all by my understanding its boot need to be loki fied first
I think the development stopped
dante_67 said:
I think the development stopped
Click to expand...
Click to collapse
Yup for now because I am not in home. next week I will get back to my comp and then I will continue the development .I compiled with both NDK toolchain 4.6 and 4.8 both compile without error but kernel gets stuck in LG logo.so I will try with linaro tool chain,let's see how it goes.
My own impression, of samsung s2 days, linaro is far more superior to ndk
Now we have official TWRP support, so this thread will not be updated anymore. For more info about official TWRP visit this thread.
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.7.0
TWRP 2.8.6.0 (this and next versions are compiled for Xperia M by me)
Older versions and CWM:
TWRP 2.8.5.0 (port from Xperia L)
TWRP 2.8.4.0 (thanks to @Rohan purohit for bringimg it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.
Download
TWRP 2.8.6.0>>>
TWRP 2.8.5.0>>>
TWRP 2.8.4.0>>>
Restoring original image
- You can restore original FOTAKernel flashing it via Flashtool by flashing any firmware (just uncheck everything in "wipe" section and uncheck everything in "exclude" section excluding "FOTA" like in attached screenshot).
- Or install attached zip via recovery or flash FOTAKernel.img from archive as it is written in OP.
cucumber09 said:
TWRP version is 2.8.0.0, because I could not boot 2.8.3.0 this way (maybe due to ramdisk size limitations), I'll look for this later and will try to fix it
Click to expand...
Click to collapse
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
kh34d said:
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
Click to expand...
Click to collapse
I don't know for sure. Download both recoveries, try to flash one that differs from yours and reboot recovery. If it changes, that means it works on CM11 kernel. BTW, even if it doesn't work on CM11, it will work when you will flash CM12 kernel. So you can flash it to be prepared.
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Okay, I will upload original FOTAKernel.
itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Everything about restoring is in 3rd post.
cucumber09 said:
Everything about restoring is in 3rd post.
Click to expand...
Click to collapse
Thangs, now all problem will be fixed ..
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
KHM90 said:
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
Click to expand...
Click to collapse
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
cucumber09 said:
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
Click to expand...
Click to collapse
Ok thx, Not needed just wanna know whether it will work or not
btw, FOTA kernel awesome idea:good:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
ndrancs said:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
Click to expand...
Click to collapse
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
I'm confused, does it work for locked bootloader?
pincheraro said:
I'm confused, does it work for locked bootloader?
Click to expand...
Click to collapse
No way. It even won't work on stock kernel with unlocked BL.
@cucumber09 Which build is the attached FOTA restore zip from? .9?
elmkzgirxp said:
@cucumber09 Which build is the attached FOTA restore zip from? .9?
Click to expand...
Click to collapse
No, it is from earlier build, but also from 4.3. From first 4.3 build, as I remember.
cucumber09 said:
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
Click to expand...
Click to collapse
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
ndrancs said:
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
Click to expand...
Click to collapse
I read these sources. And 49th line defines size of uncompressed ramdisk. But now I am not sure, which one is used in our kernel. I suppose, that newer one.
Here's a link to the important stock stuff for the Qualcomm Moto E4 Plus. Specifically the boot.img, recovery.img, system.img, fsg.bin, logo.bin, and modem.bin.
I'm too new to post links, but just go to tinyurl dot com /yauppmbc
I'm not 100% sure if system.img will flash correctly, but using
Code:
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
should work, just remember to put the system.img in /sdcard first. Also included in the zip is the partition mappings. I used dd to yank them from the phone while booted into TWRP. Huge shout out to @jasonmerc for walking me through this.
My build number is NPR26.58-25
Clickable link here
Can I just flash the zip
On my phone from TWRP ?
Miklalo said:
On my phone from TWRP ?
Click to expand...
Click to collapse
TWRP might work, but you need to set it to image flashing rather than zip flashing
jasonmerc said:
TWRP might work, but you need to set it to image flashing rather than zip flashing
Click to expand...
Click to collapse
I downloaded the zip twice and both times was unable to extract the zip file. Do I need a specific app or program to extract this to access the .img files in it?
Sent from my XT1775 using XDA Premium HD app
glockman4519 said:
I downloaded the zip twice and both times was unable to extract the zip file. Do I need a specific app or program to extract this to access the .img files in it?
Sent from my XT1775 using XDA Premium HD app
Click to expand...
Click to collapse
It's corrupted somehow. It's just a normal zip, nothing special should be needed.
aj2333 said:
It's corrupted somehow. It's just a normal zip, nothing special should be needed.
Click to expand...
Click to collapse
Thanks for letting me know, I'll see if I can reach maerk and tell him to make a new zip
Great, I made a build of Resurrection Remix 7.1.2 for the XT-1775 (Owens) and have no data. I noticed that there are no APN's in the carrier section under settings. It also has no way to add in any new APN's. My guess is that I will have to flash the modem.img and maybe a few more to get this working again. I'm hoping that I don't have to go back to completely stock...lol...
Hi,
I want to use custom rom like Ancient OS or Evolution-X.
But when I flash rom using offical TWRP (twrp-3.6.0_11-0-alioth.img, https://dl.twrp.me/alioth/)
not working WIFI, and some vendor propertary.
(Very long boot time and very many vendor error log in logcat)
When I flash rom using Nebrassy ver (TWRP-3.5.2-alioth-Nebrassy.img), It works ok.
I think there's no different because I use zip script.
But every time, offical version not working...
Is this my mistake ? or Offical TWRP is really wrong?
I use official TWRP with custom ROM and it works great. Don't think it's a recovery issue in your case.
gacman said:
I use official TWRP with custom ROM and it works great. Don't think it's a recovery issue in your case.
Click to expand...
Click to collapse
OK. thanks
I'll try again.