Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM. It is a well proven recovery for many phones.
It also adds a full touch interface a completely configurable GUI.
Original thread by @Phil3759 for i9082 - Link
I am maintaining this recovery for i9082/i9082L as there are overwhelmingly high number of devices for @Phil3759 to maintain on his own.
All credits for the source of the recovery goes to him. I am just compiling it from source for i9082.
I'll only provide recovery flashable zip files.
DOWNLOADS
Philz Touch Recovery
Reserved..
Awesome!!!!!
Sent from my GT-I9082 using Tapatalk Pro.
Del
flashed the latest philz recovery on RR 5.0.6.....as smooth as ever..great update @xenon92.....moreover thanks for contributing so much for i9082....:good::good:
Help ...
Getting status 7 error .. I am on cosmic cm 4.4.2
Sent from Cosmic CM 4.4.2 Dual Sim Rom
vasanthmes said:
Help ...
Getting status 7 error .. I am on cosmic cm 4.4.2
Sent from Cosmic CM 4.4.2 Dual Sim Rom
Click to expand...
Click to collapse
Re-download the zip. Verify md5. Flash again.
gr8 bro.....thankyou so much
---------- Post added at 09:56 PM ---------- Previous post was at 09:51 PM ----------
vasanthmes said:
Help ...
Getting status 7 error .. I am on cosmic cm 4.4.2
Sent from Cosmic CM 4.4.2 Dual Sim Rom
Click to expand...
Click to collapse
if u have used the modified recovery which support f2fs on cosmic cm then this recovery may not support it and would give error....
mr.phantom said:
gr8 bro.....thankyou so much
---------- Post added at 09:56 PM ---------- Previous post was at 09:51 PM ----------
if u have used the modified recovery which support f2fs on cosmic cm then this recovery may not support it and would give error....
Click to expand...
Click to collapse
Redownloaded recovery and tried to flash ... This error comes again..!
Sent from Cosmic CM 4.4.2 Dual Sim Rom
vasanthmes said:
Redownloaded recovery and tried to flash ... This error comes again..!
Sent from Cosmic CM 4.4.2 Dual Sim Rom
Click to expand...
Click to collapse
There have been around 200 downloads so far and none have reported any issue.
You are using CosmicCM and have probably formatted the partitions with f2fs, so while checking for the device, maybe the recovery isn't able to read f2fs partition to access the device property (baffin/i9082). Use the recovery from CosmicCM thread by k2wl which supports f2fs.
vasanthmes said:
Redownloaded recovery and tried to flash ... This error comes again..!
Sent from Cosmic CM 4.4.2 Dual Sim Rom
Click to expand...
Click to collapse
Hey Do I thing
Open the zip file and then search for updater script in the zip and open the file using text editor and then see near that starting, u will find a line containing Baffin and i9082 words. There change any one of them with the empty so that it looks like this "" instead of "Baffin" or "i9082".
mr.phantom said:
Hey Do I thing
Open the zip file and then search for updater script in the zip and open the file using text editor and then see near that starting, u will find a line containing Baffin and i9082 words. There change any one of them with the empty so that it looks like this "" instead of "Baffin" or "i9082".
Click to expand...
Click to collapse
I will try and tell you bro...
Sent from Cosmic CM 4.4.2 Dual Sim Rom
@xenon92,
Same error is occurring in my device. It is because of your "update-binary" file. Replace it from the one in official update by @Phil3759.
I replaced full META-INF from official update and it is working now. But, I think it is just "update-binary". Your update-binary file is old.
Bhargav97 said:
@xenon92,
Same error is occurring in my device. It is because of your "update-binary" file. Replace it from the one in official update by @Phil3759.
I replaced full META-INF from official update and it is working now. But, I think it is just "update-binary". Your update-binary file is old.
Click to expand...
Click to collapse
When you say "in my device", do you mean GT-i9082?
Did you flash "my" zip on "your GT-i9082"?
The reason that I am asking this is from your signature I see that you are maintaining the philz recovery for many other devices, so I am not sure if you are talking specifically about GT-i9082.
If you indeed flashed the zip that I have uploaded, on "your GT-I9082", what was the exact error that was showing up?
Are you using F2FS?
xenon92 said:
When you say "in my device", do you mean GT-i9082?
Did you flash "my" zip on "your GT-i9082"?
The reason that I am asking this is from your signature I see that you are maintaining the philz recovery for many other devices, so I am not sure if you are talking specifically about GT-i9082.
If you indeed flashed the zip that I have uploaded, on "your GT-I9082", what was the exact error that was showing up?
Are you using F2FS?
Click to expand...
Click to collapse
:cyclops: :cyclops: :cyclops:
The questions you asked were more of a common sense.
Yes for all the questions except F2FS. I'm on cm11 by @pawitp and on ext4 only, not F2FS.
And...same error = the error reported by @vasanthmes (same error message).
This is because KitKat changed the way getprop used to work until JB. So, you must update the /META-INF/com/google/android/update-binary.
Bhargav97 said:
:cyclops: :cyclops: :cyclops:
The questions you asked were more of a common sense.
Yes for all the questions except F2FS. I'm on cm11 by @pawitp and on ext4 only, not F2FS.
And...same error = the error reported by @vasanthmes (same error message).
This is because KitKat changed the way getprop used to work until JB. So, you must update the /META-INF/com/google/android/update-binary.
Click to expand...
Click to collapse
I flashed the philz recovery via CWM touch recovery and worked fine no errors nothing..
Sent from my GT-I9082 using XDA Premium 4 mobile app
Bhargav97 said:
:cyclops: :cyclops: :cyclops:
The questions you asked were more of a common sense.
Yes for all the questions except F2FS. I'm on cm11 by @pawitp and on ext4 only, not F2FS.
And...same error = the error reported by @vasanthmes (same error message).
This is because KitKat changed the way getprop used to work until JB. So, you must update the /META-INF/com/google/android/update-binary.
Click to expand...
Click to collapse
The binary that I have used in this philz recovery zip (280 downloads) is the same as the binary that I have used in the following recoveries that I have released in the past:
1) RR Recovery based "99%" on CWM 6.0.4.8 (search for the thread)
2) CWM 6.0.4.7 that I posted here (around 2500 downloads) - http://forum.xda-developers.com/showthread.php?t=2437182
Everything worked fine in those recoveries and everything seems to be working fine even in this recovery zip for me and many others as far as I can tell. I don't know why you are getting that error. Maybe @Phil3759 can share something. Till then, I'll leave the zip as it is.
xenon92 said:
The binary that I have used in this philz recovery zip (280 downloads) is the same as the binary that I have used in the following recoveries that I have released in the past:
1) RR Recovery based "99%" on CWM 6.0.4.8 (search for the thread)
2) CWM 6.0.4.7 that I posted here (around 2500 downloads) - http://forum.xda-developers.com/showthread.php?t=2437182
Everything worked fine in those recoveries and everything seems to be working fine even in this recovery zip for me and many others as far as I can tell. I don't know why you are getting that error. Maybe @Phil3759 can share something. Till then, I'll leave the zip as it is.
Click to expand...
Click to collapse
I am using RR recovery now. Its working fine. But when I tried to flash your recovery the status 7 error occurs....
Sent from Cosmic CM 4.4.2 Dual Sim Rom
vasanthmes said:
I am using RR recovery now. Its working fine. But when I tried to flash your recovery the status 7 error occurs....
Sent from Cosmic CM 4.4.2 Dual Sim Rom
Click to expand...
Click to collapse
Same error happened to me Status 7 error and got that message which i being shown in ur screenshot and I resolved by the method which i had told u.
If u r not able to do that then download the file which i am attaching with this post!
PhilZ Touch Recovery updated to v6.30.2.
Related
These are pure AOSP builds by dhacker29, all credit goes to him.
Please note these are hot off the press and may have bugs. Users have reported trouble with flashing, etc, but when you manage to get it to run the ROM runs smoothly.
Still, AOSP is bare-bones and will need device specific modifications that custom ROMs provide. Consider it a stable-ish alpha build, but not a dependable daily driver.
Please ensure you do your backups. Nobody is responsible if your phone bursts into flames.
All files you need are here:
Prerequisites: KitKat requires TWRP 2.6.3.0 which can be found here
xt925 ROM
xt926 ROM
GAPPS
By default AOSP has no root access, however Chainfire's root will work just fine. Just flash and install SuperSU.
Have fun with KitKat!
Changelog
20131108 Fix sd-mount, update blobs with 4.4 MotoX leak
Known Issues:
Ext-SD not activated
As with other AOSP builds, Google Keyboard is not working. Make sure to use AOSP keyboard.
Does not work with 16GB internal storage https://twitter.com/dhacker29/status/398946262172446720 (Try different versions of TWRP to address this)
Front camera may not work - will crash camera app. Go to app info and clear data to run it again
Video playback problems for some
Some HDMI problems when plugged in
I'm pretty happy on CM 10.2, but I may have to flash this just to see what 4.4 is all about...
Thanks for sharing! :good:
Thanks for sharing.
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Just tried to flash the ROM using CWM... obviously didnt work lol.
Flashed TWRP 2.6.3.0, then flashed the ROM
Setting up device now.
Ill post after a day or so of usage to let everyone know how its going.
TXKSSnapper said:
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
You got right.
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
dabanhfreak said:
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
Click to expand...
Click to collapse
do you mind editing the OP to include a list of known issues?
Thanks!
koftheworld said:
do you mind editing the OP to include a list of known issues?
Thanks!
Click to expand...
Click to collapse
Yet to run into any tbh (besides ex-SD of course), will give it about 24hours and see what folks pick up.
koftheworld said:
do you mind editing the OP to include a list of known issues?
Click to expand...
Click to collapse
Got stuck on the M Logo. But now, I'm wondering if it's not the infamous "Stuck on the M Logo" bug more than the recovery not working on the XT925. I'll try again.
madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
flight666 said:
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
Click to expand...
Click to collapse
Using Flashify. It flashes OK, but I can't get to the recovery... Hanging on the M logo. Damn it.
Can the atrix HD flash this??
Sent from my MB886 using xda app-developers app
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
Click to expand...
Click to collapse
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Good to see
I'm noticing that there's a bug in the AOSP launcher, I can't seem to add a new home screen.
I installed the Nexus 5 Launcher as well, same result.
No such problems on Nexus 7 when installed Google Launcher.
EDIT: nvm, it seems that installing Google Launcher messes with the AOSP launcher... didn't make sense to me either. Oh well, no N5 experience
Uh, no, not that either. I think it was a custom Wallpaper.
you've to drag an app to make a new screen on the new kk launcher ?
pls correct me if i'm wrong..
madmonkey57 said:
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
flight666 said:
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
Click to expand...
Click to collapse
Downloads are slow and tend to fail before the end... We'd better be careful! I am currently re-downloading all files needed.
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
Lets first understand,
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
Instructions :
Download compatible ROM
Download FormatPartitions.zip
Download "special" TWRP for All-F2FS: openrecovery-twrp-2.7.0.0-mako-All-F2FS.img
(This is different for that of simply F2FS)
Copy FormatPartitions.zip and ROM on Phone
Flash "special" TWRP with Fastboot
Flash FormatPartitions.zip with new Recovery
Reboot Recovery
Flash ROM with new Recovery
(Flash GApps with new Recovery)
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
Note : If you already on F2FS directly flash the zip and then Supersu from below link
Tested it..
All working fine..
Need to flash Supersu to retain root..
Downlaods
Link : Flashable Zip Folder - All Files
or
Flashable Zip - ROM
Mirror Link :
http://goo.gl/oQL9uD
Supersu : http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Wifi Fix : Wifi Fix
F2FS 4.4.3 Kernel : d-h.st/t34
Credits :
@is0l4ted - creating the F2FS version
@My Nexus 4 whatsapp group members..
@Rohit02(Me)
@CallMeAldy : Wifi Fix
Changelogs :
2014/06/03 : Initial Release
2014/06/04 : Fixed bootoop for some users. Fix zip included in the new link. (Old link removed)
Rohit02 said:
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
@My Nexus 4 whatsapp group members..
Click to expand...
Click to collapse
There's a Nexus 4 WhatsApp group?
Sent from my Nexus 4 using XDA Free mobile app
Rohit02 said:
Hello peeps...
This is Pure Stock Image 4.4.3 from deodexed it and Converted to F2FS..
Tested it..
All working fine..
Need to flash Supersu to retain root
Click to expand...
Click to collapse
I'm on stock with root, recovery and Xposed. Can I just flash the zip and root again without lose anything?
is there a big difference in speed with F2FS? any problems??
thx
Gr8 work @is0l4ted and @Rohit02 and all the Whatsapp Group members !! Really short on time but if possible will try flashing it tomm evening !!
ronakchavan said:
There's a Nexus 4 WhatsApp group?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm yes an amazing group
ttheodorou said:
is there a big difference in speed with F2FS? any problems??
thx
Click to expand...
Click to collapse
Many threads out there about f2fs its advantages and disadvantages !! Its faster in opening apps and boot times and improved io performance especially on dalvik !!
NABENDU1 said:
Many threads out there about f2fs its advantages and disadvantages !! Its faster in opening apps and boot times and improved io performance especially on dalvik !!
Click to expand...
Click to collapse
so in short it is a good upgrade for the phone. i think i will try it at some point
ok I flashed without wipe and now it's in bootloop. Uff I don't want to wipe everything
CWM ?
Is it compatible with TWRP only or can I flash it via CWM ?
Sorry Bro
gajira said:
ok I flashed without wipe and now it's in bootloop. Uff I don't want to wipe everything
Click to expand...
Click to collapse
Sorry Bro for the inconvenience.. here is the fix for your problem hope you didn't wiped again!!!
Hit Me to fix bootloop!! or Me!!
---------- Post added at 02:09 AM ---------- Previous post was at 02:03 AM ----------
spfc_jcp88 said:
Is it compatible with TWRP only or can I flash it via CWM ?
Click to expand...
Click to collapse
Only TWRP F2FS Version. To confirm that the back button on TWRP should be red in color.
is0l4ted said:
Sorry Bro for the inconvenience.. here is the fix for your problem hope you didn't wiped again!!!
Hit Me to fix bootloop!! or Me!!
---------- Post added at 02:09 AM ---------- Previous post was at 02:03 AM ----------
Only TWRP F2FS Version. To confirm that the back button on TWRP should be red in color.
Click to expand...
Click to collapse
thanks, I had a nandroid backup
Maybe that's the problem, I need a F2FS TWRP.
OP updated..
Enjoy
Can't seem to get my wifi working :/ Installer says it should be activated to view networks, but i cant activate it. If i skip the first install screen where you need to log into your google account etc, and then try to activate wifi in the settings menu nothing happens when i flip the switch :/
Did a clean install multiple times, but it just keeps on not working any fixes for this?
mumaster20 said:
Can't seem to get my wifi working :/ Installer says it should be activated to view networks, but i cant activate it. If i skip the first install screen where you need to log into your google account etc, and then try to activate wifi in the settings menu nothing happens when i flip the switch :/
Did a clean install multiple times, but it just keeps on not working any fixes for this?
Click to expand...
Click to collapse
Same here. Cannot activate wi-fi.
Can I have to install the new radio?
sychim said:
Same here. Cannot activate wi-fi.
Click to expand...
Click to collapse
flash new modem and baseband. If you change to the new android version google provides new binaries. If you haven't then maybe you're wifi won't work. Look in general section for modem baseband flashable.zip
or here:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
carepack said:
flash new modem and baseband. If you change to the new android version google provides new binaries. If you haven't then maybe you're wifi won't work. Look in general section for modem baseband flashable.zip
or here:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
Click to expand...
Click to collapse
Already got the new .02 baseband installed :/
To install this "special" recovery, which one of these commands is right?
Code:
fastboot flash boot filename.img
OR
Code:
fastboot flash recovery filename.img
Many thanks before...
omegahanggara said:
To install this "special" recovery, which one of these commands is right?
Code:
fastboot flash boot filename.img
OR
Code:
fastboot flash recovery filename.img
Many thanks before...
Click to expand...
Click to collapse
fastboot flash recovery filename.img
is the right way...
carepack said:
fastboot flash recovery filename.img
is the right way...
Click to expand...
Click to collapse
You're my hero.... :highfive:
omegahanggara said:
You're my hero.... :highfive:
Click to expand...
Click to collapse
no problem man
KitKat Complement Recovery
Samsung Galaxy SII GT-I9100G
All right guys im just going to keep this real nice and simple. Purpose of thread:
Kit Kat 4.4 ROM Installation Compatible
Just a heads up. This is NOT meant to be used as a kernel. I compiled these recoveries from source and only the recovery module is built therefore YOUR PHONE WILL NOT BOOT COMPLETELY AS THERE IS NO KERNEL. I made these recoveries so that users can flash
From ICS/JB to KK with ease
Flash This Over Stock Kernel So That You Can Update Your KitKat ROM
And Resolve Status 7 Errors When Flashing KitKat ROMs On A Out-Dated Recovery
How To Use:
To Flash a Kit Kat ROM From a Out-Dated Recovery TWRP Version Less Then 2.6.3.0:
Flash This Recovery File via Stock Recovery (Does Not Matter Which Version You Pick Just Take The Latest) And Reboot Back Into Recovery
You Should Now Have A Coloured Recovery With Version 2.8.X.X
Follow ROM Installation Guide From ROM Thread
Recovery Versions
Click The Text To Download
TWRP 2.8.4.0 (Thanks to FurFur_)
Thanks For Reading :good:
P.S.#1 This is my first thread in the Galaxy SII forum
P.S.#2 All OP Body Credits goes to -Grift-
(Updated)
Sorry guys but all links down (my dropbox account has disabled)
Thanks for FurFur_ to upload TWRP
XDA:DevDB Information
TWRP for i9100G, Kernel for the Samsung Galaxy S II
Contributors
3lo0sh, FurFur_
Kernel Special Features: TWRP 2.8
Version Information
Status: Stable
Current Stable Version: Latest Recovery
Stable Release Date: 2014-10-07
Created 2014-06-08
Last Updated 2015-02-16
Links are not redirecting properly
Links cannot be accessed...
Sent from my Nexus 5 using XDA Free mobile app
Ryuinferno said:
Links are not redirecting properly
Click to expand...
Click to collapse
tenghc said:
Links cannot be accessed...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Links Updated
Sent from my GT-I9100G using XDA Premium 4 mobile app
I have posted on @-Grift- 's thread and I think you should take note too
For the s2 family, recovery.img = boot.img, it's just copied over, and /dev/block/mmcblk0p5 is the boot partition, in other words, there is a kernel (recovery and kernel are combined, unlike other devices which have separate boot and recovery), but ROM's might not boot properly, but if it is just for the purpose of utilising the recovery to flash ROMs that require set_metadata, it's OK...you might wanna update the description to avoid confusion...
Ryuinferno said:
I have posted on @-Grift- 's thread and I think you should take note too
For the s2 family, recovery.img = boot.img, it's just copied over, and /dev/block/mmcblk0p5 is the boot partition, in other words, there is a kernel (recovery and kernel are combined, unlike other devices which have separate boot and recovery), but ROM's might not boot properly, but if it is just for the purpose of utilising the recovery to flash ROMs that require set_metadata, it's OK...you might wanna update the description to avoid confusion...
Click to expand...
Click to collapse
Yes you are right
boot.img=recovery.img=zImage
not just on s2 family but in All Galaxy S Original devices(n7000,i9000,i777 etc etc)
Yes there is recovery partition located on /dev/block/mmcblk0p6 but It's useless
And my recovery it's a boot.img extracted from my HOMEMADE.zip
it's a Kernel will only booting 4.4.3 And we don't want to boot
We only want to flash kitkat rom and I point this in OP
the stock firmware won't boot after installing this zip
And I know why u r confiusion about copy recovery directly to /dev/block/mmcblk0p5
Do ya want me to use flash_image ?
Sent from my GT-I9100G using XDA Premium 4 mobile app
I am not confused, I am telling you flashing recovery.img to that partition=flashing a kernel
I speak only about s2 because that's where I am experienced in
Ryuinferno said:
I am not confused, I am telling you flashing recovery.img to that partition=flashing a kernel
I speak only about s2 because that's where I am experienced in
Click to expand...
Click to collapse
Sorry for slow understanding
Can I use it actually?
meiyi2 said:
Can I use it actually?
Click to expand...
Click to collapse
Read the description
It's only for flashing kitkat roms
Updated:
Added Philz, Heimdall and Odin Packages
3lo0sh said:
Updated:
Added Philz, Heimdall and Odin Packages
Click to expand...
Click to collapse
Those kernels can we boot to kk Roms with it or just for flashing kk Roms ?
Bashar Jarad said:
Those kernels can we boot to kk Roms with it or just for flashing kk Roms ?
Click to expand...
Click to collapse
no It's only for flashing kitkat rom not kernel
I working know for kernel that have these recoveries you must wait until release
And Love your Signature can I take need for speed pic
3lo0sh said:
no It's only for flashing kitkat rom not kernel
I working know for kernel that have these recoveries you must wait until release
And Love your Signature can I take need for speed pic
Click to expand...
Click to collapse
Ok thank you i will be waiting for your great kernel
I spent one hour to make the signature
And no problem my friend if you want the pic so as you wish you can take it
This doesn't work.
Tried flashing over recovery, tried flashing with Odin, but i can't go into recovery. When pressing Volume UP + Home + Pwr UP, phone boots, the Samsung I9100 Image appears but just gets stuck there and won't boot into recovery.
maretodoric said:
This doesn't work.
Tried flashing over recovery, tried flashing with Odin, but i can't go into recovery. When pressing Volume UP + Home + Pwr UP, phone boots, the Samsung I9100 Image appears but just gets stuck there and won't boot into recovery.
Click to expand...
Click to collapse
This is for i9100g
It's not for i9100
All Download-Links seem to be down.
toppits said:
All Download-Links seem to be down.
Click to expand...
Click to collapse
hmm if i could i could upload the twrp package for recovery but i think op would upload the links
Not Found
The resource could not be found.
today i build clockworkmod 6.0.5.1 for s6500
and the internal storage and external storage is working
the link of download:
http://www.mediafire.com/download/0dk1689e89ec4ge/CWM-6.0.5.1-v3-jena.zip
for odin use this
http://www.mediafire.com/download/wrcw8fndmnf469g/CWM-6.0.5.1-v3-jena.tar.md5
Changelog
v1:initial build
v2:fix recovery loop
v3:fix the problem of cm11
credits
-thewhisp
-bleached for some motivation
-cyanogenmod
-samsung
good work.....
Great job simokb1996!! :good:
Well, because of the "internal mounting error" I hesitated to test any CM11 version at my Galaxy Mini2 s6500 (non-D) version. Now this has changed, - will try when I find the time.
Which ROM I should use for testing? The latest CM11 M12 build (16.12.2014) from midzan21, or an older from TheWhisp. There are two CM11 M12 midzan21 builds available, - will test the normal one.
The newest build in regards to the date is cm-10.1-20150902-UNOFFICIAL-jena.zip which seems to be absolutely stable. Furthermore there exist also a somewhat mysterious "cm-10.1-crazykernel v2-UNOFFICIAL-jena.zip" ROM with date (08.08.2015). I could not find more information about this build. Well, these are both CM 10.1 ROM's, will see if they works with this CWM 6.0.5.1 here.
On my S6500 phone it's unfortunately not possible to install this new CWM v6.0.5.1 here from stock recovery.
It says "E:signature verification failed" and on a next line "install_package = (2)"
Any idea? I found meanwhile CWM v6.0.3.3-b2 as tar package (midzan21 has uploaded that one in an other thread). So could flash it with ODIN and try then update to this CWM v6.0.5.1. Well, a direct install of the new CWM would be much nicer.
EDIT: The problem is that I have no root rights on stock ROM. There is a nice YouTube video which explains this error. So, as mentioned above, I have first to flash a CWM with ODIN and then update it to v6.0.5.1.
QUESTION, can you make a tar package of CWM v6.0.5.1 which I can flash directly with Odin?
simokb1996 said:
today i build clockworkmod 6.0.5.1 for S6500, and the internal storage and external storage is working
...
plz i want someone to test and replay
credits
-thewhisp
-cyanogenmod
-samsung
Click to expand...
Click to collapse
Ok, here we go. Your CWM build v6.0.5.1 works perfectly with stock Samsung Android 2.3.6 ROM and the latest CM10.1 07/07 ROM from bleached. :good: In CWM v6.0.5.1 I was able to access the internal and the external storage without any problem.
Really great work simokb1996! :good:
Well, there are some things which can be better. The way to install should be easier. Can someone makes a TAR package of this CWM v6.0.5.1 build here? That would be great.
As mentioned, I had to flash first CWM v6.0.3.3-b2 with ODIN, disable the verification check, and then install (upgrade to) this CWM v6.0.5.1. During the upgrade there was something noted regarding CWM v6.0.4.5. Well, I never haven't used this package.
At the moment, CM11 crashes shortly after the installation has started. Will post this information at the corresponding thread.
And yes, during power on the phone, there appears for a short time a small yellow triangle with an black exclamation mark under the Samsung brand name. Shortly thereafter, it is replaced be the CyanogenMod text. Now I ask me if this is CWM or ROM related?
@simokb1996 please remove linkbucks link and add direct download link... ******* and Linkbucks are bad idea and this thread might be closed is I report it to mods if you don't remove that link...
read first
CWM 6.0.5.1 can be installed from CWM 6.0.4.1
how flash this
ismail0100 said:
how flash this
Click to expand...
Click to collapse
I already had CWM 6.0.4.1 installed (using Odin) - so I copied 6.0.5.1 ZIP file into internal memory, restarted with 6.0.4.1 and from this installed CWM 6.0.5.1
YarpenZ said:
I already had CWM 6.0.4.1 installed (using Odin) - so I copied 6.0.5.1 ZIP file into internal memory, restarted with 6.0.4.1 and from this installed CWM 6.0.5.1
Click to expand...
Click to collapse
Thank u very much. I'll use this way
Here follows my feedback regarding CWM-6.0.5.1-v3-jena (ODIN) package. I can confirm for the Galaxy mini 2 S6500 with NFC model:
S6500XXMH1
S6500XXMD1
--> Stock Samsung Android 2.3.6 has perfect compatibility! :good:
--> bleached's CM10.1 07/07 build (latest) has perfect compatibility! :good:
--> simokb1996's CM11 build finally also has perfect compatibility! :good:
Many thanks simokb1996 for this great stable & ODIN compatible CWM!
I have just one little non technical wish, - please give this final CWM a logical and more plausible name like:
CWM-6.0.5.1-v3-jena.zip or CWM-6.0.5.1-final-jena.zip --> for zip file
CWM-6.0.5.1-v3-jena.tar.md5 or CWM-6.0.5.1-final-jena.tar.md5 --> for tar.md5 file
These examples will follow The Whisp's, bleached's & midzan21's naming scheme / convention.
A separate CM11 feedback will follow in yours CM11 thread.
Hi there!
Today I downloaded the perfectly renamed CWM 6.0.51 builds.
Unfortunately the ODIN compatible CWM-6.0.5.1-v3-jena.tar.md5 file will not be accepted. Odin reports a MD5 hash error. I had to flash cwm-6.0.3.3-b2-jena.tar.md5 and upgrade it with the CWM-6.0.5.1-v3-jena.zip package. This worked then perfectly.
when i try to flash custom recovery is says "md5 error! Binary is invalid"
ben.anter said:
when i try to flash custom recovery is says "md5 error! Binary is invalid"
Click to expand...
Click to collapse
Yes, - that error occurs because the file name was changed. simokb1996 has to hash / build a new md5 file for the final CWM-6.0.5.1-v3-jena version. You can try to rename the CWM-6.0.5.1-v3-jena.tar.md5 file to recovery.tar.md5. This was the original (unspecific) filename.
Only other method is to install with ODIN first cwm-6.0.3.3-b2-jena.tar.md5 and then update / upgrade it to CWM-6.0.5.1-v3-jena via the zip package. This has worked perfectly in my case.
This version works with S6500-D?or is only for S6500(non-D)?
Thx!
S3rgi0 said:
This version works with S6500-D?or is only for S6500(non-D)? Thx!
Click to expand...
Click to collapse
That's a good question. I thought that this CWM is only for the S6500(non-D) version. However, - when I look at the whole thread, there is nowhere any compatibility information present.
TheWhisp's original CWM 6.0.x builds are "Samsung Galaxy Mini 2" compatible. So these are usable at both models, S6500-D and S6500(non-D). As a result, simokb1996's CWM 6.0.5.1 build may be also compliant to both models? Well, I give absolutely no warranty for that assumption!
@simokb1996 can answer this question certainly correct.
At the end I installed on my s6500D, and have tried to make backups, chache wipe, wipe Dalvik cache ... and everything works perfect
S3rgi0 said:
At the end I installed on my s6500D, and have tried to make backups, chache wipe, wipe Dalvik cache ... and everything works perfect
Click to expand...
Click to collapse
Don't worry s6500 build work all variant of mini 2
lorn10 said:
Yes, - that error occurs because the file name was changed. simokb1996 has to hash / build a new md5 file for the final CWM-6.0.5.1-v3-jena version. You can try to rename the CWM-6.0.5.1-v3-jena.tar.md5 file to recovery.tar.md5. This was the original (unspecific) filename.
Only other method is to install with ODIN first cwm-6.0.3.3-b2-jena.tar.md5 and then update / upgrade it to CWM-6.0.5.1-v3-jena via the zip package. This has worked perfectly in my case.
Click to expand...
Click to collapse
Where do you downloaded the older version of cwm (cwm-6.0.3.3-b2-jena.tar.md5)?
Flop666 said:
Where do you downloaded the older version of cwm (cwm-6.0.3.3-b2-jena.tar.md5)?
Click to expand...
Click to collapse
here is the link https://www.dropbox.com/s/kfxgpg1liqh14dh/cwm-6.0.3.3-b2-jena.tar.md5
i didn't test it
Your warranty is Void, If anything happens to your device is solely your responsibility. This Rom is only tested on GT-I8200N.
Code:
First Backup Everythings-
DATA,SYSTEM,EFS,MODEM,RECOVERY
Flashing-Instruction From META-INF
#--INFORMATION
#--PREPARE DEVICE PARTITIONS
#--INSTALLATION
#--SYMLINKS
#--PERMISSIONS
#--KERNEL
#--CUSTOM SCRIPTS
#--FINISH
Click to expand...
Click to collapse
This is working for S3 mini I8200N for Devices.
This is stable Rom port form the Offical frameware.
NOTE FOR ALL
I DON’T ALLOW CHEFS/DEVS/THEMERS/COPY PASTERS TO USE MY FILES IN HIS ROM OR MOD
ROM INFO / FEATURES
1-Based on JellyBen-4.2.2
2-SU+SUbinary
3-Busybox
4-DE odexed
6-DE bloated
7-Zip aligned
INCLUDED THEMED APPS FROM STOCK-FRAMEWARE
SuperSU
Backup app
SystemUI
Calculator
Camera
Clock
InCallUI & Contacts
Galaxy Apps
4Email
Internet
Messages
Music Player
My Files
Voice
Settings
Video Player
Notes –
- Standalone flashable zip
- Rom includes XXUANL2-modem
Click to expand...
Click to collapse
Bug:-
no bug.
if find bug then post here
Click to expand...
Click to collapse
Code:
PORT FROM-OFFICAL-FRAMEWARE
Credits –
@Tecnicandriod for latest-recovery-v 3.2.7
Recovery-click on below link-->
latest-recovery-v 3.2.7-flash from-recovery not using odin
https://mega.nz/#!o44n2YqC!Y1DtSV5uuYDg-fO_o_tQJRKaX7YmHetFX8tmCQieT8s
Philz touch recovery-use odin for flash
https://mega.nz/#!woJETAqT!W0yN80XBXtRlJ8ffwFCimz-NVvoikKrWsK3-2knql58
Click to expand...
Click to collapse
LET'S GET THIS INSTALLED, THEN!!!
Turn off your S3 Mini
Turn it back on and enter recovery mode by pressing power button+home+ vol up
Wipe data and confirm with power button
Once done, pull the battery
Reboot to ODIN mode with vol down + home + power
Flash the Philz touch recovery-from ODIN, make sure the F.reset time and Auto reboot options are unticked
Pull the battery and go to recovery
Flash the ZIP and wait for it to complete.
ROM-LINK- https://mega.nz/#!ht5FnIJb!OZTX-PfGZ4rmlrU-XMeRzNCMrOQZ6s379aJOhHnSY0w
Click to expand...
Click to collapse
Reboot and enjoy (be patient, this one takes a bit longer to first-boot)
pandeyshreedhar said:
Your warranty is Void, If anything happens to your device is solely your responsibility. This Rom is only tested on GT-I8200N.
Flashing-Instruction From META-INF
This is working for S3 mini I8200N for Devices.
This is stable Rom port form the Offical frameware.
NOTE FOR ALL
I DON’T ALLOW CHEFS/DEVS/THEMERS/COPY PASTERS TO USE MY FILES IN HIS ROM OR MOD
ROM INFO / FEATURES
1-Based on JellyBen-4.2.2
2-SU+SUbinary
3-Busybox
4-DE odexed
6-DE bloated
7-Zip aligned
INCLUDED THEMED APPS FROM STOCK-FRAMEWARE
SuperSU
Backup app
SystemUI
Calculator
Camera
Clock
InCallUI & Contacts
Galaxy Apps
4Email
Internet
Messages
Music Player
My Files
Voice
Settings
Video Player
Credits –
@Tecnicandriod for latest-recovery-v 3.2.7
LET'S GET THIS INSTALLED, THEN!!!
Turn off your S3 Mini
Turn it back on and enter recovery mode by pressing power button+home+ vol up
Wipe data and confirm with power button
Once done, pull the battery
Reboot to ODIN mode with vol down + home + power
Flash the Philz touch recovery-from ODIN, make sure the F.reset time and Auto reboot options are unticked
Pull the battery and go to recovery
Flash the ZIP and wait for it to complete.
Reboot and enjoy (be patient, this one takes a bit longer to first-boot)
Click to expand...
Click to collapse
You should move the thread to the dedicated section, this is Q&A
i don't know how to move .. can you give me tips...
Hello @woodman bro can you move this thread to correct forum and can i also have author to move this thread and
also how to closed thread i don't know this process..
Sent from my GT-I9305 using Tapatalk
pandeyshreedhar said:
Hello @woodman bro can you move this thread to correct forum and can i also have author to move this thread and
also how to closed thread i don't know this process..
Click to expand...
Click to collapse
Only Admins can change stuff. You can delete here and post a duplicate in the dedicated forum.
hey @pandeyshreedhar,
one question: are you going to update/improve this rom further, or trying further to create a lineage rom
for this device?
that is not my work and not my project but i can handle and do many update for that Rom after some week..
i need someone who is ready to test and provide me screenshot and then i wll add his/her name in the work...
AND
that is correct link ------->>> https://mega.nz/#!EsYR3AzL!ecmndFpZjEb3SJN1jO7GQLvDYb7f1jhRd_Ukz9Vg4mQ
Sent from my GT-I9305 using Tapatalk
hello Guys can you help me to develop other Roms for I8200N/Q/L
I haven't that phone for few week because of repairing that phone
I can't test the any Rom develop by me in that phone. IF someone interest to help me then message here--->
I also add his/her name in the any Rom project.... give some @credit @help of his/her name in project
1. DEODEXROM-I8200N-ROOTED
The following error occurs when flashing with Philz and or TWRP Recovery:
PhilzTouch:
Code:
--Installing: /external_sd/DEODEXROM-I8200N-ROOTED.zip
Finding update package...
Opening update package...
Installing update...
E: Error in /external_sd/DEODEXROM-I8200N-ROOTED.zip
(Status 0)
Installation aborted.
press any key to continue.
E: Unable to create brightness sys file
TWRP:
Code:
Installing '/external_sd/DEODEXROM-I8200N-ROOTED.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Error executing updater binary in zip '/external_sd/DEODEXROM-I8200N-ROOTED.zip'
Error flashing zip "/external_sd/DEODEXROM-I8200N-ROOTED.zip'
Updating partition details...
2. The Nougat Theme Stock Rom with Android 4.2.2 is the one from youtuber technicandro shree
I've tested it, but it's really annoying:
menu settings are Spanish but the rest in my mother tongue
Android 7 display in the menu is fake
Virtual buttons
AlphaAnimal said:
1. DEODEXROM-I8200N-ROOTED
The following error occurs when flashing with Philz and or TWRP Recovery:
PhilzTouch:
TWRP:
2. The Nougat Theme Stock Rom with Android 4.2.2 is the one from youtuber technicandro shree
I've tested it, but it's really annoying:
menu settings are Spanish but the rest in my mother tongue
Android 7 display in the menu is fake
Virtual buttons
Click to expand...
Click to collapse
this is a guide for the custom nougat rom, if you're interested:
I circumvented it by unpack illyrianking kernel zip, unpack philz touch recovery zip, going into odin, untick auto reboot, flash illyrianking kernel, reboot manually again into download mode, flash philz touch recovery.
boot into philz.
in philz: wipe to install a new rom
now the rom can be installed!
I can only confirm this working from stock to custom rom!
illyrianking kernel also makes the device faster & has more tuning options.
here are the files:
(illyrianking kernel usually also can be downloaded on androidfilehost)
AlphaAnimal said:
1. DEODEXROM-I8200N-ROOTED
The following error occurs when flashing with Philz and or TWRP Recovery:
PhilzTouch:
Code:
--Installing: /external_sd/DEODEXROM-I8200N-ROOTED.zip
Finding update package...
Opening update package...
Installing update...
E: Error in /external_sd/DEODEXROM-I8200N-ROOTED.zip
(Status 0)
Installation aborted.
press any key to continue.
E: Unable to create brightness sys file
TWRP:
Code:
Installing '/external_sd/DEODEXROM-I8200N-ROOTED.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Error executing updater binary in zip '/external_sd/DEODEXROM-I8200N-ROOTED.zip'
Error flashing zip "/external_sd/DEODEXROM-I8200N-ROOTED.zip'
Updating partition details...
2. The Nougat Theme Stock Rom with Android 4.2.2 is the one from youtuber technicandro shree
I've tested it, but it's really annoying:
menu settings are Spanish but the rest in my mother tongue
Android 7 display in the menu is fake
Virtual buttons
Click to expand...
Click to collapse
thanks for bug i will maintain/solve that error...
or
can you also try with new twrpv3.2.7 or not???
this twrp is only flash from recovery and language is different..
thimprfct said:
me the same. I circumvented it by unpack illyrianking kernel zip, unpack philz touch recovery zip, going into odin, untick auto reboot, flash illyrianking kernel, reboot manually again into download mode, flash philz touch recovery.
boot into philz.
in philz: wipe to install a new rom
now the rom can be installed!
illyrianking kernel also makes the device faster & has more tuning options.
here are the files:
(illyrianking kernel usually also can be downloaded on androidfilehost)
Click to expand...
Click to collapse
[MENTION=227448]@thimprfc[MENTION] your method is work for this Rom or not???
If work then i will add this kernel in that Rom..
only for the nougat rom, unfortunately.
would be great if you add that kernel in the rom, I find it's the best.
it works for the nougat rom mentioned above & that has the same problem.
I only can confirm it working from stock to custom rom.
pandeyshreedhar said:
can you also try with new twrpv3.2.7 or not???
Click to expand...
Click to collapse
I've already tried, without success.
thimprfct said:
now the rom can be installed!
Click to expand...
Click to collapse
I am 100% sure that the kernel has nothing to do with flashing a custom rom. And since you haven't tested it either, I know the result.
The Nougat Theme Stock Rom I could also start with the Baroni Kernel.
pandeyshreedhar said:
that is not my work and not my project but i can handle and do many update for that Rom after some week..
i need someone who is ready to test and provide me screenshot and then i wll add his/her name in the work...
AND
that is correct link ------->>> https://mega.nz/#!EsYR3AzL!ecmndFpZjEb3SJN1jO7GQLvDYb7f1jhRd_Ukz9Vg4mQ
Click to expand...
Click to collapse
I will test.
---------- Post added at 11:39 AM ---------- Previous post was at 11:38 AM ----------
AlphaAnimal said:
I am 100% sure that the kernel has nothing to do with flashing a custom rom. And since you haven't tested it either, I know the result.
The Nougat Theme Stock Rome I could also start with the Baroni Kernel.
Click to expand...
Click to collapse
ok, I test it for you.
@pandeyshreedhar, @AlphaAnimal, you were so right,
back again. I've tested it & sorry, it did not work.
wish I could have told you something else.
but for the nougat rom it works. right done.
but I can only confirm it from stock to custom rom, not from custom to custom rom.
will edit the posts & describe it as a method for the nougat rom.
no, it's not a kernel thing, it only helps 'a little' sometimes, because it sets the binary to custom & that can sometimes help with flashing. the whole thing is more a recovery problem, this phone has much problems with custom recovery, unfortunately.
but the illyrianking kernel is nevertheless very good imho.
it was worth a try...
now you don't have to test it & be upset.
@pandeyshreedhar,
thank you for trying to create a bloat-free rom for this phone!
I haven't flashed it yet, but viewed the zip & it helped me a lot to figure out which apps & libs are bloatware, from which I never thought they were...
will the custom nougat rom, you'll create, be the same way?
I wll publish another link for fix rom flash error but i can'nt test that bocz of phone is in repair in progress..
So any one interset to test it or not????
First backup everything including all....
Sent from my GT-I9305 using Tapatalk
remove the error but not test from me..don't have phone right now..
test at your self
link---> https://mega.nz/#!nyJgyICC!7p3FMfVLG6D-AinIccKQa_NFRrcQVF_E78tNwa_kV3Y
Click to expand...
Click to collapse
pandeyshreedhar said:
remove the error but not test
Click to expand...
Click to collapse
Thank you very much. I'll try tomorrow and report back here.
The DEODEXROM has shrunk by 191MB. Is there a changelog for this?