[Recovery] & [Root] [T211] CWM Recovery v6.0.4.9.KK Unofficial - Galaxy Tab 3 7.0 Android Development

READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
Updated to CWM v6.0.4.9.KK on 10-28-14. Now works properly with KitKat bootloader.
Now with SELinux enabled kernel for flashing roms that require it.
Click HERE for the latest version.
Compiled from source.
@ketut.kumajaya has provided us with a kernel for CWM recovery.
Here is CWM recovery for the T211.
Please report any bugs here in this thread.
It takes a few seconds longer for CWM to boot than the stock recovery, so be patient.
Credits go to:
@ketut.kumajaya for working kernels
@Jamison904 for giving us root
@hkjr for getting ketut to help
@k.aibutsu and @Unjustified Dev for there device source work
and of course Koush and the CyanogenMod team
Supplied in 3 formats:
Odin flashable tar.md5 (for first time installation)
Recovery flashable zip (requires a custom recovery to currently be installed)
.img file (for those who use Flashify or other direct methods).
Instructions for ODIN: (use T211.CWMv.....recovery.tar.zip)
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the highlight doesn't move on the recovery menu, the selection actually does change. Go ahead and hit Power to select. If the menu goes blank, just hit Volume Up or Down to get it to reappear.
It appears that the menu navigation issue only happens when you use the button combination to boot into recovery. If you use the Quick Boot app or "adb reboot recovery", it seems to work properly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If it doesn't boot into recovery:
Please reboot into android (hold power until it reboots) and send me the last_kmsg. See my thread about ADB in the General section for instructions.
To get the last_kmsg with adb use: adb shell cat /proc/last_kmsg > last_kmsg.txt
Stock T211 recovery also attached.
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
+++++++++++++++++++++++++++++++
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
+++++++++++++++++++++++++++++++
DOWNLOADS
Click HERE for the latest version.

Reserved

gr8nole said:
Here is an attempt to get CWM recovery working for the T211. Please test and report back.
Click to expand...
Click to collapse
Unfortunately, Kernel Panic.
It tested a guy from Russian forum 4PDA. See here: http://4pda/
Please tell me where is the log?
I can send it later if you need.

Updated to Test #2

Dasdranamin said:
Unfortunately, Kernel Panic.
It tested a guy from Russian forum 4PDA. See here: http://4pda/
Please tell me where is the log?
I can send it later if you need.
Click to expand...
Click to collapse
I added the adb command to get last_kmsg to the OP. You have to pull it immediately after rebooting after the failure (before any secondary reboots) or it will get overwritten.

gr8nole said:
I added the adb command to get last_kmsg to the OP. You have to pull it immediately after rebooting after the failure (before any secondary reboots) or it will get overwritten.
Click to expand...
Click to collapse
:good:
IT WORKS!!!
See http://4pda.ru
Can You make the TWRP too?

Dasdranamin said:
:good:
IT WORSKS!!!
See http://4pda.ru
Can You make the TWRP too?
Click to expand...
Click to collapse
Great, I will make TWRP once we get a few more confirmations that all is working properly. Thanks for testing.:good:

Here You can see the results http://4pda.ru
Sorry, on russian.
http://cs3-3.4pda.to/3636459.jpg
http://cs3-3.4pda.to/3636435.jpg

IT WORKS!!!:laugh:
PLEASE LINK DOWNLOAD BEST ROM FOR T211. :good:

vmollz said:
IT WORKS!!!:laugh:
Click to expand...
Click to collapse
Does this mean that we will be able to flash a zip file for root (of stock ROM, without using a custom ROM?).
If so, could someone pleae link to that zip file?
Thanks

Nice!
I already know ROMs are different for 211 and 210, but what about kernels? Do we need separate, specific kernels for SM-T211 devices, or just flash SM-T210 kernels?

tristan_2468 said:
Does this mean that we will be able to flash a zip file for root (of stock ROM, without using a custom ROM?).
If so, could someone pleae link to that zip file?
Thanks
Click to expand...
Click to collapse
Universal root zip added to OP (zip provided by @ketut.kumajaya).

toxicdog said:
Nice!
I already know ROMs are different for 211 and 210, but what about kernels? Do we need separate, specific kernels for SM-T211 devices, or just flash SM-T210 kernels?
Click to expand...
Click to collapse
@ketut.kumajaya has a custom kernel for T211 in his blackhawk kernel thread.

custom ROM

vmollz said:
custom ROM
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2447053
That's the only one.
Sent from my DROID RAZR MAXX HD

New version (v2) in the OP. This version corrects the touchscreen orientation. That is only important if you flash a zip with a touch interface (such as Aroma File Manager).

im still new with this tab. there is a universal root zip. does this means i dont have to use the other method of rooting by zidkijah?

StormTrooper89 said:
im still new with this tab. there is a universal root zip. does this means i dont have to use the other method of rooting by zidkijah?
Click to expand...
Click to collapse
That is correct...just install CWM, then flash the root zip.
Sent from my DROID RAZR MAXX HD

i have dloaded the file but when i try to search for it in ODIN it didnt detect the dloaded file. i even try rename the file but still odin doesnt show up the file. any tips?

StormTrooper89 said:
i have dloaded the file but when i try to search for it in ODIN it didnt detect the dloaded file. i even try rename the file but still odin doesnt show up the file. any tips?
Click to expand...
Click to collapse
Extract it from the zip. Odin should find the tar.md5 file.
Sent from my DROID RAZR MAXX HD

Related

[RECOVERY] aCWM 6.x - N5100 / N5110 / N5120 - Sr#1

Hey, I bring to you the first Clockworkmod Recovery or commonly known as CWM for your N5100 and N5110. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods. *Now known as Advanced CWM or aCWM. Thankyou to 'xperiacle' and 'GSLEON3' for giving me the stock recoveries and kernels for N5100/10, so I could start off with my work.
Works perfectly now. OP will only be updated with stable releases, everything else will be floating around the thread.
I have provided the stock recovery if you encounter any issues, you can always flash back.
Featues:
Most things you would expect from stock CWM
EFS backup / restore
Removed option to: report error / show log / testkeys
More to come...
Downloads:
Use this if you are having problems with your SDCard. (Mount / Backup / Restore)
N5100 / N5110
Stable Release #1: ODIN | ZIP
Stock Recovery: http://d-h.st/tHx
N5120
Stable Release #1: ODIN
Stock Recovery: http://d-h.st/51H
Changelog:
Code:
[I][U]Stable Release #1[/U][/I]
Added reboot menu (rom, download, recovery)
Advanced CWM = aCWM
Code:
[I][U]Experimental #6[/U][/I]
Working EFS backup / restore under 'advanced' tab
Removed keytest / report error / show log options
Custom recovery, no more to be called 'stock' CWM, more device specific features to be added
N5120 support
Fix permissions now directed to /sdcard/.android_secure
Cleaned up some code for flashing zips
[I][U]Experimental #5[/U][/I]
[COLOR="Red"]REMOVED DUE TO ISSUES[/COLOR]
Touch recovery (reimplemented)
Universal for 5100 / 5110
Fixed up some mount lengths
Fixed up init.rc
[I][U]Experimental #4[/U][/I]
Display issues fixed
[I][U]Experimental #3[/U][/I]
Built again with fresh tree - n5110
(info: skipped for n5100)
[I][U]Experimental #2[/U][/I]
Touch Input excluded (temp)
kernel built from source with dancing cwm patch
[I][U]Experimental #1[/U][/I]
Public release
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your n5100. Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'xperiacle' for giving me the stock recovery and boot.img. Flash with Odin
This has not been tested by me and is still experimental. I hold no responsibility for any
problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $$$.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back.
Downloads:
CWM Recovery: http://d-h.st/rDv
Stock Recovery: http://d-h.st/tHx
Changelog:
Code:
[I][U]Release #1[/U][/I]
Public release
Click to expand...
Click to collapse
Thanks now we need one for the N5110.
rfb813 said:
Thanks now we need one for the N5110.
Click to expand...
Click to collapse
Just need to check if this works properly. If yes, then n5110 is up next
emwno said:
Just need to check if this works properly. If yes, then n5110 is up next
Click to expand...
Click to collapse
Thanks!
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Southrice said:
Thanks man, that was fast work
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Nothing to be credited for, until the device boots to CWM
How do you flash this custom recovery with ODIN?, what version?, thanks
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
How did you flash, Odin?
brosenz said:
How did you flash, Odin?
Click to expand...
Click to collapse
I added the zip to the pda area and flash Odin v3.07
I installed the image with ADB.
put the recovery image on the sdcard mount or ext sdcard mount
ADB to the note 8.0
su to root
go to your image directory
dd if=xxx.img of=/dev/block/mmcblk0p6
switch back to the note and reboot directly to recovery (i used goomanager)
it does boot the first time - but it is jittery and in landscape mode.
after the first system boot- the device wipes it and goes back to stock recovery.
I have seen this with other stock android devices- sometimes there
is a script that gets triggered on boot to remove any custom recoveries.
I did clear the recovery check from CWM - but it was hard to see because of the
landscape mode and the screen jumping around.
It looks like the full backup is working- now I wonder what ROM will be close enough
to the 8.0 to try flashing.
Speedy Gonzalez said:
I added the zip to the pda area and flash Odin v3.07
Click to expand...
Click to collapse
Any idea why it didn't flash with Odin?
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Speedy Gonzalez said:
I flash the file 2 times and it said pass but when reboot to recovery is stock so I don't know what went wrong
Click to expand...
Click to collapse
Found this Q&A in the Note 10.1 rooting guide in RootGalaxyNote.com:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
This may have been the problem.
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
rfb813 said:
Q: I don’t see ClockworkMod Recovery when I enter recovery, I see stock Android recovery.
A: With newer software updates, you may be encountering this error because it will overwrite ClockworkMod Recovery upon reboot. To get around this, simply boot into ClockworkMod Recovery right after flashing in ODIN. You can set auto-reboot off in ODIN then when done, just hold down Power and Volume Down straight to bootloader menu.
Click to expand...
Click to collapse
Those having issues, try that ^^^
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
Yeah, But i'd like to keep, just incase something goes insanely wrong. The stock recovery.img is provided, you can always flash back it something goes wrong. And i am readying up TWRP, may need you to pull some logs if it doesnt boot
jntdroid said:
To get it to stop resetting to stock recovery every time you reboot, under /system, there is a file named "recovery-from-boot.p". Rename it to .bak or whatever. That file is typically the culprit for custom recoveries not 'sticking'.
Also, we don't have a factory image yet, do we? I'm hesitant to mess too much with this stuff until we have a way to Odin ourselves out of a softbrick.
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
Also, to the OP, thanks for doing this. I'm pretty familiar with adb if you'd like to do TWRP. Would love to have it instead of CWM!
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-N5100
http://samsung-updates.com/device/?id=GT-N5110
I will be releasing a full Note 8.0 Toolkit today or tomorrow with support to rename the stock recovery restore files so that custom recovery isnt overwritten after flashing. If anyone wants to help test please email me at [email protected]
Mark.
Attached is a tar of recovery.log pulled with ADB while booted to CWM.
The display goes to landscape on boot - and the fonts seem extra large.
When the vol up/down navigates the screen jumps and you can't see the
highlighted option.
It is usable with trial and error if you know the order of the CWM menus and
use the vol up/down and power to navigate.
emwno said:
@xbill9
Code:
adb pull /tmp/recovery.log
for fixes
Click to expand...
Click to collapse
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
I tried changing orientation before boot - it always goes to landscape.
I attached 2 images - one is the display after the first CWM boot.
The second is after pressing Vol Up to navigate to the 2nd menu option.
I have seen jumpy CWM presentation like this on some smaller screens like the
Sony Xperia 2011/2012 phones.
emwno said:
Only thing I can judge by that are the missing mount types for the recovery.fstab. Ill fix that now. But someone, try keeping the device physically portrait and see if cwm works properly then, if not then physically landscape.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
P.S try using touch input, its a touch recovery, or so I built it
^thats why fonts are large
^thats why there are no indicators
Click to expand...
Click to collapse

[Recovery] and [Root] Galaxy Tab 3 Lite T110, CWM, TWRP, Philz Touch

End of support. Thread closed.
If you get stuck in recovery and can't boot into Android, you need to install the stock recovery to get Android to boot.
Stock recovery flashable zip located HERE.
------------------------------------------------------------------------------------------------------
READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
CWM Recovery 6.0.4.8
(TWRP is in post 3, Philz Touch in post 4)
Click HERE for the latest version.
Please report any bugs here in this thread.
Thank you to everyone who has (and still will) help in testing!!!!
Credits go to:
@Unjustified Dev for device and kernel source trees
and of course Koush and the CyanogenMod team
Watch THIS VIDEO tutorial for a step by step visual guide for performing the instructions listed below (thanks @Tomsgt for the video).
Instructions:
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them). Also need to enable USB debugging.
7. Select "PDA" (or AP) then choose the recovery file you want to flash. (Unzip the file you downloaded so that you have a file named "recovery.tar.md5".)
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 9).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Watch this video to learn about the navigation issues and Rainbow Mode: http://youtu.be/iCNdxlNzdBI
If the highlight doesn't move on the recovery menu, the selection actually does change. Go ahead and hit Power to select. If the menu goes blank, just hit Volume Up or Down to get it to reappear.
It appears that the menu navigation issue only happens when you use the button combination to boot into recovery. If you use the Quick Boot app or "adb reboot recovery", it seems to work properly. Only use the 3-button method to boot into recovery.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Flash at own risk!!!!
+++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++
Click HERE for the latest version.
Stock recovery flashable zip located HERE.
Nice!
Sent from the can using two ply
TWRP is reported to be causing problems for now. Please use CWM or Philz Touch (post 4) for now.
TWRP 2.7.0.1 (unofficial)
Click HERE to download the latest version.
I do not have a T110, so this recovery has not been tested by me. Please report if it works for you.
Same install instructions as above.
After installation, you may experience slow behavior in recovery if you use the button combination to boot into recovery. Using Quick Boot from the play store or any other software method to boot into recovery will solve this problem.
Internal card gets mounted as "/data/media/0".
Please report any issues here in this thread and be sure to include which recovery you are using.
+++++++++++++++++++++++++++++++++++++
If you already have root, you can extract the recovery.img from this zip and flash it without Odin by using Flashify from the Play Store.
+++++++++++++++++++++++++++++++++++++
Click HERE to download the latest version.
Unofficial Philz Touch Advanced CWM recovery HERE for testing.
Credits to Phil3759. Original thread located HERE.
Hey hey hey...
Sent from my SPH-L710 using Tapatalk
You are awesome!!!!!
This is so very awesome....thank you!!!!
Sent from my SM-T110 using xda app-developers app
This is amazing, super fast devs rooting the tab 3 lite in no time.
Now it's waiting for a good stock Google rom to speed up this nice tab and losing the awful touchwhizz laggynes.
I have tryed almost all your custom recoverys CWM and none were working. When i try to eneter in recovery i got only blackscreen and the device it is seen by adb
But TWRM is perfect!
Thanks
Getting a notification to update but I haven't rooted yet so I'm not sure if I should.... Had my tab for about a week now....it says some kind of security update anybody else get this
Sent from my SM-T110 using xda app-developers app
mhopewell41 said:
Getting a notification to update but I haven't rooted yet so I'm not sure if I should.... Had my tab for about a week now....it says some kind of security update anybody else get this
Sent from my SM-T110 using xda app-developers app
Click to expand...
Click to collapse
Security is something else. Not software update.
It is a new protection from samsung, generaly with knox from 4.2.2 software and newer!
TWRP updated to version 2.7.0.0
Hi, thanks for the share of recovery, i have a problem tho, the device is in a bootloop of recovery, i press reboot to system in twrp and it reboots to twrp, if i power off the tablet and power on it boots to twrp, i've factory reset but stills reboots to twrp, what can i do?
sewa2k said:
Hi, thanks for the share of recovery, i have a problem tho, the device is in a bootloop of recovery, i press reboot to system in twrp and it reboots to twrp, if i power off the tablet and power on it boots to twrp, i've factory reset but stills reboots to twrp, what can i do?
Click to expand...
Click to collapse
Did you wipe anything while booted into recovery? I sounds like system or boot was wiped. You may need to flash the stock firmware in Odin.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Did you wipe anything while booted into recovery? I sounds like system or boot was wiped. You may need to flash the stock firmware in Odin.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Stuck in bootloop in recovery as well after rooting. Using CWM recovery and did not wipe anything at all. Going to try again.
sewa2k said:
Hi, thanks for the share of recovery, i have a problem tho, the device is in a bootloop of recovery, i press reboot to system in twrp and it reboots to twrp, if i power off the tablet and power on it boots to twrp, i've factory reset but stills reboots to twrp, what can i do?
Click to expand...
Click to collapse
mhopewell41 said:
Stuck in bootloop in recovery as well after rooting. Using CWM recovery and did not wipe anything at all. Going to try again.
Click to expand...
Click to collapse
Me to.. and im looking for a solution..
Streykatorato said:
Me to.. and im looking for a solution..
Click to expand...
Click to collapse
Try wiping cache.
gr8nole said:
Try wiping cache.
Click to expand...
Click to collapse
Didnt work.. tried.. any other solution?..
Streykatorato said:
Didnt work.. tried.. any other solution?..
Click to expand...
Click to collapse
Tried a full data wipe?
Sent from my SCH-I605
gr8nole said:
Tried a full data wipe?
Sent from my SCH-I605
Click to expand...
Click to collapse
Yup.. tried that too..

How to root I9305 DBT updated with OTA 4.4.4

Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
elektronchika said:
Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
Click to expand...
Click to collapse
install costum recovery via odin and flash supersu in costum recovery, thats it
9134
klemen241 said:
install costum recovery via odin and flash supersu in costum recovery, thats it
Click to expand...
Click to collapse
This is CF-auto-root, which as I said didn't work with 4.3
elektronchika said:
This is CF-auto-root, which as I said didn't work with 4.3
Click to expand...
Click to collapse
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
klemen241 said:
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
Click to expand...
Click to collapse
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
If you let the phone reboot after flashing custom recovery, it will overwrite the custom one with stock one - tried that earlier today
---
sorry, misunderstand, if you update supersu just open knox and close after it shows you options to lock screen - then the supersu handles knox blocking properly
---
edit2: I tried with supersu by chainfire, didn't test with other party superuser.apk
adamuadamu said:
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
Click to expand...
Click to collapse
This also doesn't work...
Try also Koush's Superuser.
Sent from my GT-I9305 using XDA Free mobile app
elektronchika said:
This also doesn't work...
Click to expand...
Click to collapse
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Thank you adamuadamu !!!
It works!
Regards Sonic76
adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
sham79 said:
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
Click to expand...
Click to collapse
first attachment in the OP
direct link: http://forum.xda-developers.com/attachment.php?attachmentid=1680841&d=1359295479
Thanks for the explanation adamuadamu,
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Thanks in advance for the reply and explanation.
Cheers,
Da Fig
Do you have to flash the custom recovery first and then SuperU? Is it possible to just flash SuperU and then using Triangle Away in order to root 4.4.4?
I want root but want to stay as stock as possible.
Da Fig said:
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Click to expand...
Click to collapse
I remember using some older SuperSu (1.9xx) as the files were already on my SD Card
In case you need proper and updated files and you're a bit afraid of confusing them - google for skipsoft toolkit, choose your device, wait for the program to download appropriate files and then in order to get the files you need, you'd have to (all from my memory, in case you'd need more detailed info, let me know and I can check within couple of hours, as I'm not in front of my private PC now)
1. go to root options and use option to push supersu and recovery disabler to your card
2. let the program reboot your phone into download mode
3. contrary to the advice onscreen, use odin, but untick "Auto Reboot", flash your recovery (the program will show you the path to newest recoveries it downloaded upon first run)
4. wait for the recovery being flashed, disconnect the phone, pull the battery. DON'T CLOSE ODIN yet, you may need it if you fail to boot into recovery directly!
5. start the phone using 3-key combo into recovery. if you fail, you'll need to go back to step 2.
6. flash both files copied in step 1.
7. reboot into system
personally I stick with PhilZ touch, as it always checks for root when leaving recovery and offers to repair it
8. go to play store and download or update supersu by chainfire (whatever applies to you)
9. run SuperSU, agree to disable KNOX
Thanks for the reply adamuadamu, I'll try this and see. Apparently most supersu or the correspondent CF-auto-root will do the trick. I'll try your method first, otherwise I'll start playing with different files.
Cheers.
KennyMRos said:
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
Click to expand...
Click to collapse
SuperSU version 2.01 has the forced close problem on 4.4.4.
Download the SuperSU version 2.02 in following thread and install it. It will ask to disable KNOX. select YES.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
:good:
isn't there a way to instal just SU with towelroot installing an old samsung kernel without tripping knox like in this thread?
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
I installed Philz Touch Recovery and fix it all.

[HOW TO][SM-G9008V] Gain ROOT and install GAPPS

I saw a lot of confusion about the China Mobile TD-LTE version of the S5 in the owner's thread, also the explained method uses files that are not easily available and that, in my opinion are not up to standards. In general the procedure to obtain ROOT access and install Google Apps is not different than for any other phone and you need to use standard well known resources.
I will assume you are on the latest firmware, not that it should make any difference, but I only tested that one. At the moment the latest available firmware for the SM-G9008V is CHM-G9008VZMU1ANH3.
RECOVERY
1. Install Samsung USB drivers on your PC
2. Download Odin 3.07 on your PC
3. Download an ODIN flashable recovery onto your PC g9008v-cmw-recovery-6.0.4.8-en(0420).tar.md5 - 12.33 MB
4. Open odin, click the PDA button, navigate to the recovery file (tar file) you just downloaded, MAKE SURE only F. Reset Time is selected, do not select Auto reboot, this is very important!
5. Boot into download mode (hold the menu button, power button, and volume down button all together simultaneously until the device reboots)
6. When you see that odin detects your device(a colored indicator will turn on) click start
7. When Odin is done, disconnect the USB cable and pull out the battery, then boot into Recovery (hold the menu button, power button, and volume up button all together simultaneously until the device reboots)
8. Once in CWM recovery select "reboot system now". CWM will eventually ask you if you want to disable recovery reflashing and you'll be good to go (it may not ask, but in that case you are good to go anyway). This happens only at the first boot after recovery flashing.
If you do not carefully follow steps 6-7-8, the stock ROM will reflash the stock recovery and you'll have to repeat the process.
ROOT
1. Download SuperSU flashable zip from Chainfire UPDATE-SuperSU-v2.14.zip - 2.5 MB
2. Copy UPDATE-SuperSU-v2.14.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate UPDATE-SuperSU-v2.14.zip on your phone and proceed with the installation.
5. Reboot the phone and look for SuperSU, open the app and it will alert you of the presence of KNOX and ask if you want to disable it, go for it, it may take some time.
GOOGLE APPS
1. Download the KitKat official signed package from Cyanogen gapps-kk-20140105-signed.zip - 83.1 MB
2. Copy gapps-kk-20140105-signed.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate gapps-kk-20140105-signed.zip on your phone and proceed with the installation.
5. Reboot your phone and you're done.
To remove/hide bloatware I suggest to use Titanium Backup.
CHANGELOG
16/10/2014
- updated SuperSU to 2.14
- added additional steps to avoid automatic stock recovery reflash
I added some steps to avoid stock recovery reflash, forgot that very important step!
Hi bubbl3,
I was wondering if you have tried to install the gapps without a custom recovery.? The reason I am asking is that when I try to flash gapps with stock recovery I get an error message that says: signature verification failed. Tried with and without root.
I don't have exactly your phone but close, Sm-g9008w.
//Jaco
Jaco_dk said:
Hi bubbl3,
I was wondering if you have tried to install the gapps without a custom recovery.? The reason I am asking is that when I try to flash gapps with stock recovery I get an error message that says: signature verification failed. Tried with and without root.
I don't have exactly your phone but close, Sm-g9008w.
//Jaco
Click to expand...
Click to collapse
Gave up on trying on stock recovery and installed custom recovery, then everything went smoothly.
//Jaco
Jaco_dk said:
Gave up on trying on stock recovery and installed custom recovery, then everything went smoothly.
//Jaco
Click to expand...
Click to collapse
Yes, sorry for the late reply, you cannot flash the gapps in stock recovery.
Which recovery did you flash on your G9008W, the one in this thread?
bubbl3 said:
Yes, sorry for the late reply, you cannot flash the gapps in stock recovery.
Which recovery did you flash on your G9008W, the one in this thread?
Click to expand...
Click to collapse
No problem at all, just meant I was forced to test a bit in the blind, as it really hard to find any information regarding the SM-G9008W.
Yeah, I used your recovery as your phone got almost the same firmware version(G9008WZMU1ANH3), so I expected that it would work and it worked like a charm.
How much bloatware did you remove with Titanium? I got a few things apps I am not sure if I can remove without any consequence.
Jaco_dk said:
No problem at all, just meant I was forced to test a bit in the blind, as it really hard to find any information regarding the SM-G9008W.
Yeah, I used your recovery as your phone got almost the same firmware version(G9008WZMU1ANH3), so I expected that it would work and it worked like a charm.
How much bloatware did you remove with Titanium? I got a few things apps I am not sure if I can remove without any consequence.
Click to expand...
Click to collapse
Thanks for the confirmation, there's some people that will appreciate as there is no official english recovery for the 9008W.
I basically removed all the chinese stuff and a couple of samsung apps.
bubbl3 said:
Thanks for the confirmation, there's some people that will appreciate as there is no official english recovery for the 9008W.
I basically removed all the chinese stuff and a couple of samsung apps.
Click to expand...
Click to collapse
@Jaco_dk : there is a specific CWM for the SM-G9008W, you may want to flash this one to avoid any hidden incompatibilities: http://www.studenikin.ru/svarom/files/g9008w-cwm-recovery-6.0.5.0-en(0715).tar
bubbl3 said:
@Jaco_dk : there is a specific CWM for the SM-G9008W, you may want to flash this one to avoid any hidden incompatibilities: http://www.studenikin.ru/svarom/files/g9008w-cwm-recovery-6.0.5.0-en(0715).tar
Click to expand...
Click to collapse
Hi. Even I have the Chinese version G9008W and was looking how to root it with English language.
The link you gave is of a Russian site. Is the recovery in English? Are the recoveries given in OP in English?
Thanks for your replies.
gverma1 said:
Hi. Even I have the Chinese version G9008W and was looking how to root it with English language.
The link you gave is of a Russian site. Is the recovery in English? Are the recoveries given in OP in English?
Thanks for your replies.
Click to expand...
Click to collapse
Yes, both recoveries are in English.
bubbl3 said:
I saw a lot of confusion about the China Mobile TD-LTE version of the S5 in the owner's thread, also the explained method uses files that are not easily available and that, in my opinion are not up to standards. In general the procedure to obtain ROOT access and install Google Apps is not different than for any other phone and you need to use standard well known resources.
I will assume you are on the latest firmware, not that it should make any difference, but I only tested that one. At the moment the latest available firmware for the SM-G9008V is CHM-G9008VZMU1ANH3.
RECOVERY
1. Install Samsung USB drivers on your PC
2. Download Odin 3.07 on your PC
3. Download an ODIN flashable recovery onto your PC g9008v-cmw-recovery-6.0.4.8-en(0420).tar.md5 - 12.33 MB
4. Open odin, click the PDA button, navigate to the recovery file (tar file) you just downloaded, MAKE SURE only F. Reset Time is selected, do not select Auto reboot, this is very important!
5. Boot into download mode (hold the menu button, power button, and volume down button all together simultaneously until the device reboots)
6. When you see that odin detects your device(a colored indicator will turn on) click start
7. When Odin is done, disconnect the USB cable and pull out the battery, then boot into Recovery (hold the menu button, power button, and volume up button all together simultaneously until the device reboots)
8. Once in CWM recovery select "reboot system now". CWM will eventually ask you if you want to disable recovery reflashing and you'll be good to go (it may not ask, but in that case you are good to go anyway). This happens only at the first boot after recovery flashing.
If you do not carefully follow steps 6-7-8, the stock ROM will reflash the stock recovery and you'll have to repeat the process.
ROOT
1. Download SuperSU flashable zip from Chainfire UPDATE-SuperSU-v2.14.zip - 2.5 MB
2. Copy UPDATE-SuperSU-v2.14.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate UPDATE-SuperSU-v2.14.zip on your phone and proceed with the installation.
5. Reboot the phone and look for SuperSU, open the app and it will alert you of the presence of KNOX and ask if you want to disable it, go for it, it may take some time.
Click to expand...
Click to collapse
Thanks for your detailed step-by-step instructions. Just wanted to reconfirm in Step 8 when it asks to disable recovery reflashing - do I have to say 'yes' (disable recovery reflashing) or 'no' (don't disable recovery reflashing).
Thanks
gverma1 said:
Thanks for your detailed step-by-step instructions. Just wanted to reconfirm in Step 8 when it asks to disable recovery reflashing - do I have to say 'yes' (disable recovery reflashing) or 'no' (don't disable recovery reflashing).
Thanks
Click to expand...
Click to collapse
You should answer 'yes' (disable recovery reflashing)
bubbl3 said:
Yes, both recoveries are in English.
Click to expand...
Click to collapse
Great! I had got this phone pre-rooted by the vendor and he has messed up deleting apps and deleted important stuff like keyboard, etc. I will be flashing latest stock Samsung firmware from Sammobile.com and then try your method to root. Hope that goes through fine. Will I have to flash GAPPS as well?
Also, I hope I don't lose my dual SIM functionality by rooting the stock ROM. Will I?
Thanks
gverma1 said:
Great! I had got this phone pre-rooted by the vendor and he has messed up deleting apps and deleted important stuff like keyboard, etc. I will be flashing latest stock Samsung firmware from Sammobile.com and then try your method to root. Hope that goes through fine. Will I have to flash GAPPS as well?
Also, I hope I don't lose my dual SIM functionality by rooting the stock ROM. Will I?
Thanks
Click to expand...
Click to collapse
You will have to flash GAPPS as the original stock ROM doesn't include them, also I don't see how you can loose dual SIM functionality if you flash the stock ROM.
bubbl3 said:
Thanks for the confirmation, there's some people that will appreciate as there is no official english recovery for the 9008W.
I basically removed all the chinese stuff and a couple of samsung apps.
Click to expand...
Click to collapse
Yes, I had a lot of problems finding any informations about the G9008W, that's also why I decided to write in your thread, hoped others could find it useful.
Nice, I will try to remove as much as possible myself then.
bubbl3 said:
@Jaco_dk : there is a specific CWM for the SM-G9008W, you may want to flash this one to avoid any hidden incompatibilities: http://www.studenikin.ru/svarom/files/g9008w-cwm-recovery-6.0.5.0-en(0715).tar
Click to expand...
Click to collapse
Thanks for the help, however I don't have any problems what so ever, so I think I will keep using yours for now.
Does it work on SM-G9006W?
bubbl3 said:
I saw a lot of confusion about the China Mobile TD-LTE version of the S5 in the owner's thread, also the explained method uses files that are not easily available and that, in my opinion are not up to standards. In general the procedure to obtain ROOT access and install Google Apps is not different than for any other phone and you need to use standard well known resources.
I will assume you are on the latest firmware, not that it should make any difference, but I only tested that one. At the moment the latest available firmware for the SM-G9008V is CHM-G9008VZMU1ANH3.
RECOVERY
1. Install Samsung USB drivers on your PC
2. Download Odin 3.07 on your PC
3. Download an ODIN flashable recovery onto your PC g9008v-cmw-recovery-6.0.4.8-en(0420).tar.md5 - 12.33 MB
4. Open odin, click the PDA button, navigate to the recovery file (tar file) you just downloaded, MAKE SURE only F. Reset Time is selected, do not select Auto reboot, this is very important!
5. Boot into download mode (hold the menu button, power button, and volume down button all together simultaneously until the device reboots)
6. When you see that odin detects your device(a colored indicator will turn on) click start
7. When Odin is done, disconnect the USB cable and pull out the battery, then boot into Recovery (hold the menu button, power button, and volume up button all together simultaneously until the device reboots)
8. Once in CWM recovery select "reboot system now". CWM will eventually ask you if you want to disable recovery reflashing and you'll be good to go (it may not ask, but in that case you are good to go anyway). This happens only at the first boot after recovery flashing.
If you do not carefully follow steps 6-7-8, the stock ROM will reflash the stock recovery and you'll have to repeat the process.
ROOT
1. Download SuperSU flashable zip from Chainfire UPDATE-SuperSU-v2.14.zip - 2.5 MB
2. Copy UPDATE-SuperSU-v2.14.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate UPDATE-SuperSU-v2.14.zip on your phone and proceed with the installation.
5. Reboot the phone and look for SuperSU, open the app and it will alert you of the presence of KNOX and ask if you want to disable it, go for it, it may take some time.
GOOGLE APPS
1. Download the KitKat official signed package from Cyanogen gapps-kk-20140105-signed.zip - 83.1 MB
2. Copy gapps-kk-20140105-signed.zip on your External SD Card
3. Boot the phone into recovery mode (shutdown the phone, then start it pressing Volume+/up, home button and power for several seconds)
4. Select "install zip" and then "choose zip from /storage/extSdCard", locate gapps-kk-20140105-signed.zip on your phone and proceed with the installation.
5. Reboot your phone and you're done.
To remove/hide bloatware I suggest to use Titanium Backup.
CHANGELOG
16/10/2014
- updated SuperSU to 2.14
- added additional steps to avoid automatic stock recovery reflash
Click to expand...
Click to collapse
I have seen these threads for a while and I couldn't find anything related to my SM-G9006W, even on other threads, I didn't see anything about SM-G9006W. I also recently updated it to Lollilop 5, not sure if that make more complicated to install GAPPS. If you know anything about how to root this phone and install GAPPS, please let me know, I would be really appreciated. Thank you
Hi. G9008W has got Lollipop update. I plan to flash it after downloading from sammobile site. Will this method be still valid to root the phone running Lollipop? Will this CWM work? Of course, I'll flash Lollipop CM gapps. Thanks.
Sent from my Nexus 5 using XDA Free mobile app
gverma1 said:
Hi. G9008W has got Lollipop update. I plan to flash it after downloading from sammobile site. Will this method be still valid to root the phone running Lollipop? Will this CWM work? Of course, I'll flash Lollipop CM gapps. Thanks.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi gverma1,
Have you tried it yet?
I am downloading the lolipop update right now, and I was wondering exactly the same if the CWM will work with Lolipop, as I need google play.
I will try and see if Chainfire is willing to make a new CFAuto root for Lolipop for SM-G9008W when I am done with downloading the firmware.
//Jaco
Downloading here myself. But on checking CWM versions for other phones including other S5 variants, the version required seems to be 6.0.4.8 whereas we have 6.0.5.0 here. So I don't think there would be any issues.
gverma1 said:
Downloading here myself. But on checking CWM versions for other phones including other S5 variants, the version required seems to be 6.0.4.8 whereas we have 6.0.5.0 here. So I don't think there would be any issues.
Click to expand...
Click to collapse
Hi gverma1,
I just finished updating to Lolipop, and I installed the 6.0.5.0 and it works just fine.
However it didn't like the PA Gapps Nano, got stuck att starting up apps. So I am going to test some different once now.
Update. The Gapps actually worked after a factory reset.
//Jaco.

[ROM] 100% Stock L720_OD2 - 5.0.1 (Original Model Only)

**Suggested** FlashFire - Play BETA - PREVIEW (ROM is also compatible with TWRP).
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Caution!** The following process is only for the original Sprint L720 S4 Variant. Use on any other device may result in a hardbrick!
Download:
- L720_OD2_Stock_Rooted_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Wipe" and check all options except "Internal storage" then press the checkmark to continue.
5. Press "(+)" once again and select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
6. From the main menu "Tap-Hold-Drag" your "Actions" and place them in the following order:
- "Wipe"
- "Flash Zip or OTA"
7. Uncheck all options under "EverRoot" and use default "Reboot" setting.
8. Last, press the lightning bolt then "Ok" to begin the flash.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Samsung splash screen for about 5 - 7 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- Wifi may not function. To resolve the issue...power down (or pull battery) before entering "Download" Mode then Odin flash the modem from Post #2.
Notes:
1. The ROM will update your Modem, Non-hlos, Kernel, System, and Bootloader to OD2 (your recovery will not be updated).
2. The ROM is also compatible with TWRP (Full wipe recommended)!
3. To learn more about FlashFire's capabilities see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Alternative Odin Method:
1. Extract the L720_OD2_Pre-Rooted_Firmware.tar from the .rar archive.
2. Pull battery from your device then reinsert and boot into "Download" mode.
3. Uncheck "Auto-Reboot" in Odin and flash the firmware using PDA/AP Slot (depending on your Odin version).
4. Once the flash completes pull the battery again and boot into Recovery, perform a Factory Data Reset then Reboot. Done!
Notes:
1. This method will void your warranty and set your warranty bit to (0x1).
2. This method will update your modem, kernel, and system to OD2 but will not update your bootloader or recovery.
Allow from 5 - 7 minutes for first boot.
Stock - Odin Flashable
Stock - Odin Flashable
- L720V_OD2_Stock_Modem
- L720V_Stock_Recovery
- L720V_OD2_Stock_Kernel
Possible to make a complete firmware, bootloader and modem only (no stock recovery) flashable?
troyboytn said:
Possible to make a complete firmware, bootloader and modem only (no stock recovery) flashable?
Click to expand...
Click to collapse
Yes, its possible.
muniz_ri said:
Yes, its possible.
Click to expand...
Click to collapse
Awesome, those would be flash by Odin in the PDA slot, correct?
troyboytn said:
Awesome, those would be flash by Odin, correct?
Click to expand...
Click to collapse
Yes, but you can also flash with FlashFire.
Great work! Glad to see there are still some developers left for this device!
Just curious - for the modem only, I see it includes non-hlos.bin and mdm.bin. What does apnhlos.bin do, and why is it not included in the modem tar? I also noticed previous modem-only's have not included apnhlos, but I am wondering if we are missing out on added functionality by not keeping that up to date as well?
Thanks.
It is compatible with TWRP, but I assume it isn't compatible with Philz Recovery(CWM), correct?
koivth said:
Great work! Glad to see there are still some developers left for this device!
Just curious - for the modem only, I see it includes non-hlos.bin and mdm.bin. What does apnhlos.bin do, and why is it not included in the modem tar? I also noticed previous modem-only's have not included apnhlos, but I am wondering if we are missing out on added functionality by not keeping that up to date as well?
Thanks.
Click to expand...
Click to collapse
The non-hlos is the lte portion of the modem and you can get away with it on unlocked bootloader devices but still a good practice to have all matching partitions in my opinion.
will flashing this with FlashFire replace a custom recovery with the stock recovery?
Thanks for doing this so fast! Great work!
aypanthony said:
will flashing this with FlashFire replace a custom recovery with the stock recovery?
Thanks for doing this so fast! Great work!
Click to expand...
Click to collapse
Yes it will, but as I understand it, if you use Flashfire, a custom recovery is no longer needed?
aypanthony said:
will flashing this with FlashFire replace a custom recovery with the stock recovery?
Thanks for doing this so fast! Great work!
Click to expand...
Click to collapse
Yes, it will replace your custom recovery with stock OD2.
The idea was to share a way to update to stock, rooted OD2 without first having to Odin back to stock to successfully take the ota.
You can then reflash Twrp after flashing the ROM or continue using FF for flashing zips/backups, etc.
muniz_ri said:
Yes, it will replace your custom recovery with stock OD2.
The idea was to share a way to update to stock, rooted OD2 without first having to Odin back to stock to successfully take the ota.
You can then reflash Twrp after flashing the ROM or continue using FF for flashing zips/backups, etc.
Click to expand...
Click to collapse
This is awesome! I am running a backup right now. I will report back once I have completed the flash.
Thanks!
So I was referenced here by the main thread: http://forum.xda-developers.com/gal...ginal-galaxy-s4-update-zip-od2-t3105607/page5
I rooted a long time ago but went back to stock (through recovery) about a month ago. I'm attempting to update to OD2 but I keep getting error 7. Can I just download this zip and push it via ADB?
monkeychef said:
So I was referenced here by the main thread: http://forum.xda-developers.com/gal...ginal-galaxy-s4-update-zip-od2-t3105607/page5
I rooted a long time ago but went back to stock (through recovery) about a month ago. I'm attempting to update to OD2 but I keep getting error 7. Can I just download this zip and push it via ADB?
Click to expand...
Click to collapse
No, this is ROM and must be flashed with FlashFire if rooted or Twrp.
muniz_ri said:
No, this is ROM and must be flashed with FlashFire if rooted or Twrp.
Click to expand...
Click to collapse
So after flashing with TWRP I will have updated modem and ROM and can simply ODIN TWRP and be ready for business?
clshores said:
So after flashing with TWRP I will have updated modem and ROM and can simply ODIN TWRP and be ready for business?
Click to expand...
Click to collapse
yes
muniz_ri said:
yes
Click to expand...
Click to collapse
And I could then restore my TWRP backup from my current ROM and backup OD2?
clshores said:
And I could then restore my TWRP backup from my current ROM and backup OD2?
Click to expand...
Click to collapse
lol, once you reflash twrp it's twrp....
I can remove the stock OD2 recovery from the ROM so it doesn't overwrite twrp. Thoughts?
muniz_ri said:
lol, once you reflash twrp it's twrp....
I can remove the stock OD2 recovery from the ROM so it doesn't overwrite twrp. Thoughts?
Click to expand...
Click to collapse
If there isn't a benefit to stock recovery (Doesn't sound like it) then I would remove it and simply update the modem and the OS.

Categories

Resources