Related
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.
Hello all,
I'm new to Xperia L but not to rooting. I rooted my own HTC sensation and I'm planning to do the same to the Xperia to fix a not working camera and insane battery drain. On the HTC, I needed to flash a custom recovery, update bootloader, update radio before I could install a custom ROM.
Do I need to repeat the same procedure with the XPL? Or just unlock bootloader -> flash ROM done (which is what I'm getting from going through these forums)?
onemanshow85 said:
Hello all,
I'm new to Xperia L but not to rooting. I rooted my own HTC sensation and I'm planning to do the same to the Xperia to fix a not working camera and insane battery drain. On the HTC, I needed to flash a custom recovery, update bootloader, update radio before I could install a custom ROM.
Do I need to repeat the same procedure with the XPL? Or just unlock bootloader -> flash ROM done (which is what I'm getting from going through these forums)?
Click to expand...
Click to collapse
Yep !! Kk roms n many jb roms r pre-rooted..if u dont need backup n stuff then no need to root..unlock bootloader..wic clears internal storage..so unlock>flash kk kernel>rom
Hit thanks if i helped
Rohan purohit said:
Yep !! Kk roms n many jb roms r pre-rooted..if u dont need backup n stuff then no need to root..unlock bootloader..wic clears internal storage..so unlock>flash kk kernel>rom
Hit thanks if i helped
Click to expand...
Click to collapse
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
onemanshow85 said:
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
Click to expand...
Click to collapse
I have a 3rd n better option , u can backup everything before unlock as it erases apps n internal sd..so fo this
1)root n thn titanium backup 2)cwm on locked (go to original development) recovery instaler tool
3)nandroid backup
4)unlock
5)flash custom rom..wicever ..just u cnt flash kk rom frm jb recovery
---------- Post added at 07:56 PM ---------- Previous post was at 07:53 PM ----------
onemanshow85 said:
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
Click to expand...
Click to collapse
I have a 3rd n better option , u can backup everything before unlock as it erases apps n internal sd..so fo this
1)root n thn titanium backup 2)cwm on locked (go to original development) recovery instaler tool
3)nandroid backup
4)unlock
5)flash custom rom..wicever ..just u cnt flash kk rom frm jb recovery
N if u go with ur 2nd option there wont be anything to backup after unlocking..so u cwm on locked bootloader by tht tool
---------- Post added at 07:59 PM ---------- Previous post was at 07:56 PM ----------
onemanshow85 said:
thanks
the way I see it now is 2 options:
- first root, and make a TA backuo
or
- unlock, flash recovery (CWM from what I've gathered), flash kernel/ROM.
correct?
Can I backup the stock ROM in CWM if I choose to follow the second option?
Click to expand...
Click to collapse
Rohan purohit said:
I have a 3rd n better option , u can backup everything before unlock as it erases apps n internal sd..so fo this
1)root n thn titanium backup 2)cwm on locked (go to original development) recovery instaler tool
3)nandroid backup
4)unlock
5)flash custom rom..wicever ..just u cnt flash kk rom frm jb recovery
N if u go with ur 2nd option there wont be anything to backup after unlocking..so u cwm on locked bootloader by tht tool
Click to expand...
Click to collapse
I like that option.
Problem is I can't get this thing rooted, I tried Doomlord Rootkit and the motochopper root method (untill I found out it won't work on 4.2.2)
I know I could just unlock and flash a custom ROM/kernel, but I really want to backup with TA before unlocking (not my own phone) and for that I need full root first.
onemanshow85 said:
I like that option.
Problem is I can't get this thing rooted, I tried Doomlord Rootkit and the motochopper root method (untill I found out it won't work on 4.2.2)
I know I could just unlock and flash a custom ROM/kernel, but I really want to backup with TA before unlocking (not my own phone) and for that I need full root first.
Click to expand...
Click to collapse
There's rooting kit in the general section that works on 4.2.2. Backing up TA partition is always a good idea. I would suggest you to take a full nandroid backup AFTER flashing a custom kernel. There's no need for titanium backup too (I don't understand why the above post mentions that). Now that you have a working recovery and backup, proceed with flashing your rom.
Hope it helps
Hit thanks if it does.
abhi007.john said:
There's rooting kit in the general section that works on 4.2.2. Backing up TA partition is always a good idea. I would suggest you to take a full nandroid backup AFTER flashing a custom kernel. There's no need for titanium backup too (I don't understand why the above post mentions that). Now that you have a working recovery and backup, proceed with flashing your rom.
Hope it helps
Hit thanks if it does.
Click to expand...
Click to collapse
thanks, I managed to get it rooted, TA backup, bootloader unlock and flashed a stock FTF. I'm looking for a kernel that contains the CWM recovery so I can flash some ROMS.
onemanshow85 said:
thanks, I managed to get it rooted, TA backup, bootloader unlock and flashed a stock FTF. I'm looking for a kernel that contains the CWM recovery so I can flash some ROMS.
Click to expand...
Click to collapse
use any custom kernel. use phantom v7 for jellybean, above that are all for kitkat onli. There's a stock kernel with recovery too. And it's really god
abhi007.john said:
use any custom kernel. use phantom v7 for jellybean, above that are all for kitkat onli. There's a stock kernel with recovery too. And it's really god
Click to expand...
Click to collapse
tnx.
One more thing though...it seems I can't get into the recovery by default. The purple LED light doesn't lit up when I boot my phone and I tried wigling the volume buttons during boot multiple times but it just boots regularly. I was on the verge to flash a recovery with a boot.img, from phantom I believe, but I figured I wouldn't before I figure out how to get into the recovery. Supose the ROM won't boot after flashing a new recovery, there's no way for me to enter CWM
onemanshow85 said:
tnx.
One more thing though...it seems I can't get into the recovery by default. The purple LED light doesn't lit up when I boot my phone and I tried wigling the volume buttons during boot multiple times but it just boots regularly. I was on the verge to flash a recovery with a boot.img, from phantom I believe, but I figured I wouldn't before I figure out how to get into the recovery. Supose the ROM won't boot after flashing a new recovery, there's no way for me to enter CWM
Click to expand...
Click to collapse
You cannot enter the recovery by keypress on stock. You'll have to do that via ADB or Gravitybox etc.
Joery360 said:
You cannot enter the recovery by keypress on stock. You'll have to do that via ADB or Gravitybox etc.
Click to expand...
Click to collapse
I see, so the volume button trick is a custom ROM only feature to enter the recovery..? So I gues I would have to flash a custom ROM with recovery included with flashtool. Can someone hoop me up with a ROM like that?
I did some research into this Gravitybox but it sais it requires a working custom recovery, which I lack.
onemanshow85 said:
I see, so the volume button trick is a custom ROM only feature to enter the recovery..? So I gues I would have to flash a custom ROM with recovery included with flashtool. Can someone hoop me up with a ROM like that?
I did some research into this Gravitybox but it sais it requires a working custom recovery, which I lack.
Click to expand...
Click to collapse
Unlock bootloader, download a JB Custom Kernel (Vengeance is a good one), extract boot.img and flash it in fastboot mode with flashtool.
onemanshow85 said:
I see, so the volume button trick is a custom ROM only feature to enter the recovery..? So I gues I would have to flash a custom ROM with recovery included with flashtool. Can someone hoop me up with a ROM like that?
I did some research into this Gravitybox but it sais it requires a working custom recovery, which I lack.
Click to expand...
Click to collapse
It's NOT the ROM. Recovery comes with custom KERNEL. If you're on stock kernel then you won't be able to enter recovery by pressing volume down.
Unlock your bootloader, flash a custom kernel and then you will have a recovery and glowing led on boot. In case your phone doesn't boot( that you cautioned) flash stock FTF using flashtool. It will reset your kernel(which means flash stock kernel, which works anyways).
Hope this helps
Hit thanks if it does.
abhi007.john said:
It's NOT the ROM. Recovery comes with custom KERNEL. If you're on stock kernel then you won't be able to enter recovery by pressing volume down.
Unlock your bootloader, flash a custom kernel and then you will have a recovery and glowing led on boot. In case your phone doesn't boot( that you cautioned) flash stock FTF using flashtool. It will reset your kernel(which means flash stock kernel, which works anyways).
Hope this helps
Hit thanks if it does.
Click to expand...
Click to collapse
ok, got it. thanks.
next problem: I got the CWM working and I was about to flash a custom ROM. the AOSP ROM from Taoshan gave me an error so I wanted to flash a different one. I dowloaded and stored a different ROM+gapps on a different SD card to save some time. Now for some reason, CWM memorizes the content of the combination of the 2 SDcards, and it won't update it's content no matter what SDcard I use. I formatted the SD card and stored the ROM+gapps again, but CWM keeps showing me the content of the old status of the SD card. So I can't select any new zips.
quesiton is, can I fix this somehow OR, can I reflash the boot.img to overwrite the current CWM without any issues? I have no working ROM atm since I already to apply a new one.
onemanshow85 said:
ok, got it. thanks.
next problem: I got the CWM working and I was about to flash a custom ROM. the AOSP ROM from Taoshan gave me an error so I wanted to flash a different one. I dowloaded and stored a different ROM+gapps on a different SD card to save some time. Now for some reason, CWM memorizes the content of the combination of the 2 SDcards, and it won't update it's content no matter what SDcard I use. I formatted the SD card and stored the ROM+gapps again, but CWM keeps showing me the content of the old status of the SD card. So I can't select any new zips.
quesiton is, can I fix this somehow OR, can I reflash the boot.img to overwrite the current CWM without any issues? I have no working ROM atm since I already to apply a new one.
Click to expand...
Click to collapse
Yes, you can flash new kernel anytime. I am not sure what's causing this problem. I wonder if there's any refresh or reload option in CWM or any option to reset/clear CWM data. Look for these options and if you don't find, feel free to flash the kernel again.
Hit thanks if it helped.
abhi007.john said:
Yes, you can flash new kernel anytime. I am not sure what's causing this problem. I wonder if there's any refresh or reload option in CWM or any option to reset/clear CWM data. Look for these options and if you don't find, feel free to flash the kernel again.
Hit thanks if it helped.
Click to expand...
Click to collapse
solved
I was using a JB kernel and trying to flash KK roms. Extracted a kernel from LS 4.4 ROM and flashed it, phone is booted and working fine now.
about the CWM issue, reflashing the same kernel won't solve the it. When I flashed a different kernel, it did do the trick. Seems CWM stores SD partitions in its own memory. I managed to install zips from the SDcard by accesing the external SDcard partition. Haven't seen any refresh or reload options in CWM.
thanks for the help, overall I just had to do some more reading. I'm quite familiar with rooting but I come from a HTC device, which is entirely different imo. (using 4ext recovery there which I personally find a lot more user friendly). Getting accustomed with Sony devices, the rooting and the terminoligy takes some time I guess.
OK got a p900 again and dare I say it's been actually really fun to use again. Everything is more mature, I updated to 5.0.2 I r a the p900 WiFi model however, how do I root again please.
Plus is there any recommended roms? Ideally looking for one with less bloats are to be honest as I find the spend useful to clip ideas whi'e drawing etc from websites and pdf.
bump, anyone?
There's a recent thread talking about king root working. Not sure the full process though for lollipop as I didn't root lollipop I just went straight to a rooted lollipop ROM.
My advice is download and install TWRP (http://forum.xda-developers.com/showthread.php?t=2706982), make an nandroid backup and then install the latest version of civs ROM.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
There's a recent thread talking about king root working. Not sure the full process though for lollipop as I didn't root lollipop I just went straight to a rooted lollipop ROM.
My advice is download and install TWRP (http://forum.xda-developers.com/showthread.php?t=2706982), make an nandroid backup and then install the latest version of civs ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Hi
Can you explain the process, I'm on 5.0.2 so not sure what to do and the process exactly?.
rirawin said:
Hi
Can you explain the process, I'm on 5.0.2 so not sure what to do and the process exactly?.
Click to expand...
Click to collapse
I believe there's a guide thread for lollipop and root and you were the last poster in it (http://forum.xda-developers.com/gal...guide-install-official-lollipop-p900-t3154362). While I don't know for certain what the answer is for you in the UK I am fairly confident that following the TWRP+Root section in the first post in that thread will work for you.
Just be mindful of the locations you download the TWRP and SuperSu files (you download one to your computer, you download the other to the tablet's SD card). Also pay attention to button combinations in the instructions because they're important (i.e. Power+Home+VolumeDown does something different than Power+Home+VolumeUp !!). Lastly make sure to heed the red text in the instructions too because if you allow the tablet to reboot prior to installing SuperSu then you'll likely end up in a bootloop and have to get back into stock recovery and restart the process again (worse, you may even have to wipe the device clean using Kies).
Good luck.
If you can at least get TWRP and root working on your device you can then do a backup in TWRP and also get backups of your apps/data using Titanium Backup prior to exploring other ROMs.
muzzy996 said:
I believe there's a guide thread for lollipop and root and you were the last poster in it (http://forum.xda-developers.com/gal...guide-install-official-lollipop-p900-t3154362). While I don't know for certain what the answer is for you in the UK I am fairly confident that following the TWRP+Root section in the first post in that thread will work for you.
Just be mindful of the locations you download the TWRP and SuperSu files (you download one to your computer, you download the other to the tablet's SD card). Also pay attention to button combinations in the instructions because they're important (i.e. Power+Home+VolumeDown does something different than Power+Home+VolumeUp !!). Lastly make sure to heed the red text in the instructions too because if you allow the tablet to reboot prior to installing SuperSu then you'll likely end up in a bootloop and have to get back into stock recovery and restart the process again (worse, you may even have to wipe the device clean using Kies).
Good luck.
If you can at least get TWRP and root working on your device you can then do a backup in TWRP and also get backups of your apps/data using Titanium Backup prior to exploring other ROMs.
Click to expand...
Click to collapse
Thank you, if I root can anything bad go wrong?
Do I get the original samsung rom and then flash back to stock if needed?.
Also does Wanam Xposed work with Lollipop, want to download an adblocker for my tablet and grant sd access.
To be honest given your apprehension I'm of the mind that if your best course of action is going with the custom ROM. I would root using the documented method first, install Titanium Backup once your stock ROM is rooted and then do a full backup of your apps. I would also do a full backup of your system in TWRP. If you're pressed for space after that then copy the backup files off of the device onto your computer before erasing them.
Once your backups are done (and I'm presuming you want to back things up first) then proceed with doing the Civs ROM install. This will get you Xposed framework and adblocking installed without any need for you to do the installs yourself. It keeps you out of trouble and best of all the support thread for his ROM is still active.
As for downloading the orginal ROM that's up to you . . doing the full backup in TWRP of your original rooted ROM is usually sufficient.
Keep in mind the methods I'm describing assume that you're not concerned with Knox or warranty status.
muzzy996 said:
To be honest given your apprehension I'm of the mind that if your best course of action is going with the custom ROM. I would root using the documented method first, install Titanium Backup once your stock ROM is rooted and then do a full backup of your apps. I would also do a full backup of your system in TWRP. If you're pressed for space after that then copy the backup files off of the device onto your computer before erasing them.
Once your backups are done (and I'm presuming you want to back things up first) then proceed with doing the Civs ROM install. This will get you Xposed framework and adblocking installed without any need for you to do the installs yourself. It keeps you out of trouble and best of all the support thread for his ROM is still active.
As for downloading the orginal ROM that's up to you . . doing the full backup in TWRP of your original rooted ROM is usually sufficient.
Keep in mind the methods I'm describing assume that you're not concerned with Knox or warranty status.
Click to expand...
Click to collapse
HELP!!
I went throught the steps and now my Note is stuck on the Samsung logo??
Please help stuck on Samsung animation???
Boot back into recovery (power+home+volume up). Which recovery comes up? If recovery doesn't go back into download mode and try flashing TWRP usin odin again.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
Boot back into recovery (power+home+volume up). Which recovery comes up? If recovery doesn't go back into download mode and try flashing TWRP usin odin again.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Hi recovery is twrp, says neowin or something if that makes sense.
muzzy996 said:
To be honest given your apprehension I'm of the mind that if your best course of action is going with the custom ROM. I would root using the documented method first, install Titanium Backup once your stock ROM is rooted and then do a full backup of your apps. I would also do a full backup of your system in TWRP. If you're pressed for space after that then copy the backup files off of the device onto your computer before erasing them.
Once your backups are done (and I'm presuming you want to back things up first) then proceed with doing the Civs ROM install. This will get you Xposed framework and adblocking installed without any need for you to do the installs yourself. It keeps you out of trouble and best of all the support thread for his ROM is still active.
As for downloading the orginal ROM that's up to you . . doing the full backup in TWRP of your original rooted ROM is usually sufficient.
Keep in mind the methods I'm describing assume that you're not concerned with Knox or warranty status.
Click to expand...
Click to collapse
Also can you link me to Civs rom please, not sure which one you are talking about?.
One of the things I want is, can I add different apps for the multi window function please?.
http://forum.xda-developers.com/showthread.php?t=3155589
Based upon your post in the other thread I assume that you got root working.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
http://forum.xda-developers.com/showthread.php?t=3155589
Based upon your post in the other thread I assume that you got root working.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks so this rom:
http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589
and not this one here which I replied too:
http://forum.xda-developers.com/gal...m-lollipop-5-0-2-stock-root-bussybox-t3207857
rirawin said:
Thanks so this rom:
http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589
and not this one here which I replied too:
http://forum.xda-developers.com/gal...m-lollipop-5-0-2-stock-root-bussybox-t3207857
Click to expand...
Click to collapse
Yes because the second one is stock rooted (as the title indicates) and you are already stock rooted.
At this point I hope you are aware that installing the ROM will erase all of your settings and applications, right?
Sent from my SM-N910T using Tapatalk
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
try these roms.
rocketfans14 said:
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
Click to expand...
Click to collapse
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Zte blade l said:
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Click to expand...
Click to collapse
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Not much difference.
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
rocketfans14 said:
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Click to expand...
Click to collapse
it is not necessary to unloack bootloader for tab 2 as it comes with a unlocked bootloader from stock.
Zte blade l said:
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
Click to expand...
Click to collapse
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
rocketfans14 said:
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
Click to expand...
Click to collapse
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...?
Tab 2 has got marshmallow.
Zte blade l said:
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...��
Tab 2 has got marshmallow.
Click to expand...
Click to collapse
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
billysam said:
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
Click to expand...
Click to collapse
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
rocketfans14 said:
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
Click to expand...
Click to collapse
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
Did you clear dalvik cache in recovery before flashing rom?
Zte blade l said:
Did you clear dalvik cache in recovery before flashing rom?
Click to expand...
Click to collapse
Yes, I cleared the top four options in recovery, and formatted data before flashing.
billysam said:
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
Click to expand...
Click to collapse
That's what I did. Let me just briefly summarize what I have done:
used odin with twrp
booted into recovery and made back up
cleared dalvik, cache, system, and data, formatted data
flashed update supersu, booted into system and checked root with root checker
rebooted into recovery, cleared dalvik, cache, system, and data, formatted data again
flashed cm12.1 and gapps, rebooted but ran into bootloop at splash screen
rebooted into recovery and restored back up
So I'm rooted and on stock 4.2.2 currently.
champ1919 said:
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I did.
Try flashing blisspop or slimLP.
I have a Shield Tablet (post battery fire exchange) and I would like to update it to the newest firmware/os... It is currently rooted, running BitO-Kernel, and stock nvidia rom. I did all the rooting and flashing on this tablet originally, but I never kept it up to date with newer updates. I heard on this forum awhile back that it's not just as simple as flashing a new rom, something about having to flash some other system stuff first or some partition or something. Basically I'm looking for a guide on how to update a Shield Tablet from rooted 5.1.1 to the newest OS version avalible. I tried sreaching the forum, but I couldn't find what I was looking for (maybe I'm not using the right search keyworks).
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20wifi&tx=$additional,shield
redpoint73 said:
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet wifi&tx=$additional,shield
Click to expand...
Click to collapse
Thanks I appreciate the help! Yes it's an original tablet (not the k1). It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root. I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
https://forum.xda-developers.com/shield-tablet/help/how-update-rooted-shield-tablet-to-t3355436
bluegizmo83 said:
It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root.
Click to expand...
Click to collapse
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
bluegizmo83 said:
I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
Click to expand...
Click to collapse
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
redpoint73 said:
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
Click to expand...
Click to collapse
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works. After that, I should be able to flash any current update (like 6.0) also, correct? And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
bluegizmo83 said:
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works.
Click to expand...
Click to collapse
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!
bluegizmo83 said:
After that, I should be able to flash any current update (like 6.0) also, correct?
Click to expand...
Click to collapse
Correct.
bluegizmo83 said:
And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
Click to expand...
Click to collapse
Not 100% sure. It's a full OTA zip, not an incremental update. So in those cases (full OTA) it may not need the preceding update installed. But again, I'm not sure.
redpoint73 said:
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!.
Click to expand...
Click to collapse
Ok thanks again, I appreciate all the help! One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
bluegizmo83 said:
One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
Click to expand...
Click to collapse
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
redpoint73 said:
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
Click to expand...
Click to collapse
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
bluegizmo83 said:
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
Click to expand...
Click to collapse
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
redpoint73 said:
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
Click to expand...
Click to collapse
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
bluegizmo83 said:
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
Click to expand...
Click to collapse
I'm not sure if it matters with the OTA. My feeling is, that it won't matter, and it will still install.
My guess is that in the worst case, the OTA fails, and you have to resort to flashing the recovery OS version.