I've rooted my GT 10.1 but I have two questions that I can't find the answer.
1. Has anyone discovered how to unroot back to stock?
2. If rooted, will I be able to get the OTA of touchwiz by checking for updates under settings?
PS I flashed the TouchWiz UX found in this forum. Got to say it is really nice and I can't wait to get the version from Sammy. I then restored a backup using Rom Manager and restored fine except when checking for software updates. It used to say no update available, but today it says failed to connect to servers. Anyone else getting this error?
I guess that is actually 3 questions.
Thanks
1. Unrooting is pretty simple. Just flash the 3.1 OTA in the dev forum, after doing a full wipe. If you feel the need to go back to full stock, you'll also want to nvflash back to the original retail recovery, which you undoubtedly saved when you first rooted.
2. No one knows yet, but rest assured, within a day (less probably) of the update being released, it'll be available here as a rooted flashable ROM. If you learn one thing from your time on XDA, it should be "never accept an OTA update." Let the devs pull it apart and repackage it in a nice root-safe download.
Undoubtedly! (I wish) I wasn't planning to root but while playing with Odin, I thought I was locked at the downloading screen while testing odin. (Didn't hold down the power button long enough to shut off tab) I thought my only solution was to continue and root. No problems rooting, it was easy. I just wanted to make sure I get the TouchWiz update. Now I learned my lesson I will never do an OTA update.
Glad you told me that, otherwise I probably would have screwed up my GT. I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
pmsrefugee said:
Glad you told me that, otherwise I probably would have screwed up my GT.
Click to expand...
Click to collapse
It's not so much that you'll screw up your device by accepting an OTA, but rather that you might lose root and/or your custom recovery (perhaps permanently). Nevertheless, there are some cases of OTAs screwing up devices when accepted over non-stock installs, so IMHO its always best to wait for a flashable ROM.
pmsrefugee said:
I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
Click to expand...
Click to collapse
Yes, I believe the stock retail recovery is posted in the CWM recovery download package here: http://forum.xda-developers.com/showthread.php?t=1130574. You'll note that Step 3 is where you were advised to backup your original stock recovery, although the step is (correctly) noted as optional. No big deal, in any event. Glad I could help.
I have solved this problem I think last night by updating to XXEMB1 on Kies last night - I have of course lost root for the moment but will get back to that later when I have more time
I have an international galaxy gt19300
It had begun to restart itself a few times a day and then would run for days with no issues
I eventually decided to root it when I found the new toolkit on here which seemed to work a treat
I now had superuser installaed titanium back up and ROM Toolboxand paid for pro versions of this and toolkit
to be honest apart from doing one back up using the toolkit the only other thing I did was to disable the auto scanning on start up to speed up booting the phone. A day or two after this the problems started again but this time with it no rebooting but just freezing. Eventually I took out the sd card as I remembered I had an sd card problem with my old S2 - though this is a new samsung sd card. At first I thought that was it but then a bit later it froze while i was browsing the app store and has done so periodically, though today it ran all day without freezing onvce. Then suddenly it froze again for no reason - I was just swithcing screens and it froze part way through the process
As far as I can see I have three options
1) Flash a new ROM (for the moment I am still using the stock rom having only just rooted it using Toolkit.exe from here) but not sure which one I should use so need reccommendations
2) Use the toolkit to download a stock odin flashable rom (but dont I have this already?) and then 3 reset the flash counter using triangle away (seems risky to me) install the stock rom , undo root (if necessary) and then return the phone to Samsung
3) go to Kies and install the latest update in the hope that the problem will go away - though if S User pro doesnt manage to keep root I wiill presumably have to re-root all over again.
What attracted me to S3 Toolkit was that it packaged up all sorts of options into one easy package - on the other hand this may have made me a little over confident with rooting. If I hadnt rooted it the earlier problem, though not as bad, would still have been there but I could easily have sent it back to Amazon UK or Samsung UK for repair and replacement.
My biggest worry at the moment is that whichever process I go for - or even a third option suggested here - there must be a risk that the phone might lock up during flashing or upgrade - probably not likely as it didnt when I restored the back up I had done (didnt help either) and the touch wiz ui wont be running
Anyway would really appreciate some help guys - even if it is only what you would do in the same circumstances. I guess I should have tried to have the problem fixed but earlier I put that down to maybe having too many apps and crapware and thougth rooting would help me solve it. I have unintstalled every app that I dont regularly use but it is still happening
gbswales said:
...
Click to expand...
Click to collapse
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Thanks for your advice
chrismast said:
First of all you have to be aware of the fact that rooting & flashing ROMs is always a risk, toolkit or not.
The safest way is to stay un-rooted stock if you do not know why you need root in the first place. If you know you need root, and actually also before, read the guides & information in the stickies under the General section as they explain you in detail how to root, un-root, use triangle away etc.
As for your situation, I would try to 1) flash another kernel than the stock one, if this does not work, 2) flash the most up-to-date stock ROM (you can get it here on XDA or sammobile.com) via Odin or Mobile Odin, not the toolkit (Odin is as simple as the toolkit if you follow the how-to), if this also does not work 3) try a custom rom, and if it also does not work 4) return back to stock and give it to Samsung service centre.
I wish you good luck!
Click to expand...
Click to collapse
Firstly the good news is that it turned out to be a problem with the last XXELLA upgrade - I found a new one on KIES ran the update and it is fine
Of course I lost root access but expected that anyway.
I do enjoy tinkering with Systems and although I know my way around Windows I have not tried with Android until now - this is my second Galaxy so was naturally wary of bricking it if I rooted. Christmas time I bought myself a galaxy tab 2 10.1 with the express aim of rooting it and was prepared to take the risk - after a few false starts I got it rooted fine - was still wary of the phone but once the kit came out the benefit that has for me is the way you have to check things step by step systematically as you do things - my problem with doing stuff from instructions on line is that I find it is all to easy to skip a step (which I did with the tab first time around) Also with it being a system I haven't explored before I like having a step by step approach which is the same way that I learned DOS way back in time.
I do want to try some different ROMs on it to see what they offer and I would really have liked to have got some apps running from my external SD card and I also like having a complete image back up (as I have for Windows 8) so that in the event of a serious issue it is easy to wipe all and restore from new (I keep several images which I make on a weekly basis so that I don't have to re-install everything.
I confess to playing with computers and devices as a hobby - evidence of this was the 350 apps I had installed before I started purging them in case that was the cause of the problem. I pretty nearly try every new app I find just to see what it does and so there being a whole range of apps that I couldn't install without root access upset me. I am not going to rush to root again and will at least wait until the current version has been on the phone a while - just to make sure the XXEMB1 version is stable now - it has a lot of new admin features to keep me amused for a while!
Two things that disappointed me about root were that it looked as if I couldn't overclock the device to improve speed - the main CPU bar was already on max (though I didn't have time to explore more than that) and that it still seemed pretty hard , if possible at all on the hardware, to run apps from the external SD card -- as I do now with windows (using a smaller SSD ) I will have to be a bit more prudent about uninstalling the apps I find I don't really use.
I guess deep down the main reason why I want root is I don't like any manufacturer telling me what I can and cannot do with the device I paid for - one thing I did try was installing Linux but that didn't quite get finished before I lost root access.
Your advice however is very sound for people who don't like or enjoy tinkering or taking risks and I don't think I would recommend any normal phone user to root their device.
Thanks again
Just to add quickly....to overclock you need to flash a kernel that supports it.....And know what you are doing before doing it
i have been seeing a lot of threads about rooting this phone, but, they all have windows scripts, even the thread that is said to have a runme.sh does not have it in any of the links that i unzipped - only a runme.bat, but yet, people keep mentioning a runme.sh in it... also, i really don't see any one lying out the steps for doing this with linux.
i'm a noob, and dont really know much about this stuff, but i've done this ONCE before with a galxy exhibit, but it was very easy, i just copied a file to the phone (stock rom?), rebooted into recovery, told it to recover from that file, and i was done.
i have no idea how to do it with my new phone, and so i'm wondering:
1: where can i find the files i need to do this with linux - i just want root, nothing special
2: where can i find the steps necessary to do it - in the easiest manner possible?
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
any help is appreciated.
sentientsystem said:
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
Click to expand...
Click to collapse
Your phone is running ICS 4.0, that is the version which it shipped with. Pretty much everyone on here has upgraded to JB either with software update on the phone or they have manually updated with the offline KDZ flash method.
I dont have any experience in linux so I cant help. I hope you can get your phone rooted!
Sent from my LG-P768 using xda app-developers app
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
sentientsystem said:
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
Click to expand...
Click to collapse
You would need wine and then set it up...
Sent From My Xperia Themed P769
well, i tried that "LGpwn" and it didn't work, as well as a fake lg-recovery app. i figured out that i've got a "10g" phone (P769 V10G ICS). i'm not sure what the next step is. some one mentioned downgrading to JB... is there some where you can point me to for that???
i've GOT to get this t-mobile junk off my damned phone... i've even TRIED to install cyenogenmod, but i can't figure out how to get my phone to go into recovery mode (NOT factory rest) - i've tried volup+power+home and volup+power, and neither seem to be working.
Setup a sandbox, windows xp. LG uses windows, no other way to root as of right now for the t-mobile version.
Sent from my LGMS769 using xda app-developers app
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrade to a samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
sentientsystem said:
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrad to an samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
Click to expand...
Click to collapse
Option #1
If you are rooted on stock T-Mobile 10e or 10g ROM and have the CWM installed from this thread:http://forum.xda-developers.com/showthread.php?t=2095825 follow my instructions.
Place one of these CWM ROM images on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2136204
Place this JB radio firmware from T-Mobile 20d ROM on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2256350
Power off the device.
After power on the back/menu capacitive buttons will flash repetedly. Press Volume down while the lights are flashing and the phone should go into recovery.
Flash the ROM first.
Flash the radio second.
Reboot.
***Notes***
1.) 20d is the latest T-Mobile, 21b is the latest Wind Mobile. Both work.
2.) 21b is lighter/faster but has no wifi-calling.
3.) 21b will require you to manually enter your APN settings for cellular data and MMS. Be sure to write down your APN settings before flashing this ROM.
4.) Some users say battery life sucks on JB. I notice that 21b is better on battery life than 20d.
Option #2.
In Linux install a Windows VM and follow the standard instructions here:
http://forum.xda-developers.com/showthread.php?t=2173465
Use KVM with a GUI or even easier use VirtualBox.
I'm a die hard linux geek too. I even run linux at work while all of our msp software was written for windows. You are better off just running an old copy of xp inside virtualbox trust me its just easier that way. You can use adb if you like (its the same thing the windows users use in their batch files and just rewrite the bash script, but you will save yourself lots of headaches just using virtualbox. -- my .02
Sent from my LG-P769 using xda premium
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
# what's the difference between unlocked boot loaders and being rooted?
# do you have to unlock the bootloader to get root access?
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
My bad. I should have read through your original question all the way before posting. I see that you are not rooted.
If you are on 10e ROM you can root in Linux:
http://forum.xda-developers.com/showthread.php?t=1990705
It will require rewriting the batch script as a Linux shell script. It is possible but nobody has done it yet.
If you are on 10g you will need Windows. I have also answered your questions below.
sentientsystem said:
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
It allows you to boot an un-signed kernel. You can boot custom ROMs basically.
# what's the difference between unlocked boot loaders and being rooted?
Root allows you to `su -` to the root user and own the whole system.
# do you have to unlock the bootloader to get root access?
No.
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
Click to expand...
Click to collapse
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
sentientsystem said:
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
Click to expand...
Click to collapse
Welcome!
I know that a long time ago when I ran VirtualBox in Ubuntu there was something I had to do to allow USB access to the VM.
Here are the current instructions directly from Ubuntu:
https://help.ubuntu.com/community/VirtualBox/USB
Good luck.
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
sentientsystem said:
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
Click to expand...
Click to collapse
Yes you can flash a pre-rooted image. They are available. Use the search?
I posted instructions on the first page showing how to boot recovery.
that's great news - that's all i really needed - i didn't see them before, at least, not conspicuously, but i'll search around again.
and, i must have some how missed your instructions, i'll look again.
thanks!
kevev said:
I posted instructions on the first page showing how to boot recovery.
Click to expand...
Click to collapse
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @everyone for your help.
sentientsystem said:
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
Click to expand...
Click to collapse
I've decided to help you out This page will give you some more info on the P769 and several kdz (roms) for the P769
The fastest way to root is to flash the V21B kdz (this is the Jelly Bean version for Canada) using this guide, http://forum.xda-developers.com/showthread.php?p=36351786
The reason why you want this rom is because it has a vulnerability that is easy to exploit with Jcase apk
Once your followed everything (and rooted), install Super Su and Busybox
Next install artas182x second init CWM (in case you can't find it on his page, the link is here )
Note: you will see blinking led lights when you see the LG logo (booting up) appear after a couple of seconds. To enter the CWM press the vol (-) when the lights start flashing.
After you installed Artas182x CWM you can recover from someones clockworkmod backup.
following info from Cmahendra's thread
Note: only restore CWM backups from P769 versions or MS769!!!!
Or check out the V10B (MetroPCS "JellyBean") CWM backup
Now the only 2 reasons to unlock the bootloader are:
1. Install a safer and better CWM
The reason why is because Artas182x CWM is a second init (bootstrap), so if you mess around with a busybox apk and something goes wrong or you remove a file that is required (for CWM), it will stop operating. You will have to reflash the kdz or fix what you changed to get it working again.) I've had this problem several times while messing around with different busybox apps and etc.
2. Custom roms
(which you stated you are not looking for) not worth talking about right now.
Answer to questions
The only pre rooted roms are clockworkmod backups, lol
The default recovery is useless to us (unless you feel like solving the problem)
Flashing back and forth (ice to jelly) comes with risk, the program used on Windows to flash is buggy at times. The best way (in my opinion) is to flash only when really required and mostly restore from clockwormod backups. The device is actually hard to hard brick, but it will require at lot more knowledge to get your device running again.
---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------
sentientsystem said:
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @all for your help.
Click to expand...
Click to collapse
So what version are you on right now
Ice? Jelly?
i'm still on ICS for the moment. still trying to understand what i need to do next. re-reading your post for the 2nd time, and all the threads it references. making sure i don't screw any thing up. thinking about upgrading to JB, and trying this CWM. and looking into this "cyanogenmod" some more, to understand why i never see any one on this site mention it, and what all these "other roms" are about. lmao, like i said, i'm way new to this . it's a lot to take in, even for a web developer .
thanks \m/ (>_<) \m/
So i got this phone yesterday, and i came from my old Galaxy S3. I am used to rooting and installing custom ROMs on that device and was wondering if there was anything I should be aware of with this phone. I do plan on rooting it in about 2 weeks depending on how I feel about touchwiz then, but for now i would like any information about possible brickings due to knox. thank you.
DO NOT USE Kingo root. - I wish I saw that earlier
I tried to use it. ended up failing. Then I followed qbking77s' instructions which also did not work out well for me. I bricked my note 3 and tripped knox on the first day I got the thing lol.
Thankfully I was able to find an odin-flashable to push over to my device and everything is ok. still gotta root the damn thing tho.
Number 1 Rule!!!/ General tips
1.) Heres the big thing about the note 3.
You cannot revert (odin flash) back to previous builds of the note 3, it will soft-brick (maybe even hard-brick) your phone.
Meaning if you are on NC5 its not a good idea to dowgrade back to NAB. This is a smaller jump but ive read of issues. Though NEVER try to odin from kit-kat to Mj4 jellybean. They have different incompatible bootloaders, and it will brick. So ya no downgrading.. Unless you really feel comfortable with "engineering boot loaders" But currently the newest build is "NC5"
2.) think the most convenient root method is to..
-put chainfire's UPDATE-SuperSU-v1.94.zip onto sd card
http://download.chainfire.eu/396/SuperSU
-odin twrp 2.7.01.tar, (found in original development) or link
http://teamw.in/project/twrp2/201
-immediately boot into twrp (Home+Power+Volume Up) and flash UPDATE-SuperSU-v1.94.zip
reboot
Now rooted with twrp recovery to flash new roms
3. Just another warning. Factory reseting with STOCK recovery for this device wipes internal sd card.
Edit/Add on: About knox: Dont worry too much about it. Once your rooted on stock rom, it will probably prompt to attempt to disable knox. just hit okay and thats probably the last you hear about knox. When you flash a new rom the rom devs have it disabled so it never prompts. But ya knox isnt really much of anything but a counter in download mode. Yes it cant be reset, but thats about the only thing that cant. You can still be fully unrooted, with official status. You probably wont have any problems with sprint. Theyd have to check download mode for the 0x1, and they would have to know what that means too lol. And you definitely wont have problems if you have sprint warranty.
Hope that helps good luck, I love this phone!
CollinsB said:
1.) Heres the big thing about the note 3.
You cannot revert (odin flash) back to previous builds of the note 3, it will soft-brick (maybe even hard-brick) your phone.
Meaning if you are on NC5 its not a good idea to dowgrade back to NAB. This is a smaller jump but ive read of issues. Though NEVER try to odin from kit-kat to Mj4 jellybean. They have different incompatible bootloaders, and it will brick. So ya no downgrading.. Unless you really feel comfortable with "engineering boot loaders" But currently the newest build is "NC5"
2.) think the most convenient root method is to..
-put chainfire's UPDATE-SuperSU-v1.94.zip onto sd card
http://download.chainfire.eu/396/SuperSU
-odin twrp 2.7.01.tar, (found in original development) or link
http://teamw.in/project/twrp2/201
-immediately boot into twrp (Home+Power+Volume Up) and flash UPDATE-SuperSU-v1.94.zip
reboot
Now rooted with twrp recovery to flash new roms
3. Just another warning. Factory reseting with STOCK recovery for this device wipes internal sd card.
Edit/Add on: About knox: Dont worry too much about it. Once your rooted on stock rom, it will probably prompt to attempt to disable knox. just hit okay and thats probably the last you hear about knox. When you flash a new rom the rom devs have it disabled so it never prompts. But ya knox isnt really much of anything but a counter in download mode. Yes it cant be reset, but thats about the only thing that cant. You can still be fully unrooted, with official status. You probably wont have any problems with sprint. Theyd have to check download mode for the 0x1, and they would have to know what that means too lol. And you definitely wont have problems if you have sprint warranty.
Hope that helps good luck, I love this phone!
Click to expand...
Click to collapse
I 2nd what CollinsB says, SuperSu v1.94 best way to go to root your note 3. You also might look into Philz CWM recovery. As for KNOX and your warranty don't worry sprint and Samsung have not turned down a warranty fix that I'm aware of. Besides, They have already figured out a way to reset KNOX on the Exynos processor its only a matter of time before they solve KNOX for the Qualcomm processor.
---------- Post added at 05:06 AM ---------- Previous post was at 05:02 AM ----------
One of the best things you can do, is disable touchwiz!!!!! Install the nova launcher, better, faster, and more features. Enough said!!!!
First of all, I apologise if I have posted this in the wrong section. Secondly, please be aware right now that the device in question is the S3 4G VERSION. Very different to the vanilla S3. I have dabled in rooting/flashing and general messing around with android firmwares before so I have a mild understanding but please be patient
Now the problem: Rooting. It shouldn't be hard. Should it? Not with tools like chainfires auto rooting kit these days... Alas, CF's auto root isn't doing it for me. At first I was having dramas with KNOX (congrats on loosing a long time customer there samsung). After i got rid of that with the de-samsungizer kit flashed through CWM it stopped showing the stupid "an application has attempted to gain root access and was blocked" crap. However SuperSu continued to crash, I'm assuming because the root was not properly completed. NO error codes or anything are ever returned from Odin, or CWM, everything looks like its happy but just not rooting. Confirmed with rootchecker.
Now a couple of other things I should mention: CWM keeps getting erased or something aswell? Like I'll turn the phone off to go into recovery mode, and im sitting at the bone stock one again, with the little red exclamation mark over my poor android corpse D:
I even tried disabling auto-reboot in ODIN when flashing CF's auto root, droppping the battery and manually starting recovery mode. I get excited when I see the red pirate-droid executing instructions, all goes well, everything is happy, still no root -_-
EDIT: In download mode, knox still exists and has logged EVERY attempt i've made. so everything is definitely executing just fine...
This is also my first time rooting in the presence of KNOX
I don't know what else to do... Am I missing something? is there a glaringly obvious thread or bit of information I've missed?
Thank you in advance for any help provided.
Ok so I took a break from this for a while cos i got really busy and didn't fancy doing MORE work on my phone when i finally got a spare tic. However, I came back to it today and managed to find a magic combination.
I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE, PLEASE FEEL FREE TO CRY IN A PM ABOUT IT THOUGH I COULD DO WITH A LAUGH.
The following is a guide for anyone having issues making the root stick on their GT-i9305 samsung galaxy s3 4G/LTE on android 4.3. DO NOT ATTEMPT THIS ON ANY OTHER OS VERSION, VARIANT OR DEVICE.
I noticed a particularly important piece of information in the following link: How to Fix Android 4.3 Jelly Bean Rooting Problem for Galaxy S3/S4/Note 2/3 - W0lfDroid
A superSu update. So i went there grabbed that package ( SuperSU Download for update package ) and started my grand master plan. If you would like to actually read what hte user said yourself, its in a quote bubble naer the bottom, just before the comments.
now. Using an important piece of information in a thread I cannot, for the life of me, find through my browser history (apologies) I grabbed a copy of pihlz touch which you can find in the following thread: [CWM][PhilZ Touch][GT-I9305] 4.00-b21 Touch … | Samsung Galaxy S III I9300, I9305 | XDA Forums
Now. grab yo-self a copy of busybox's supersu root How to root Galaxy S3 I9305 with SuperSU 1.02 - Samsung Update located on that page. Make a folder on both your phone's internal storage and external, name them both the same thing and something you will remember. For instanceI called mine Root stuff. I only do folders on each of them in case I can't extract from external for whatever reason, its not necessary. Put both the supersu update you downloaded earlier and the one you just downloaded from above, busyboxes root, into both of these folders if you did it my way.
To avoid having to reboot your phone an extra time, make sure you did the above step BEFORE moving on
First up, I flashed philz touch with Odin (ensure you have the latest version, use your PDA checkbox and be sure that auto reboot and F. reset time are checked). Next up, turn your phone off and boot into your magnificent (no seriously, this is amazing. Its like a GUI in todays BIOS's...) new CWM recovery mode. Go into advanced and hit reset permissions or something like that... My phone is downstairs atm and I CBF in going and getting it and rebooting. Note that I am unsure if this is actually an essential part of the process, this is something I did because I worried about the permissions on the phone after my, by KNOX's count, 15 attempted flash operations -_- More like freaking 20 thousand....
Now once you have done that, go back to the main menu and tap install zips. FIRST you select the actual root, supersu1.02 busybox. Next, select the extra zip file option and que the UPDATE supersu-v2.02 after the actual root package. Once you have done this, swipe to install. THESE TWO PACKAGES MUST BE IN ORDER!!!!
Thats all I did. My phone rebooted and I was able to use Root checker to conform the root, allowed access to supersu and no crashing. Finally. THat was way too hard.
Thank you for hosting the website gentlemen/ladies where we can all come and share knowledge.
all credits go to anyone/webpage I linked people to and the brilliant programmers that made the packages. And finally, a HUGE thanks to Google and Linux (from which android is based) for freeing us from the shackles of iOS.