Related
Hello all... Recently my girlfriend and I had purchased the Epic Touch 4g for her. She absolutely loves the phone but the signal strength isn't the best. I have had a Droid 1 for 2 years now and have flashed roms/kernels on a weekly basis for the past year and a half. Can anyone recommend a good starter Rom/Kernel? Is flashing a rom/kernel for the Epic Touch just as easy as flashing for the Droid? I've done some research and I am a bit overwelmed. It seems like clockworkmod recovery is being ran on the Epic Touch but the process for flashing is different? (maybe not, but like I said, I'm a tad overwelmed ).. Also, are there any tweaks after root that would improve signal strength? If anyone can help me out to get us started I would greatly appreciate it. Thanks in advance.
-Mike
I recommend starburst rom v1.6.. it comes with LostKernel which is a good kernel to use.. for root though, there are dif. methods, i originally rooted mine with Zedomax Kernel through Odin.. fairly easy .. so get it rooted, and i'd go with starburst v1.6 which when flashing it through CWM once you have root, also flashes the lostkernel
I recommend Starburst. Runs sooo smooth and its the only ROM that I see being actively updated. Viper just got into the game so if you don't like touchwiz, you can flash his ROM too which uses another launcher but i would say equally great. Comes down to preference and what works best.
And to get root and clockwork, I followed bubbys
http://forum.xda-developers.com/showthread.php?t=1287776
It seems to get root you have to use odin, but once thats done you can use clockwork to flash ROMs. If you get issues Odin is there for support.
Thanks! Too bad my girlfriend starts work in an hour
Take a look at this thread Id really recommend to check the links I have linked to save you some pain....
http://forum.xda-developers.com/showthread.php?t=1309078
So wait... after reading that thread it says that the bootloader keeps a record of everytime you flash with Odin? So if something happens to her phone and we need to take it in, they will know we rooted it?
A good reason to use starbursts rom is because its just way smoother some how and he stream lined the rom and did a bunch of tweaks that make noticably fast/smoother. That's the reason most are using it
mrkelly88 said:
So wait... after reading that thread it says that the bootloader keeps a record of everytime you flash with Odin? So if something happens to her phone and we need to take it in, they will know we rooted it?
Click to expand...
Click to collapse
Yes, but you can reset the counter some how. Just do a search for reset counter and you should find the thread
bluefire808 said:
Yes, but you can reset the counter some how. Just do a search for reset counter and you should find the thread
Click to expand...
Click to collapse
Cool, thanks, I got worried for a little bit there... I mean, we got it rooted and everything just fine, but I failed to mention to my girlfriend that there might be a slight problem if we tried to take the phone in ... I figured that problem would get solved eventually but it's good to know I'm in the clear
yeah I wouldn't worry about it, chances are if you flash everything stock theres still a counter chances are they wont notice or pay it much attention. its possible but, I've had friends take their evo in with security off and everything else flashed stock and it was ok.
Bring her to me I will root her. Don't bring your cable I will use mine to plug in her smoothly in order to root through odin.
mrkelly88 said:
So wait... after reading that thread it says that the bootloader keeps a record of everytime you flash with Odin? So if something happens to her phone and we need to take it in, they will know we rooted it?
Click to expand...
Click to collapse
You can use a jig, it will get rid of the yellow triangle on bootscreen and bring the counter down to zero.
The jig costs $7 MAX, all you do is plug it into microusb while phone is on, and the phone reboots automatically, and everything is back to normal. Process takes about 30 seconds max, and you can use the jig multiple times, with how many ever samsung phones, it is NOT a one time use deal.
Sent from my SPH-D710 using xda premium
So there are a few things that happen when I root so i had to unroot the phone cause of these issues.
Anyone else have trouble finding 3g connection?
After rooting, the phone cant find 3g / 1x after a little while. So no calls or data can be received
Ive tried two different tar files but both have the same issue
http://forum.xda-developers.com/showthread.php?t=1265399
http://forum.xda-developers.com/showthread.php?t=1268548
Any help would be nice.
I had the same issue when rooting. Check out this thread http://forum.xda-developers.com/showthread.php?t=1273730. It fixed it for me.
Good luck.
Kangster82 said:
So there are a few things that happen when I root so i had to unroot the phone cause of these issues.
Anyone else have trouble finding 3g connection?
After rooting, the phone cant find 3g / 1x after a little while. So no calls or data can be received
Ive tried two different tar files but both have the same issue
http://forum.xda-developers.com/showthread.php?t=1265399
http://forum.xda-developers.com/showthread.php?t=1268548
Any help would be nice.
Click to expand...
Click to collapse
You may be experiencing the LOS bug. There are many threads on this, but try resetting your data profile. I posted the instructions here:
http://forum.xda-developers.com/showpost.php?p=18790538&postcount=46
andygallo said:
You may be experiencing the LOS bug. There are many threads on this, but try resetting your data profile. I posted the instructions here:
http://forum.xda-developers.com/showpost.php?p=18790538&postcount=46
Click to expand...
Click to collapse
this is why im afraid to root this phone. i cant afford to be with out service.
cruton said:
I had the same issue when rooting. Check out this thread http://forum.xda-developers.com/showthread.php?t=1273730. It fixed it for me.
Good luck.
Click to expand...
Click to collapse
I'll give this a try
Sent from my SPH-D710 using XDA App
Use the epic touch Zedomax kernel v3 ,, it is the best out it is already rooted overclocked to 1.6 more battery life, flashes perfect with odin put into pda and flash youll be rooted with orange clockwork recovery!
if you need t go back to stock first use the eg30.tar put ino pda in odin!
This works perfect and is flawless
lojak29 said:
Use the epic touch Zedomax kernel v3 ,, it is the best out it is already rooted overclocked to 1.6 more battery life, flashes perfect with odin put into pda and flash youll be rooted with orange clockwork recovery!
if you need t go back to stock first use the eg30.tar put ino pda in odin!
This works perfect and is flawless
Click to expand...
Click to collapse
Do i have to restore to factory after i flash that kernel?
Not booting into recovery...
I also am wondering if I have to go back to stock. When I reboot into recovery, I get the exclamation point inside a triangle with little green android guy, and have to hold down power button long time and _then_ reboot into clockwork mod. That’s not right, is it? Here is the detail: Got my SGS2, Sprint, rooted, using ZedoMax's method (Odin, flash his ROM, voila: rooted). But then had trouble flashing Clockwork Mod. Recovery 3e requires signature verification for flashing external files, so it's barfing, throws error can't read file signature, hard stop. Replaced the ROM with his new one: SPH D710_Zedomax_EpicTouchKernel-v2.tar. So then flashed acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar to try to fix Clockwork mod...no. Then flashed latest build from Zedomax: SPH-D710_Zedomax_EpicTouchKernel-v3.tar. Still, recovery doesn't go straight to orange menu, which is not right, right? I know, I'm a noob, but I can't even begin to explain how much time this has taken. Thx to anyone who can help.
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Try flashing the stock tar in odin if nothing else works.
DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok
I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol
fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha
Hey guys the official rom is out
http://blogs.att.net/consumerblog/story/a7783602
you have to update your device over kies.
Cheers
Got the message just now
" AT&T Free Msg: Samsung Captivate Glide upgrade to Android 4.0 Ice Cream Sandwich is now available! The OS update supports enhanced performance, user interface and other device improvements. Open the link from your PC (not your phone), and follow the instructions: www.samsung.com/us/attcaptivateglide/update "
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
page was working about an hour and now page not found. Maybe they pulled the update? I haven't tried it yet because of the keyboard backlight issue from other posts...and I have no desire to do any rooting/CWM stuff.
Page worked for me just now. It basically just says download kies and let it upgrade.
Does the official rom have the same version number as the leaked one?
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
There are no bugs, samsung has fixed it all
Does the official version have CarrierIQ?
Nevermind.
R3D X said:
There are no bugs, samsung has fixed it all
Click to expand...
Click to collapse
Oh? That's not what others have reported - the keyboard backlight is supposedly still broken, unsure about tethering or the other problems.
gnahc79 said:
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
Click to expand...
Click to collapse
No backlight on my wife's Glide... She's pissed...
Then root and install the zip
I actually passed on this phone because I was worried it might not get ICS. I'm glad it did all the same. I miss having a hard keyboard.
Sengfeng said:
No backlight on my wife's Glide... She's pissed...
Click to expand...
Click to collapse
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
gnahc79 said:
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
Click to expand...
Click to collapse
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
gnahc79 said:
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
Click to expand...
Click to collapse
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
Anh56 said:
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
Click to expand...
Click to collapse
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
bakageta said:
To fix the keyboard backlight bug, you'll need the following:
Odin 1.85
Clockworkmod Recovery
The Keyboard Backlight fix The one labeled LH2 is for the official, the one labeled CWM is for the leak. If you're not sure what you're on, go to About Phone, and check the Baseband Version, if it ends in LH2 you're on the official, if it ends in LG9 it's the leak.
Optionally, SuperUser 3.2 RC3 if you'd like root.
First, make sure you have Kies installed, so that you have the correct USB drivers. Download the 4.0.4 .exe file from here. Power off your phone, hold Volume Up and Power to turn it back on. Keep holding them until you get a screen warning you about custom software, and release, then press volume up again to enter download mode. Hook the phone up to your pc and run Odin 1.85. Uncheck "F. Reset Time" and make sure that the only box checked is Auto Reboot, you shouldn't need to change anything else. Click on the PDA button, and load the clockworkmod .md5 file you downloaded, then press the start button and wait for the device to reboot.
This time you'll reboot into recovery. Power the phone off, hold the volume down and power button to turn the phone one. Keep holding them until you see text about entering recovery in the top left, and release. Use the volume keys to navigate and power to select, and go to Install zip from sdcard. Select the keyboard backlight fix zip. Once that's finished, if you'd like to be rooted, repeat the process to flash a zip, and this time select Choose zip from sdcard, selecting the superuser zip you downloaded earlier. Select Yes, and wait for superuser to flash. If you plan on keeping Clockwork Mod Recovery, you should make a backup now. To do so, select Backup and restore, and backup. This will take a bit, just be patient. When you're finished, select reboot system now, and you should be set.
From here, if you rooted you can install something like Titanium Backup, which will use root access to let you remove the various AT&T bloatware.
Click to expand...
Click to collapse
Yeah backlight isn't working sorry, someone on a blog had said so. Very unprofessional of samsung. A rom cooked with cm9 willl have to include the backlight fix
bakageta said:
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
Click to expand...
Click to collapse
:good:
Cool, thanks for the info. Good to know root is not required. I'll still hold off on the update but I'm sure others will apply ICS+backlight fix.
I updated last night, and I can report that after ending any call the phone app reports a hard stop rather than just going away, and that resets your cell connection. And I imagine the keyboard backlight will be fixed very soon. But did these issues exist on the leaked rom in its first release and then programmers modified to get them back?
-Ara
Sent from my SGH-I927 using xda app-developers app
Am I just being stupid or is there a way to root the new note 10.1 2014 edition on t-mobile's network? The model is SM-P607T & I don't see that listed anywhere on odin/s list or anything. Or is it just too soon from release?
Extra info: Baseband P607TUVUANE2, Android 4.4.2, Kernal 3.4.0-1433887
riffy504 said:
Am I just being stupid or is there a way to root the new note 10.1 2014 edition on t-mobile's network? The model is SM-P607T & I don't see that listed anywhere on odin/s list or anything. Or is it just too soon from release?
Extra info: Baseband P607TUVUANE2, Android 4.4.2, Kernal 3.4.0-1433887
Click to expand...
Click to collapse
I am looking for this as well since i got one today. It looks like it is the same thing as the P605 which is LTE. The non LTE ones do not use the Qualcomm chip. It also looks like 4.4.2 just came out for the P605 not to long ago and there really isn't anything out for it yet. Bigbuff is talking about updating TWRP to 4.4.2 for the P605. At that time I am sure we will get a recovery and be able to flash SuperSU. If it is out already I have not found it and would like to know as well.
OK so it's not just me then. Usually by the time I get a device all this stuff is out all ready.
I wonder if you can use the international version P605. That's got the qualcomm chip with LTE. I have the 605v and there's been no development for it. Verizon has locked the bootloader, as they tend to do, so we are stuck. If you understand Knox and how that works I would try the P605 method. I tried it on mine and it failed and it didn't cause any damage.
Sent from my SM-N900P using Tapatalk
Have you guys tried to put your tablets into download mode. My underdstanding you need to hold down volume down plus the power button for three seconds, but when I try this mine boots into regular mode and not the download mode. Can someone else try this and see if you get a different outcome?
Sent from my SM-P607T using XDA Premium 4 mobile app
Haven't tried it but you have to add home to that as well I thought. Yeah, Google search:
Boot your phone into Download Mode by Pressing and Holding the Volume Down + Home + Power buttons at the same time till you see a warning message on your screen. You’ll be asked to hit the Volume Up to continue into download mode.
draigons said:
Have you guys tried to put your tablets into download mode. My underdstanding you need to hold down volume down plus the power button for three seconds, but when I try this mine boots into regular mode and not the download mode. Can someone else try this and see if you get a different outcome?
Sent from my SM-P607T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
its Power + Vol-D + Home gets you to a screen that says vol up to get to download mode or vol down to reboot. I can get to Download mode by doing that. I am going to try doing the P605 root they have out and see how that goes in asec. Make sure you down the Full Odin Firmware.
http://www.sammobile.com/firmwares/3/?download=29807
So you can use this if you need to.
Good luck! I'm not adventurous enough to try it.
WARNING: By doing this your Spen will not work anymore
Ok here is how to root the P607T right now. It is the same way as Root for the P605 right now. After reading http://forum.xda-developers.com/showthread.php?t=2766394&page=9
on post 88. Someone with the P605 used the P905 CF-Auto root to root their 605.
here are the steps
1. Download to your PC http://download.chainfire.eu/385/CF-Root/CF-Auto-Root/CF-Auto-Root-viennalte-viennaltexx-smp905.zip
2. Reboot your P607T into Download Mode. You can do this by turning off the tablet. then hold Home + Vol-D + Power you will get a screen that says Press Vol D to get into Download mode.
3. Plug your P607T into your PC.
4. Open Odin 3.07 which is included with the down you already did. You should see a Blue tab that says something like Com1.
5. Make sure the only thing that is checked is Auto-reboot.
6. Click PDA and file the CF-Auto-Root-viennalte-viennaltexx-smp905.tar that was in the Zip file you just unziped.
7. Click start and wait.
Your tablet will now reboot into a P905 recovery and flash SuperSU. It can take awhile for the reboot into recovery to happen so just wait. After this is all done your tablet will boot back into Android. Go into the play store and update SuperSU. SuperSU will keep FCing until you update it in the Playstore.
Now here is the problem we run into if you do all this. After CF-Auto Root is done it is going to put a P905 recovery on your Tablet not a P607T recovery. If you want to get your P607T recovery back for future OTAs you need to Odin the full Firmware for the P607T which you can find here. http://www.sammobile.com/firmwares/3/?download=29807 Once they get a working TWRP for KitKat and the P605 we should be able to get everything else we need to get back our old recovery.
Now another problem That I have found as well is that the Spen does not work after doing this. I do not really care because I do not really use the Spen. I know there is a fix in this thread http://forum.xda-developers.com/showthread.php?t=2766394&page=9 but I have yet to get it to work because I do not know how to type the *#2663# in phone app and then update wacom firmware from kernel to get the Spen to work. We do not have a Phone app to do that. So you are warned that your Spen will not work after doing this.
Other Wise enjoy root until a better way is out.
LTE still work?
riffy504 said:
LTE still work?
Click to expand...
Click to collapse
No clue I don't use LTE I just opened a 200mb line to get the Tablet on EIP. I will pop in my sim when i get home from work and check it for u.
Edit: yes lte still works I am still trying to fix the spen however that still doesn't work.
Also looks like TWRP has a working recovery now for the P607T. here is a link to a odin file for it. http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776 I would use that and just flash SuperSU with it. should give you root and hopefully a working Spen.
May be possible to use mobile odin pro and inject root to the stock firmware, without tripping the knox flag?
This works on the note 3, upgrading to 4.3.
Edit: mobile odin requires to have already root, I used it when upgrading to 4.3
to not lose root.
Thanks.
To late... I already tripped stupid knox. hehe I love the samsung note lines but I really REALLY hate knox! Just a reason for them to deny warranty, or else it'd be optional.
That odin file worked great. Now to wait for some custom roms.....
Just jumping in on the got-this-yesterday train and glad to see some folks have jumped on ahead of me. Thanks for the information you've all provided thus far. I'm hopeful that development on this thing will be strong, I'm liking the device so far.
I'm interested in rooting ASAP but I've been out of the Android loop for a little while, so this KNOX thing freaks me out a bit (I'm just getting familiar with what it is). Seems like it is a simple warantee related thing. Is it irreversible? How common is flashing a custom ROM without triggering it? Does it affect usability at all to have it triggered?
I'm interested if flashing this this evening but not really sure what I'm in for as far as KNOX.
amirite said:
Just jumping in on the got-this-yesterday train and glad to see some folks have jumped on ahead of me. Thanks for the information you've all provided thus far. I'm hopeful that development on this thing will be strong, I'm liking the device so far.
I'm interested in rooting ASAP but I've been out of the Android loop for a little while, so this KNOX thing freaks me out a bit (I'm just getting familiar with what it is). Seems like it is a simple warantee related thing. Is it irreversible? How common is flashing a custom ROM without triggering it? Does it affect usability at all to have it triggered?
I'm interested if flashing this this evening but not really sure what I'm in for as far as KNOX.
Click to expand...
Click to collapse
Edit: Originally used root de la vega method for the note3. Mobile odin requires root.
The procedure to inject root with mobile odin pro is on the international note 3 forum.
Worked for my tmo note 3 upgrading to 4.3 and not lose root, but only flashing the original firmware.
Any custom rom, custom recovery or custom kernel will trip knox.
This is not tested yet on the note 10.1 2014.
Will check on the mobile odin thread or Chainfire's blog.
Tripping knox for now is irreversible and voids the warranty.
Normal device operation is not affected. What is lost is the security feature.
Only a concern if your company uses knox, and you use your device for work.
I am going to wait a few weeks, hoping for a no knox tripping root method,
to keep the warranty. But I know that eventually will not care on tripping knox.
Well fudge! I never thought to test the s pen before I rooted. Guess what, it doesn't work.
riffy504 said:
Well fudge! I never thought to test the s pen before I rooted. Guess what, it doesn't work.
Click to expand...
Click to collapse
I posted a big huge warning sign saying that the s pen would not work if you rooted
Sent from my HTC One_M8 using Tapatalk
No I mean it didn't work hardware wise. I thought the touch screen was off by 1/4th an inch but never thought to try the s pen before last night. I even flashed back to stock and it was the same way. Where ever you touched with the s pen it'd either do nothing or it'd randomly draw in a tiny little square up near a corner. The touch screen was really noticeable trying to click on links in chrome cuz I'd always missing, but I thought it was me till I realized the s pen didn't work either. Then I figured it was just the hardware was messed up. Messing around in the drawing app proved that the touch screen was off to a corner by 1/4th an inch. Even if I turned the device around it always was off to that same physical corner.
Oh! Also, I used the new Odin file btw. I assume the s pen works on that one. Never did use the one for the P905, that you posted with that warning.