Related
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Revert back to recovery problem
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
Anyone can help me ? Thank's
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
Having same issue with SGH-T889. Any help? Heard of similar issue with Nexus 4. They have revert recovery disabler. Not tried on my Note 2. Is similar solution available for T889?
After flashing recovery in Odin are you booting up the phone (or is odin - i.e. auto reboot is checked)? There is a file (/system/etc/install-recovery.sh) that you need to disable to have recovery "stick". There are a few ways to do this, but my preference has been to do it within cwm/twrp recovery via adb after flashing in odin but prior to first bootup of phone.
Hope that helps!
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
^^ this
same prob
hazzel said:
Hi everyone
I've tried every thing : tool kit 3 => several version of recovery : CWM, TWRP, installed with Odin (Pass/ RESET : ok). But i'm still boot my recovery to "android system recovery 3e" (cf pic), I can't reach CWM or TWRP : //
I pull off bettery, but till the same way.
-----------------------------------
I'm using Galaxy Note 2 GT N7100
4.1.2
Click to expand...
Click to collapse
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Nintendoassasin64 said:
I have the same problem :/ i tried going back to odin and unchecking auto root as suggested, but whenever i clicked start it just stayed stuck at "Setup Connection" or whatever... i'm trying to install a custom rom and i just cant access CMW! I have the AT&T model by the way.
Click to expand...
Click to collapse
I know you can't access CWM Recovery..
Allot of us use TWRP Recovery and it works great. I think it is safe to say it is a Superior Recovery now. I suggest you use that Recovery.
You can get it installed easily by downloading GooManager from the play store, opening the app, hit your menu button and tap Install Open Recovery Script. That's it. Quick and easy!
For the people having a hard time, are you rooted? If you are just download goomanager and use it to install twrp
Sent from my SGH-T889 using xda app-developers app
Finally got fixed
I tried by un ticking the "Reboot" in Odni and manually pulled out battery and cable and tried Recovery mode... it went smoothly as expected... thanks dude
This works when everything else fails!
dj_spore said:
Ive had luck un-checking auto-reboot in odin, flashing recovery, wait for it to say pass, unplug USB, pull battery, and boot straight into recovery by holding home + vol up when powering on.
This can be dangerous so make sure odin is completely done before unplugging.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Been looking for a solution for hours and the android system recovery was feeling like a thorn in the foot that will never go away. But surprise, surprise, your simple suggestion did the trick!
Thanks a ton!! :good:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Have you tried twrp?
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see
+1 for twrp
athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.
aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help
xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.
athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks
xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM
Hello Everyone,
I'm hoping someone can help me out.
I installed ROM Manager on my phone, and (honestly not sure why!) but I did. When I launched the application, it told me that v. 6.0 was available if I wanted to update - Stupid me, updated ClockWorkMod to v6.0.
Well, everything was fine.. until I decided to use the ROM Manager Backup option - When I rebooted, it got stuck on
"Could not do normal boot"
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-OEM_CONFI_LSB: 0X30
WRITE PROTECTION: Enable
Downloading....
Do not turn off target!!
I'm not sure what to do at this point. I've tried VOL UP + HOME + POWER - but it goes right back to this spot. I've pulled the battery waited for 5 mins - then tried the same VOL UP + HOME + POWER - still nothing.
Any help would be greatly appreciated.
Thanks,
Jay
Don't press the home button is the first thing I can think of.
Power + Volume up = Custom Recovery
Power + Volume down = ODIN/Download mode
To get into Recovery mode:
Pull battery
Insert battery but Don't turn phone on.
Press Power + Volume up buttons and hold them until you see the custom recovery prompt in blue lettering in the upper left corner of the S4, and then immediately release the buttons. You should enter into Recovery.
I don't use CWM so I'm not that familiar with its installation, etc. But there are a few threads that go into CWM in detail.
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
Here's the TWRP 2.5.0.2 file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
Install with ODIN.
Steps to follow........
Method #1 -
Place file in PDA box*
Uncheck all other boxes.
Press start.
When installation is complete, unplug usb cord and pull the battery.
Insert the battery but Don't turn on the phone.
Place phone in Recovery mode via the Power + Volume up buttons.
Method #2 -
The other way I've read to install TWRP Recovery is:
Place the TWRP 2.5.0.2 tar in the PDA box*
Check the auto reboot box and f time reset box.
Start the installation and let the phone reboot.
I believe the above method is method of choice, but sometimes the Recovery doesn't take, so Method #1 is then recommended.
Here is an explanation why:
http://forum.xda-developers.com/showpost.php?p=41166759&postcount=28
TWRP been having some issues, even the one people claim to be stable. Be caution with that one as well. Let us know how it works out if not can direct you to other recoveries. There are several out there all working flawlessly. Just matter of what you want you know?
mgbotoe said:
TWRP been having some issues, even the one people claim to be stable. Be caution with that one as well. Let us know how it works out if not can direct you to other recoveries. There are several out there all working flawlessly. Just matter of what you want you know?
Click to expand...
Click to collapse
TWRP looks to have worked for me.
But I can see what you mean. I no longer get stuck in ODIN MODE - but I was having issues after dropping a ROM on my phone. Even after successful setup of the ROM, if I decided to reboot just for giggles. It would freeze on Samsung S4 Logo.
Well, I have since fixed this issue:
I believe the reason why I was getting stuck on Samsung S4 Logo on reboot was because in addition to wipe data/wipe cache/wipe dalvik - I also formatted the internal_sd - this is just a theory but my internal_sd regardless of me dumping a ROM on there, after reboot would do nothing - When I went in recovery - internal_sd showed 0MB. Thus, stuck boot screen. Nothing to boot too.
FIX: Installed STOCK ROM, and KERNEL - Confirmed, that reboot works after setting up phone. My understanding is that it installs all the necessary folder structure required. Got the STOCK ROM from: http://galaxys4root.com/galaxy-s4-stock-firmware/
Then followed this root process and recovery:
http://galaxys4root.com/galaxy-s4-ro...g-twrp-method/
Once I did that, booted to recovery did the normal (wipe data/wipe cache/wipe dalvik) then dropped ALPHA ROM on my phone, along with Infamous KERNEL, and everything is great. Reboots like a champ now. -- Still using TWRP, but v. 2.5.0 - (no issues as of yet! )
Glad to see all working out for you
JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
When you say "plugged it back up to ODIN" what exactly are you doing. Do I need to download an app to my PC? I am new to this... I'm stuck on the same screen.
Thanks in advance!
sincity said:
When you say "plugged it back up to ODIN" what exactly are you doing. Do I need to download an app to my PC? I am new to this... I'm stuck on the same screen.
Thanks in advance!
Click to expand...
Click to collapse
Install ODIN 3.07 to your pc
Install drivers for your device onto your pc
I'll post a link to the ODIN thread so you can see how it's done
Update:
Here ya go:
http://forum.xda-developers.com/showthread.php?t=2258628
Please read the above thread in the link carefully.
If your device is stuck on a screen, what were you doing prior to get to that state.
First, boot into custom recovery and Wipe cache and dalvik cache, reboot, and see if that helps.
Either way, you should have ODIN on your pc
Biker1 said:
Install ODIN 3.07 to your pc
Install drivers to your device.
I'll post a link to the ODIN thread so you can see how it's done
Update:
Here ya go:
http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
Thanks a million... I'll give it a try! Wish me luck!
sincity said:
Thanks a million... I'll give it a try! Wish me luck!
Click to expand...
Click to collapse
I edited my link above.
You'll be fine.
Any questions, ask in the thread after you read about ODIN and how it works.
Once you install it on to your pc, along with the drivers which enable youropc totrecognize your device you'll find it very helpful when needed.
I have, and so have almost everyone who have ever rooted their devices and/or flashed ROMs, etc
By the way, you are not rooted?
I ask because if you are, you would have used ODIN.
What is exactly wrong now with your device?
---------- Post added at 11:58 PM ---------- Previous post was at 11:43 PM ----------
JayCapo1-8125 said:
Plugged it back up to ODIN - pushed out the old ClockWorkMod and system booted back up!! Phew!!
I think I'm going with TWRP..
Click to expand...
Click to collapse
If you go with TWRP, don't use Goo Manager as that will install 2.6.0.0 which has some issues for some, as you probably know.
Install TWRP 2.5.0.2 with ODIN, which I did many months ago, and have had zero issues.
You can install with Mobile ODIN also I believe.
Biker1 said:
I edited my link above.
You'll be fine.
Any questions, ask in the thread after you read about ODIN and how it works.
Once you install it on to your pc, along with the drivers which enable youropc totrecognize your device you'll find it very helpful when needed.
I have, and so have almost everyone who have ever rooted their devices and/or flashed ROMs, etc
By the way, you are not rooted?
I ask because if you are, you would have used ODIN.
What is exactly wrong now with your device?
Click to expand...
Click to collapse
Ok I figured it out... I really appreciate your help! My blood pressure went down! LOL!
Yes my cell was rooted... I used GX4EX by:
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.
brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.
nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
-Deleted-
Recently tried to root my Samsung Galaxy Tab S (I am not allowed to post links yet so I'll just say the site is techbeasts)
I believe I went through these instructions and followed them all precisely.
This method also installs SuperSU on my device..
However, I tried checking the root status with Root Checker, and it says "verification failed"
I then checked SuperSU, and it said something along the lines of "binary needs updating". I tried the "normal" method for doing this twice, but it didn't seem to work. There is an option presented in SuperSU to do this through TWRM or CWM, so I tried that option. ( NOTE I do NOT have TWRM or CWM installed)
**Then when I started the tablet, a whole bunch of messages came up saying "unfortunately, ____ stopped" [/B]and a whole bunch of these are there. I'm sure this is a crash.... **
I managed to get the tablet back to semi-working state by using the factory reset from the recovery partition (it's the stock recovery partition). However, the crash-on-reboot problem still persists.
Any help on getting back to working state? I can use the tablet but I cannot restart it as it will crash again (have had to do the factory reset from recovery twice now...)
I should mention that i am trying to:
1) have a rooted tablet
2) Not have these crash-on-reboot issues...
Bharat
Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!
Wow, how to massively over complicate something.
Just install the stock firmware, then look for my build of cf_autoroot in the dev section, flash in ODIN. Done.
If you want to upgrade twrp to the latest version you will find it in the dev section too. This version fixes some of the issues with the official version and has more options.
Hi guys,
TThanks so much for your replies! Complicated or not, anything helps...
I had previously used Odin to flash the rooted firmware to the tablet, so I amn faniline with the software.
Alta1r: looked at the links and it looks like sprue stock firmware. A couple of questions about this procedure:
1) Is it normal that the stock firmware file (as downloaded) is larger than firmware images used to root the tablet?
2) Would using TWRP to flash Supersu onto the tablet root the tablet, even if the stock firmware is installed?
Thanks again guys!!
Not sure what you mean with firmware images to root the tablet. Do you mean a custom rom? Those should be smaller in size yes, as the are usually de bloated.
Maybe you flashed a wrong version if a custom rom for your tablet before, that would give you problems when flashed.
Both my or ashyx's method can be applied on a stock rom. I'm running just stock with root.
@Asynx: I flashed the latest firmware on my T800 this week and twrp didn't stick after the first boot. Tried many versions, also the one you mention in the dev section, but to no avail. Even replaced the recovery in the samsung's tar file and flashed it like that: twrp screen showed up right after the flash, but on next boit it was stock again. Only way to make it stick was to reboot into recovery right after flashing it.
Never had that problem before though on the Tab S (did have it already once on Galaxy S6).
Edit: forgot to mention I hadn't seen there was cf-auto root available for our current firmware. If I knew it would have saved me some time. Could have flashed the recovery with Flashify afterwards.
Apologies I am still getting used to the lingo with this stuff
Have done some stuff with Linux and some tweaking in Windows as well, so figured this shouldn't be too bad...
@Alta1r: so the process you describe is what you said, flashing the stock ROM and then root it afterwards...
Will try this process and report results here
(aside: I think the tablet was working fine after flashing with CF autoroot ROM -- is that the right word? -- what I think ruined it was when I told Supersu to try updating its binary through TWRP or CWM....which isn't yet on my tablet)
Alta1r said:
Only way to make it stick was to reboot into recovery right after flashing it.
Click to expand...
Click to collapse
It seems since lollipop this has to be done if flashing over stock recovery or it will be replaced at boot with stock.
Twrp will patch the recovery install script at first boot.
Sooooo...
First off, thanks for the "luck wishing"
I decided to try the method of @Alta1r.
@ashyx - I tried the CF-autoroot thing before (this was first attempt at getting a rooted tablet), and this didn't work for me. So I wanted something a bit more "hands on".
This is procedure I followed and worked for me (as of this post):
1) Before I began, I accidentally went into recovery mode instead of download mode. So I had to restart the tablet *gulp*
....yet I was able to restart just fine (no crashed as mentioned in my first post). I think this ~might~ have something to do with the fact that I downgraded the version of supersu that was "updated" through Google Play, but I'm not really sure...
2) Downloaded all relevant files.
3) Flashed firmware for tablet as instructed:
Alta1r said:
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Click to expand...
Click to collapse
Result was that tablet booted just fine!
Made sure that a few apps worked OK, and also rebooted the tablet a few times to make sure it was stable
(this is a linux based system, not Windows, but I still like reboot tests for stability checking...)
4) Next I did the TWRP flash through Odin:
Alta1r said:
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Click to expand...
Click to collapse
TWRP flashed fine. But then....
5) Tried to boot into TWRP recovery:
Alta1r said:
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Click to expand...
Click to collapse
As predicted, Alta1r, the TWRP didn't flash properly. I got an error on the stock recovery saying:
"Error message is "E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)"
So I tried your odin + reboot trick as above, and this booted into TWRP recovery.
6) Then I flashed supersu.zip (had kept on microSD card that is in tablet).
Andddddd.....
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!
bsquared938 said:
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!
Click to expand...
Click to collapse
Glad to hear all went well, and by the looks of it had fun doing it.
Although computer/device problems can get me agitated, I still have fun in the end
Not sure if I can ask this here, but two other slight issues after the rooting:
1) Upon rebooting the tablet, I always get the message "android is upgrading", even if I didn't touch any apps through Titanium Backup or other root-only apps that are meant to remove pre-installed applications.
Is this an issue? And if so, is there a way to get rid of this?
2) I am able to uninstall/remove apps with Titanium Backup (freezing them isn't possible without the paid version of the app), but I am not able to restore them. I made a full backup before I started to uninstall stuff. I put on USB debugging mode in developer options, but still I cannot put apps back. Any thoughts on this?
Thanks again!
Bharat
I wouldn't worry about the upgrading message, most get that.
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)
ashyx said:
I wouldn't worry about the upgrading message, most get that.
Click to expand...
Click to collapse
Okay thanks, I will not worry about that upgrading message for now...
ashyx said:
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)
Click to expand...
Click to collapse
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)
bsquared938 said:
Okay thanks, I will not worry about that upgrading message for now...
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)
Click to expand...
Click to collapse
Are you sure you have full root?
ashyx said:
Are you sure you have full root?
Click to expand...
Click to collapse
Yes I am sure I have full root.
I used root checker to check if I have full root access and it comes back green (to say root access is good).
(Just checked again now before posting this...)
Using either Titanium Backup and Root App Deleter, I am unable to restore deleted apps...
I have enabled USB debugging in the developer tools, as instructed to by Titanium Backup....
I read something about the "mount namespace separation" in supersu, I might try to toggle that option to see if it helps this situation.
Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?
ashyx said:
Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?
Click to expand...
Click to collapse
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...
bsquared938 said:
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...
Click to expand...
Click to collapse
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.
ashyx said:
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.
Click to expand...
Click to collapse
Okay I'm just going to say exact issue...
I deleted calendar storage, thinking that it's part of Samsung's calendar app (when in fact it is used by all calendar apps).
So now Google Calendar doesn't show me my calendar....and I'm trying to restore calendar storage, but it's not restoring
(had previously deleted through System App Remover, but now can't get it back)
Edit: I uninstalled and reinstalled Google Calendar, and that seemed to bring back my calendar.....
Sorry to cause you this trouble, I guess I panicked too early...
But will still be careful of what I remove...
Alta1r said:
Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!
Click to expand...
Click to collapse
worked for me thx :good: