Related
I am N1 newbie but not Android newbie - have been using rooted Droid Incredible as my "main" phone for several months.
I just purchased officially unlocked N1 that is currently activated on prepaid T-Mobile account in USA and in future it will be used on my vacation in Europe.
Phone came with OS v. 2.2
I read a lot and things are sure different for N1 comparing to DInc. For DInc there was just one OS update and just one way to root it. For N1 its almost too much of a good thing for someone who hasn't followed it until now - 3 or 4 official OS updates and gazillion ways to root .
At this time I would like to root the phone (definitely, so that I can use third-party apps that require root access) and upgrade OS (possibly). I am not planning to use custom ROMs at this time but would like to try them in the future if rollback to stock ROM is possible.
As I already mentioned - my phone currently uses OS 2.2 and when I checked for an update via phone menu no updates were found. I was connected to internet at the time.
Questions:
1) From what I read some of the official ROMs between 2.2 and 2.3.4 (latest version) had problems. Are these versions even worth considering now that 2.3.4 is out?
2) Are there any known issues in 2.3.4 that are not present in 2.2?
3) What are advantages of going from 2.2 to 2.3.4?
4) Can I upgrade from 2.2 to 2.3.4 directly? All guides I found usually describe 2.2->2.2.1 etc - that is ROMs are updated consequently as they were released.
5) Should I a) update ROM to the latest and then root or b) first root 2.2 and then update ROM?
6) What are advantages of rooting with unlocking bootloader as opposed to rooting without unlocking bootloader?
Read the wiki. It is there to answer most of your ?s. Or use the search function.
If anything is still unclear ask about it and you will get help.
Sent from my Nexus One using XDA App
albundy2010 said:
Read the wiki. It is there to answer most of your ?s. Or use the search function.
If anything is still unclear ask about it and you will get help.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I read the WIKI and searched and it is still unclear.
1. 2.3.4 is the only version that currently has a fix for the recently found security hole that affects every version of Android other than 2.3.4. But this only affects non-https logins over an open wifi network, and people have to be scanning it.
2. I think the only major issue (depending on who you talk to) is the 2-3 second delay when you first answer a call before your microphone works. It has never really been a bother to me, and doesn't seem to affect everyone (maybe some just take longer to talk after they swipe, IDK).
3. There are a lot. Bugfixes, better UI, faster, support for video calling with GTalk (although obviously, only the back camera works, but you can still receive fine).
4. Almost, you can upgrade directly to 2.3.3. I don't think I have enough posts to add links, but a quick google search of "nexus one full gingerbread update" (without quotes) showed some results and the second one for me is how to manually update to Gingerbread. From there, you have to root the phone, because there are no hacks known to root 2.3.4 yet. This is where it gets a bit tricky because flashing a new update will kill your root. There are a number of guides on xda which can walk you through this part, because it is pretty detailed.
5. Kinda touched on with the above. Don't wait until you get to 2.3.4 until you root.
6. An unlocked bootloader makes things a lot easier. You can actually root your phone if it is running 2.3.4, because this allows you to load a custom recovery, which will give you access to the system partition of your phone. From there, you can add the files needed for root and remove the ones that will replace the recovery. The only benefit to keeping your bootloader unlocked is that it will keep its warranty through HTC, although HTC has been really good about replacing defective phones even if the bootloader is unlocked.
Okay. Well I recently rediscovered my droid OG. Got it working again (thought it was bricked), factory reset and SBF'd since root wasn't working properly and now I can't find a working root method. I can't get it to show up in my virtual machine (i have a mac) without unenabling usb debugging.
also, once i've got it rooted, can i turn all data stuff off so it's a wifi only device and it doesn't bug me about activation? also what are the most stable ROMs and what are some things i can do with this device?
This is a complete guide: http://www.mrmuh.com/2012/01/update-a-motorola-milestone-from-motorola-firmware-to-cyanogenmod-7/
Activation isn't mobile data related; it's Android default rom related. You can skip that step, but keep in mind that using Play store needs an active Google account. If you don't need play store and google apps, do not install gapps after flashing CyanogenMod
scoutme said:
This is a complete guide: http://www.mrmuh.com/2012/01/update-a-motorola-milestone-from-motorola-firmware-to-cyanogenmod-7/
Activation isn't mobile data related; it's Android default rom related. You can skip that step, but keep in mind that using Play store needs an active Google account. If you don't need play store and google apps, do not install gapps after flashing CyanogenMod
Click to expand...
Click to collapse
That guide is for the Milestone, he is talking about the Droid.
Don't use anything built for the Milestone on your Droid - they are not compatible. Browse the forums here, and take look at this guide:
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
I think there's some apps to handle the root part (superoneclick? droidmod?)
Sorry I can't help more, I don't know the Droid very well and don't want to lead you the wrong direction.
scoutme said:
This is a complete guide: http://www.mrmuh.com/2012/01/update-a-motorola-milestone-from-motorola-firmware-to-cyanogenmod-7/
Activation isn't mobile data related; it's Android default rom related. You can skip that step, but keep in mind that using Play store needs an active Google account. If you don't need play store and google apps, do not install gapps after flashing CyanogenMod
Click to expand...
Click to collapse
yes i can skip it but the problem is that every time the thing reboots it asks me to reactivate so i was wondering if there was a way to get rid of it.
CanAndroid said:
That guide is for the Milestone, he is talking about the Droid.
Don't use anything built for the Milestone on your Droid - they are not compatible. Browse the forums here, and take look at this guide:
http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
I think there's some apps to handle the root part (superoneclick? droidmod?)
Sorry I can't help more, I don't know the Droid very well and don't want to lead you the wrong direction.
Click to expand...
Click to collapse
i actually have gotten my phone rooted and found that guide. i also found a universal wifi only flashable zip. however, the phone gets way too hot to be practical lol
jkingaround said:
Okay. Well I recently rediscovered my droid OG. Got it working again (thought it was bricked), factory reset and SBF'd since root wasn't working properly and now I can't find a working root method. I can't get it to show up in my virtual machine (i have a mac) without unenabling usb debugging.
also, once i've got it rooted, can i turn all data stuff off so it's a wifi only device and it doesn't bug me about activation? also what are the most stable ROMs and what are some things i can do with this device?
Click to expand...
Click to collapse
Here is a working root method for the Motorola Droid (Its also mac friendly the guide since you mentioned you have a mac). Do not follow the guide the person above me posted it is for the GSM Motorola Milestone not your CDMA Motorola Droid 1 ! The guide will also tell you how to install the latest version of Cyanogenmod (7.2) and Google apps. What virtualization software are you using? After you root the phone the easiest way to turn off data is put it in airplane mode and just connect to your wifi network. As far as ROM's the above mentioned CM 7.2 is the most stable, as far the getting the most performance using Chainfire3D, V6 supercharger, and these build.prop tweaks. Let me know if you need any further help
thanks. i've gotten as far as rooting it and i put CM7 on it. however, i think it's got a bad battery, plus it gets really hot so i'm pretty sure i'm just going to give up on this device. Was hoping it could be useful as a media remote for my mac or something of that sort but pretty unlikely.
jkingaround said:
thanks. i've gotten as far as rooting it and i put CM7 on it. however, i think it's got a bad battery, plus it gets really hot so i'm pretty sure i'm just going to give up on this device. Was hoping it could be useful as a media remote for my mac or something of that sort but pretty unlikely.
Click to expand...
Click to collapse
If you search online you can find a droid 1 battery on amazon for under $5 :thumbup:
Sent from my SCH-I535 using xda premium
hmm it's possible. i might do it if there is anything cool i can really do with it? otherwise it's not worth my time haha
if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
trinniboy68 said:
if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
Click to expand...
Click to collapse
Since you have the developer edition, are you rooted? If so, why not use the stock framework tether? You can use the Xposed module, or the Entitlement Check remover.
Also, if you are rooted, you can use the latest experimental build of WiFi Tether for Root Users.
Is there a specific reason you are wanting to use FoxFi? The only reason I can imagine is that you are not rooted.....but if you aren't rooted, why did you get the Developer Edition?
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
moto x
KidJoe said:
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
Click to expand...
Click to collapse
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
No 'hacks' for your phone? The entire android SDK is available for MAC. We have several users here who have flashed their phones 100% with MAC.
If you download the MAC Toolkit, it includes everything you need, even though it isn't supported by its devs anymore. You just won't use any of the scripts (that's all that no longer supported). Also, since you have the DEV edition, you WON'T lose your warranty by rooting it. It's HIGHLY unlikely you will brick your phone unless you do something totally stupid that is well documented here (like: you NEVER downgrade or flash older firmwares/versions on your Moto X - this is one of the few ways you can brick it).
Since you have already unlocked the BL, all you would do is fastboot flash TWRP recovery, and it will root for you. Then you can use either method that @KidJoe and I have suggested for you. There honestly isn't much at all you can mess up.
Additionally, once you install TWRP, you can take a full backup that you could restore in the event of a problem. PLUS the SBF images are available, so even without a backup your phone could still be restored back to stock.
trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
thanks
KidJoe said:
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
Click to expand...
Click to collapse
thank you for the info
I have an ATT S5 (SM-G900A), completely stock, unrooted, updated to the latest 5.0 OTA update. My requirements for my phone are that it be able to pass Airwatch checks and that it be able to be encrypted (Personal device used at work). Some background first:
Last time I tried to play around with rooting, other mods, and whatnot was on my ATT S3 (I think I747?) and I discovered that an unspecified combination of rooting, installing a custom loader (CWM in my case) and installing a custom mod (Cyanogenmod at the time) made my phone unable to encrypt. At the time I was not required to use Airwatch, but encryption was required for my phone to connect to work, so I gave up on the whole lot.
I have now discovered that ATT, in their infinite wisdom, has replaced the S Voice drive mode with their own "ATT Drive Mode", and it's been verified they went so far as to remove the related APKs from the phone entirely. For those unaware, S Voice Drive mode is an feature of S Voice that (when turned on) reads out all callers and text messages, and then verbally prompts you for actions; reply, answer, ignore, etc. It allows fully hands free functionality. ATT Drive Mode, on the other hand, automatically kicks in whenever speeds of 20 MPH are detected (even if you're a passenger), rejects all calls and texts excluding a user-defined 5 person list, and essentially makes your phone useless anytime you're in a car. The goal is to "reduce texting and distracted driving", but as I'm on-call as part of my job and need to at least be aware of texts that come in within 10 minutes of receipt, it actually makes my drive much more dangerous. ATT Drive mode is a good idea for teens, perhaps, but i'm not a teen.
This brings me to my question: What are my options?
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
Honestly, the ideal solution would be something like the stock rom from the international version that would run on my ATT version...but I don't know if such a thing exists or is possible. I don't mind Samsung's cruft, but I do dislike ATT's lobotomizing of my phone to push their own little product that treats me like a kid. I know that I am less safe as a driver without the S Voice drive mode than I was with it.
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
sheaiden said:
I take it I have no options? And that no one knows how rooting affects encryption?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Waiting4MyAndroid said:
I will make it easy for you. Since you took the 5.0 OTA update rooting is not possible anymore. Also there is no way to downgrade to KitKat which was rootable. Sorry. Not much you can do until someone finds a way to root 5.0. If you find the S Voice Drive app, you can side load it and see if it works.
Click to expand...
Click to collapse
Actually, while I greatly appreciate the fact that you took the time to reply (seriously! at least you took the time!), this is neither easy nor related to the questions I asked. If you look at my post, I'm not asking "how can I root", I'm asking three rather different questions:
--Does rooting break my ability to encrypt? I know airwatch will flag, but I'm thinking there's a possibility of being able to root, put a custom loader on my phone, and then restore stock with that custom loader, whereupon I can try to install the drive mode APK...which leads me to my next question:
--Does having a custom loader (like safestrap or CWM or whatever is in use nowadays) break my ability to encrypt?
--Does anyone know of a way to install the S Voice drive mode in the G900A? I tried searching, but the only references involved being rooted, or ended with something vague like "download a stock rom and find the apk using root explorer" as the solution (which is vague to me because I don't know which stock rom to use, what apk to look for, and last time I used root explorer on my s3, it needed root...)
In fact, I am unable to remain rooted (Airwatch; it's part of the post title), and the whole point and thrust of my question lies in the fact that I am looking to find out what affects encryption and what options I have as far as getting S Voice Drive mode on my phone while staying Airwatch compliant (not rooted). In addition, "if you can find the s voice drive app" is part of the problem too, as evidenced by the third question I asked above; I don't know where to find said app.
Does anyone know anything regarding what I was actually asking?
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
https://www.dropbox.com/s/oe7i2g81iuhjv38/S-Voice_Android_phone_J.apk?dl=0
Waiting4MyAndroid said:
Everything that you want to do requires ROOT! Safstrap needs root, CWM will brick you phone since the bootloader is locked. Again, there is no way as of now to root the S5 with 5.0 att OTA.
Here is the link to download the GS4 S Voice app. You can try and side load it,
Click to expand...
Click to collapse
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
sheaiden said:
Awesome, I'll start with that sideloading, and test it out. Thanks! As far as the rest, I suppose that does clarify some things (that I admittedly already knew), so I do appreciate it, but it still does leave the answers to the other questions. I can infer, of course, that the answer to whether having a custom bootloader on the Galaxy S5 breaks encryption will be dependent on whether root breaks the encryption, since as you pointed out custom bootloaders need root to install, but the fantasy I entertained for a little while was rooting when there's a method (hope springs eternal, so I'm hoping it will eventually be possible), installing a custom bootloader so I can do things like backups and sideload, getting the proper apk's installed for the drive app, and then unrooting it so I can connect it via airwatch to my work's network. Perhaps I should have marked this as a solidly theoretical question, since as you said, there currently exists no root. I just want to know, with the unique way that Samsung implemented Knox and the encryption on the S5, what will break encryption and what won't?
Of course, there is a side question brought up by all this...how possible is it to load another firmware on my phone? as in, use Odin to put the tmobile image on my phone. That is likely a bad example, since I'm fairly certain there are actual hardware differences between the ATT and the tmobile models, but the concept still stands. At what level are the hardware configurations different between phone companies?
Click to expand...
Click to collapse
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
OPOfreak said:
You will not be able to change your bootloader period... At this point the locked bootloader is unbreakable. That leads to your next question about tmobile and that's a no as well due to the locked down bootloader.
Even with root you won't be able to do anything you've suggested due to the locked bootloader.
Click to expand...
Click to collapse
Interesting. I had been under the impression that I had seen people referring to installing clockworkmod or some similar thing on an S5, but I think I may be getting caught up in terminology; those are recoveries, aren't they? not bootloaders? Or perhaps people were posting about the other S5s with unlocked bootloaders. 15 different versions of S5, and I get stuck with the most apple-like of all the carriers....(in the sense of "you take what we give you and don't play with it!")
So, assuming I don't manage to get it installed via the link Waiting4MyAndroid was kind enough to post, I think that rules out anything other than the method of:
--wait for a root method to be established for the new OTA
--root, install the drive apk
--unroot, so I can encrypt and pass airwatch
Does anyone know if the old method of rooting broke encryption? and whether encryption was able to be performed after unrooting again?
Edit: Attempted to Sideload. Sadly, it is telling me "App not installed" (other sideloads do work; it's not the unknown sources setting). I'm thinking either the apk is marked for s4, and it's not compatible, or it's trying to overwrite files from the established svoice system, and that's not allowed. I suppose if someone has the drive apks from a tmobile S5 image or some such thing (same model, different carrier), then I could try again, but unfortunately this apk doesn't work. Thanks for the attempt, Waiting4MyAndroid!
Hello guys and Gals, this will be my first time posting so please bear with me. I have been trying to find the best option to root my Samsung Galaxy Note 3 Sm-n900a for a while now, seems to be one of the harder phones to root... this will be my first time attempting to root a device, so I want to make sure I do everything correctly. I have watched multiple videos and read a lot of threads on the subject but it is hard to find anything that is current and has the proper links to be files needed. if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it, if you do respond to the thread please dumb it down I am still learning terminology. I am determined to get this done come hell or high water. so if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it. Thank you for helping me put a nail in this coffin i I have been trying to do this far too long.
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/note-3-att/general/root-att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
GregJ7 said:
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/no...att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
Click to expand...
Click to collapse
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
XxLightxX said:
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
Click to expand...
Click to collapse
I just ended up stayin on kk rooted on mine. Everytime i goto lolipop i brick it. Its almost a hassle to try. I would odin the kk firmware and use towel root. Install xposed and some root apps. If ures is anything like mine dont debloat it. I debloat lightly. And next reboot get all kinds of spen and other force closes. The note 3 in general seem unstable. But i need to restore m8ne back stock now as its keeps force closing. I will be starting mine over for the 100th time it feels like. Dont let my ramblings discourage you. It is a awsome device and having a lgg5 iphone 5 and a few others my note 3s outer glass is destroyed. Got it like that. I would take the note 3 over the rest if i could get it to run rite more than 2 or 3 days at a time. Ive. Always set all my devices the same way. Debloated them the same but this one is really touchy.... Im on here a lot if u gots any ?s just hollar at me.
If you're still interested in an easy way to root, use Wondershare Dr Phone. It worked for me on stock OC1 and then the just used Flashfire to flash whatever I wanted.