Related
I just recently rooted my phone using the newest root method for the 98.30.1 build. The phone was rooted successfully, but for some reason now, the Google Play Services crashes occassionally with a message on the phone that it stopped responding. I was wondering if anyone else if experiencing any issues with Google Play Services. Although this started to happen shortly after I rooted my phone, I don't believe the issue is related and is most likely being caused by something else. Anyone have any insight or solution to this?
Also, I was wanting to restore my phone to factory default, but was wondering if after I restore the phone, will I need to rerun the root tool to re-root the phone and/or reinstall the SuperSU app? I was thinking that the su binary and busybox are stored on the /system partition, so they shouldn't be affected, but would I then just need to install the SuperSU app from the Play Store? I am wondering if I would need to re-run the root tool or just install SuperSU from the app store for the phone to be rooted properly after a factory restore. Thank you in advance
Have you tried a safe boot?
PM notification is not on by default, btw.
aviwdoowks said:
Have you tried a safe boot?
PM notification is not on by default, btw.
Click to expand...
Click to collapse
Thank you for the quick response. I haven't tried safe boot yet, but I will definitely try it. Right now, I wiped the cache partition via stock recovery and am seeing if Google Play Services crashes again.
If I do decide to do a factory reset. What are the steps I need to do to ensure I keep root or can root again? I wasn't sure if I just do a factory reset and rerun the root tool, or do I just factory reset and install SuperSU through Play Store, or do I need to user OTARootkeeper to temporarily unroot and then factory reset and restore root? Just cautious to not mess up my phone. Thanks for all your help!
ScallywagginIT said:
do I just factory reset and install SuperSU through Play Store, or
Click to expand...
Click to collapse
Or use SS Bootstrap as it gives you more options like BU before you wipe.
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
goodboy1 said:
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First make sure you have the latest twrp, then boot into it, flash the ota zip from inside twrp, the ota zip is located in /cache...be sure to wipe cache and dalvik before restarting.
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Me too!
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
goodboy1 said:
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brandypuff said:
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
Click to expand...
Click to collapse
Both of you modified /system, you must dirty flash your stock system.img then flash the ota. Additionally, if you are using a custom kernel, you will probably have to flash the stock boot.img as well.
And both if you, don't forget to do a nandroid first!
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
brandypuff said:
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
Click to expand...
Click to collapse
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Updated!
Bought my Nexus recently and it was android 4.3 [Dad bought it in US and forgot to check the version)
I got the OTA update to 4.4.2 a few days back but it didnt install though it finished downloading. After trying all methods, i decided to do it with Nexus Root Toolkit. But to my surprise, NRT had the 4.4.3 stock img already! I flashed it and my Tablet is smooth. No problems noted till now. If you want me to check whether a particular app is working in 4.4.3 properly or not, let me know. I will test it and tell you
mdamaged said:
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Click to expand...
Click to collapse
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
brandypuff said:
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
Click to expand...
Click to collapse
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but any changes you made to /system will be gone, you will have to reapply those changes.
You did not ask, but I use MultiROM, and I will flash a new version to a secondary, then use titanium on app data, then boot into the new secondary, make whatever changes I need to, once I am fine with how it works, I then migrate my data to it, then use the swap ROM function in MultiROM. The whole OTA thing is a PITA when you modify too much of the system.
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but anychanges you made to /system will be gone, you will have to reapply those changes.
Click to expand...
Click to collapse
Thank you very much!
I will try this.
James
I fought with the Nexus 7 {2013} 4.4.3 update for a good day and a half. Tablet rooted with xposed modules , etc. Same messages you got.
Found that this method works very easily and preserves all data. Takes a few minutes to accomplish, then just one minute to reroot. Try this, it works:
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
sucess
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
brandypuff said:
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
Click to expand...
Click to collapse
Just download the newest SuperSU and flash it from recovery. Then install busybox from playstore.
I had to uninstall xposed, re enable all apps. Recovery, install update in cache, wipe cache dalvik, reboot, reboot to recover flash su, boot, install supersu, reboot to TWRP and boot then reinstall xposed.
Yep if you're unlocked and rooted it can be done without a computer but it's way slower!
Sent from my Nexus 7 using Tapatalk
Thank you everyone. I used the nexus toolkit suggested a few posts back and everything works.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
mccartad said:
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
Click to expand...
Click to collapse
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
mdamaged said:
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
Click to expand...
Click to collapse
Holy shnikies it worked! Thanks so much!
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
Click to expand...
Click to collapse
can anyone please confirm that this is a flashable .zip of a full stock Kit Kat 4.4.3. or can anyone point me to one. - thanks :cyclops:
I rooted my Galaxy Note 10.1 2014 Edition (P600) tablet using CF AutoRoot. I ran odin and flashed the two tars. (autoroot mj4 and stock recovery mj4).
Next I decided to put TWRP on, so i opened odin and flashed TWRP. It worked fine for a few days, then suddenly i lost root on some of my applications. I opened up TWRP and tried to flash Super SU again and it had a problem clearing the cache. It then wouldn't mount the cache at all. Meaning my tablet wouldn't boot.
I managed to fix it by running autoroot again and flashing the stock recovery, but now i have issues with my tablet only working for about 5-10 minutes, then it restarts itself. I'm assuming the cache might be corrupted and it ends up getting filled and then crashes. After about 5 minutes, it freezes and then goes to a black screen and restarts itself.
Can anyone help me fix this?
you should try this method : http://forum.xda-developers.com/showpost.php?p=53125229&postcount=409
lightman33 said:
you should try this method : http://forum.xda-developers.com/showpost.php?p=53125229&postcount=409
Click to expand...
Click to collapse
As i said previously, that's the method I used.
SPV2010 said:
As i said previously, that's the method I used.
Click to expand...
Click to collapse
Try reflash stock recovery, clear cache, davik cache and data, let it boot up then power down and start over with re root method again. MAKE SURE you use the correct CF autoroot for the p600 device.
you are saying you loose root after a few days, did you remove or freeze knox apps ?
see previous message advice, you should restart with a full wipe and full flash and it should be ok. An other way is to flash a custom already rooted and knox freed.
hope it will help you, good luck.
I lost root after a few days, not that i lose root. It happened the first time and from then the problems started occurring. I froze knox applications (all 8 of them).
I did a logcat using adb to see what errors occurred and i got an error saying
Fatal Signal 7 <SIGBUS> at 0xb6a3cc64 <code = 2>, thread (changes).
Unable to open connection to debuggerd: Connection refused.
Click to expand...
Click to collapse
Does anyone know what this error means and how to fix it? I heard its a data alignment problem, but not sure how to fix it, but i assume a full format would do it.
SPV2010 said:
I lost root after a few days, not that i lose root. It happened the first time and from then the problems started occurring. I froze knox applications (all 8 of them).
I did a logcat using adb to see what errors occurred and i got an error saying
Does anyone know what this error means and how to fix it? I heard its a data alignment problem, but not sure how to fix it, but i assume a full format would do it.
Click to expand...
Click to collapse
I would say a corruption would cause this and until you reformat, otherwise, you're going to get it again. Data corruption could cause many "unknown" errors, so you should reformat and do a clean install.
Whats the best way to format if you havent got a custom recovery,stock recovery? Odin? (scary)
My issue is I get rooted ,freeze up knoxes but then when I go to install TWRP (any ver.) it doesn't take..
sorry to piggy-back but it sounded similar to my situation
Hey guys, I have the p600 and was running stock NIL1 and decided to root. I ran in to all kinds of issues, very similar to what you are experiencing but managed to fix it so haven't had the instability. I believe you're missing a crucial step. I wasn't able to mount system or wipe cache until I did this.
Here's what I recommend:
Odin back to stock recovery
Boot to stock recovery and perform a factory reset and clear cache, this part was important
Reboot to download mode
CF Auto root again
Flash TWRP
Flash rom of your choice, I'm running http://forum.xda-developers.com/gal...opment/p600ueucni1-pure-stock-rooted-t2896910 and it works great!!
Hope it works for you!!
majorassface said:
Hey guys, I have the p600 and was running stock NIL1 and decided to root. I ran in to all kinds of issues, very similar to what you are experiencing but managed to fix it so haven't had the instability. I believe you're missing a crucial step. I wasn't able to mount system or wipe cache until I did this.
Here's what I recommend:
Odin back to stock recovery
Boot to stock recovery and perform a factory reset and clear cache, this part was important
Reboot to download mode
CF Auto root again
Flash TWRP
Flash rom of your choice, I'm running http://forum.xda-developers.com/gal...opment/p600ueucni1-pure-stock-rooted-t2896910 and it works great!!
Hope it works for you!!
Click to expand...
Click to collapse
Hey What TWRP was it?
Me too! ......Ill let you know Thanks
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
skallal said:
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
Click to expand...
Click to collapse
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
I was rooted with the Wugfresh toolkit. I downloaded the 5.0 (and later 5.0.1) factory image from Motorola and unpacked it. I edited the flash-all.bat batch file (right click, Edit -or- right click, Open With, select notepad/wordpad) and removed the -w flag from the end of the file. It's not the very end, but very close. Just delete the -w and any excess spaces and save the file. The -w flag is what tells it to do a wipe of all data, removing it will prevent that. Put your Nexus into bootloader mode and double click the batch file.
Once it finishes flashing, it will boot up and say "optimizing apps" or "Android is updating" or something like that. Mine took about 15 minutes. After that, run the Chainfire Auto Root (CFAR) script to get root access back, and you're back in business.
Note: flashing Factory Images and running CFAR require an unlocked bootloader. CFAR will unlock the bootloader AUTOMATICALLY as part of the script. This WILL RESULT IN A LOSS OF DATA. If you are already unlocked, you're fine, as long as you remove the -w flag from the batch file.
Also, you do not need to go from 4.4.4 to 5.0 to 5.0.1, you can jump straight from 4.4.4 to 5.0.1.
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Telyx said:
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Click to expand...
Click to collapse
^I am going to do this, after reading similar reports of success.
However, to OP I want to stress that it is important that you update your bootloader before flashing the ROM. The patch is attached to the linked post.
While I am definitely tech savvy, I am not that comfortable with the WugFresh toolkit. For example, I just updated it to v1.9.9 and connected my device. While I know I previously unlocked the boot loader and rooted my device, the toolkit itself does NOT tell me if my device is unlocked or rooted.
Is there a tutorial somewhere describing how to update to Lollipop with the WugFresh toolkit? Thanks to @fury683 for the comment about editing the batch file. But I don't know what that means with respect to the toolkit user interface, that is what buttons are clicked in what order. I need a step by step list of instructions before starting.
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
I used the WugFresh toolkit a few months ago, but have forgotten the steps I took. Should have written it down. I'll try to stick with the WugFresh toolkit.
Thanks for all the comments
Factory images and Wugfresh are not used together. Wugfresh is a collection of things while factory images return the device to 100% factory stock out of the box. If you modify the batch file as detailed above, no user data/apps are removed, just the system, recovery, etc partitions.
Factory images are a one click method that has a very similar end result as Wugfresh does to return to stock. I would go with factory images as it is the easiest and most straight forward method. Run batch, confirm, wait about 1-2 minutes, done.
skallal said:
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
Click to expand...
Click to collapse
Well if your hung up on running the OTA then the 4.4.4 but if I were you I would just flash the 5.0.1 and skip the who OTA.
I managed to update to 5.0.1 without wiping the device using WugFresh. I went to the WugFresh site, read the FAQ, and found how to update without wiping clean. Turns out there is an option to disable wipe without editing the batch file. I was able to do the while procedure leaving the device unlocked.
I did have an unexpected issue. I had to reinstall in the USB drivers on my PC before I could re-root it. WugFresh made this part easy too, though I'm surprised a reinstall was even required. Once that was done, USB connection was restored and I could complete the rooting process.
I always stress out whenever updating Android in any way. The rules are different with each device and OS version.
One change I've noticed I'd that my Nexus 7 brightness I'd dimmer and I have to turn to setting higher. Hope the update is worth the trouble.
Follow up: after all the work upgrading to 5.0.1, I decided I didn't like the new version. I did the upgrade without a clean wipe. But I did the downgrade with a clean wipe.
The WugFresh toolkit is quite capable utility. I couldn't imagine doing it the hard way with the adb command line interface. At least know how to recover and rebuild my system should the need ever occur in the future. And Titanium Backup is indispensable too.
I found Lollipop to be a battery hog. Perhaps I'll try it again when some of the issues are worked out. There is no compelling reason change from Kit Kat at this time, IMHO.
OrBy said:
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
Click to expand...
Click to collapse
This is NOT true. I upgraded while rooted and it went fine. Just beware of xposed and other tools that mess up with /system and thus the upgrade scripts.
While I was able to update from KK (4.4.4) to LP (5.0.1) without wiping the data, it didn't work out for me. The battery life was terrible. It drained at least twice as fast compared to before the update. I was trying to avoid the pain of a clean install. But in the end, it wasn't worth with it.
I ended up going back to KK, and then to LP again but with a clean install. When installing LP the second time, I wiped the data and let Google reinstall all of the apps. There were a small number of apps, that I later restored the data from Titanium Backup, for example games with previous scores.
This made a huge difference in battery life. Plus the look and feel of many apps changed to the new Material design.
I'm not entirely sure I like the look of LP. I'd prefer LP under the hood, but the look of KK. Oh well!
Bottom line: don't do OTA updates with a major new release.
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Seattleweather said:
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Click to expand...
Click to collapse
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Y314K said:
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Click to expand...
Click to collapse
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Seattleweather said:
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Click to expand...
Click to collapse
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Y314K said:
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Click to expand...
Click to collapse
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Seattleweather said:
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Click to expand...
Click to collapse
np, glad it is back to normal.
Method 1 helps when you flash a new PreRooted ROM. And Method 5 helps to make sure your FW version is never low enough to think an update would apply to your device. Method 5 needs to be redone when ever you flash a ROM. And Method 1 must be redone when ever you factory reset thru TWRP or clean more then the Dalvik Cache & Cache thru TWRP. NEVER do a factory reset from FireOS 5. Only use TWRP for that.
Forgot to add. NEVER INCLUDE SYSTEM IN ANY OF YOUR WIPES. Flashing a PreRooted ROM will take care of System. So leave it alone. Most bricks happen because folks wipe SYSTEM & they do not Flash a PreRooted ROM before doing a reboot.