[FIX][JB 4.1.1] Placeholder for Jelly Bean OTA Leak Fix - Galaxy Tab 2 7" Android Development

UPDATE 24/09/2012:
As a complement to http://forum.xda-developers.com/showthread.php?t=1898377, GTAB2_JB_REBRANDING-signed.zip will install Google Nexus 7 boot animation, remove power on and power off sound, and also remove power off animation.
The code inside:
Code:
#!/tmp/busybox sh
if /tmp/busybox [ -f /system/bin/samsungani ] && /tmp/busybox [ "$(/tmp/busybox strings /system/bin/samsungani | /tmp/busybox grep "samsung" -c)" != "0" ]; then
/tmp/busybox mv /system/bin/samsungani /system/bin/samsungani.backup
fi
if /tmp/busybox [ -f /system/media/audio/ui/PowerOff.ogg ]; then
/tmp/busybox mv /system/media/audio/ui/PowerOff.ogg /system/media/audio/ui/PowerOff.ogg.backup
fi
if /tmp/busybox [ -f /system/media/audio/ui/PowerOn.ogg ]; then
/tmp/busybox mv /system/media/audio/ui/PowerOn.ogg /system/media/audio/ui/PowerOn.ogg.backup
fi
if /tmp/busybox [ -f /system/media/video/shutdown/shutdown.qmg ]; then
/tmp/busybox mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/shutdown.qmg.backup
fi
UPDATE 20/09/2012:
FOR SOUTH EAST ASIAN USER ONLY!
South East Asian CSC for Germany JB XXCLI5. Enabling all South East Asian languages for UI and Samsung keyboard, DioPenChineseIME.apk included. Flash this using modified Samsung recovery for automatic CSC update support from http://forum.xda-developers.com/showthread.php?t=1880010
UPDATE 18/09/2012:
P3100 XXCLI5 OTA missing a lot of PowerVR SGX proprietary binary, so the graphic subsystem fail to start. An update.zip attached here to resolve this problem by reuse binaries from XXCLI4, thanks to bspatch tools.
After GT-P3100_P3100XXCLI5-OTA-P3100XXBLH2_DBT_364229274.zip applied:
Boot to download mode and then flash P3100_CWM_RECOVERY-6.0.1.3_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5 or P3100_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5 from http://forum.xda-developers.com/showthread.php?t=1880010 using odin or heimdall
Boot to recovery mode and then apply GT-P3100_P3100XXCLI5_FIX-signed.zip
Reboot
I confirm both camera and hardware accellerated video works!
TIP:
To force your device powered off, connect your device to PC or charger and then long press POWER button. When charging animation shown, unplug your device from PC or charger and then boot to recovery or download mode.
UPDATE (XXCLI4 fix)
Hardware accelleration video issue fixed. Install both jb-screen_fix-p3100 and jb-screen_fix-p3100-fix .
Has anyone experienced screen corruption on boot (after the boot logo/before the boot animation) on the latest Germany OTA XXCLI4?
Click to expand...
Click to collapse
Confirmed by RGDNI this happens on P3113 too. But my solution here only tested on P3100.
Kernel and modules taken from Germany OTA JB P3100 XXCLI3, the rest from Germany OTA JB P3100 XXCLI4 using bspatch, unpackbootimg, and my own script repackbootimg. Flash this using CWM or a modified Samsung recovery at your own risk.

ketut.kumajaya said:
Confirmed by RGDNI this happens on P3113 too. But my solution here only tested on P3100.
Kernel and modules taken from Germany OTA JB P3100 XXCLI3, the rest from Germany OTA JB P3100 XXCLI4 using bspatch, unpackbootimg, and my own script repackbootimg. Flash this using CWM or a modified Samsung recovery at your own risk.
Click to expand...
Click to collapse
FIX Working Awesome on P3113! You Rock Dude (Im Out of Thanks for Today, But You'll Get it!) :good:
UPDATE: IT DID FIX THE BOOT SCREEN, BUT "BROKE" YOUTUBE AND SOME WIFI FUNCTIONALITY I REVERTED BACK AND ALL IS GOOD buthave the boot corruption again
---------- Post added at 08:09 PM ---------- Previous post was at 07:41 PM ----------
EDIT^

RGNDI said:
FIX Working Awesome on P3113! You Rock Dude (Im Out of Thanks for Today, But You'll Get it!) :good:
UPDATE: IT DID FIX THE BOOT SCREEN, BUT "BROKE" YOUTUBE AND SOME WIFI FUNCTIONALITY I REVERTED BACK AND ALL IS GOOD buthave the boot corruption again
---------- Post added at 08:09 PM ---------- Previous post was at 07:41 PM ----------
EDIT^
Click to expand...
Click to collapse
Thanks for your feedback! My solution broke hardware accelleration video on P3100 too but don't worry, I found away to fix it. Newer ducati firmware incompatible to the older kernel. Before I update this fix, please report back the output of:
Code:
# lsmod
# ls /lib/modules
# ls /system/lib/modules
on your P3113 for possibilty to fix P3113 WIFI issue using P3100 kernel.

#1 post updated.

Fixed on my P3100. No more corrupt startup animation.

#1 post updated. JB XXCLI5 fix.

Any fixes for the P3113UECLI4 ?

Bibicp said:
Any fixes for the P3113UECLI4 ?
Click to expand...
Click to collapse
What the problem? If no boot animation after the boot logo, you can try XXCLI5 fix.

ketut.kumajaya said:
What the problem? If no boot animation after the boot logo, you can try XXCLI5 fix.
Click to expand...
Click to collapse
Yeah, which fix? There's 3 zips here, and are those flashable in stock recovery?

Bibicp said:
Yeah, which fix? There's 3 zips here, and are those flashable in stock recovery?
Click to expand...
Click to collapse
A modified stock recovery or CWM recovery for P3113 from http://forum.xda-developers.com/showthread.php?t=1880010 and then apply GT-P3100_P3100XXCLI5_FIX-signed.zip from recovery flash update.

ketut.kumajaya said:
A modified stock recovery or CWM recovery for P3113 from http://forum.xda-developers.com/showthread.php?t=1880010 and then apply GT-P3100_P3100XXCLI5_FIX-signed.zip from recovery flash update.
Click to expand...
Click to collapse
Thanks, but I'm not rooted and don't want CWM recovery, so I'll probably wait for another OTA leak.

Bibicp said:
Thanks, but I'm not rooted and don't want CWM recovery, so I'll probably wait for another OTA leak.
Click to expand...
Click to collapse
Ha..ha..ha.. and another fix. Thinking about removing my fix

#1 post updated. FOR SOUTH EAST ASIAN USER ONLY!

I'm currently using P3100XXCLI4.
How can i update to CLI5 ?
I tried to flash it from CWM or modified Samsung recovery, but always error failed. some kind of assert failed espresso bla bla bla..
PS: currently mine already rooted. should i un-root first to update OTA CLI5 file ? i tried to un-root, but still getting error while flashing that OTA zip file..

I updated with the P3113UECLI4, and with odin flash P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip. Now it doesnt boot at all. Black screen, tried power button y volume up and nothing happens or power botton down nothing. I plug it a my pc, the logo of charging almost appear for 2 seconds and the goes off, appear the screen of charging once again for 2 seconds. Nothing its working for me. Any help??!!!

#1 post updated!
UPDATE 24/09/2012:
As a complement to http://forum.xda-developers.com/showthread.php?t=1898377, GTAB2_JB_REBRANDING-signed.zip will install Google Nexus 7 boot animation, remove power on and power off sound, and also remove power off animation.

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]【T210R & T210】 CWM Recovery v6.0.4.9.KK [Unofficial]

[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.

[ROM] Stock rom kitkat 4.4.2 for T210R

Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes

[SM-T11x] TWRP 2.6.3.0 for Tab3 lite

No more bootloops on custom recoveries!!! Tested onT110, but should work in T111 too. feedback would be great
Kernel sources: http://github.com/pazos/android_kernel_samsung_goyawifi
Device tree: http://github.com/pazos/android_device_samsung_goyawifi (not uploaded yet )
Credits:
@ketut.kumajaya for the initial kernel base for lt02
@gr8nole for inital goyawifi device tree to build TWRP
all people sharing code here, in xda
Thank you so much for your work!
:cyclops: !!! Of course If something crashes I won't pay you for any damage :cyclops:
Hi paziusss,
I am on the case of recovery bootloop after flashing CWM.
Thanks for this work but how does it work ? How to use the files on the link ?
Many thanks for your answer.
EDIT : Well, I will answer myself telling my solution
1. flash cmw with odin
2. reboot into recovery and flash twrp.zip
3. reboot recovery
4. Flash root zip
5. reboot system ..... no more bootloop
Flashed this with Flashify and it has fixed my bootloop issue.
Sent from my SM-T110 using Tapatalk
Working well, tested on 2 tablets, thanks.
I'm glad it worked for you
I just noticed some non-critical errors:
- it doesn't backup boot.img
- wipe preload partition does not work because of Selinux
- screen timeout (sometimes) puts the system in unresponsive state -> Disable it!
- Missconfigured "screen_brightness"
Everything else should work as expected.
In the next days I'll upload a new version to fix above errors and make an odin installable tar.md5
Next version will be shipped without SELinux, because we don't need that until samsung releases 4.4 for the Tab3 lite (or someone ported CM11 with Selinux support)
Feedback, as always, is _VERY_ welcome !!!
will it work on sm t 111 tab india ?
sushil888 said:
will it work on sm t 111 tab india ?
Click to expand...
Click to collapse
Yes, it should work, but I didn't test
ok
paziusss said:
Yes, it should work, but I didn't test
Click to expand...
Click to collapse
ok
boot loop gone on T110 ?
paziusss said:
In the next days I'll upload a new version to fix above errors and make an odin installable tar.md5
Next version will be shipped without SE Linux, because we don't need that
Click to expand...
Click to collapse
Wow! Does your kernel mean T110 users have a custom recov which does not bootloop anymore?
That would be awesome! Fantastic break thru on T110 ! :good:
no stock ASR install
this recov does not simply install via stock ASR on my T110 (reboot, "missing signature").
I guess one has to flash PhilZ first using ODIN, and only then install this recov from within PhilZ
Uploaded a new version! for both Odin and recovery!
Tested last two weeks and everything works well!!
Have fun
brief install how-to much appreciated
paziusss said:
new version! for both Odin and recovery!
Have fun
Click to expand...
Click to collapse
people would have more fun if you dropped 1 or 2 lines about how to install the NON-ODIN version.
does one have to flash CWM with ODIN prior to using that ?
So that stock users should go for the ODIN version straight away cuz it saves install time?
---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------
Also:
is this TWRP permanent and does not exhibit the dreaded bootloop? re-edit : YES this TWRP exhibits NO bootl loop acc. to DEV.
i.e. T110-users finally do indeed have a WORKING CUSTOM RECOV ? re-edit: YES ! FINALLY THE BREAK THROUGH IS THERE !!
that would make you the KING DEV of planet-T110 ! :good:
excellent !
:laugh::laugh::laugh:
smashing ! for us T-110 users the day has finally come !
KING of "planet T-110", the dev Sir paziusss
gave us a non-bootlooping custom recovery !
we now can handily
root (straight from within TWRP, works like a charm)
flash customs roms (well there are only 2 for T110: Criskelo and stock debloated)
above all: make nandroid backups & restore them
just flash the recov with ODIN 3.09, see pic attached :
http://forum.xda-developers.com/showpost.php?p=60707541&postcount=2
in TWRP, if u do a "advanced wipe" and wipe "internal storage" too (all is tagged except "MicroSD"), then that will kill the bloody bloatware installer that will otherwise spam ure storage with sh!tty apk's after fresh stock ROM or Criskelo ROM install (as part of most branded versions) .
I guess u get the bloated stuff back when flashing full OS with ODIN.
I found however, that Criskelo deletes TWRP. You would have to reinstall TWRP. Instead I chose to kill Criskelo which was OK but slightly bloated, I felt.
I run this TWRP , no prob so far. excellent T110 feel.
recovery.fstab safestrap
Code:
[FONT=Courier New]/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
#/misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/efs emmc /dev/block/platform/msm_sdcc.1/by-name/efs flags=backup=1;display=EFS
/external_sd vfat
/dev/block/mmcblk1p1
/dev/block/mmcblk1
/usb-otg vfat
/dev/block/sda1
/dev/block/sda flags=removable;storage;display=USB-OTG[/FONT]
https://raw.githubusercontent.com/T...samsung_lt02ltetmo/android-4.4/recovery.fstab
fstab of the lt02ltetmo, the expensive NON-LITE Tab 3 7"
it may apply to our T110 as well.
what about safestrap ?
http://blog.hash-of-codes.com/how-to-safestrap
http://forum.xda-developers.com/tags.php?tag=safestrap
take abow
:angel: ur great
nodobt abt that ur something special dev...
feeling happy for 110 users
njoy
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
funny
Dudash said:
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
Click to expand...
Click to collapse
well did anyone report successful use of that recov earlier ?
clearly PhilZ recov is bootlooping and no one suggested a replacement. :crying:
Dudash said:
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
Click to expand...
Click to collapse
You're right here. Bootloop problem only happens if you tell your device to go to recovery (via adb reboot recovery, or with programs like quickboot). If you boot in recovery with buttons combo you'll never see a bootloop cause the tablet doesn't know it boots recovery. The only real scenario you'll find a bootloop is after a factory reset, because It will trigger a reboot-recovery like command and custom recoveries don't handle this. I didn't try to change this from userspace (I know some phones have a /misc partition with BCD data inside, but Tab3 don't). Instead I built a kernel from stock sources which triggers "recovery-done" at every reboot.

[Root] system mode root for SM-G900H 6.0.1

* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, if you followed my guide you dont face any problem
*i warned you:silly:
​After 6.0.1 update we got system-less system and supersu not granting some apps such es file explorer etc... but after greenapple kernel that somasdul maked for 900h device we have system mode root now
requirements
1-twrp any version i recommend twrp 3.0 by @Fevax in here http://forum.xda-developers.com/galaxy-s5/development/recovery-twrp-recovery-v3-0-0-0-t3336570
2-Greenapple Kernel For 6.0.1 By @somadsul in here http://forum.xda-developers.com/galaxy-s5/orig-development/support-dev-s-little-g900h-t3416061
3-supersu 2.76 system-mode by @aufarxda in here http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Installing
1-unroot If you are rooted
2-Flash the twrp if you dont have custom recovery
3-Flash the kernel
4-flash the supersu
5-wait about 15-20min until the phone booting :fingers-crossed::victory:
6-enjoy
WIFI password fix go to system and open build.prob search for securestorage.support=true and change it to securestorage.support=false and reboot thats all :victory:​
Greeting thread
somadsul said:
Greeting thread
Click to expand...
Click to collapse
dude i love ur kernel battery life is so good and i dont have heating like stock
Works like a charm, but there isn't a app for controlling the governors??
pranaytandan said:
Works like a charm, but there isn't a app for controlling the governors??
Click to expand...
Click to collapse
yes this app https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
but please press thanks button for the kernel thread
shahram Ali said:
yes this app https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
but please press thanks button for the kernel thread
Click to expand...
Click to collapse
Will try and let know for bugs
Thanks btw :good:
pranaytandan said:
Will try and let know for bugs
Thanks btw :good:
Click to expand...
Click to collapse
Thanks bro that will be help for kernel devloper
@shahram Ali
Good job
all works good
yash92duster said:
@shahram Ali
Good job
all works good
Click to expand...
Click to collapse
you are welcome bro
error message while opening kernel and recovery
while opening recovery : recovery is not seandroid enforcing
while powering ON device: kernel is not seandroid enforcing
what does this mean ?
now rooted on Marshmallow G900H Exynos
Thank you! Works well on SM-G900H 6.0.1 Oct.1st 2016 security update on Android 6.0.1 with build G900HXXS1CPJ6
Can anyone help me please? I am unable to root my S5 900H which is on latest update 1 day ago 6.0.1 . I tried 4-5 times using ODIN but even after ODIN showing I was successful, the phone doesnt go into TWRP. i know i am doing something wrong but not sure where. Here is what i am doing.
1) Downloaded TWRP recovery (3.0.2 and even tried previous version 3.0)
2) Started ODIN 3.09 (also did on 3.12 latest)
3) Put Recovery.tar.md5 file in AP and clicked Start
4) Successful message confirmation and phone reboots itself
5) Vol Up + Home + Power button and it goes into Default Android recovery.
6) Knox meter shows 1 instead of 0
So what am i doing wrong? Could it be my USB cable? its not original, but ODIN recognizes the phone and says successful at the end.
baz00ka said:
Can anyone help me please? I am unable to root my S5 900H which is on latest update 1 day ago 6.0.1 . I tried 4-5 times using ODIN but even after ODIN showing I was successful, the phone doesnt go into TWRP. i know i am doing something wrong but not sure where. Here is what i am doing.
1) Downloaded TWRP recovery (3.0.2 and even tried previous version 3.0)
2) Started ODIN 3.09 (also did on 3.12 latest)
3) Put Recovery.tar.md5 file in AP and clicked Start
4) Successful message confirmation and phone reboots itself
5) Vol Up + Home + Power button and it goes into Default Android recovery.
6) Knox meter shows 1 instead of 0
So what am i doing wrong? Could it be my USB cable? its not original, but ODIN recognizes the phone and says successful at the end.
Click to expand...
Click to collapse
When you in Odin, go to Option and uncheck the "Auto Reboot", then flash the recovery... after Odin say it is Successful e to then u have to pull off the battery and put it back again and turn on the phone and go to recovery mode... this way works on mine. Hope that help.
frenxl said:
When you in Odin, go to Option and uncheck the "Auto Reboot", then flash the recovery... after Odin say it is Successful e to then u have to pull off the battery and put it back again and turn on the phone and go to recovery mode... this way works on mine. Hope that help.
Click to expand...
Click to collapse
Excellent! This Worked! Thank you very much.
Do i have to unlock the bootloader ?
N if it's yes can any one give me the file needed ?
I dont have the line in my build.prop.should I add it? If yes,where exactly?
frenxl said:
When you in Odin, go to Option and uncheck the "Auto Reboot", then flash the recovery... after Odin say it is Successful e to then u have to pull off the battery and put it back again and turn on the phone and go to recovery mode... this way works on mine. Hope that help.
Click to expand...
Click to collapse
I also have tried this many times, It just wont boot into TWRP, any help? please.
Thank you
frenxl said:
When you in Odin, go to Option and uncheck the "Auto Reboot", then flash the recovery... after Odin say it is Successful e to then u have to pull off the battery and put it back again and turn on the phone and go to recovery mode... this way works on mine. Hope that help.
Click to expand...
Click to collapse
i have done with this way but i didn't flash the kernel just flash UPDATE-SuperSU-v2.76-SYSTEMMODE.zip
now my phone stuck on samsung logo with notification light blinking.
---------- Post added at 06:26 PM ---------- Previous post was at 05:44 PM ----------
kernel is mandatory ? i havn't install kernel just superuser and its stuck on booting i have tried data wipe per same result.
Good but....
You have to take battery out immediately after Odin pass flashing TWRP
Unless it doesn't work.
I have root . My phone is working but Im seeing Kernel is not seandroid enforcing on boot up .
And when playing online games sometimes it restart suddenly
---------- Post added at 11:20 PM ---------- Previous post was at 11:14 PM ----------
while opening recovery : recovery is not seandroid enforcing
while powering ON device: kernel is not seandroid enforcing
What should I do?

Categories

Resources