Related
i just got OTA update notification for 4.4.3 on my rooted ,stock,custom recovery Nexus 4 running on 4.4.2.
i use SuperSU,Xposed etc.
i have few questions hoping that someone will help me,
1. what happens if i update OTA normally , i lost data?root ? or there is possibility of softbrick while updating.
2. what is the best way of updating rooted phone with stock.
thanks in advance!!:good:
mrYogii said:
i just got OTA update notification for 4.4.3 on my rooted ,stock,custom recovery Nexus 4 running on 4.4.2.
i use SuperSU,Xposed etc.
i have few questions hoping that someone will help me,
1. what happens if i update OTA normally , i lost data?root ? or there is possibility of softbrick while updating.
2. what is the best way of updating rooted phone with stock.
thanks in advance!!:good:
Click to expand...
Click to collapse
Download and Install the OTA, you will loose your ROOT AND RECOVERY but not the data. That is the easiest way.
plz elaborate the process, i am new to it.
and one more question : what if i do OTA normally(over wifi).
with custom recovery and xposed OTA will fail and maybe soft brick.
please read here: http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
carlosmg2 said:
with custom recovery and xposed OTA will fail and maybe soft brick.
please read here: http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
Click to expand...
Click to collapse
thats what i am fearing , plz guide me for updating my rooted stock .
anyone in the same situation? OTA hit on device but not sure to update due to rooted and custom recovery, with Xposed and other modifications, plz help
mrYogii said:
anyone in the same situation? OTA hit on device but not sure to update due to rooted and custom recovery, with Xposed and other modifications, plz help
Click to expand...
Click to collapse
You have two (best I think) solutions:
1) Get back to stock and download OTA... before you do that, download Titanium Backup, backup your apks with it's cache so you won't have to set them up or start games from beggining... to backup messages etc you can use My Backup Pro, for calendar and contacts synchronize your Google account
2) Try to "get back to stock" as near as you can and try OTA... if it fails, it's not difficult to recover from softbrick
parkourz said:
You have two (best I think) solutions:
1) Get back to stock and download OTA... before you do that, download Titanium Backup, backup your apks with it's cache so you won't have to set them up or start games from beggining... to backup messages etc you can use My Backup Pro, for calendar and contacts synchronize your Google account
2) Try to "get back to stock" as near as you can and try OTA... if it fails, it's not difficult to recover from softbrick
Click to expand...
Click to collapse
i think 1 option i will try, what will be the process of
parkourz said:
Get back to stock
Click to expand...
Click to collapse
, if i am running stock but with custom recovery and xposed like modifications .
mrYogii said:
thats what i am fearing , plz guide me for updating my rooted stock .
Click to expand...
Click to collapse
in the link I posted OTA HELP DESK is all well explained.
I was in your same situation (stock + franco kernel+ TRWP recovery + Xposed) and i have just installed the OTA. This is what I did:
1- Uninstall Xposed (from inside the installer)
2- Uninstall Cerberus app (because in some cases it modifies system)
2- Flash stock kernel
3- Flash OTA in recovery
* It failed because Franco kernel modifies /system/lib/hw/power.msm8960.so --> so renamed power.msm8960.so.bak to power.msm8960.so
4- Flash OTA in recovery
5- Flash TRWP recovery
6- rooted
carlosmg2 said:
in the link I posted OTA HELP DESK is all well explained.
I was in your same situation (stock + franco kernel+ TRWP recovery + Xposed) and i have just installed the OTA. This is what I did:
1- Uninstall Xposed (from inside the installer)
2- Uninstall Cerberus app (because in some cases it modifies system)
2- Flash stock kernel
3- Flash OTA in recovery
* It failed because Franco kernel modifies /system/lib/hw/power.msm8960.so --> so renamed power.msm8960.so.bak to power.msm8960.so
4- Flash OTA in recovery
5- Flash TRWP recovery
6- rooted
Click to expand...
Click to collapse
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only, if i uninstall xposed m i good to go for OTA from wifi? or i have to flash it in recovery?if so then plz point me to 4.4.3 update download link.
thanks!
mrYogii said:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only, if i uninstall xposed m i good to go for OTA from wifi? or i have to flash it in recovery?if so then plz point me to 4.4.3 update download link.
thanks!
Click to expand...
Click to collapse
read THIS http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848
I'm not sure, but your situation may need 'Scenario #2' (+ uninstalling Xposed)
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
mrYogii said:
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
Click to expand...
Click to collapse
yeah, you need to uninstall Xposed too (from within the app, not like uninstalling normal apps). Then you can reinstall and have all modules and config untouched.
carlosmg2 said:
yeah, you need to uninstall Xposed too (from within the app, not like uninstalling normal apps). Then you can reinstall and have all modules and config untouched.
Click to expand...
Click to collapse
i tried as you told, while installing OTA from zip i got following error:
/syaystem/priv-app/SystemUI.apk has unexpected contents.
installation aborted.
plz help
stock 4.4.2 nexus 4 SystemUI.apk
anyone has stock 4.4.2 nexus 4 SystemUI.apk? i have to revert back to install 4.4.3 update through recovery.
mrYogii said:
can anyone else conform me on this:
i have stock kernel , i used xposed for ui tweaks and boot animation etc apart from that all other things are stock only.
suggested(http://forum.xda-developers.com/nexus-4/general/info-nexus-4-ota-help-desk-t2145848) :
Section B: Flashing in a custom recovery
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
i am not sure that xpose modifications come in this condition or not
Click to expand...
Click to collapse
mrYogii said:
i tried as you told, while installing OTA from zip i got following error:
/syaystem/priv-app/SystemUI.apk has unexpected contents.
installation aborted.
plz help
Click to expand...
Click to collapse
Try this it'll work for you
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file
jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away
viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)
Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.
Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).
I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.
So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?
Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
work great
thanks
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.
Rooted my Shield two times wth CWM without problems.
astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse
Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)
From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.
If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day
I am not responsible for any bricked devices or any other damage do your Kindle Fire, SD Cards, or yourself.
Steps:
1. Using RootJunky's SuperTool, root your Fire then install FlashFire
2. Download CM12.1 from here.
3. Follow the instructions listed.
4. Profit
To re-root your tablet or enable ADB:
1. Go to settings
2. Scroll to the bottom, tap on About Tablet.
3. Tap on build number until it says "You have enabled developer settings."
4. Go back and open Developer Options.
5. You now have the options for rooting and ADB.
llamasking said:
I am not responsible for any bricked devices or any other damage do your Kindle Fire, SD Cards, or yourself.
Steps:
1. Using RootJunky's SuperTool, root your Fire then install FlashFire
2. Download CM12.1 from here.
3. Follow the instructions listed.
4. Profit
Click to expand...
Click to collapse
Just tried it out. Worked perfectly! Went from Fire 5.3.1 to CM12.1 successfully.
Thanks for the simplified tutorial!
ChronicAlbert said:
Just tried it out. Worked perfectly! Went from Fire 5.3.1 to CM12.1 successfully.
Thanks for the simplified tutorial!
Click to expand...
Click to collapse
Thank you!
Kingroot from the Super tool keeps failing for my Fire on 5.3.1.0. Frustrating. Can't even get passed that step.
fuelvolts said:
Kingroot from the Super tool keeps failing for my Fire on 5.3.1.0. Frustrating. Can't even get passed that step.
Click to expand...
Click to collapse
Try doing factory reset, then use the supertool without loging into your amazon account
Sorry for the noob question, but is this gonna work on a 6th gen HD 8" running 5.3.1.1?
usererror404 said:
Sorry for the noob question, but is this gonna work on a 6th gen HD 8" running 5.3.1.1?
Click to expand...
Click to collapse
Wrong forum; ask here. Hint: nope.
Worked perfect!
Edit: Just a short question after installing CM12.1, my device isn't rooted anymore? How to root it again in order to get Flashfire working? Or ist TWRP automatically installed?
SwitzXXL said:
Worked perfect!
Edit: Just a short question after installing CM12.1, my device isn't rooted anymore? How to root it again in order to get Flashfire working? Or ist TWRP automatically installed?
Click to expand...
Click to collapse
- enable developer options (Google for procedure)
- locate/enable root toggle under developer options
- no twrp; must use FlashFire as needed
I wanted to do this but IDK how to find my firmware version. My kindle has had updated disabled ads removed and all that for a while now.
Davey126 said:
- enable developer options (Google for procedure)
- locate/enable root toggle under developer options
- no twrp; must use FlashFire as needed
Click to expand...
Click to collapse
Tried that and gave root to apps & adb but I still can't install SuperSU nore use FlashFire (no root)?
SwitzXXL said:
Tried that and gave root to apps & adb but I still can't install SuperSU nore use FlashFire (no root)?
Click to expand...
Click to collapse
Have you rebooted after enabling root? Sometimes required. Verify root status with a checker app; I linked one below for convenience (both source and app are well regarded). There are many others including dozens in the Play Store if you have access.
http://www.apkmirror.com/apk/jrummy-apps-inc/root-check/
Sorry guys for asking a question that been asked many time but i just wanna be sure
my fire is on 5.3.1.0 installed on jully 29,2016.... CAN I ROOT IT? cause i heard i could brick it
Thanks
caymera said:
Sorry guys for asking a question that been asked many time but i just wanna be sure
my fire is on 5.3.1.0 installed on jully 29,2016.... CAN I ROOT IT? cause i heard i could brick it
Thanks
Click to expand...
Click to collapse
Yes - use the SuperTool linked in the OP (first post in this thread). Don't get all knotted up following some other guide that will lead you down a rabbit hole.
was able to install CM12.1 - but no Google stuff was installed, now enabled root again and can't get access to SuperSU, any tips, says it failed, rebooted, did factory reset, no luck.
fventura03 said:
was able to install CM12.1 - but no Google stuff was installed, now enabled root again and can't get access to SuperSU, any tips, says it failed, rebooted, did factory reset, no luck.
Click to expand...
Click to collapse
This commonly happens when (one of more):
- full system wipe does not proceed rom flash
- FlashFire zip options are twiddled (defaults are fine)
- wrong version of GAaps or GAaps not included w/rom
You'll likely need to restore FireOS via stock recovery and start over.
fventura03 said:
was able to install CM12.1 - but no Google stuff was installed, now enabled root again and can't get access to SuperSU, any tips, says it failed, rebooted, did factory reset, no luck.
Click to expand...
Click to collapse
Did you flash gapps?
ldeveraux said:
Did you flash gapps?
Click to expand...
Click to collapse
Which version of GAPPS do we need in this case?
jonathanmoneill said:
Which version of GAPPS do we need in this case?
Click to expand...
Click to collapse
Recommend Open GAaps arm/5.1/nano (here). You will likely need to reflash CM 12.1 along with the GAaps. Flashing a stand-alone GAaps package after CMxx has initialized often doesn't work. You will need to reinstall FlashFire (here) to accomplish the above. You do NOT need to reload FireOS provided the system partition is wiped before flashing CM+GAaps. Ask further questions as needed.
hi guys, i just used rootjunkys tool to root a new Fire 5.3.1 ,i put in kingroot and them
then supersu , chexked to see if i got root app sys yes, now i put in flasfire it says invalid file, so please what do i do now, and when i do get it to work plz explain how i put on cm.12,,thankyou