Develop Bugs

Q&A with Shidell: FAQ on EVO, Root, what you should do, and more.

It seems there is a lot of questions regarding the EVO, root and more--so in an effort to clean up redundancy, I'll make an attempt to answer many questions in this thread. I'll touch on a number of important points initially, then you can fire away with questions which I'll (do my best) to answer.
If you have a question, you should read this thread before asking, as it may very well be answered here. If you don't see it, ask away!
Is the EVO GSM-compatible? Can I use it with Verizon?
Short answer: No. The EVO is CDMA-only, and does not contain a SIM card slot. You can try to get Verizon to accept the EVO on their network, but doing so will require you to first convince a representative to do so, which has been virtually unheard of (Sprint and Verizon, despite using the same CDMA technology, maintain HEX ID white lists for phones, and if your phone doesn't match, they can't activate it in their system.)
If you're on Verizon, I'd advise you to consider the Incredible, or wait for the Shadow.
What is 'Root'?
Root access (in linux/unix terms) is the equivalent of being an Administrator in Windows. Without being 'Root', or 'Administrator', what you can and cannot do is severely hampered. You are essentially using a 'Guest' account, with 'Guest' priveledges. This means that whatever HTC/Sprint/Etc. has deemed appropriate for 'Guest' users is all you have access to.
So why do I (or we) want Root access?
Having Root access means we can do whatever we please to our phones. As I said above, this gives us Administrator rights to add, delete, or do as we please to our devices. Without Root, you are forced to do (and use) whatever software Sprint/HTC want you to use.
Can you give us some examples?
Yes. With Root, you can flash a build of Android that someone else has created and/or customized. You can update/reskin your device as you please, add or remove software at your liking, and tether free of Sprint's surcharge. Additionally, without Root, you'll have to wait for Sprint and HTC to release updates for the EVO (which could be months..) with Root, you can load a build as the developers produce it.
Froyo will most certainly arrive (in time), but what about Gingerbread (2.3)? Whatever comes after (2.4)? There is no guarantee that Sprint and HTC will support the EVO that far out. The developers who have this phone, however, most certainly will.
I'm going to have my EVO for at least two years, and I plan on migrating and updating my device to the latest version of Android regardless of what other customers/users who do not have Root access are able to do.
...But there's a risk in getting Root, right?
Yes, there's a risk of bricking your phone, and however minimal that risk is, it needs to be stated. Your best friend is knowledge, so read carefully, read again, and follow directions. You're already here on XDA, you'll be just fine.
I'm concerned that the developer's builds of Android Eclair 2.1 and/or Froyo aren't fully functional, or we won't have the same functionality after Rooting.
Patience. Functionality is dependent on having a Kernel that supports all the technology on the device; an OS to run with that Kernel that supports all of the technology on the device, and the device itself. We have the device and the Kernel, we're just waiting on an official AOSP Froyo release.
If that doesn't make sense, consider this: HTC heavily modified Eclair to support technology like tethering, 4G, front and rear cameras, HDMI, etc. They had to modify it manually because support for it wasn't available in Eclair, but it IS available in Froyo.
In time, everything on the EVO will be fully functional in Froyo.
Where's Froyo?
Google will make Froyo available on AOSP when prepared to do so. Until then, the latest release of Android is Eclair 2.1r1. Again, Eclair doesn't support everything the EVO has to offer, so until Froyo is available, some items may not come to fruition in the developer community (4G access, tethering, etc. as examples.)
Wait a minute, can't I run Froyo from an SDK build?
Yes, you can--but an SDK (Software Development Kit) build is essentially OS files torn from the emulator in the SDK. This may or may not contain all of Froyo's end-result code, and may not be completely indicative of what a final release of Froyo will be like. It IS very useful for testing and tinkering, and isn't necessarily even a bad build to use on a day-to-day basis, as long as you understand it's limitations. When you're reading threads about functionality for a Froyo SDK build for the EVO, now you'll hopefully have a better idea as to why that functionality is limited right now.
I hate Sense UI! What can I do? Can we remove it? Can we replace the modified applications?
You can disable Sense, but you can't remove it (unless you're Root and can replace the OS entirely, that is.) Sense is deeply integrated into the core of Android in the release HTC and Sprint provide, so much so that certain applications (People, Messages, Internet) cannot be "undone" short of (again) replacing the ROM. You can disable the widgets, and replace the launcher (ADW Launcher is a solid alternative), but at the end of the day, Sense is so tightly coupled with the EVO stock ROM that you can't completely remove/replace or restore the original Android system files.
This is another good argument for wanting Root access.

[Reserved]

[Reserved x2]

Nice work.

is there a good tutorial somewhere on how to root in Ubuntu...this is my first droid phone, coming over from winMo

dahray02 said:
is there a good tutorial somewhere on how to root in Ubuntu...this is my first droid phone, coming over from winMo
Click to expand...
Click to collapse
do a search for adb ubuntu
the sdk for ubuntu is at google's android site.

First, thanks for taking the time to post a good compilation for some beginners like myself.
This is my first android phone, however I have been following the progression of the OS for some time.
As you stated above,
"With Root, you can flash a build of Android that someone else has created and/or customized."
I have seen on other forums, such as the hero forums, that there are several different choices for custom roms. I tried to see what the main "features" were but they seemed a little too technical for me at this point.
What are the main differences between different custom roms in terms of how they function or what they do differently, aside from OS versions?
Also, I do see that certain roms indicate they have the Sense UI turned off or tuned down. For someone who has only used stock roms which have sense already on, what does a reduced/disabled version of sense look like?
Thanks again!

I read that the Sprint OTA update that fixes the SD card issue breaks the first exploit for root, but that the Unrevoked exploit can still root even if the OTA exploit has been applied. Since I'm having SD card issues, I wanted to go ahead and accept the OTA update I initially declined. I tried the option to check for a firmware update, and it says there are none for me. I also tried the HTC software update, and it says I was already up to date. Does this mean the update got applied somehow already? Is there a way I can tell? Am I doing the wrong thing to try to force the update? My phone says "Firmware version 2.1-update1". But I'm still having SD card issues.
I'm also wondering if this thing can be unrooted, in case I need Sprint to handle it.

Thanks Shidell...much needed!!!
I am interested in a future update to froyo 2.2 w/ its new features, removing a few stock sprint apks and mainly, replacing the painful htc sense with AOSP. I much prefer the new AOSP launcher and 3d app drawer. UNTIL THEN, i would probably just like to remove some apks and add in some that may not be allowed from sprint (google nav? usb tether? etc) and maybe disable sense (like above).
What do you recommend? Toast Root, unrevoked sticky apk? Should i wait to root altogether?? Do i need to avoid future OTA's etc? or would rooting now be the way to go to protect future root options?? i just don't know what to do!
Thanks for your thread! Can't wait to utilize the evo in all its glory!! My vogue just couldn't cut it anymore.

Can we get this stickied? It's great info to refer to for all people (new or just new to android)

RN-Dude said:
I read that the Sprint OTA update that fixes the SD card issue breaks the first exploit for root, but that the Unrevoked exploit can still root even if the OTA exploit has been applied. Since I'm having SD card issues, I wanted to go ahead and accept the OTA update I initially declined. I tried the option to check for a firmware update, and it says there are none for me. I also tried the HTC software update, and it says I was already up to date. Does this mean the update got applied somehow already? Is there a way I can tell? Am I doing the wrong thing to try to force the update? My phone says "Firmware version 2.1-update1". But I'm still having SD card issues.
I'm also wondering if this thing can be unrooted, in case I need Sprint to handle it.
Click to expand...
Click to collapse
If you want to "unroot":
http://geekfor.me/evo/ruu/evo_ruu_1326511/
This is an exe that just flashes the phone back to the way it was when it was shipped (you'll lose all your data on the device, but your SD card should be untouched).
Also, to check for the update, you want to look under the Menu>Settings>About Phone>Software Info>Software Number
The OTA changed the last digit from a .1 to a .6.
Hope that helps!

sticky???
agreed, sticky please???? that would be great

MichaelWestin said:
First, thanks for taking the time to post a good compilation for some beginners like myself.
This is my first android phone, however I have been following the progression of the OS for some time.
As you stated above,
"With Root, you can flash a build of Android that someone else has created and/or customized."
I have seen on other forums, such as the hero forums, that there are several different choices for custom roms. I tried to see what the main "features" were but they seemed a little too technical for me at this point.
What are the main differences between different custom roms in terms of how they function or what they do differently, aside from OS versions?
Also, I do see that certain roms indicate they have the Sense UI turned off or tuned down. For someone who has only used stock roms which have sense already on, what does a reduced/disabled version of sense look like?
Thanks again!
Click to expand...
Click to collapse
In regard to rooting and ROM customization, one primary difference (always) is that you have root access, so that's something to keep in mind. From there, the differences usually include what version of Android you're using (Cupcake, Donut, Eclair, Froyo, etc.) and then what software packages are included.
"Sense UI", for example, is HTC's skin for the Android OS. "MotoBlur" is Motorola's skin, and Samsung has their own variant, as do others. This is a lot like customizing Windows; it'd be like changing the background, the system sounds, and the way Windows appear/look. Skinning is akin to theming. Attached is a picture example.
Note that different skins/themes sometimes include more than just visuals; Sense UI, for example, replaces the default MMS and Contacts applications with HTC's variants, as well as replacing the default system keyboard application. How much is customized is up to the manufacturer.
adeyo said:
I am interested in a future update to froyo 2.2 w/ its new features, removing a few stock sprint apks and mainly, replacing the painful htc sense with AOSP. I much prefer the new AOSP launcher and 3d app drawer. UNTIL THEN, i would probably just like to remove some apks and add in some that may not be allowed from sprint (google nav? usb tether? etc) and maybe disable sense (like above).
What do you recommend? Toast Root, unrevoked sticky apk? Should i wait to root altogether?? Do i need to avoid future OTA's etc? or would rooting now be the way to go to protect future root options?? i just don't know what to do!
Thanks for your thread! Can't wait to utilize the evo in all its glory!! My vogue just couldn't cut it anymore.
Click to expand...
Click to collapse
I'd suggest using Toast's method. The process is straightforward, and will allow you to achieve root access. From there, you can flash the ROM of your choice--be it Toast's Fr0y0 build, or an alternative ROM from another member. Toast also links to a Stock-ROM that's been modified for root access. This will give you the same experience as your phone was default, but with root access. This also means that you can uninstall certain applications, like Sprint TV, should you desire to do so.
However, you'll still be stuck using other Sense UI applications, like contacts and MMS, which I don't really care for. It's just life right now.
Froyo should (hypothetically) be made available soon, and then everyone with any iota of knowledge is going to be working frantically to build a full, feature-complete ROM with everything working (and then some), including tethering, HDMI out, full GPS/Wifi/Bluetooth/4G support, etc.
My recommendation? Root now using Toast's method, be wary (and read about) any updates before you perform them, and experiment with a few ROMs before Froyo is made available. Prep yourself now for Froyo and it'll be smooth sailing once it's available.

Nice thread
-------------------------------------
Sent from EVO

flipzmode?
Shidell said:
Toast also links to a Stock-ROM that's been modified for root access. This will give you the same experience as your phone was default, but with root access. This also means that you can uninstall certain applications, like Sprint TV, should you desire to do so...
However, you'll still be stuck using other Sense UI applications, like contacts and MMS, which I don't really care for. It's just life right now...
My recommendation? Root now using Toast's method...
Click to expand...
Click to collapse
1. So "toasts link stock rom", is that flipzmode's rom you are referring to? And that will give me the same exact experience as i have now, except for with root so if i want to modify SenseUI or some sprint apks i can? (i don't want anything to be removed or changed already, i just want to protect root for future when froyo comes out for our device with everything working).
2. and what does it mean when toast says: "you will need to wipe data and dalvic cache before flashing this." How do i do this?
Thanks!!

nand unlocking?
What is the significance of the nand unlocking? if we can already root, what extra does this allow us to do?

[Q] Flashing ROMs looks cool! But.. what about my carrier?

I'll get this out of the way first, I'm pretty new to rooting and flashing ROMs. The only thing I've ever rooted before was a free Kindle Fire I got from Amazon, and got some version of Android on it a looong time ago. Now I want to get LiquidSmooth on my Galaxy S3 i747. I'm completely willing to follow all noob guides by myself namely http://forum.xda-developers.com/showthread.php?t=1802160]this one.
HOWEVER, since this is a phone from AT&T with a data plan, texting, and calling, and not some free Kindle with none of that, I'm extremely paranoid to do anything risking losing all these features. There's really no clear indication anywhere that this will or won't happen, since I assume this is either just extremely common knowledge, and most trouble shooting is about screwing up in general or bricking.

Rooting and flashing doesn't affect any if those things.
Think of it as a new operating system for your computer. New look, new feel same basic functions.
Sent from my SGH-I747M using XDA Free mobile app

EGSuda said:
I'll get this out of the way first, I'm pretty new to rooting and flashing ROMs. The only thing I've ever rooted before was a free Kindle Fire I got from Amazon, and got some version of Android on it a looong time ago. Now I want to get LiquidSmooth on my Galaxy S3 i747. I'm completely willing to follow all noob guides by myself namely http://forum.xda-developers.com/showthread.php?t=1802160]this one.
HOWEVER, since this is a phone from AT&T with a data plan, texting, and calling, and not some free Kindle with none of that, I'm extremely paranoid to do anything risking losing all these features. There's really no clear indication anywhere that this will or won't happen, since I assume this is either just extremely common knowledge, and most trouble shooting is about screwing up in general or bricking.
Click to expand...
Click to collapse
I have the same phone and there are a few things that are good to know that will help you and possibly keep you from making a bad choice.
Have you accepted the 4.3 OTA update from AT&T on the unit or...? If you have, then you have upgraded to a specific bootloader/modem and can no longer downgrade those items without causing problems.
audit13 said:
If you took the 4.3 OTA AT&T ROM update, your phone has the 4.3 mjb bootloader.
To confirm which bootloader is on your phone, boot into download mode and let us know what it says on your screen.
Click to expand...
Click to collapse
If you did not take the update then you dont have these new items and your options are more open i guess.
First, your going to need to root your phone, without tripping the flash counter. There are lots of guides on how to do this, and it's pretty simple.
Secondly you will need to install a custom recovery such as ClockWorkMod or TWRP. I used CWM on my i747 and installed it using "ROM Manager" from the Play Store. It was amazingly simple and did the entire process for me.
Third you will need to choose the ROM you would like to try. There are a few different kinds, so happy hunting. I chose S3Rx and I love it. It's packed full of goodies and it seems that the Dev seems pretty good at answering any posts on his thread in this forum about the ROM.
Before you do any of that, you should verify what version your are running right now so you know what bootloader/modem you have, then go from there.
I just got back into this stuff myself and I love this phone. Good luck.

38589556 507
Ed Murray said:
I have the same phone and there are a few things that are good to know that will help you and possibly keep you from making a bad choice.
Have you accepted the 4.3 OTA update from AT&T on the unit or...? If you have, then you have upgraded to a specific bootloader/modem and can no longer downgrade those items without causing problems.
If you did not take the update then you dont have these new items and your options are more open i guess.
First, your going to need to root your phone, without tripping the flash counter. There are lots of guides on how to do this, and it's pretty simple.
Secondly you will need to install a custom recovery such as ClockWorkMod or TWRP. I used CWM on my i747 and installed it using "ROM Manager" from the Play Store. It was amazingly simple and did the entire process for me.
Third you will need to choose the ROM you would like to try. There are a few different kinds, so happy hunting. I chose S3Rx and I love it. It's packed full of goodies and it seems that the Dev seems pretty good at answering any posts on his thread in this forum about the ROM.
Before you do any of that, you should verify what version your are running right now so you know what bootloader/modem you have, then go from there.
I just got back into this stuff myself and I love this phone. Good luck.
Click to expand...
Click to collapse
I had already flashed my phone after getting the verification from the last user. I was running 4.3, and am now running LiquidSmooth 3.0 Kitkat 4.4.2 now, with pretty much no problems at all. But thank you for your help.

Questions regarding rooting.

I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 

Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.

Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.

Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.

Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.

You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu

Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.

The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app

Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt

Xposed for V500?

I'm trying to get Xposed on my shiny new(ish) V500.
I've tried installing Xposed on both CM12.1 as well as the pure build of AOSP Android 6.0, and keep getting a message that "xposed is not compatible with android SDK version 23 on your processor architecture..." (see screenshot for exact error).
Is Xposed not compatible with the device?
Am I missing something?
edit: terribly sorry, I was trying to install using an old apk file. Nevermind...

I'm far from an expert in Xposed as I've never felt the need to use it, however I did read about it when people were raving about it to see what it was all about.
As I understand it it is good for modifying stock firmware to tweak things to your liking, stock being what your device comes from the manufacturer with. We all know stock firmware doesn't have enough options so if you can't stand it you end up here on XDA.
Once here you have options, too many some might say.
Option 1
Go for a completely custom firmware. This will leave you with zero bloatware and a pretty clean state to start with, most of the custom firmwares - other than straight AOSP - come with more options to adjust them than most people know are there*.
This way isn't without it's drawbacks though, there may be bugs and some extra stuff from the stock firmware might not work. Infra-red and FM radios being the two which spring to mind, but even then sometimes they work too.
Option 2
Just get root access and modify the stock firmware with bonus tools made available as you've gained root access. This is things like custom recoveries letting you do full backups, the ability to backup app data through TB or something similar.
Then there is the thing you mentioned, Xposed.
This will let you do a lot of the stuff which a custom firmware would allow you to do all while keeping the stock firmware and the fancy additions your devices manufacturer might have added.
Option 3
Is a combination of the above.
The trouble with this option is that you're trying to do the same thing two different ways at the same time. You may have noticed that in many of the custom firmware threads the guys compiling them say not to report bugs if you're using Xposed, or straight up tell you not to use it.
This is because it will cause problems, not always and generally not with the well made modules, but problems arise and the people spending their free time to make custom firmware available don't want to waste their time trouble shooting a bug which was user created.
So you've chosen option 3 @dude101.
To make it do what you want you'll need to do lots of research, find the version which will work with what you want to use and then trouble shoot any problems you have.
Earlier you might have noticed the * in there. I did that as there are normally options to do what people want to do with Xposed but they haven't looked far/hard enough. If there isn't an option asking in the custom firmware thread about "how to achieve this effect" might lead to a solution. Be it someone pointing you at the option you've missed, or the person compiling the firmware to include it in the next build.

That version of xposed is for Kitkat.

Help with my note 4, downgraded, rooting, etc

I've been on this forum for roughly a week looking through articles and I'm seriously confused at this.
I have a Samsung Verizon note 4 on Lollipop
Baseband N910VVRU2BOG5
I'm trying to either downgrade it, root it, etc. Everything I've tried just sends me in circles. I get theres no perma-root method, but can I do anything at this point?

DikStarrbuck said:
I've been on this forum for roughly a week looking through articles and I'm seriously confused at this.
I have a Samsung Verizon note 4 on Lollipop
Baseband N910VVRU2BOG5
I'm trying to either downgrade it, root it, etc. Everything I've tried just sends me in circles. I get theres no perma-root method, but can I do anything at this point?
Click to expand...
Click to collapse
It depends on what you want to do, as there are ways around doing certain things that usually require a rooted device. For instance, if you want to back up your apps and their data, there's an app called Helium that works on non-rooted devices.

will4958 said:
It depends on what you want to do, as there are ways around doing certain things that usually require a rooted device. For instance, if you want to back up your apps and their data, there's an app called Helium that works on non-rooted devices.
Click to expand...
Click to collapse
Right now, what I really want to do is 'block' mock locations check. But I cannot figure out how to downgrade my phone, if its even possible. And I cant root my phone. I have tried Kingroot, but it said my phone wasnt rootable yet. But I read somewhere I can downgrade my phone to a rootable OS, but that didnt work either, so I dunno what I can do.

DikStarrbuck said:
Right now, what I really want to do is 'block' mock locations check. But I cannot figure out how to downgrade my phone, if its even possible. And I cant root my phone. I have tried Kingroot, but it said my phone wasnt rootable yet. But I read somewhere I can downgrade my phone to a rootable OS, but that didnt work either, so I dunno what I can do.
Click to expand...
Click to collapse
Unfortunately, unless you updated to a version of Lollipop using one of the safe update options mentioned in one of the threads, you can't downgrade to a previous version. There is a program called Debloater, I believe, that will block any app you want on your phone, but you still can't uninstall said app. All the program does is essentially disable the blocked app from running. For instance, when I didn't want my phone automatically checking for system updates, I would use Debloater to block the two apps on the phone that are required for it to perform those automatic checks. All you do is start Debloater on your computer, plug your phone into a USB port, set the phone to 'Media Device', and wait for the program to recognize the device. Once it does, just select the app(s) you want to block. Just out of curiosity, though, what version of Lollipop are you currently running? If you're on 5.0.1, I can understand why you don't want to stay there. I was on it for a little while, but only as a pit stop on my way to 5.1.1. I can say with assurance that after running my phone on 5.1.1 for at least a couple weeks or more, it runs very smoothly, even better than it did on 4.4.4, which was supposed to be better than 5.0.1 as far as performance goes. My battery lasts about as long as it did on Kit Kat, and I haven't experienced any crazy overheating issues.