Hi folks! Just received a 2013 Nexus 7 from my fiancé as a birthday gift. I wanted it for quite specific purposes so was hoping I could ask a few questions here and get pointed in the right direction before I start using this thing
I intend to mainly use the tablet for remote play with my PS4 and emulating old console games. Since I want to connect a PS4 controller to it wirelessly I'm told I need to root the device. I'm guessing this is an easy process and there are some guides on the site here?
The main thing I was after advice about is firmware updates. The system came on 4.3 and has already downloaded an update for 4.4.2 but I haven't installed that yet. Is this firmware fine to upgrade to? Any performance issues? I've heard people saying that upgrading their Nexus to 5+ (Lollipop?) has created a load of performance issues and this should be avoided? Also, if I upgrade to a certain firmware version can I lock myself out of being able to root the device? I'm pretty sure all of the apps I was planning on using work no 4.3 so I have no reason to upgrade at all but if I can go safely to a higher firmware that is reliable with no performance issues I may as well?
First time using an Android device so sorry if my questions come off as a little stupid. Also, wasn't sure if I should post this here or if it should be on the Q&A board so sorry if I've got that wrong!
As far as I know, the problems with lollipop were the standard number of complaints that come with any new release. Well, I'm not really positive, but lollipop seems fine to me and I think most people have upgraded by now. I would go for it because I think it's really fun to use.... Plus you can always revert if you choose.
As far as rooting, you never need to worry about not being able to do it... Rooting your Nexus 7 will always be easy. The by-hand method is fun and relatively simple, or you can just use the toolkit in the forum to do it even easier.
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Thanks for all the advice everyone
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
I'm fairly competent with computers (as I should be with a degree in computer science!) but this is all like a foreign language to me. I guess I'm better sticking with the toolkit for now until I'm familiar with all the lingo?
Masteryates said:
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Click to expand...
Click to collapse
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
chunk3rvd said:
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
Click to expand...
Click to collapse
If you unlock the bootloader then familiarise yourself with ADB and flashing factory images, you can manually flash any version of Android (That has been availible for your device,) manually. You dont need to be rooted to do this.
It also allows you to go back when you've made the mistake of updating, (but does wipe all of your data!)
It ended up offering me the updates incrementally anyway. I went from 4.3 > 4.4.2 > 4.4.3 > 4.4.4 which I'm currently on and will leave it there for now. It's downloaded 5.0.2 but I've skipped the install for the time being
Think I need to do a little reading up before I root the device as I haven't got a clue what some of you are talking about haha. Thanks for all the advice so far though
No problems.
I've had a few Nexus devices and never felt the need to root them. :angel:
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
The majority of problems stem from Qualcomms crappy broken mess Adreno gpu drivers, hence the delayed
rollouts of Android for the Nexus 4 and 7 that both use the Adreno 320, don't be suprised if the Nexus 4 and 7 get a
Android 5.1.1 release instead.
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
madbat99 said:
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
Click to expand...
Click to collapse
You for got to mention the disclaimer if your tab came with 5.x.x out of box you cant go back to KK. Also a lot of us who recently bought Nexus 7, I have 3 that I have acquired, came with 5.0.1 installed are having issues with partitions/memory mounting in recovery. Some sort of revision done in the latest batch sent out. If his tab came with 5.0.1 or higher and has his bootloader at FLO 4.04 he may have problems trying to go back with either bootloops and what not.
masterchiefb117 said:
... with 5.0.1 installed are having issues with partitions/memory mounting in recovery...
Click to expand...
Click to collapse
Seems to be solved in TWRP_multirom_(flo|deb)_20150328 (updated to 2.8.6.0)
See http://forum.xda-developers.com/showpost.php?p=45886569&postcount=1
Related
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
EDIT: Phones are brand new- they are STOCK. (Not rooted)
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well liked rom image for the S3 currently? (Stable)
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of what needs to be done, but rusty on the "particulars".
.
WeAreNotAlone said:
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well likely rom image for the S3 currently?
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of want needs to be done, but rusty on the "particulars".
.
Click to expand...
Click to collapse
Are you already rooted? If you update you could lose root I'm not really sure since I'm not on stock but it is easy to re-root it if you have too. And no updating wont permanently block your device from being rooted.
check out this thread: http://forum.xda-developers.com/showthread.php?t=1949687
it has all the official firmwares & pre-rooted official firmwares that are odin flashable
WeAreNotAlone said:
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well likely rom image for the S3 currently?
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of want needs to be done, but rusty on the "particulars".
.
Click to expand...
Click to collapse
These aren't like playbooks or ONE X's. We can flash firmwares and updates through Odin. You are safe bro
j_smith305 said:
Are you already rooted? If you update you could lose root I'm not really sure since I'm not on stock but it is easy to re-root it if you have too. And no updating wont permanently block your device from being rooted.
check out this thread: http://forum.xda-developers.com/showthread.php?t=1949687
it has all the official firmwares & pre-rooted official firmwares that are odin flashable
Click to expand...
Click to collapse
RE: Are you already rooted?
Nope, bone stock. Would like to run the units for about 30-days (Of course that may change, EG Sooner)
Appreciate the links, will check it out.
On a recommendation on a rom, Looking for rom with a high WAF. (Wife Approval Factor)
Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
Lakeshow423 said:
These aren't like playbooks or ONE X's. We can flash firmwares and updates through Odin. You are safe bro
Click to expand...
Click to collapse
Thank you,
After experiencing the "joy" of PlayBook #1 of #4 doing a forced update to a OS version which was not rootable, plus was non reversible wanted to get a feel on what was going on. In the end with the PlayBooks I have (1) unit left that I'm debating to root or not... REASON? There's like (1) person on the CrackBerry forums that has a in-depth knowledge of the QNX OS.... and the info on flashing a "rootable" version of the OS is not well documented. (Info is scattered amongst multiple threads- the (1) poster with a in-depth knowledge posts in a cryptic fashion.
Process seems pretty simple, but there is little "traffic" in the rooting section so that does not inspire confidence in getting answers to problems that may pop up after the "root".
From what I read BlackBerry /RIM closed the loophole that allowed the PB's to be rooted fairly quickly and numerically the numbers of persons who even have a "rooted" PlayBook is few and far between, VS those with Android powered devices. )
Getting back to the Samsung,
As noted above: Looking for rom with a high WAF. (Wife Approval Factor)
Stability is a factor, and "time" tweaking is at a premium.
What rom would you recommend?
PS: Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
(If tethering can be done without rooting, may leave the units stock for about 30-days or so until hardware is proven to be defect free. If you have any info on that, I'd be all ears.)
.
WeAreNotAlone said:
Thank you,
After experiencing the "joy" of PlayBook #1 of #4 doing a forced update to a OS version which was not rootable, plus was non reversible wanted to get a feel on what was going on. In the end with the PlayBooks I have (1) unit left that I'm debating to root or not... REASON? There's like (1) person on the CrackBerry forums that has a in-depth knowledge of the QNX OS.... and the info on flashing a "rootable" version of the OS is not well documented. (Info is scattered amongst multiple threads- the (1) poster with a in-depth knowledge posts in a cryptic fashion.
Process seems pretty simple, but there is little "traffic" in the rooting section so that does not inspire confidence in getting answers to problems that may pop up after the "root".
From what I read BlackBerry /RIM closed the loophole that allowed the PB's to be rooted fairly quickly and numerically the numbers of persons who even have a "rooted" PlayBook is few and far between, VS those with Android powered devices. )
Getting back to the Samsung,
As noted above: Looking for rom with a high WAF. (Wife Approval Factor)
Stability is a factor, and "time" tweaking is at a premium.
What rom would you recommend?
PS: Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
(If tethering can be done without rooting, may leave the units stock for about 30-days or so until hardware is proven to be defect free. If you have any info on that, I'd be all ears.)
.
Click to expand...
Click to collapse
If it's for your wife then I would probably stick with stock so she doesn't complain about minor bugs lol or you could try a touchwiz based rom. Just check out the different roms in the android development & original android development thread and see if you find any that you like
As for tethering I can't help you much since I don't really use it. I did a quick search and found this thread that might be able to help: http://forum.xda-developers.com/showthread.php?t=1988735
If you are wanting to root I would use the root injected rom. The instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1771687
This gives root but fully stock otherwise. It is probably one of the safest ways to root.
Sent from my SGH-T999 using xda app-developers app
ioitall said:
If you are wanting to root I would use the root injected rom. The instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1771687
This gives root but fully stock otherwise. It is probably one of the safest ways to root.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
That sounds exactly like what I, and others than are concerned about "warranty" issues on new phones- baring a total hardware failure would benefit from until the hardware is proven itself to be DEFECT FREE.
Would like to "burn-in" the device, making sure nothing is amiss.
Thanks!
mrRobinson said:
This is a completely stock ODIN flashable ROM with root injected into the system image.
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
Click to expand...
Click to collapse
For a few months or so I've been running my tablet on the 4.2.2 update and have had the device rooted and never really took advantage of said rooting and so decided to undo it.
Just to check I downloaded Root Checker to verify root was undone and it says that it has, including apps that needed root access no longer work, however there are some small issues that struck me as odd; 1. When going into fastboot mode it still says that it's unlocked, unless that's referring to the bootloader which is still unlocked, 2. I still have custom recovery installed unless that's an issue in which I can undo if need be, 3. Whenever attempting to apply the 4.3 update it reboots my device as it says it will, but upon getting to the google splash screen it goes right into custom recovery when it attempts to apply the update but suddenly goes to the custom recovery main menu without applying the update.
And finally when going back to my settings and it says my system is up to date.
So is there a step that I missed in unrooting my tablet? If so please let me know, I'd like to update to 4.3 as soon as possible and take advantage of it's new features.
Namely the Open GSL 3.0 has me intrigued.
You have the old nexus 7 tab. This is the forum for the new one. The new one launched on 4.3 and I think the old one is in the process of otas.
And for any device you need stock recovery to take an ota. Any further questions need to be addressed in the proper forum.
Sent from my Nexus 7 using Tapatalk 4 Beta
tiny4579 said:
You have the old nexus 7 tab. This is the forum for the new one. The new one launched on 4.3 and I think the old one is in the process of otas.
And for any device you need stock recovery to take an ota. Any further questions need to be addressed in the proper forum.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks I guess? I must have misunderstood, when I clicked the forum link I didn't see anything distinguishing it from the old one to the new one.
Besides the 2013 part?
khaytsus said:
Besides the 2013 part?
Click to expand...
Click to collapse
Well at the time I didn't think anything of it and assumed it was the same forum as before and didn't bother to look as I rarely did before.
So, the other day I got the 5.0 OTA on my rooted 4.4.2, and I naively updated it, without knowing that:
1 - I'd loose root and my recovery
2 - There's no way to root 5.0
After two days of trying stuff, I finally understood what many people know, I suppose, but I couldn't see it written clearly anywhere, so I thought I'd share. You have to:
1 - Flash back 4.4.2
2 - Root 4.4.2
3 - Flash a custom recovery
4 - Flash a rooted 5.0 from custom recovery
I now have a rooted 5.0
Here. It's not very complicated to do, but maybe it's so obvious for people who know it that they never care to put it like this (I'm not complaining, I actually did find all the information I needed on XDA and learned a good deal of things about my phone on the way so it's cool).
You cant.
DelBoy said:
You cant.
Click to expand...
Click to collapse
Sorry I lack experience so much with the forum that I posted without any content initially so you must have thought that I was asking for the solution. I get that you can't simply root 5.0, but you can actually get 5.0 rooted if your phone has 5.0 non rooted by switching to 4.4.2 first, which is really what people want to do when they ask that question. I have seen your answer before, and almost gave up trying, but I'm glad I insisted. Just saying "you can't" is just being deliberately unhelpful (or not knowing what you are talking about).
GordonFreemanK said:
Sorry I lack experience so much with the forum that I posted without any content initially so you must have thought that I was asking for the solution. I get that you can't simply root 5.0, but you can actually get 5.0 rooted if your phone has 5.0 non rooted by switching to 4.4.2 first, which is really what people want to do when they ask that question. I have seen your answer before, and almost gave up trying, but I'm glad I insisted. Just saying "you can't" is just being deliberately unhelpful (or not knowing what you are talking about).
Click to expand...
Click to collapse
Yeah, there was only name of the thread and word "So"
So I thought you were looking for solution :laugh:
Some more information on how to get there:
To get 5.0 rooted, you need to:
- take note of which 5.0 version you have on your phone and check you can get the bumped image somewhere, if you want to have exactly the same at the end.
- update LG PC Suite or at least the Windows drivers for the G3? Honestly I'm not sure how important this is, since I was playing around for hours and I did that in the process, maybe it's necessary. It is necessary to have the drivers installed at least.
- find the 4.4.2 version of the ROM for your phone (mine was V10e-EUR-XX), versions are different for 16GB/32GB versions.
- flash it with Flashtool (http://forum.xda-developers.com/showthread.php?t=2785089)
- root using your favourite tool (I used one I had on my PC, not sure which version but PurpleDrake should do: http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000)
- find a TWRP image
- flash TWRP (I used this tutorial: http://www.phonearena.com/news/How-to-flash-a-custom-recovery-like-CWM-or-TWRP-on-Android_id53914)
- find the bumped version of 5.0 for your phone (mine is V20e-EUR-XX and I found it on this forum)
- flash it using TWRP
- start the phone and set it up (it should be rooted already)
- install the SuperSU binaries using TWRP
Fun and heavy Titanium Backup freezes ensue! My phone has now 80% battery left 8h after being disconnected from the charger this morning, as opposed to 60% after two hours just after installing the OTA update.
Note: this was done on the unlocked 16GB European D855 version I bought in the UK. Not sure about other versions!
Bonus: in order to improve my battery life, besides Titanium-Backup-freezing the hell of the LG bloatware (I think McAfee and LG Health are the main culprits) and some Google bloatware I don't use (Google Play Apps anyone?) I also disabled knock on by following the advice #8 in this tutorial: http://www.androidauthority.com/lg-g3-problems-517832/
I've read all about the problem with rooting the G3 Stock Lollipop Version.
But there is no info, where I can find out WHY it is how it is.
So, why is 5.0 actually unrootable? And will this change in future?
SlideMouse22 said:
I've read all about the problem with rooting the G3 Stock Lollipop Version.
But there is no info, where I can find out WHY it is how it is.
So, why is 5.0 actually unrootable? And will this change in future?
Click to expand...
Click to collapse
Ummm. Have you tried looking on XDA?
There was a BIG post with details. The technical part is here: link
No, this won't change. Restricting services to their context means that bug in almost any service won't be able to compromise entire system. That's a great security feature, actually.
Newbie but ive been lurking here since the evo4g days always glad there are updates for anyone to follow. lately i havent come up with one for my note 4, can anyone help me on this matter? atm its rooted 4.4.4 knox has been tripped and if it helps SM-N910P. tried searching for youtube, google, and throughout different threads. i connected my phone to smart switch pc samsung program and it detects an update for it but im too scared it will brick it if i go on that route. Many thanks in advance
xxSEIYAxx said:
Newbie but ive been lurking here since the evo4g days always glad there are updates for anyone to follow. lately i havent come up with one for my note 4, can anyone help me on this matter? atm its rooted 4.4.4 knox has been tripped and if it helps SM-N910P. tried searching for youtube, google, and throughout different threads. i connected my phone to smart switch pc samsung program and it detects an update for it but im too scared it will brick it if i go on that route. Many thanks in advance
Click to expand...
Click to collapse
oops forgot to post, i would like to keep it rooted since i use my sd card a whole bunch. saw that since jelly bean not just any app can use sd card to read write info.
xxSEIYAxx said:
oops forgot to post, i would like to keep it rooted since i use my sd card a whole bunch. saw that since jelly bean not just any app can use sd card to read write info.
Click to expand...
Click to collapse
Ok, pretty easy.
First you have to get your phones partitions right for 5.1.1.
To do it go to this link:
http://forum.xda-developers.com/showthread.php?t=3252903
and follow the op carefully.
The instructions written in red a couple paragraphs down in the the thread has the link you need to get your phone to 5.1.1.
After that you can flash any rom in this forum you'd like.
Good luck and don't forget to give @tx_dbs_tx a big thanks (and any thing else you'd like) for the commitment and hard work he has done for us all.
jhill110 said:
Ok, pretty easy.
First you have to get your phones partitions right for 5.1.1.
To do it go to this link:
http://forum.xda-developers.com/showthread.php?t=3252903
and follow the op carefully.
The instructions written in red a couple paragraphs down in the the thread has the link you need to get your phone to 5.1.1.
After that you can flash any rom in this forum you'd like.
Good luck and don't forget to give @tx_dbs_tx a big thanks (and any thing else you'd like) for the commitment and hard work he has done for us all.
Click to expand...
Click to collapse
thanks so much, i might have messed up i pull up supersu and it tells me "there is no su binary installed and supersu cannot install it. this is a problem!" - i dont know if i really need this, i mainly rooted jelly bean note 4 to get sd card access on my 3rd party apps and it works as is right now
also it keeps bugging me if i want to install a 150.16MB update N910PVPS4COK1/N910PSPT4COK1/N910PVPS4COK1 - should i just go ahead and install it?
other than that everything seems to be working, faster and better than before.
xxSEIYAxx said:
thanks so much, i might have messed up i pull up supersu and it tells me "there is no su binary installed and supersu cannot install it. this is a problem!" - i dont know if i really need this, i mainly rooted jelly bean note 4 to get sd card access on my 3rd party apps and it works as is right now
also it keeps bugging me if i want to install a 150.16MB update N910PVPS4COK1/N910PSPT4COK1/N910PVPS4COK1 - should i just go ahead and install it?
other than that everything seems to be working, faster and better than before.
Click to expand...
Click to collapse
First of, don't take the ota just yet. Wait for comments about it first. If your on a custom rom you shouldn't be getting that update notification.
Which rom are you on when you get the SuperSU message?
If you are now up to 5.1.1 and flashed a custom rom you don't need to root.
Explain a little what you did to see if the issue can be sniffed out.
jhill110 said:
First of, don't take the ota just yet. Wait for comments about it first. If your on a custom rom you shouldn't be getting that update notification.
Which rom are you on when you get the SuperSU message?
If you are now up to 5.1.1 and flashed a custom rom you don't need to root.
Explain a little what you did to see if the issue can be sniffed out.
Click to expand...
Click to collapse
Yeah i followed the instructions in full of the thread you connected me to. im on 5.1.1 stock, i flashed the odexed version tx_dbs_tx placed on there.
i dont really flash any other rom in there that isnt stock since i know most have issues recognizing the spen
if it helps software version im on is N910PVPU4COJ6
hardware version N910P.05
the supersu message i mentioned earlier only appears if i hit the supsu app
xxSEIYAxx said:
Yeah i followed the instructions in full of the thread you connected me to. im on 5.1.1 stock, i flashed the odexed version tx_dbs_tx placed on there.
i dont really flash any other rom in there that isnt stock since i know most have issues recognizing the spen
if it helps software version im on is N910PVPU4COJ6
hardware version N910P.05
the supersu message i mentioned earlier only appears if i hit the supsu app
Click to expand...
Click to collapse
for the full steps on what i did is
Odin flash the stock OJ6 rom tar using odin on your PC. on that step it took forever it build the library and then i just made sure i was able to connect to usb for the next step.
i went ahead and placed the downloaded sprint stock rom onto my external
went to the recovery mode i wiped my internal 3 times
then i hit the apply update on external i believe is the option i chose (the way he explained on the thread was way different from what i had, i mean the wording). i selected the sprint stock and it hung up for a while on the sprint spark, built library again and phone was as if it was brand new asking me to signin google.
it downloaded all my previous apps even the sprint crap ( i was able to uninstall those) other than updating the apps and messing around w them i really havent done much else. bluetooth works as well as texting and calls, wifi too
Well, you can be sure if @tx_dbs_tx released a rom it's darn near perfect. His roms come prerooted.
If you are still having supersu issues do a wipe and install any of his roms. They don't have issues... I've been using his roms for over a year and have found problems are usually user created.
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
nubry said:
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
Click to expand...
Click to collapse
I don't think it will work because Samsung has anti rollback in its phones which prevents the bootloader from being downgraded. However, a system and boot flash might work. I don't know about the modem though.
Samsung is one of the few brands that implement it.
I don't really see the use though as it is quite possible to bootloop and if done incorrectly, could result in a hard brick.
nubry said:
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
Click to expand...
Click to collapse
Quick question...
Why would you want to?
I did this with my old Moto X Play and bricked it
iloveoreos said:
I don't think it will work because Samsung has anti rollback in its phones which prevents the bootloader from being downgraded. However, a system and boot flash might work. I don't know about the modem though.
Samsung is one of the few brands that implement it.
I don't really see the use though as it is quite possible to bootloop and if done incorrectly, could result in a hard brick.
Click to expand...
Click to collapse
that is what I thought... I think the only real solution would be to find a custom Rom of the Stock 6.0 but untouched. It would not need the bootloader to be downgraded would it?
I really like samsung phones but I hate the way the treat costumers, it feels like being fooled.
Thank you for your reply though !
moozer said:
Quick question...
Why would you want to?
I did this with my old Moto X Play and bricked it
Click to expand...
Click to collapse
When I bought my Moto g 2015 it was very fast and that was surprising. All the updates started to drain the battery and make the device work slower . I tried almost all the custom Rom possible and after flashing back the stock 5.1 out of the box version I have to admit they wanted the device to become slow with all the updates.
Now when I received my A5 it was already running nougat. I think the best you can get from your phone is with the outbox version because everything is planned to be running perfectly so people buy it. For me even though it brings new features and stuff, update wont get you device any better.
So ya that's the reason I'd like to downgrade.
nubry said:
that is what I thought... I think the only real solution would be to find a custom Rom of the Stock 6.0 but untouched. It would not need the bootloader to be downgraded would it?
I really like samsung phones but I hate the way the treat costumers, it feels like being fooled.
Thank you for your reply though !
Click to expand...
Click to collapse
You could extract the system and boot out of the stock firmware, but I don't know if it's worth the risk.
nubry said:
When I bought my Moto g 2015 it was very fast and that was surprising. All the updates started to drain the battery and make the device work slower . I tried almost all the custom Rom possible and after flashing back the stock 5.1 out of the box version I have to admit they wanted the device to become slow with all the updates.
Now when I received my A5 it was already running nougat. I think the best you can get from your phone is with the outbox version because everything is planned to be running perfectly so people buy it. For me even though it brings new features and stuff, update wont get you device any better.
So ya that's the reason I'd like to downgrade.
Click to expand...
Click to collapse
Motorola got in trouble for that. Others too. It's illegal now, so you should leave out that theory.
I've had only positive experiences with my last 5 smartphones. Upgrading does precisely that...makes it better. An OEM would not produce an upgrade without testing it. That's why we had a better experience with Nougat and even better with Oreo.
What do you do differently with Oreo than you did with Nougat?