[Recovery] & [Root]【T210R & T210】 CWM Recovery v6.0.4.9.KK [Unofficial] - Galaxy Tab 3 7.0 Android Development

[Recovery] & [Root]【T210R & T210】 CWM Recovery v6.0.4.9.KK [Unofficial]
READ THIS POST BEFORE INSTALLING ANY CUSTOM RECOVERY
Updated to CWM v6.0.4.9.KK on 9-23-14 to cooperate 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.
Please report any bugs here in this thread.
Please take a moment to say thanks and/or donate to @ketut.kumajaya for helping us out.
Thank you to everyone who has (and still will) help in testing!!!!
Credits go to:
@ketut.kumajaya for getting this initially working (see THIS post)
@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
@Tomsgt for the video
Link to kernel source https://github.com/kumajaya/android_kernel_samsung_lt02
Watch THIS VIDEO tutorial for a step by step visual guide for performing the instructions listed below (thanks @Tomsgt for the video).
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 the ...tar.md5)
1. Download ODIN to 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).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
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).
~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
Flash at own risk!!!!
+++++++++++++++++++++++++++++++
DOWNLOADS
Click HERE for the latest version.
-

If you are using the recovery in post #1, then you can skip this post. This post contains modified stock recoveries only.
I recommend all T210R users should flash the newest firmware from Sammobile, ( or just use my pre-rooted version located HERE ).
The modified stock recovery zips below contain a recovery.tar.md5 file that can be flashed using ODIN. These will allow only Google test key signed zips to be flashed. There are two versions, one for the T210R and one for the T210 devices. Both versions work on my T210R, so try whichever one you feel is appropriate.

gr8nole said:
Since we don't have a working full custom recovery (i.e., TWRP or CWM) yet, we have modified the stock recovery to accept update zips that are signed with the Google test keys.
The zips below contain a recovery.tar.md5 file that can be flashed using ODIN. There are two versions, one for the T210R and one the T210 devices. Both versions work on my T210R, so try whichever one you feel appropriate.
Credits go to:
@ketut.kumajaya for getting this initially working (see THIS post)
@Jamison904 for giving us root
@hkjr for getting ketut to help
Instructions:
1. Download ODIN on your computer (just do a google search to find it...version 3.07 will work fine). http://forum.xda-developers.com/showthread.php?t=2189539
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.
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"
9. Wait for device to restart.
10. Restart to recovery mode to verify it works. It looks just like stock recovery.
It is not as difficult as it looks.
Please report if it works for you and what firmware and device (T210R or T210) you have.
Flash at own risk!!!!
Click to expand...
Click to collapse
Ok. I just flashed the original firmware. Still i cant get into recovery. Then i flashed your modified recovery, but no luck. Now i have tried T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar and then it boots direct in to recovery, but i can not navigate..
---------- Post added at 10:04 PM ---------- Previous post was at 09:58 PM ----------
loselvis777 said:
Ok. I just flashed the original firmware. Still i cant get into recovery. Then i flashed your modified recovery, but no luck. Now i have tried T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar and then it boots direct in to recovery, but i can not navigate..
Click to expand...
Click to collapse
One more thing. Its only when i flash T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar it goes in to recovery, But if i yse the volume key and power nothing..

loselvis777 said:
Ok. I just flashed the original firmware. Still i cant get into recovery. Then i flashed your modified recovery, but no luck. Now i have tried T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar and then it boots direct in to recovery, but i can not navigate..
Click to expand...
Click to collapse
To make sure you are entering recovery correctly, can you install Quick Boot from the play store and use it to enter recovery mode.

gr8nole said:
To make sure you are entering recovery correctly, can you install Quick Boot from the play store and use it to enter recovery mode.
Click to expand...
Click to collapse
No needs root.. just shuts down..
i think one of the problemt is the cache file maybe..
---------- Post added at 10:31 PM ---------- Previous post was at 10:18 PM ----------
loselvis777 said:
No needs root.. just shuts down..
i think one of the problemt is the cache file maybe..
Click to expand...
Click to collapse
by the way when i use T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar i get..
E:Error in /cache/recovery/uroot.zip and stock android recovery..
---------- Post added at 10:49 PM ---------- Previous post was at 10:31 PM ----------
loselvis777 said:
No needs root.. just shuts down..
i think one of the problemt is the cache file maybe..
---------- Post added at 10:31 PM ---------- Previous post was at 10:18 PM ----------
by the way when i use T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar i get..
E:Error in /cache/recovery/uroot.zip and stock android recovery..
Click to expand...
Click to collapse
now i want to try something new.. I just downloaded jamisons prerooted uk firmware, and then i will try the recovery again..

loselvis777 said:
No needs root.. just shuts down..
i think one of the problemt is the cache file maybe..
---------- Post added at 10:31 PM ---------- Previous post was at 10:18 PM ----------
by the way when i use T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar i get..
E:Error in /cache/recovery/uroot.zip and stock android recovery..:
Click to expand...
Click to collapse
FWIW...I got that error too, but I'm already rooted.

loselvis777 said:
No needs root.. just shuts down..
i think one of the problemt is the cache file maybe..
---------- Post added at 10:31 PM ---------- Previous post was at 10:18 PM ----------
by the way when i use T210_SAMSUNG_RECOVERY_SUPERSU-1.55_BUSYBOX-1.22.0.tar i get..
E:Error in /cache/recovery/uroot.zip and stock android recovery..
---------- Post added at 10:49 PM ---------- Previous post was at 10:31 PM ----------
now i want to try something new.. I just downloaded jamisons prerooted uk firmware, and then i will try the recovery again..
Click to expand...
Click to collapse
Okay.. I flashed jamisons prerooted firmware. So now im a superuser. And i have root. I use quick boot to go to recovery, and then i flashed universal-root-t21x-signed.zip from recovery. Its seems that it works now. So now all we have to do is wait for custom roms fingers crosed..
---------- Post added at 11:37 PM ---------- Previous post was at 11:07 PM ----------
Hate to say this. But this means that there is still no root and recovery for original firmware.
So here is a new guide for SM-T210 with normal firmware
Download https://mega.co.nz/#!dkQ1iSYQ!N7TdP2uBs-kc7CYBXnBVMwJyrRQqhoXIXY-90z1nG1E preerootet firmware
Flash with odin PDA. Now you are a superuser
then flash T210_modified_recovery.zip
Install quick boot from playstore.
go to recovery from quickboot and flash universal-root-t21x-signed.zip
http://forum.xda-developers.com/showthread.php?t=2391367&page=27
Now wait for custom roms

loselvis777 said:
Okay.. I flashed jamisons prerooted firmware. So now im a superuser. And i have root. I use quick boot to go to recovery, and then i flashed universal-root-t21x-signed.zip from recovery. Its seems that it works now. So now all we have to do is wait for custom roms fingers crosed..
---------- Post added at 11:37 PM ---------- Previous post was at 11:07 PM ----------
Hate to say this. But this means that there is still no root and recovery for original firmware.
So here is a new guide for SM-T210 with normal firmware
Download https://mega.co.nz/#!dkQ1iSYQ!N7TdP2uBs-kc7CYBXnBVMwJyrRQqhoXIXY-90z1nG1E preerootet firmware
Flash with odin PDA. Now you are a superuser
then flash T210_modified_recovery.zip
Install quick boot from playstore.
go to recovery from quickboot and flash universal-root-t21x-signed.zip
http://forum.xda-developers.com/showthread.php?t=2391367&page=27
Now wait for custom roms
Click to expand...
Click to collapse
If you already have prerooted firmware, then you don't need to flash the universal root zip. You can install SuperSu from play store.

gr8nole said:
If you already have prerooted firmware, then you don't need to flash the universal root zip. You can install SuperSu from play store.
Click to expand...
Click to collapse
I had to flash it to see if would do on the uk firmware. When i flash on the original, it made kernel panic.
Now i can flash it. Wanna hears something strange? My CSC is still NEE(nordic)

I think this relates also to the bootloader version. I will try to build T210 kernel with LZMA initramfs support so we can create a small recovery image. Blame Samsung/Marvell :laugh:

gr8nole said:
Since we don't have a working full custom recovery (i.e., TWRP or CWM) yet, we have modified the stock recovery to accept update zips that are signed with the Google test keys.
The zips below contain a recovery.tar.md5 file that can be flashed using ODIN. There are two versions, one for the T210R and one for the T210 devices. Both versions work on my T210R, so try whichever one you feel is appropriate.
Credits go to:
@ketut.kumajaya for getting this initially working (see THIS post)
@Jamison904 for giving us root
@hkjr for getting ketut to help
Flash at own risk!!!!
Click to expand...
Click to collapse
Awesome job my friend! Working one the first custom ROM now. Should be up tonight. (maybe kernel...muhahaha)

gentlemen - i go without my kids tablet (lol they get the tab3 and i keep the tab2) for 24 hrs or so, and you've gotten to this point? awesome. goes to show everyone's skills and cooperation!

The modified stock recovery does not work for t210r. It still has navigation errors and flashing a google signed.zip(ex. Universalrootsigned.zip) has error called status 7. The only recovery that can run the signed root even in original firmware is the 2nd recovery posted by ketut.kumajaya.
I posted this on the root method thread
Sent from my SM-T210R using xda app-developers app

trazfer said:
The modified stock recovery does not work for t210r. It still has navigation errors and flashing a google signed.zip(ex. Universalrootsigned.zip) has error called status 7. The only recovery that can run the signed root even in original firmware is the 2nd recovery posted by ketut.kumajaya.
I posted this on the root method thread
Sent from my SM-T210R using xda app-developers app
Click to expand...
Click to collapse
It seems to be hit or miss. It works great on my T210R and I tested it with a signed zip.
I plan on returning to stock non-rooted tomorrow and testing more.

Jamison904 said:
Awesome job my friend! Working one the first custom ROM now. Should be up tonight. (maybe kernel...muhahaha)
Click to expand...
Click to collapse
So we can get custom ROMs even with this non CWM/TWRP Recovery??!?!? And you're uploading tonight?.... I'm so excited I might as well explode
Sent from my SM-T210 using xda premium

gr8nole said:
It seems to be hit or miss. It works great on my T210R and I tested it with a signed zip.
I plan on returning to stock non-rooted tomorrow and testing more.
Click to expand...
Click to collapse
I will test more. I will take into consideration ur output. Well i managed to root the original firmare of t210r using the modified recovery and flashing of universalrootsigned.zip in the modified recovery.
Sent from my SM-T210R using xda app-developers app

I compiled recovery kernel from source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t210 + http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat . LZMA support added, the attached recovery image compressed in LZMA format (smaller). I also slightly change my "universal" root, remove device model checking routine. Both package untested, flash it at your own risk!
NOTE: Kernel compiled using Google's arm-eabi 4.6, *lt023g_defconfig. Just compared 3g and wifi defconfig and saw different GPIO config (different buttons behavior?) I need T210 "cat /proc/version" output and please, a quick feedback :good:

Just uploaded the world's smallest Android recovery Both kernel and ramdisk compressed using xz compression method. Try it, may open the opportunities of CWM

Non of the recovery works in my rooted 210R. Same navigation issue.
Sent from my GT-N7100 using xda premium

ketut.kumajaya said:
I compiled recovery kernel from source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t210 + http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat . LZMA support added, the attached recovery image compressed in LZMA format (smaller). I also slightly change my "universal" root, remove device model checking routine. Both package untested, flash it at your own risk!
NOTE: Kernel compiled using Google's arm-eabi 4.6, *lt023g_defconfig. Just compared 3g and wifi defconfig and saw different GPIO config (different buttons behavior?) I need T210 "cat /proc/version" output and please, a quick feedback :good:
Click to expand...
Click to collapse
My results from testing this morning.
I did a factory data reset and then flashed the full US (T210R) firmware to return to completely stock non-rooted status. Then I flashed the T210R modified stock recovery (that I posted here yesterday) and it worked perfectly. I then flashed the new universal root zip provided by @ketut.kumajaya (it did return one error 7 at the end, but still worked) and I was rooted. :good:
I then tried the ketut's new T210R LMZA recovery and it did work, but still had navigation issues. :good:
I then tried ketut's new XZ recovery, but got a kernel panic. :crying:
So, at least for my T210R (with the newest T201R firmware from Sammobile), the recovery in the OP still works perfect.
I look forward to hear more feedback from others users, but for now, I recommend all T210R users should flash the newest firmware from Sammobile, ( or just use my pre-rooted version located HERE ) then give the modified recovery a try.

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] & [Root] [T211] CWM Recovery v6.0.4.9.KK Unofficial

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

CyanogenMod 10.2 Nightlies. M Snapshot released.

3/11/2013 cm-10.2-20131103-NIGHTLY has been released. Download
1/11/2013 M Snapshot has been released. Download
31/10/2013 CyanogenMod 10.2 Nightlies are now up and running. Download link is posted below.
Dogo 10.2 Nightlies
akash4357 said:
CyanogenMod 10.2 Nightlies are now up and running. Download link is posted below.
Dogo 10.2 Nightlies
Click to expand...
Click to collapse
Thanks Bro, could you test this ?
APN option doesnt work !!
what are the bugs??
hey friends! could any one have test it. Please report the bugs. I also want to use this.
akash4357 said:
1/11/2013 M Snapshot has been released. Download
31/10/2013 CyanogenMod 10.2 Nightlies are now up and running. Download link is posted below.
Dogo 10.2 Nightlies
Click to expand...
Click to collapse
I am using it for last eight hours and no bugs so far!
Sent from my C5503 using xda app-developers app
akash4357 said:
1/11/2013 M Snapshot has been released. Download
31/10/2013 CyanogenMod 10.2 Nightlies are now up and running. Download link is posted below.
Dogo 10.2 Nightlies
Click to expand...
Click to collapse
Hi Budy what is the different betten SNAPSHOT and NIGHTIES roms ?
Thanks
there aren't much differences between cm build and fxp build. fxp build may contains a few more patches which haven't trickled down to official cm.
right?
---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------
there aren't much differences between cm build and fxp build. fxp build may contains a few more patches which haven't trickled down to official cm.
right?
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
"M snapshot" = milestone.
http://www.cyanogenmod.org/blog/cyanogenmod-10-2-m1-release
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
"M snapshot" = milestone.
http://www.cyanogenmod.org/blog/cyanogenmod-10-2-m1-release
nostupidthing said:
there aren't much differences between cm build and fxp build. fxp build may contains a few more patches which haven't trickled down to official cm.
right?
---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------
there aren't much differences between cm build and fxp build. fxp build may contains a few more patches which haven't trickled down to official cm.
right?
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
"M snapshot" = milestone.
http://www.cyanogenmod.org/blog/cyanogenmod-10-2-m1-release
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
"M snapshot" = milestone.
http://www.cyanogenmod.org/blog/cyanogenmod-10-2-m1-release
Click to expand...
Click to collapse
Nightlies can be very problematic, but they also get you the latest and greatest. Many times the nightlies work great and get you the latest features (privacy guard) and newest bug fixes (the Android security bugs were fixed in the nightlies before they released new stable builds). In fact, most of the time, nightlies work great. But there are those few times that something gets screwed up (they are built and released automatically with no human intervention). That is why you should always keep your last good install zip on hand, that way you can easily revert if needed.
M Snapshots are designed to be more stable and better tested, but they aren't released nearly as often.
It really depends on the individual. I always use the nightlies (I usually don't even bother installing the stable builds), but I know others who only want the stable builds. You need to decide for yourself.
05/11/2013 cm-10.2-20131105-NIGHTLY has been released
http://get.cm/get/jenkins/46600/cm-10.2-20131105-NIGHTLY-dogo.zip
Edit...
The Link DONT WORK
06/11/2013 cm-10.2-20131106-NIGHTLY has been released
http://get.cm/get/jenkins/46709/cm-10.2-20131106-NIGHTLY-dogo.zip
juanenbas said:
06/11/2013 cm-10.2-20131106-NIGHTLY has been released
http://get.cm/get/jenkins/46709/cm-10.2-20131106-NIGHTLY-dogo.zip
Click to expand...
Click to collapse
how to install this rom can u plz explain in steps plz..
ayushbh said:
how to install this rom can u plz explain in steps plz..
Click to expand...
Click to collapse
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. CONTINUE AT YOUR OWN RISK!!!
Method 1, need to have any rooted rom installed that IS NOT CM 10.2 and a custom recovery (like clockworkmod, more commonly know as CWM)
Step 1. Download the ROM and the latest GAPPS (goo.im/gapps) and put them on your sd card or internal storage, they should be .zip files, if they arent, this wont work.
Step 2. Power of your phone/tablet
Step 3. Boot into your custom recovery by holding the vol.up button, the home button, and the power button, keep holding these buttons but let go when something shows up on the screen (on the sIII (GT-i9300) it says samsung galaxy sIII GT-i9300) if you have a different phone it will say something different.
Step 4. (these steps will differ if you have something other than CWM, but they will be very similar), use the volume keys and the power button to navigate to "install zip" then navigate to where you put the .zip for the rom. If you put it on the internal storage, hit the option at the very top, if you put it on your external microsd card, hit the option above "go back"
Step 5. Do the same as ^step 4^ but choose the gapps .zip instead of the rom .zip
Step 6. Hit "Go Back" then hit "Reboot System Now" ENJOY!!!
Method 2. need to have CYANOGENMOD 10.2 and a custom recovery (like clockworkmod, more commonly know as CWM)
Step 1. Open your settings app and navigate to /About Phone or Tablet/Cyanogenmod Updates/ and hit the download button next to the rom that you want.
Step 2. When its downloaded, your phone will do the rest and then your good to go.
Method 3. phone isnt rooted and NOTHING HAS BEEN FLASHED TO IT, no kernels, no roms, just plain, boring old android straight from the manufacturer.
Step 1.Root your device and install a custom recovery (I dont know what device you have so google it, make sure that a custom recovery is also installed
Step 2. (Follow Method 1 at the top if this post)
ayushbh said:
how to install this rom can u plz explain in steps plz..
Click to expand...
Click to collapse
1) Download and Save the RoM in your phone, like the latest GAPPS
2)You must extract the BOOT.IMG from the ROM
3)With Flashtool flash the boot.img in your phone
4)With CWM first Wipe all and then flash the ROM
5) Flash Gapps
6)Reboot
Like ever do Backup !! this is important if you have any error in the ROM
tomosh22 said:
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. CONTINUE AT YOUR OWN RISK!!!
Method 1, need to have any rooted rom installed that IS NOT CM 10.2 and a custom recovery (like clockworkmod, more commonly know as CWM)
Step 1. Download the ROM and the latest GAPPS (goo.im/gapps) and put them on your sd card or internal storage, they should be .zip files, if they arent, this wont work.
Step 2. Power of your phone/tablet
Step 3. Boot into your custom recovery by holding the vol.up button, the home button, and the power button, keep holding these buttons but let go when something shows up on the screen (on the sIII (GT-i9300) it says samsung galaxy sIII GT-i9300) if you have a different phone it will say something different.
Step 4. (these steps will differ if you have something other than CWM, but they will be very similar), use the volume keys and the power button to navigate to "install zip" then navigate to where you put the .zip for the rom. If you put it on the internal storage, hit the option at the very top, if you put it on your external microsd card, hit the option above "go back"
Step 5. Do the same as ^step 4^ but choose the gapps .zip instead of the rom .zip
Step 6. Hit "Go Back" then hit "Reboot System Now" ENJOY!!!
Method 2. need to have CYANOGENMOD 10.2 and a custom recovery (like clockworkmod, more commonly know as CWM)
Step 1. Open your settings app and navigate to /About Phone or Tablet/Cyanogenmod Updates/ and hit the download button next to the rom that you want.
Step 2. When its downloaded, your phone will do the rest and then your good to go.
Method 3. phone isnt rooted and NOTHING HAS BEEN FLASHED TO IT, no kernels, no roms, just plain, boring old android straight from the manufacturer.
Step 1.Root your device and install a custom recovery (I dont know what device you have so google it, make sure that a custom recovery is also installed
Step 2. (Follow Method 1 at the top if this post)
Click to expand...
Click to collapse
i also have xperia zr only..and i am on stock rom but have rooted it via vroot..so plz tell me the custom recovery which should be installed in order to follow your method 1..thnx
ayushbh said:
i also have xperia zr only..and i am on stock rom but have rooted it via vroot..so plz tell me the custom recovery which should be installed in order to follow your method 1..thnx
Click to expand...
Click to collapse
I used clockworkmod which can be installed with this https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en_GB but you can use any recovery you want as long as it has the ability to flash .zip files.
tomosh22 said:
I used clockworkmod which can be installed with this https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en_GB but you can use any recovery you want as long as it has the ability to flash .zip files.
Click to expand...
Click to collapse
can u also plz post some screen shots of the rom..as to see how it looks like..i don't have much idea about custom roms..thnx
ayushbh said:
i don't have much idea about custom roms..thnx
Click to expand...
Click to collapse
thats ok, we all have to start somewhere, the screenshots are in the attachments
couldnt uplaod more in that post for some reason, theres some more here
tomosh22 said:
I used clockworkmod which can be installed with this https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en_GB but you can use any recovery you want as long as it has the ability to flash .zip files.
Click to expand...
Click to collapse
I dont see any Xperia phone in ROM Manager app for install the CWM Recovery in our Xperia ZR...
How do you installed?
Enviado desde mi C5503 mediante Tapatalk
skorpioneMM said:
I dont see any Xperia phone in ROM Manager app for install the CWM Recovery in our Xperia ZR...
How do you installed?
Enviado desde mi C5503 mediante Tapatalk
Click to expand...
Click to collapse
i just typed in ROM Manager into google play, if you cant find it use this link on either your pc or your phone.
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
tomosh22 said:
i just typed in ROM Manager into google play, if you cant find it use this link on either your pc or your phone.
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Click to expand...
Click to collapse
Sorry, maybe at cause of my bad english i think that i not explained well the question...
Im saying that i can install and open ROM Manager app, but when i open and choose the option for install CWM Recovery i cant see Xperia ZR in the list of devices to install CWM Recovery.
Even If i pick in "show more devices" Xperia ZR doesnt are here then cant install CWM Recovery with ROM Manager
Enviado desde mi C5503 mediante Tapatalk

[Q] Newly Rooted Note 4 T Mobile help

Hello fellas...just rooted my note 4 using odin. After rooting I tried to install the TWPR flash recovery to no evail. For some reason after downloading the recovery file, when I open it up in odin it get's stuck on the screen ( using my computer). So I cannot install it to my phone....yet. I did download ROM toolbox pro...i do notice there is a recovery option here. Is this the same thing as the TWPR recovery? Do I absolutely need TWPR recovery? really new to this so all and any info will help thanks!
Use an older version of Odin. I'm using 3.04 everyday. Yes you need a custom recovery.
http://forum.xda-developers.com/showthread.php?t=1703998
freshverse said:
Hello fellas...just rooted my note 4 using odin. After rooting I tried to install the TWPR flash recovery to no evail. For some reason after downloading the recovery file, when I open it up in odin it get's stuck on the screen ( using my computer). So I cannot install it to my phone....yet. I did download ROM toolbox pro...i do notice there is a recovery option here. Is this the same thing as the TWPR recovery? Do I absolutely need TWPR recovery? really new to this so all and any info will help thanks!
Click to expand...
Click to collapse
Did you install Chainfire Root before trying to install TWRP. I have a short Odin video on YouTube I made for another member that you can check out. See if it helps you
http://youtu.be/hMOsw0RDeSQ
Remember that this was for a specific member and rom he was installing as far as the Firekat files. The Odin, chain root, and twrp will work for your needs. You might want to update the twrp to 2.8.4.
2.8.1 works fine for me so that what I have installed
lances1027 said:
Did you install Chainfire Root before trying to install TWRP. I have a short Odin video on YouTube I made for another member that you
Remember that this was for a specific member and rom he was installing as far as the Firekat files. The Odin, chain root, and twrp will work for your needs. You might want to update the twrp to 2.8.4.
2.8.1 works fine for me so that what I have installed
Click to expand...
Click to collapse
Yes used odin for chainfire root...i downloaded the recovery file but when i load in odin via pda it says program not responding and I end up having to shut down Odin.
freshverse said:
Yes used odin for chainfire root...i downloaded the recovery file but when i load in odin via pda it says program not responding and I end up having to shut down Odin.
Click to expand...
Click to collapse
make sure your file is a tar file and not an image, if it is good then I would try a different version of Odin as mentioned before. If still no luck I would definitely try a different file location to get the Download or a different version of TWRP. I have files that I know work if you need.
Hope we helped
Also when your loading in the pda slot it takes a minute to populate in the slot sometimes 60 seconds....
That is normal. Sometimes when loading firmware it takes up to 3 minutes or so for the md5 check to be done. Usually root and recovery aren't quite as long but still can take a min.
freshverse said:
Do I absolutely need TWPR recovery?
Click to expand...
Click to collapse
To answer this question, are you planning on flashing ROMs? If not, I wouldn't worry about TWRP. Some people just like to ROOT and be on their way.
lances1027 said:
That is normal. Sometimes when loading firmware it takes up to 3 minutes or so for the md5 check to be done. Usually root and recovery aren't quite as long but still can take a min.
Click to expand...
Click to collapse
Yeah I realized that when I loaded the chainfire file in odin. But after waiting 10 minutes for the recovery file , I figured something was wrong. If you can provide me with the recovery link that would be great. Its for the note 4 t mobile.
What version where you using?
---------- Post added at 07:06 AM ---------- Previous post was at 06:57 AM ----------
Here is 2.8.4
http://www.techerrata.com/file/twrp2/trltetmo/openrecovery-twrp-2.8.4.0-trltetmo.img.tar
And 2.8.1
http://www.techerrata.com/file/twrp2/trltetmo/openrecovery-twrp-2.8.1.1-trltetmo.img.tar
lances1027 said:
What version where you using?
---------- Post added at 07:06 AM ---------- Previous post was at 06:57 AM ----------
Here is 2.8.4
http://www.techerrata.com/file/twrp2/trltetmo/openrecovery-twrp-2.8.4.0-trltetmo.img.tar
And 2.8.1
http://www.techerrata.com/file/twrp2/trltetmo/openrecovery-twrp-2.8.1.1-trltetmo.img.tar
Click to expand...
Click to collapse
okay here is the thing when I try to save this file to my computer it saves it as openrecovery-twrp-2.8.4.0-trltetmo.img ...not openrecovery-twrp-2.8.4.0-trltetmo.img.tar what gives?
That is the problem. Try adding the .tar to the end
lances1027 said:
That is the problem. Try adding the .tar to the end
Click to expand...
Click to collapse
Ok now do I open up this file using winrar before i select it in odin pda ...or select it in odin pda as is?
As is
---------- Post added at 09:27 AM ---------- Previous post was at 08:59 AM ----------
Make sure that after it reboots you turn off your device. Hold volume up, power and the home button at the same time and go into recovery mode and back your device up. Leave what is x'ed off as is but I also back up the modem. Change the location of the back up to be saved to your SD card. Factory wipe, the advanced, checking off dalvik, system, data and cache. DO NOT WIPE INTERNAL or SD card. Reboot your phone. Let it sit for 5 min on the welcome screen then enjoy
---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------
If you need some good apks and a great couple roms go check out Megas Fire Kat V8. Awesome rom.
If I've helped don't forget to hit the thanks button
lances1027 said:
As is
---------- Post added at 09:27 AM ---------- Previous post was at 08:59 AM ----------
Make sure that after it reboots you turn off your device. Hold volume up, power and the home button at the same time and go into recovery mode and back your device up. Leave what is x'ed off as is but I also back up the modem. Change the location of the back up to be saved to your SD card. Factory wipe, the advanced, checking off dalvik, system, data and cache. DO NOT WIPE INTERNAL or SD card. Reboot your phone. Let it sit for 5 min on the welcome screen then enjoy
---------- Post added at 09:28 AM ---------- Previous post was at 09:27 AM ----------
If you need some good apks and a great couple roms go check out Megas Fire Kat V8. Awesome rom.
If I've helped don't forget to hit the thanks button
Click to expand...
Click to collapse
Okay so I figured out what was wrong..for some reason my winrar program was messing up the .tar file, so I deleted winrar and was able to do the recovery without a problem! Thank you for your help fellas I hit that thanks button as much as I could..lol. Okay so now I think I want to try out a rom but....I don't see any youtube videos of people showing off firekat rom for the note 4...is firekat compatible with the note 4?
Firekat is definitely compatible with the note 4. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2916463
Screen shot 2
Android_Monsters said:
Screen shot 2
Click to expand...
Click to collapse
okay im about to install firekat....so im in recovery mode now I need to do factory reset correct before I install firekat? Which do I check in advanced ...dalvik cache...system..date...cache..??
I don't always clean install firekat, but mega does recommend it. Cache, Dalvik cache, and data.

[ROM][ROOT][i9506] How to FLASH N' ROOT Lollipop Samsung TW

This guide help you to
install the Samsung Lollipop TouchWiz and get the root permissions
on Galaxy S4 GT-I9506​
Do it on your own responsibility! and keep in mind that you will lose your warranty!​
Before you proceed, make sure:
1) You have installed your Samsung Galaxy S4 GT-I9506 USB drivers on your PC (the easiest way is to install Kies)
2) Your S4 should have 70-80% charge remaining.
3) Backup all your important data like Call logs, SMS and other data stored in phone memory in case if anything goes wrong, your data is not hurt
4) Make sure that Kies software is not running and disable your antivirus
Download the requirements:
Click on each one for download
-Odin software
-Recovery TWRP "flashable"
-SuperSu "flashable"
-Samsung Lollipop Firmware from SAMMOBILE (only if you have KitKat installed)
WARNING! I FOUND PROBLEMS WITH SOME SAMMOBILE FIRMWARE'S READ BELOW
The Czech Republic - ETL firmware (I9506XXUDOA6_I9506OXXDOA1), has WiFi broken
The Czech Republic (Vodafone) - VDC firmware (I9506XXUDOA6_I9506VFGDOA4), has wrong "Hidden" partition size
If you meet this problems you can download this official firmware from samsung updates site:
Greece - EUR firmware (I9506XXUDOAA_I9506EURDOB1)
BUILD DATE: 30.01.2015
How to install the firmware and root
If you already have the Lollipop firmware installed: Skip to the Step 8
NOTE: I racommend you to do the wipe of cache, dalvik cache, system, data partitions before proceeding,
this to prevent any problems with the apps (through recovery)
Step 1
Unzip the downloaded firmware, you will get a tar.md5 file.
Step 2
Turn OFF you mobile and go to Download Mode by pressing and holding the Power + Volume Down + Home Buttons.
together for few seconds followed by Power button then proceed with volume up.
Step 3
Now open ODIN on your PC and connect your Galaxy S4 to your computer.
Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn blue (or yellow) and will show the COM port number.
Step 4
Click on PDA (or AP) in Odin and choose the file ".tar.md5"
Step 5
Check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
Step 6
Click on Start button in ODIN window to start the flashing process. The process will take few minutes to complete.
Step 7
When the installation is completed, you read a "Reset " then a "Pass". your phone will restart (first boot will take a longer time so don't panic)
> Step 8
now you have to do again all steps from Step 2, for flash the TWRP recovery needed for apply the ROOT,
the only difference is when you arrive on Step 4 you must have to choose the TWRP Recovery ".tar.md5" downloaded file
Step 9
Turn OFF you mobile and go to Recovery Mode by pressing and holding the Power + Volume Up + Home Buttons.
Step 10
Connect the mobile with USB and copy the "UPDATE-SuperSU-v2.45.zip" in the SD
Step 11
Click on the "INSTALL" button, select "UPDATE-SuperSU-v2.45.zip", and swipe to flash. After this reboot
Finish! Enjoy!
----------------------------------------------------------------------------------------------------------------------------​
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat the procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Make sure the antivirus is disabled
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install the USB driver.
- Try another computer.
Titanium Backup does not recognize the root:
- Install Titanium Backup version 7.0+
Titanium Backup does not recognize external SD:
- Install SDFix app for applying the missing external SD card permissions
Thanks to samersh72 for the inspiration to create the guide​
Thx for this guide! What about Knox value after manual flash?
Envoyé de mon LG-V500 en utilisant Tapatalk
byanou69 said:
Thx for this guide! What about Knox value after manual flash?
Envoyé de mon LG-V500 en utilisant Tapatalk
Click to expand...
Click to collapse
After flash the warranty Knox is rightly marked,
that's becouse i wrote that you lose the warranty,
but this happens anyway if you perform unauthorized flash...
General Information:
CastagnaIT and my GT-I9506 devices are originally from ETL CSC... so Czech Republic firmware.
We found that the original ETL firmware has broken WiFi, and we discover that flashing the cache partition of Vodafone firmware has solved the issue... this is the reason we provide here an already fixed firmware.
Probably with newer updates it will be automatically solved, but for now this fix is working perfectly.
I dirty flashed the modified firmware file directly over my TW 4.4.2 installation, and I saw the phone has correctly get the update without any loosing of apps or datas... so my installation is exactly equivalent to a normal Sammy update.
Thanks for the attention.
German Vodafone have also broken WiFi...
The German rom seemed to work for me, no issues.
The German rom seemed to work for me, no issues.
Flash procedure check...
Developer.WL said:
German Vodafone have also broken WiFi...
Click to expand...
Click to collapse
Drady said:
The German rom seemed to work for me, no issues.
Click to expand...
Click to collapse
Hi,
I have a doubt... let me explain.
When you flashed with Odin, the correct procedure I think is this one.
1) After flash complete the phone must restart automatically
2) at the first boot, the recovery must be automatically activated and a flash of a cached element must appear
3) after this recovery flash, the phone reboot automatically and finally start with rom initialization
I think that for @Drady this has happened, and I think also that for @Developer.WL this has not happened.
This recovery flash is the culprit (probably) that give as result the wifi working.
I saw this, because I prepared a modded firmware with removed the recovery.img, so my Odin flash has not installed the stock recovery, leaving twrp as recovery.
After my flash, the phone was just shutdown (no reboot). Remembering that recovery flash was also done for previous KK firmware, I switched on the phone by pressing the buttons Vol-up + Power + Home, and my phone has booted into twrp and has flashed the missing cache part, than the phone auto-rebooted correctly and the system is working as it must.
My suggestion to @Developer.WL, is to reflash the firmware, taking care that at the first boot the phone must go to recovery (flash is about a couple of seconds) and after this must reboot into the rom...
Please let us know if this solve the wifi issue.
Thanks for cooperation.
AFAIK you should turn off device before enter download mode and then flash Czech version, this will let you to replace old modem with new one.
kornelius1982 said:
AFAIK you should turn off device before enter download mode and then flash Czech version, this will let you to replace old modem with new one.
Click to expand...
Click to collapse
Yes, the download mode must be enabled from phone off status with buttons procedure (Vol-Down + Power + Home).
The fixed firmware is finally ready for download!
5.0
I am curious to try the official 5.0 even though i am waiting for the Nordic Countries(NEE) Release , ill just see if the WI-FI on German version works till than ..
Arter97 aosp kernel
Is it possible to flash this kernel (link below) on this latest Official lollipop samsung release for i9506 ?
http://forum.xda-developers.com/showthread.php?t=2691648
---------- Post added at 05:41 PM ---------- Previous post was at 05:00 PM ----------
I have the answer : i9506 not supported for the moment by these kernels
Your fixed ROM's link is dead. MediaFire says "Dangerous File Blocked". Please upload it to another cloud.
boggy27 said:
I am curious to try the official 5.0 even though i am waiting for the Nordic Countries(NEE) Release , ill just see if the WI-FI on German version works till than ..
Click to expand...
Click to collapse
For your information, official 5.0.1 NEE has been released...
---------- Post added at 09:24 PM ---------- Previous post was at 09:10 PM ----------
yazsers said:
Is it possible to flash this kernel (link below) on this latest Official lollipop samsung release for i9506 ?
http://forum.xda-developers.com/showthread.php?t=2691648
---------- Post added at 05:41 PM ---------- Previous post was at 05:00 PM ----------
I have the answer : i9506 not supported for the moment by these kernels
Click to expand...
Click to collapse
Absolutely NOT!!! Arter kernel is AOSP based, Official Lollipop is TW...
---------- Post added at 09:32 PM ---------- Previous post was at 09:24 PM ----------
ShaneDiNozzo said:
Your fixed ROM's link is dead. MediaFire says "Dangerous File Blocked". Please upload it to another cloud.
Click to expand...
Click to collapse
Thanks for the head-up... already requested to Mediafire to remove the block on download... file is safe, not dangerous...
how to debloat after root? using root explorer how can i do?
smeroni68 said:
For your information, official 5.0.1 NEE has been released...
---------- Post added at 09:24 PM ---------- Previous post was at 09:10 PM ----------
Thank you! It has been released just today , that is great ! And thx for this helpfull post!
Click to expand...
Click to collapse
sibellius said:
how to debloat after root? using root explorer how can i do?
Click to expand...
Click to collapse
At this moment there is no way I tried root uninstall, TB and uninstall without any result.
I think we have to wait for updates
i don't fix glonass on this NEE version....
I have LineageOS 13, TWRP and I want to ROOT my i9506. As I understand, I can't ROOT it on LineageOS 13 - I have to install official ROM, ROOT it, and then install LineageOS again, yes?

Categories

Resources