CLOCKWORKMOD-RECOVERY FOR EPIC 4G TOUCH
Click to expand...
Click to collapse
for use with Stock ROMs
I'll update it every time something important has changed, like CWM changes or kernel updates from samsung.
It's built from samsung kernel sources + teamhacksung initramfs template.
Instructions
Power your device off
Boot into Download-Mode using Volume Down + Power
Hit Volume Up to accept the warning
Start Odin
Choose "SPH-D710_ClockworkMod-Recovery_X.X.X.X.tar" as PDA (no repartition)
Connect your Phone
Start flashing
After reboot you can easily root your device using SuperOneClick
Usage
Volume Up + Power brings your Phone into Recovery Mode.
VolUp + VolDn = Highlight Up/Dn
Power = toggles menus off/on
Home = Select
Back = Back
Download
OFFICIAL: http://t.co/2LRpfmZ0
Testing - 5.0.2.3: http://www.multiupload.com/O2SIVM7SSS (md5: 7722cafbfdebf222ef8ea003216781e0)
Don't forget to thank koush for his awesome work on ClockworkMod / ROMManager.
INITRAMFS TEMPLATE FOR DEVELOPERS
Click to expand...
Click to collapse
Here's a initramfs template you can use as a base for your haxx0ry:
https://github.com/teamhacksung/clockworkmod_epic4gtouch_initramfs
It's stock initramfs + ClockworkMod Recovery and necessary modifications to make it work.
Instructions
git clone https://github.com/teamhacksung/clockworkmod_epic4gtouch_initramfs gingerbread
remove hidden directorys from your cloned repo like .git
use it as your initramfs source
To make sure to include fresh modules (vermagic) use a buildscript like this:
build.sh (inside your kernel dir)
Code:
#!/bin/bash
INITRAMFSDIR=/home/user/android/samsung/epic4gtouch_initramfs
TOOLCHAIN=/home/user/android/cyanogenmod/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
make c1_rev05_na_spr_defconfig
make -j8 CROSS_COMPILE=$TOOLCHAIN CONFIG_INITRAMFS_SOURCE="$INITRAMFSDIR"
cp drivers/bluetooth/bthid/bthid.ko $INITRAMFSDIR/lib/modules/
cp drivers/net/wireless/bcm4330/dhd.ko $INITRAMFSDIR/lib/modules/
cp drivers/samsung/j4fs/j4fs.ko $INITRAMFSDIR/lib/modules/
cp drivers/scsi/scsi_wait_scan.ko $INITRAMFSDIR/lib/modules/
cp drivers/samsung/vibetonz/vibrator.ko $INITRAMFSDIR/lib/modules/
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko $INITRAMFSDIR/lib/modules/
make -j8 CROSS_COMPILE=$TOOLCHAIN CONFIG_INITRAMFS_SOURCE="$INITRAMFSDIR"
Example updater-script: http://pastebin.com/wiUANQ9X
Kernel Sources: http://opensource.samsung.com
greets
codeworkx
Whoa! Hello!
And so it begins .
Edit: Is this going to be officially supported through Rom Manager?
Is this going to be officially supported through Rom Manager?
Click to expand...
Click to collapse
Koush was given a phone and said he was gonna pass it along after getting initial support. Makes me think it will be official now/soon.
Sent from my SPH-D710 using xda premium
Something missing
there is no .....go back........
where I think there should be, I could be wrong but check it out THANKS
It says in the OP that after flashing this you can root simply by using superoneclick, I thought there was no one click method for our device yet?
aaron130 said:
It says in the OP that after flashing this you can root simply by using superoneclick, I thought there was no one click method for our device yet?
Click to expand...
Click to collapse
Normally there is no.
But this is a insecure kernel which means that it can be rooted this way.
Awesome, awesome, awesome!
Sent from my SPH-D710 using XDA App
codeworkx said:
Normally there is no.
But this is a insecure kernel which means that it can be rooted this way.
Click to expand...
Click to collapse
Can't thank you enough for jumping in here. Are you taking an interest in getting CM7 going for the ET4g?
This is exciting, thank you for your work!
sweet. im already rooted using stock kernal but without cwm. this will simply give me cwm but keep root? thank you.
itrackit said:
sweet. im already rooted using stock kernal but without cwm. this will simply give me cwm but keep root? thank you.
Click to expand...
Click to collapse
No... It will flash a new kernel as well.
Samsung Galaxy S II
Hey codeworkx, I saw on your blog that you got CyanogenMod flashed onto the AT&T SGSII. What are the chances that the Epic 4G Touch will get some of that love?
Also, thanks for this CMR kernel.
stangdriverdoug said:
No... It will flash a new kernel as well.
Samsung Galaxy S II
Click to expand...
Click to collapse
thank you for the quick reply
Your welcome
Samsung Galaxy S II
Awsome news...I'm sure everyone has been waiting on a updated version of CWM.
I'm rooted using Stock Kernel with Crawjr's Deodexed method.
Will I be ok flashing this CWM???
Please disregard my question about CM7 I posted above. I just saw on your blog that "Looks like [you are] maintaining all three Galaxy S II Devices now." This is the best piece of news regarding ET4g development yet!
Hey man, did koush push this out in rom manager?
http://www.github.com/bubby323/android_device_samsung_epic_4g_touch
Chris and I got internal storage and sd card mounting last night.
Also, if you are planning on working on Cyanogenmod for the Epic Touch I would love to help you guys out.
Let me know.
I believe if you flash this over midNIGHT ROM you will retain root as the ROM is already prerooted. I odined this and retained root.
The only thing you will notice is the custom boot animation will revert to the stock boot animation. Other then that, this kernel is perfect. Thank you so much for putting this out.
Quickboot will boot you into the new recovery. Have not tried ROM Manager yet, only cause the like to be able to use the reboot option in Quickboot.
GREAT WORK.....
bubby323 said:
Hey man, did koush push this out in rom manager?
http://www.github.com/bubby323/android_device_samsung_epic_4g_touch
Chris and I got internal storage and sd card mounting last night.
Also, if you are planning on working on Cyanogenmod for the Epic Touch I would love to help you guys out.
Let me know.
Click to expand...
Click to collapse
The Epic Touch uses a diffrent block for emmc and sd card. Might want to check out my device files.
Also a change has to be made to recovery.rc to mkdir /emmc.
Related
This has been tested on I9000BUJV9 and it's working
You'll need the following :
- Heimdall
https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.1.1-win32.zip
for it to work you need Microsoft Visual C++ 2010 , link in the program README
- fuguroot kernel for Heimdal
http://fugumod.org/zImage-root
- zImage from your desired firmware (extract the zImage file from the PDA.tar or the onefile firmware .tar using 7zip)
You'll need to do the following :
1. backup your files just in case , or if you're not on a clean firmware and wish to do so
2. turn your phone off and remove the battery for a few seconds
3. put the battery in and start the phone in download mode
4. connect the phone to the PC and start zadig.exe from Heimdall folder
- select options -> list all devices
- select samsung usb composite device
- select install driver and wait (select install driver anyway if warning appears)
5. exit zadig.exe and start heimdall-frontend.exe
6. browse from the kernel category and select the fuguroot kernel for Heimdall
-> the zImage-root you've downloaded previously
7. click start and wait for it to be done
DO NOT REMOVE THE USB CABLE AFTER IT'S DONE
8. right after the flashing is done you'll see the fugu bootlogo ( red fish ) and then the phone turns itself off and starts charging
AS SOON AS YOU SEE THE CHARGING BATTERY , REMOVE THE PHONE'S BATTERY AND CABLE
9. after a few seconds put the battery back in and start the phone in download mode again
10. connect the phone back to the pc and now browse from the KERNEL category to your stock zImage you've extracted from the stock firmware
11. select start again and as it completes you MAY REMOVE THE CABLE
The phone starts , and voila , superuser is there and also the phone is rooted
You may also perform a hard/factory reset as the root and superuser will still be present.
thanks to Heimdall readme file
thanks to nikademus for creating fuguroot kernel
thanks to me ^^
root I9000BUJV9 JV9
root I9000XXJVO JVO
I stopped using fuguroot since discovering it was deleting files without being upfront about it. If the author fixed that it would be great.
Sent from my GT-I9000 using XDA Premium App
can i use gingerbreak for JVO ?
gingerbreak doesn't quite work , but for JVO theres this method , theres CF-ROOT
{Angel} said:
I stopped using fuguroot since discovering it was deleting files without being upfront about it. If the author fixed that it would be great.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Which files does it delete and why? Is it just drexe and npsmobex? These can be restored fairly easily. If removing these is integral to gaining root, then yes, it should be noted.
Apart from fscking Kies up (which is no great loss), what else does this cause issues with?
Personally, I think fuguroot is a great tool which works faultlessly for me over JVB-JVO, but I agree file deletion should be stated somewhere in the release notes.
fauxdeluxe said:
Which files does it delete and why? Is it just drexe and npsmobex? These can be restored fairly easily. If removing these is integral to gaining root, then yes, it should be noted.
Apart from fscking Kies up (which is no great loss), what else does this cause issues with?
Personally, I think fuguroot is a great tool which works faultlessly for me over JVB-JVO, but I agree file deletion should be stated somewhere in the release notes.
Click to expand...
Click to collapse
Yes those files. Deleting them is not required for rooting which is the sole intended purpose of this kernel as per the authors description. I dont want something deleting stuff it shouldnt for no aparent reason and no disclosure. I am also uncomfortable the author has not rectified this. What else it might be doing? Catch my drift? ...otherwise this would be a very useful tool.
Sent from my GT-I9000 using XDA Premium App
myshu said:
[HOWTO]Root JV9 / JVO ( no custom kernel )
Click to expand...
Click to collapse
Not to be a douche but since when was fuguroot not a custom kernel?
Yeah this is a custom kernel, as it involves flashing a Z-Image, which is kind of misleading...
jaju123 said:
Yeah this is a custom kernel, as it involves flashing a Z-Image, which is kind of misleading...
Click to expand...
Click to collapse
I was also thinking this. To defend the OP though, I think the point is that you can flash back to stock kernel afterwards
no custom kernel as in , you don't have to stay onto a custom kernel to keep the root , once you flash back to stock kernel you can factory reset and its 100% stock but with root access
myshu said:
no custom kernel as in , you don't have to stay onto a custom kernel to keep the root , once you flash back to stock kernel you can factory reset and its 100% stock but with root access
Click to expand...
Click to collapse
Thats the case with pretty much every other custom kernel...
Sent from my GT-I9000 using XDA Premium App
On every ginger rom,flash the speedmod k13 for froyo without autoreboot,install root in the recovery options and flash any kernel you want after has always worked so far.
From the fuguroot thread. Good news?
Originally Posted by {Angel}
This should really be addressed, why is FuguRoot deleting these files in the first place?
That is a relic of fugumod, I will address that as soon as time permits.
Click to expand...
Click to collapse
This does not work. I tried it and was corrected. The Samsug Galaxy S doesn't have a recovery partition according to users in this thread. Therefore, this thread has been discontinnued and should be closed.
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the Samsung Galaxy S (i9000).
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Only available in standard orange, I actually can't be bothered to find out how to make different color variants.
Download:
GalaxyS_recovery-clockwork-3.2.0.0-j_r0dd_mod.zip (Without the /sdcard mounting bug)
GalaxyS_recovery-clockwork-4.0.0.0-j_r0dd_mod.zip (Buggy when mounting /sdcard)
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
OK, and what am I to do with it?
Does this support RFS ?
Or only EXT4 ?
The recovery image is not supported to flash it on I9000.....
this is great.... i don't think it's Odin flashable rightnow, so not trying anything for now but would like to see it in flashable form. I am right, right?
The problem is I don't know anything about flashing an SGS phone. I simply assumed one uses an img file for the recovery. I'll see tomorrow if there's a way to make it work.
Sent from my Nexus S using Tapatalk
Stupid question?
Why remove it if all you need to do is touch /sdcard/clockworkmod/.no_confirm with stock recovery? and it does the same thing?
No, with this one you don't have so many "no" choices in the menu. And other differences in the menus as well. Look in the Nexus S thread for more details.
Sent from my Nexus S using Tapatalk
zyonee said:
No, with this one you don't have so many "no" choices in the menu. And other differences in the menus as well. Look in the Nexus S thread for more details.
Click to expand...
Click to collapse
If you touch /sdcard/clockworkmod/.no_confirm on stock CWM you get dont get the "no" choices" menu changes I understand, but i dont see the point in removing the confirmation if you can turn it on / off by default
nitr8 said:
If you touch /sdcard/clockworkmod/.no_confirm on stock CWM you get dont get the "no" choices" menu changes I understand, but i dont see the point in removing the confirmation if you can turn it on / off by default
Click to expand...
Click to collapse
No, that's a different thing. In this recovery, you'll still need to confirm, but you won't have to go through so many "no's" to reach the "yes". You'll have no and yes as the two only choices. Also, j_r0dd moved some wipe features into main menu -> wipe. He also removed the obsolete "Install update.zip", seeing as people will browse directories and name files other things than update.zip nowadays. Things like that. That's the reason for the mod.
Updated OP to version 4.0.0.0.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
Thanks for trying but a SGS does not have a recovery partition.
The recovery executable you have built needs to be embedded into the kernels zimage on SGS.
Its the one thing that stopped me building a psfmod recovery for SGS unlike every other device where recovery has its own kernel etc, the SGS recovery is in the main system kernel. Bad practice on Samsung for that.
People will have to wait.
FYI, CWM 4.0.0.1 is on githib now with sdcard bug fixed.
Klutsh said:
Thanks for trying but a SGS does not have a recovery partition.
The recovery executable you have built needs to be embedded into the kernels zimage on SGS.
Its the one thing that stopped me building a psfmod recovery for SGS unlike every other device where recovery has its own kernel etc, the SGS recovery is in the main system kernel. Bad practice on Samsung for that.
People will have to wait.
FYI, CWM 4.0.0.1 is on githib now with sdcard bug fixed.
Click to expand...
Click to collapse
Thanks for the heads up!
Sent from my Nexus S using Tapatalk
Where i can find the CWM Sources guys?
Sent from my GT-I9000 using XDA Premium App
simone201 said:
Where i can find the CWM Sources guys?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
github.com - search for cyanogen bootable recovery.
Sent from my Nexus S using Tapatalk
zyonee said:
github.com - search for cyanogen bootable recovery.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Nothing found.....link please?
simone201 said:
Nothing found.....link please?
Click to expand...
Click to collapse
j_r0dd's mod: https://github.com/j-r0dd/android_bootable_recovery
Koush's original: https://github.com/koush/android_bootable_recovery
Mods: Maybe we should close this thread, seeing as there's no use for me trying to compile an .img file for this device when in fact it will never work that way.
zyonee said:
j_r0dd's mod: https://github.com/j-r0dd/android_bootable_recovery
Koush's original: https://github.com/koush/android_bootable_recovery
Mods: Maybe we should close this thread, seeing as there's no use for me trying to compile an .img file for this device when in fact it will never work that way.
Click to expand...
Click to collapse
Many thanks!
Yeah, i think it is a better choice....
Team Epic Blog: CWM Recovery for all SGS3 LTE variants
Downloads and instructions for CWM recovery to enable rooting and customization of all SGS3 LTE variants.
Team Epic Blog: Root from Recovery
Simply flash this.zip in CWM and your phone is rooted! This is the easiest method to root the stock Samsung ROM.
Team Epic Blog: Unroot from Recovery
Simply flash this.zip in CWM and your phone is unrooted! This is the easiest method to unroot the stock Samsung ROM.
**Version 2 released, adding volume key scrolling and external sdcard support. Tested so far on Sprint SGS3. Requesting confirmation from AT&T and T-Mobile users
CyanogenMod's Team Epic specializes in Sprint's flagship Android phones on Sprint.
If you appreciate our work, please consider supporting us with a tiny contribution. Thanks!
noobnl said:
http://i.imgur.com/mWg1z.jpg http://i.imgur.com/Q5uUm.jpg
We know clockworkmod is a little buggy.. don't complain about them.
clockworkmod download: http://d-h.st/lTv
flash it with odin in pda tab
Donate to TeamEpic, an official division of CyanogenMod:
http://www.epiccm.org/p/about-team-epic.html
Click to expand...
Click to collapse
This is great, thanks.
But when you say buggy, what do you mean exactly? Which parts are buggy?
So is this installing a rooted
kernel as well?
Sent from my SPH-L710 using xda premium
humdrum2009 said:
So is this installing a rooted
kernel as well?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Nope it doesn't install rooted kernel
noobnl said:
Nope it doesn't install rooted kernel
Click to expand...
Click to collapse
so at this point can we flash super su, ect?
Nice
noobnl said:
Nope it doesn't install rooted kernel
Click to expand...
Click to collapse
good to see you here man, i miss testing for you on the og epic.
so how did you install superuser?
Its been a while since I used a samsung, how do I get into recovery again?
in recovery, download the superuser 3.0.7, extract it, then
adb push Superuser-3.0.7-efghi-signed/system /system
adb shell chmod 6755 /system/bin/su
No, it isn't magic and it isn't hard...
teh roxxorz said:
Its been a while since I used a samsung, how do I get into recovery again?
Click to expand...
Click to collapse
Volume up and power and home button
Sent from my SPH-D710 using xda premium
dtr145r said:
Volume up and power
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
See, did that, and it didn't boot into recovery for me, but odin said all went well, so i was confused.
teh roxxorz said:
See, did that, and it didn't boot into recovery for me, but odin said all went well, so i was confused.
Click to expand...
Click to collapse
home, volume up, and power
noobnl said:
home, volume up, and power
Click to expand...
Click to collapse
I knew it, thank you, was doing that as I typed this.
Edit: Still nothing, I saw a quick blue text like it was going into recovery, but then nothing.
Edit 2: I remembered you basically have to let it go at that point. All is good in my hood.
teh roxxorz said:
See, did that, and it didn't boot into recovery for me, but odin said all went well, so i was confused.
Click to expand...
Click to collapse
On the et4g it was volume up and power..
Find an application in the market that will reboot to recovery.
There are a bunch.
Rom Manager
Rom tool box
Absolute system root
You can also adb recovery as well..
Sent from my SPH-D710 using xda premium
Now how do we get into download mode for odin?
Nevermind, vol down + home +power.
shane6374 said:
Now how do we get into download mode for odin?
Nevermind, vol down + home +power.
Click to expand...
Click to collapse
Volume down, power and home
Thanks noobnl, who all on the team has an sgs3, just wondering?
Sent from my SPH-D710 using prefetch engrish...
noobnl said:
in recovery, download the superuser 3.0.7, extract it, then
adb push Superuser-3.0.7-efghi-signed/system /system
adb shell chmod 6755 /system/bin/su
No, it isn't magic and it isn't hard...
Click to expand...
Click to collapse
Would you please post a link to su 3.0.7?
Can I flash superuser zip from recovery?
I can't get adb working from recovery... What am I doing wrong?
EDIT:
I installed Samsung USB drivers, but the phone isn't recognized as an adb device while in recover,,,
obender said:
Would you please post a link to su 3.0.7?
Click to expand...
Click to collapse
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
nabbed said:
Can I flash superuser zip from recovery?
I can't get adb working from recovery... What am I doing wrong?
Click to expand...
Click to collapse
I generally use adb when booted into the OS, and then do the remount on a pc with the sdk installed. Make sure you have the proper drivers installed.
teh roxxorz said:
I generally use adb when booted into the OS, and then do the remount on a pc with the sdk installed. Make sure you have the proper drivers installed.
Click to expand...
Click to collapse
Can't do remount w/o root.
Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.4
for your AT&T Samsung Galaxy S 4
Read this whole post before doing anything
I use nandroid manager to edit/alter my nandroids made by this recovery, you can find the app here : https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=en Enjoy
CWM Flashable - OUDHS CWM-based Recovery 1.0.3.4 (need to already have a recovery for this)
Directions:
1) Download the above files
2) Flash in recovery
-------------------------------------------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now.
-------------------------------------------------------------------------------------------------------------------------------------------------
Keep in mind as of 1.0.3.4 it auto loki's kernels for ya, so its even easier to customize your device read more here - http://forum.xda-developers.com/showthread.php?p=41803523#post41803523
Source for jflteatt
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) for being the best we can for those whom need us
garwynn for helping with setting up jflte-common stuff
howtomen & RehpotsirhC for helping test 1.0.3.4's autoloki on teh jflteatt
bhp090808 & an21281 & MR H3LLMAN for helping test
Version 1.0.3.5
Improved exit script, now it checks for working bootloaders and will skip otherwise. as well as avoids writing to your nand if you dont need the auto loki (as in the boot.img is already patched )
Version 1.0.3.4:
Adds suppoirt for exit scripts
I've set up a custom one to auto loki kernels on exit
shabbypenguin said:
Hey guys, now obviously you cant flash this yet, but i didnt want yall to know you werent going to be left out
if you decide to be lazy and flash twrp via goo manager i made a flashable zip so you can just flash it and go
Click to expand...
Click to collapse
Sounds good to me, good job. Thanks for not leaving us low life's out. Our forum smells of emptiness.
Do you have to use Odin 3.04, 3.07 should work eh?
Thanks! Cant wait to be able to put it to use.
TheAxman said:
Sounds good to me, good job. Thanks for not leaving us low life's out. Our forum smells of emptiness.
Do you have to use Odin 3.04, 3.07 should work eh?
Click to expand...
Click to collapse
yea it should, i just happen to work on a lot of phones so for a lot of my recovery threads i do a bit of copying and pasting.
As I've been away... Is there a main difference between this recovery and twrp?
.. Good work shab
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
iSaint said:
As I've been away... Is there a main difference between this recovery and twrp?
.. Good work shab
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
this has nothing to do with twrp?
its a fork off cwm 6.0.3.0 and i started to make my own. added some much needed features, rainbows, etc you know the usual
shabbypenguin said:
Hey guys, now obviously you cant flash this yet, but i didnt want yall to know you werent going to be left out
Click to expand...
Click to collapse
Those of us with a SGH-I337M can!
Sent from my SGH-I337M using xda app-developers app
cholywell said:
Those of us with a SGH-I337M can!
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
well enjoy the asserts are different since this is compiled for jflteatt so i am not sure if you will have any issues flashing cm/aosp roms for your device
shabbypenguin said:
this has nothing to do with twrp?
its a fork off cwm 6.0.3.0 and i started to make my own. added some much needed features, rainbows, etc you know the usual
Click to expand...
Click to collapse
Rainbows?!
I'm definitely in
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Failed?
I've tried it twice. Failed both times. Downloaded the tar, download odin when into download put tar in PDA start...failed...Tried both 304 and 307 odin...both failed. Any suggestions?
brojoe11 said:
I've tried it twice. Failed both times. Downloaded the tar, download odin when into download put tar in PDA start...failed...Tried both 304 and 307 odin...both failed. Any suggestions?
Click to expand...
Click to collapse
on your att sgs4?
shabbypenguin said:
on your att sgs4?
Click to expand...
Click to collapse
Yes...Do we need to wait for bootloader unlock or am I missing something?
brojoe11 said:
Yes...Do we need to wait for bootloader unlock or am I missing something?
Click to expand...
Click to collapse
Gotta wait bro
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
iSaint said:
Gotta wait bro
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Man was I excited!!! But I can wait. Thanks for the replies and I look forward to it as soon as it's possible. Have a great day.
Everyone needs to read the OP!!!! it is not ready.
www.shabbypenguin.com/OUDstuff/Samsung/ATT/jflteatt/loki_flash
www.shabbypenguin.com/OUDstuff/Samsung/ATT/jflteatt/Recovery/OUDHS-Recovery-jflteatt-1.0.3.3.lok
usage:
adb push OUDHS-Recovery-jflteatt-1.0.3.3.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/OUDHS-Recovery-jflteatt-1.0.3.3.lok
Click to expand...
Click to collapse
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
you will need to make sure you remove /system/etc/install-recovery.sh otherwise youll end uyp with stock recovery again. use a root explorer or teh like
can you post the additions to CWM recovery? it would be useful for people to know what you've added
shabbypenguin said:
www.shabbypenguin.com/OUDstuff/Samsung/ATT/jflteatt/loki_flash
www.shabbypenguin.com/OUDstuff/Samsung/ATT/jflteatt/Recovery/OUDHS-Recovery-jflteatt-1.0.3.3.lok
usage:
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
Click to expand...
Click to collapse
Yay!!!
Im assuming i need to do all of that in ADB? Also, does the file need to be on the phone or computer?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
MrPlNK said:
Yay!!!
Im assuming i need to do all of that in ADB? Also, does the file need to be on the phone or computer?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
the commands will guide ya through. forgot teh command to remove a nasty script though, will eidt it in
This is an unofficial port from the n7100 (International Note2) of PhilZ-Touch recovery.
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
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Click to expand...
Click to collapse
Download links
Latest versions can be found here:
t0ltespr
http://www.androidfilehost.com/?w=files&flid=8094
Click to expand...
Click to collapse
Flash the above in recovery and then do a "reboot recovery" to get into Philz Touch!
Enjoy
Screenshot attached (thanks Skunk Ape1).
Huge thanks to @Phil3759 for an awesome recovery, and @Skunk Ape1 for testing! :thumbup::thumbup:
This will be getting updated later today since Philz Touch 5.15 has been released
Thank you again for all your support :good:
I would like to thank Phil3759 for this very cool recovery and CNexus for the port for the gn2.
This is great! Considering all of the features this has I think it should be in original development forum. Thanks CNexus!
Sent from my SPH-L900 using Tapatalk 4
Going to flash this baby after the update!
Sent from my SPH-L900 using Tapatalk 4
Mephistonian said:
Going to flash this baby after the update!
Sent from my SPH-L900 using Tapatalk 4
Click to expand...
Click to collapse
Something came up and it's looking like I won't be able to do it today, unfortunately
No worries, this is your playground, we just play here.
Sent from my SPH-L900 using Tapatalk 4
CNexus said:
Something came up and it's looking like I won't be able to do it today, unfortunately
Click to expand...
Click to collapse
No problem buddy. My thinking goes something like, if it ain't broken, why fix it.
Getting an error when trying to flash though recovery. It gives an error "failed: getprop ("ro.product.device")"
I flashed 5.11 after I ran into an issue with TWRP 2.6.3.0 not formatting my system correctly. Very impressed with the features, but I wish the category buttons were just a few pixels wider. Other than that it flashes and erases perfectly. Thank you for the port!
AlkaliV2 said:
I flashed 5.11 after I ran into an issue with TWRP 2.6.3.0 not formatting my system correctly. Very impressed with the features, but I wish the category buttons were just a few pixels wider. Other than that it flashes and erases perfectly. Thank you for the port!
Click to expand...
Click to collapse
You can resize that in Philz settings > GUI Preferences > Menu Height
I'd suggest you spend some time in recovery lol....you can basically customize everything
spotopolis said:
Getting an error when trying to flash though recovery. It gives an error "failed: getprop ("ro.product.device")"
Click to expand...
Click to collapse
That means that this recovery is not for your device.
All I did was fallow your link and DL the file listed on AFH. It was file name philz_5.11-d2spr_cnexus.zip
Edit: just checked again. Same file. Was listed for gnote2.
Im running whomp4.2 and saber kernel. Tried flashing in cwm and in twrp and same error in both.
Awesome. I'll check it out now. I got a little nervous when I saw brightness settings and a file explorer option that didn't respond so I stuck with what I knew I will go in and change it now though. Thanks for the tip!
spotopolis said:
All I did was fallow your link and DL the file listed on AFH. It was file name philz_5.11-d2spr_cnexus.zip
Edit: just checked again. Same file. Was listed for gnote2.
Im running whomp4.2 and saber kernel. Tried flashing in cwm and in twrp and same error in both.
Click to expand...
Click to collapse
Oh shoot. Sorry I botched the updater script. Should be fixed now, please check the folder again and download the new one!
AlkaliV2 said:
Awesome. I'll check it out now. I got a little nervous when I saw brightness settings and a file explorer option that didn't respond so I stuck with what I knew I will go in and change it now though. Thanks for the tip!
Click to expand...
Click to collapse
Read main thread to enable aroma file manager. It can be accessed using gestured (double tap outside menus by default)
CNexus said:
Oh shoot. Sorry I botched the updater script. Should be fixed now, please check the folder again and download the new one!
Click to expand...
Click to collapse
Just downloaded and updater script still has d2spr as ro.product.device
my phone has t0ltespr as ro.product.device
Hopefully I can just edit the script. I'm going to Nandroid and try. will let you know results.
EDIT==
Changed the update-script and zip flashed with no errors, but TWRP still starts when I reboot to recovery.
Just tried to Flash this but is just "Failed"
all set..Skunk and Daniel got me squared away..thanks...are the twrp backups compatible w/this recov?
3.0VTEC23 said:
Just tried to Flash this but is just "Failed"
all set..Skunk and Daniel got me squared away..thanks...are the twrp backups compatible w/this recov?
Click to expand...
Click to collapse
Yes, if you find the "custom backup and restore" menu
Sorry, I'll just remove the checks from the updater-script then, they don't seem to be working right