Related
Hi all,
Long time reader, first time poster.
Please don't kill me if my questions are somehow dumb. I promise I searched the web and xda thouroughly before posting.
1) I rooted my phone with HTCDev.com for the sole purpose of installing titanium backup. I tried to unintall some unwanted bloatware (scribble, tv, twitter, zoe, fitbit and more...) but they keep returning after boot. Why is that? Is it related to S-on? Is there a simple way to fix this?
2) My current software version is 1.54.707.7, I can update OTA to 2.22.707.3. Should I? From my experience with my previous samsung device, I'm afraid that updating blindly can cause more harm than good at some cases.
3) Can I update OTA even when I'm rooted? Will I need to replace the recovery and root again?
Thanks in advance,
Tal
talla1 said:
Hi all,
Long time reader, first time poster.
Please don't kill me if my questions are somehow dumb. I promise I searched the web and xda thouroughly before posting.
1) I rooted my phone with HTCDev.com for the sole purpose of installing titanium backup. I tried to unintall some unwanted bloatware (scribble, tv, twitter, zoe, fitbit and more...) but they keep returning after boot. Why is that? Is it related to S-on? Is there a simple way to fix this?
2) My current software version is 1.54.707.7, I can update OTA to 2.22.707.3. Should I? From my experience with my previous samsung device, I'm afraid that updating blindly can cause more harm than good at some cases.
3) Can I update OTA even when I'm rooted? Will I need to replace the recovery and root again?
Thanks in advance,
Tal
Click to expand...
Click to collapse
Hi Tal,
ok let's see if I can help you a little bit.
Regarding (1) I got a question: where and which files of the named apps did you delete?
Regarding (2) Sure you could update vis OTA as long as all system apps and stock recovery ist installed. Did you reinstall stock recovery, or are you unsing some custom recovery? As with custom recovery you can download but not install the OTA. This can then be done even if you are rooted. If you use supersu having the pro version installed you could try activating OTA survival mode and maybe root acces will still be there after performing the OTA. If not you could simply reinstall a custom recovery and using this root.
Hope this helps!?
If you could give me some answers regarding (1) I'll try to help ypu with this as well.
HTCNerdYoda said:
Hi Tal,
ok let's see if I can help you a little bit.
Regarding (1) I got a question: where and which files of the named apps did you delete?
Regarding (2) Sure you could update vis OTA as long as all system apps and stock recovery ist installed. Did you reinstall stock recovery, or are you unsing some custom recovery? As with custom recovery you can download but not install the OTA. This can then be done even if you are rooted. If you use supersu having the pro version installed you could try activating OTA survival mode and maybe root acces will still be there after performing the OTA. If not you could simply reinstall a custom recovery and using this root.
Hope this helps!?
If you could give me some answers regarding (1) I'll try to help ypu with this as well.
Click to expand...
Click to collapse
Thanks for the detailed and fast response, Yoda!
Regarding (1), I'm not sure I understand what you mean "where and which files". I backed up the mentioned apps in titanium backup, and then uninstalled them, again, with titanium backup. This method worked for me on my previous device (Samsung i9300).
Regarding (2), that's valuable information that I did not get anywhere from reading the sticky posts. I didn't know that the original recovery is needed in order to update OTA. I installed TWRP in order to install SuperSU. Is there a specific version of stock recovery that goes with the device? Or is there just one stock recovery for m8?
I had another question hidden in there, I'll make it number 3:
(3) Can someone tell me if the 2.22.707.3 version is any good? Stable enough? Or should I stick with 1.54.707.7 in the meanwhile?
Thanks allot!
Tal
talla1 said:
Thanks for the detailed and fast response, Yoda!
Regarding (1), I'm not sure I understand what you mean "where and which files". I backed up the mentioned apps in titanium backup, and then uninstalled them, again, with titanium backup. This method worked for me on my previous device (Samsung i9300).
Regarding (2), that's valuable information that I did not get anywhere from reading the sticky posts. I didn't know that the original recovery is needed in order to update OTA. I installed TWRP in order to install SuperSU. Is there a specific version of stock recovery that goes with the device? Or is there just one stock recovery for m8?
I had another question hidden in there, I'll make it number 3:
(3) Can someone tell me if the 2.22.707.3 version is any good? Stable enough? Or should I stick with 1.54.707.7 in the meanwhile?
Click to expand...
Click to collapse
(1) there are two folder /system/app and /system/priv-app. And overall there is the rw settings of the new kernel used. To be abled to unistall unwanted system apps maybe take a look at this post: http://forum.xda-developers.com/showthread.php?t=2723463, as maybe you need another kernel to accomplish it.
(2) you have to use a corresponding recovery, meaning you would have to download the 1.54.707.7 recovery (just google for it and you should find it in any forum) to work.
(3) I'm sorry that I can't be of any help here, as I performed an S-OFF debranding my phone and changin the CID to HTC__102 right from the start, setting it up to be on the WWE 2.22.401.4 since then.
3) the newest update (2.22 one) is very stable for me, no problems at all.
Sent from my One M8 using XDA Free mobile app
Thanks for this information!
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Thanks for this information!
Click to expand...
Click to collapse
1) HTCDev unlocks the boot loader, it doesn't root. This can delete some default system apps, preventing an OTA. In order to have changes to system stick after reboot you need a kernel module: http://forum.xda-developers.com/showthread.php?p=51543139
2) Don't worry, HTC are much better with updates than Samsung. They work, you can trust them.
3) Once you have unlocked boot loader, you may struggle to update OTA due to the missing apps, but there are threads here explaining what to do. As mentioned, you'll need stock recovery and yes, you may need to root again, after installing your custom recovery after the update.
BenPope said:
1) HTCDev unlocks the boot loader, it doesn't root. This can delete some default system apps, preventing an OTA. In order to have changes to system stick after reboot you need a kernel module: http://forum.xda-developers.com/showthread.php?p=51543139
2) Don't worry, HTC are much better with updates than Samsung. They work, you can trust them.
3) Once you have unlocked boot loader, you may struggle to update OTA due to the missing apps, but there are threads here explaining what to do. As mentioned, you'll need stock recovery and yes, you may need to root again, after installing your custom recovery after the update.
Click to expand...
Click to collapse
Thanks for all the valuable info!!
I tried searching for the recovery, but as always, it's not that simple.. Too many sources of information and I don't know who's genuine. I haven't found a link on XDA yet (to the full stock ROM yes, not for the recovery only).
You say that OTA is a hassle when the recovery is replaced. I'm not stressed on upgrading OTA. How WOULD YOU SUGGEST to upgrade? Downloading the newest stock from XDA and using fastboot?
I created nandroid backups before but never restored one, so JUST TO BE SURE: this backup will be the full snapshot? Meaning: my old version (if the new one sucks) + apps + data? I don't need to backup ANYTHING except doing a nandroid backup?
Thanks again.
Tal
UPDATE: dug around some more and found the stock recoveries here after following the link from this post.
But before I flash anything, I just want to make sure that:
1) The nandroid I'll do in TWRP is the only backup I need to do.
2) There is no simpler option than returning to stock recovery, updating OTA, returning to TWRP recovery, rooting.
Tal
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G
I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512
OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..
Hi all, please correct me if I placed this at the wrong thread.
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it?
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so?
Can I flash back a lower version of ROM? For instance, 1.54.707.7
Thanks for helping in advance!
My responses below, in red font:
jkidz91 said:
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it? Totally normal, no need to worry.
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so? This is usually due to using an older version of TWRP (known bug). This number is useful for determining your current firmware version (hboot, radio, etc.) but you can also determine that by looking at the hboot number and radio numbers themselves
Can I flash back a lower version of ROM? For instance, 1.54.707.7 Yes. Usually, you want the ROM version (1.x, 2.x etc.) to correspond to your current firmware. But its usually been found that a higher number firmware will usually work with older (smaller number) ROMs
Click to expand...
Click to collapse
redpoint73 said:
My responses below, in red font:
Click to expand...
Click to collapse
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
jkidz91 said:
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
Click to expand...
Click to collapse
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
redpoint73 said:
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
Click to expand...
Click to collapse
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
jkidz91 said:
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
Click to expand...
Click to collapse
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
redpoint73 said:
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
Click to expand...
Click to collapse
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
jkidz91 said:
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
Click to expand...
Click to collapse
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
redpoint73 said:
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
Click to expand...
Click to collapse
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
jkidz91 said:
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave
Click to expand...
Click to collapse
Meaning you updated by RUU?
jkidz91 said:
as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
Click to expand...
Click to collapse
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
redpoint73 said:
Meaning you updated by RUU?
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
Click to expand...
Click to collapse
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
jkidz91 said:
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
Click to expand...
Click to collapse
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
redpoint73 said:
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
Click to expand...
Click to collapse
I need the Titanium backup to recover my apps and data ><
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
About the stock recovery, I am fully aware of this
I am really sorry if I keep causing trouble to you...I just want to double confirm...I have spent few days just to get my phone for working right...really exhausting to the mind ><
jkidz91 said:
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
Click to expand...
Click to collapse
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
jkidz91 said:
I am really sorry if I keep causing trouble to you...
Click to expand...
Click to collapse
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
redpoint73 said:
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
redpoint73 said:
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
jkidz91 said:
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
Click to expand...
Click to collapse
If the intent was to just backup a "stock ROM" than no need to backup user data.
If the intent is to make a recovery image, that you can just revert to and start using with no (or very little other actions) than backup data. But as you said, you can restore data (at least app data) with Titanium.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
jkidz91 said:
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
Click to expand...
Click to collapse
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
redpoint73 said:
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
Click to expand...
Click to collapse
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
jkidz91 said:
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
Click to expand...
Click to collapse
You can run the RUU until the cows come home, if you want.
redpoint73 said:
You can run the RUU until the cows come home, if you want.
Click to expand...
Click to collapse
What does that mean? >< i tried to do it...it failed...should I just download a stock 4.19.707.2 rom and flash it?
Guys, I got the notification to update my ZE551ML to WW_2.20.40.59_20150807_7712_user_rel. Problem is, I already rooted and uninstalled many bloatware. Fortunately though, I've backed up all the bloatware before I uninstalled them with Titanium Backup. Will I be able to update my phone if I were to restore all of the original apps? And do I need to remove root/and or Xposed completely or do I just turn off root via SuperSU? Thanks in advance.
PS: I've tried updating the update directly prior to WW_2.20.40.59_20150807_7712_user_rel and it failed. I didn't restore any bloatware last time though. And I have NOTHING to do with any boot loader because I don't understand any of it. Please give me step by step to successfully update my phone (preferably without OTA).
I have the same question please help me
Sent from my ASUS_Z00AD using XDA Free mobile app
1st you need unroot.
2nd uninstall exposed.
3rd restore all system apps.
Update your device.
mr_gourav2000 said:
1st you need unroot.
2nd uninstall exposed.
3rd restore all system apps.
Update your device.
Click to expand...
Click to collapse
Or flash the pre-rooted rom using fastboot, re-install xposed and again freeze unwanted apps...
ultramag69 said:
Or flash the pre-rooted rom using fastboot, re-install xposed and again freeze unwanted apps...
Click to expand...
Click to collapse
:good:
BTW downloading ROM about 1 GB is not good idea.
mr_gourav2000 said:
:good:
BTW downloading ROM about 1 GB is not good idea.
Click to expand...
Click to collapse
Always worked for me...
Good idea to check MD5 sum if you can, unless you like to live life on the edge or just can't wait that extra minute or so (like me)....
ultramag69 said:
Always worked for me...
Good idea to check MD5 sum if you can, unless you like to live life on the edge or just can't wait that extra minute or so (like me)....
Click to expand...
Click to collapse
Better idea, TWRP backup before doing anything.
Easiest way?
Apply pre rooted image, you will not loose your setting or need unfreeze or reinstall bloatwear, just will need reinstal busybox and Xposed framework and update superSU. This is the fast way, Xposed will also wipe cache so phone will run smothie.
mr_gourav2000 said:
Better idea, TWRP backup before doing anything.
Click to expand...
Click to collapse
Yeah, but it takes so long.... And not everyone had the forethought to unlock their bootloader. Though I suppose you could still do it with the untethered TWRP too...
Ginuz said:
Easiest way?
Apply pre rooted image, you will not loose your setting or need unfreeze or reinstall bloatwear, just will need reinstal busybox and Xposed framework and update superSU. This is the fast way, Xposed will also wipe cache so phone will run smothie.
Click to expand...
Click to collapse
As I said a few posts back...
Ginuz said:
Easiest way?
Apply pre rooted image, you will not loose your setting or need unfreeze or reinstall bloatwear, just will need reinstal busybox and Xposed framework and update superSU. This is the fast way, Xposed will also wipe cache so phone will run smothie.
Click to expand...
Click to collapse
Can someone please give me a clear step by step (like 1, 2, 3 lol) of how to do this and which and where to download the files I need? Sorry, I'm fairly new at this. Thank you for replies.
gmahadhika91 said:
Can someone please give me a clear step by step (like 1, 2, 3 lol) of how to do this and which and where to download the files I need? Sorry, I'm fairly new at this. Thank you for replies.
Click to expand...
Click to collapse
yes i would like to know the same thing. downloaded prerooted image, but fear to do something wrong. now new version out already again and i still not updated. can somebody please help with a nice and simple guide? 1000000x thx in advance
files i downloaded are:
system.img
boot.img
droidboot.img
recovery.img
so now?
fastboot flashall??
would be really happy to get some help here... don't wanna brick my phone....
hi guys, new to asus zenfone 2 ze551ml, indian version, just looking around and found that my device is already rooted, is it possible? installed titanium backup root and it works fine...confused :S
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-developer-os-images
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Hi there,
my shield is on stock now with several apps on it.
How can I flash without losing my data? Is it enough to NOT flash the userdata?
THX
Chaos
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
BillTheCat said:
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
I have a question, where do you find pre-root load in below link?
I only find Open source and recovery image.
you mean to modify Open source and build pre-root load?
https://developer.nvidia.com/shield-open-source
https://developer.nvidia.com/shield-developer-os-images
BillTheCat said:
https://developer.nvidia.com/shield-developer-os-images
Click to expand...
Click to collapse
thanks
hardwarechaos said:
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
Click to expand...
Click to collapse
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
hardwarechaos said:
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image
Click to expand...
Click to collapse
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Hi
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
IMHO if you have adb root there should be a way to install it via adb too, but I could not find one and didn't want to mess around with installing the SuperSU files manually.
THX
Chaos
hardwarechaos said:
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
Click to expand...
Click to collapse
Agreed - turns out the Dev images are no real benefit. I found that installing TWRP, rebooting the bootloader, entering recovery and then flashing SuperSU works like a champ.
Anyone else having trouble flashing system and userdata? Keeps saying FAILED (Remote: data too large)
BillTheCat said:
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Click to expand...
Click to collapse
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
jweaks said:
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
Click to expand...
Click to collapse
Yes it will kill amazon video.
BillTheCat said:
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Click to expand...
Click to collapse
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
dillfever said:
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
Click to expand...
Click to collapse
can close this got er all done.......dill
hardwarechaos said:
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
Click to expand...
Click to collapse
Hello,
Same result for me.
I've just received my Shield, I've followed the instructions given on the developers web page. I have an up-to-date 3.0.0 version, but applications don't have the root authorisations (tested with ES File Explorer).
I think I'll use the TWRP method...
i download 3.0 rooted version it came a zip with all files on it on nvidia shield.com tutorial said just ento bootloader and type comand flash-all.bat and gualahhh! but try like 1000 times and always said null error message and force close adb
can some one tell what im doing wrong please and thanks people!
bye the way gamestop its selling shield tv for 100bucks so for those who want another its the right time to get one
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
dismissthesky said:
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
Click to expand...
Click to collapse
to remove zulu rom this is easy.
just go to nvidia site and get the complete factory images for your shield.
it will come with a guide on how to flash your shield with them.
it will delete everything in your shield and it will be stock like brand new.
then you can root it if you want or install a different rom.