Have the 8.9. I have the3.2.6 bin. I keep getting "update failed". Am rooted. I believe the file is in the correct folder. What could I be missing? What is the exact file path? I've followed the directions as far as what to do. I can't help but wonder if the file is in the wrong place or if there is something else I have to do because I'm rooted.
Sent from my KFAPWI using Tapatalk
first remove safetrap, unroot and try to update it.
If you still cannot update, then root, install safetrap; rename the bin file to zip file and install it via safetrap. This method worked for me but the modem firmware may not be updated.
v941726 said:
Have the 8.9. I have the3.2.6 bin. I keep getting "update failed". Am rooted. I believe the file is in the correct folder. What could I be missing? What is the exact file path? I've followed the directions as far as what to do. I can't help but wonder if the file is in the wrong place or if there is something else I have to do because I'm rooted.
Sent from my KFAPWI using Tapatalk
Click to expand...
Click to collapse
if you have xposed and the HDXpose module installed you must find and uncheck it under modules and uninstall framework and uninstall the app . If you used the toolkit to block OTA updates you must undo this under the «more» option , uninstalled safestrap properly including deleting its files . Do a factory reset under security settings skip set up choose language only. Dropped your update Bin file on root of sdcard in other words drop it directly on "kindle" on pc.. Give it a few minutes then check for updates via settings with no Wi-Fi connection it should . Acknowledge it and run update.
---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------
v941726 said:
Have the 8.9. I have the3.2.6 bin. I keep getting "update failed". Am rooted. I believe the file is in the correct folder. What could I be missing? What is the exact file path? I've followed the directions as far as what to do. I can't help but wonder if the file is in the wrong place or if there is something else I have to do because I'm rooted.
Sent from my KFAPWI using Tapatalk
Click to expand...
Click to collapse
if you have xposed and the HDXpose module installed you must find and uncheck it under modules and framework and uninstall the app . If you used the toolkit to block OTA updates you must undo this under the «more» option , uninstalled safestrap properly including deleting its files . Do a factory reset under security settings skip set up choose language only. Dropped your update Bin file on root of sdcard in other words drop it directly on "kindle" on pc.. Give it a few minutes then check for updates via settings with no Wi-Fi connection it should . Open settings and set check for update ..it should Acknowledge it and run update
I'm not using safestrap. So I don't have to worry about that I guess
Sent from my KFAPWI using Tapatalk
So I have to reset it? After all this? Oh boy. Haven't heard that yet. I'll have to redo everything I've just done?
Sent from my KFAPWI using Tapatalk
wow
v941726 said:
So I have to reset it? After all this? Oh boy. Haven't heard that yet. I'll have to redo everything I've just done?
Sent from my KFAPWI using Tapatalk
Click to expand...
Click to collapse
If you haven't heard that before then you haven't read very much around here it has at least a dozen times in multiple problem update threads where people have used some type of OTA blocker method . Some people have gotten away without doing it but if your having problems then it shouldn't really be a question . It's easy back everything up to your PC and start over . If you feel the need to have the latest update then you may have to work for it a lil sorry . I do know I had to factory reset to get mine to update to .4 from .1 after using different blocking methods... people are having the same problem when they try to roll back... After using blocking methods.And you never mentioned which firmware you are starting on. I don't believe that you can skip up to far....1 to .4 probably the biggest jump you can do .5 and .6 would be different I believe .btw do not factory reset unless you are sure you have uninstalled the framework for xposed within app. It's not necessary to uninstall the app because they've a factory reset will do that for you but you must remove the framework I have seen it complicate peoples issues
I can not upgrade from 13.3.1.0 to 13.3.2.6.
but I can upgrade from 13.3.2.5 to 13.3.2.6.
I hope this will help.
Well. Now, if I'm gonna go through all the trouble, then I will wait for v4. I have a feeling that I'll run into the same problem. But I may as well wait. Thanks for the feedback. I'm sure I'll be back. ?
Supposed to be within a few weeks for the update
I'm also having issues getting 3.2.6 (or 3.2.5) to go from 3.2.4. I've uninstalled HDXposed and deactivated the XPosed framework (Towelroot is still in place along with SuperSu) and uploaded the bin files, rebooted, and get the "last update failed" still. So, whatever HDXposed did to block OTA updates is still in place.
Before doing a factory reset, I wanted to backup the system. "adb -backup -apks -all ..." though starts just fine and then the kindle reboots after just a few items (16Mb). Really not rather start from total scratch - just hoping to update. Any thoughts on how to backup / restore given this odd reboot behavior?
Figured it out by looking at the source code for HDXposed. HDXPosed is disabling a few things and all we need to do is re-enable them.
So, assuming we've got ADB up and going:
./adb shell
su
pm enable com.amazon.dcp
pm enable com.amazon.dcp.contracts.library
pm enable com.amazon.dcp.contracts.framework.library
exit
exit
Bingo! OTA updates are back alive (as are updates via a download of the bin file).
Some very different methods mentioned in replies
Hello,
I just wanted to confirm steps that people have used in running the update before I go in and tap the wrong thing. I have used the HDX Toolkit v0.94 (http://forum.xda-developers.com/showthread.php?t=2665683) to root my device at the original out of the box version, then upgraded it to 3.2.4 and used HDX Toolkit to install and then run towelroot to reroot it.
When I try to use HDX Toolkit to reenable OTA updates, in order to sideload the update, I'm getting the upload failed message that I've seen other users with.
I have tried the following. At the end of each attempt I would still get the update failed message.
Disable OTA updates with HDX Toolkit
Reboot
Try to run the sideloaded update
Disable OTA updates with HDX Toolkit
Disable the HDXposed module
Reboot
Try to run the sideloaded update
Disable OTA updates with HDX Toolkit
Disable the HDXposed module
Uninstall the Xposed Framework
Reboot
Try to run the sideloaded update, from Device -> System Updates
From looking at a few replies in this thread, I've seen some different sets of steps to do the update
Method 1 - Safestrap
http://forum.xda-developers.com/showpost.php?p=55718487&postcount=2
Install Safestrap
Rename the .bin update file to .zip
Reboot into Safestrap Recovery
Install the update with SafeStrap
Method 2 - Factory Reset
http://forum.xda-developers.com/showpost.php?p=55724207&postcount=3
Disable the HDXposed module
Uninstall the Xposed Framework
Uninstall the Xposed Installer App
Reenable OTA Updates with HDX Toolkit
Factory Reset
Try to run the sideloaded update, from Device -> System Updates
With this method, do I leave Safestrap installed, what about SuperSU, before the factory reset?
Method 3 - adb commands
http://forum.xda-developers.com/showpost.php?p=55836317&postcount=11
Get adb running on your machine
As well as the Kindle drivers and whatnot
With it plugged in, run the following
./adb shell
su
pm enable com.amazon.dcp
pm enable com.amazon.dcp.contracts.library
pm enable com.amazon.dcp.contracts.framework.library
exit
exit
Try to run the sideloaded update, from Device -> System Updates
With this method do I disabled the HDXPosed module and uninstall the XPosed framework? I assume you do.
So which have people gotten to work?
first method I updated successfully from 3.2.4 to 3.2.5 and 3.2.6 (safetrap 3.75-B02). No problem so far.
I think the hash of the file does't match the correct bin file
You 'd better download the bin file through the “Internet Download Manager” 。
Then you will get the correct bin file。
The correct bin file can be unpacked。 remember this。
can you speak more specific about it，i don't know how to make it correct. thank you
spock2112 said:
Figured it out by looking at the source code for HDXposed. HDXPosed is disabling a few things and all we need to do is re-enable them.
So, assuming we've got ADB up and going:
./adb shell
su
pm enable com.amazon.dcp
pm enable com.amazon.dcp.contracts.library
pm enable com.amazon.dcp.contracts.framework.library
exit
exit
Bingo! OTA updates are back alive (as are updates via a download of the bin file).
Click to expand...
Click to collapse
can you speak more specific about it，i don't know how to make it correct. thank you
Btw, official quote from Amazon website:
Important:Your device must be on software version 3.2.5 or above in order to download this software update. If your device is running software version 3.2.4 or a previous version, you will need to download and install software version 3.2.5 in order to download Software Update 3.2.6. Click the link below to download the software needed to update your device:
Click to expand...
Click to collapse
Didn't work. Still get "last update failed".
try to rollback to 13.3.1.0 according to this http://forum.xda-developers.com/showthread.php?p=55759790#post55759790 and after that try again update to 13.3.2.5
And please post your /cache/recovery/last_log after fail. In this file we can see errors ocurred during update.
Related
Rooted my Atrix 4G successfully with this method: http://forum.xda-developers.com/showthread.php?t=1240130.
Trying to unroot, but it gives me this error:
ERROR: /restore/ backup doesn't exist or is incomplete!
These files must be downloaded and saved to your computer in a /restore/ subfolder
Download links can be found in the Help menu in this program
There are no downloads available for my phone.... I made no modifications when I rooted, just rooted to see if it would work. Trying to unroot for the new SOAK test. Any help?
bump?.......
You might have to flash the correct sbf for your phone and carrier using RSDLite.
Sent from Rob's Atrix
Sounds exactly like that. Definitely start from scratch and flash the initial 1.8.3 SBF with RSDlite.
http://forum.xda-developers.com/showthread.php?t=1136261
The process, depending on how far up the chain of in updates you go, can take a bit of time, but make sure you follow it EXACTLY.
Why were you using a Droid 3 tutorial to root your Atrix anyway?
Unroot
If you can restore to the Stock Moto, then you can use the Moto upgrade software as if you were upgrading to the 4.5.91.
motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
It will tell you that you are on the highest version but will allow you to reinstall the software. When it does this, it will unroot and relock the bootloader.
e07015 said:
If you can restore to the Stock Moto, then you can use the Moto upgrade software as if you were upgrading to the 4.5.91.
motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
It will tell you that you are on the highest version but will allow you to reinstall the software. When it does this, it will unroot and relock the bootloader.
Click to expand...
Click to collapse
Tried this, but wouldn't work. Said no update available at this time. My phone is 100% stock except the root. I'm on 4.xx, whatever is Gingerbread.
It should ask you if you want to reinstall the software anyway. It basically overwrites the system files. I was on the latest but it still let me refresh it thus removing root.
Are you using the motor update software you download from the motorola website? You install it on your computer then hook up your phone via usb cable.
Sent from my MB860 using XDA App
UNROOT?
OK. I am in the same boat. My Atrix has the latest update and I am rooted. No other mods done. I want to UNROOT, get the next OTA update, then ROOT again. I believe I rooted using ADB, ROOT, ADB FASTBOOT.
I do NOT want to lose my current setup since I have WAY too much time and energy into it and I love it.
I came across this on the web:
Un-root Steps:
1. Open Android Terminal Emulator (see download link above)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su mount -o rw,remount /dev/block/mmcblk0p12 /system mount -o
rw,remount /dev/block/mmcblk0p17 /preinstall rm /system/bin/su rm /preinstall/sqlite3 rm /preinstall/dosu
rm /preinstall/Superuser.apk rm /preinstall/su reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
4. You're un-rooted and all files that /preinstall put on your phone have been removed.
I don't know if this will work, or if it will leave my setup unchange, or if there is ANY chance of bricking my phone.
ALSO, there is an app in the market called OTA ROOTKEEPER and several other apps that claim to hide your rooted device so you can get updates, then unhide the root.
Anyone know?
THANKS.
This wont be an issue if the OTA will install perfectly fine with root. Owning the phone since launch day, I recall hearing that if you update with root access it bricks your phone. Is this true or not?
Anyway, @e07015, I used the method on the Motorola website, putting the image on my SD card. I assumed it wouldn't work but tried anyway. What exactly is the method your trying to explain?
Having root access might give the user the ability to alter the phone in ways that can effect stability, but root access alone doesn't change anything like that.
e07015 said:
If you can restore to the Stock Moto, then you can use the Moto upgrade software as if you were upgrading to the 4.5.91.
motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
It will tell you that you are on the highest version but will allow you to reinstall the software. When it does this, it will unroot and relock the bootloader.
Click to expand...
Click to collapse
pretty sure the bootloader dont relock
Motorola states that the Atrix will NOT be able to install this latest update if the phone is rooted or unlocked.
Sent from my MB860 using XDA App
On the Moto website, there are two options: Manual upgrade or automated update(pc users only). Do the automated update. You download the update tool and then connect your phone to the PC. Once it has recognized your phone, it will check for updates. It will tell you that you are on the latest version but asks if you want to reload it anyway. Do that and it will clear root and relock. Good Luck.
---------- Post added at 07:50 AM ---------- Previous post was at 07:43 AM ----------
I thought so also but after restoring to stock using the Moto Automatic Update tool, I rooted and tried to restore an old backup using CWM. It was giving me an error that my bootloader was locked. It no longer had the unlocked text at startup but I though it was still unlocked. Went through the unlock process again and then it let me use CWM again. Based upon this, I now assume that you can relock the bootloader.
e07015 said:
On the Moto website, there are two options: Manual upgrade or automated update(pc users only). Do the automated update. You download the update tool and then connect your phone to the PC. Once it has recognized your phone, it will check for updates. It will tell you that you are on the latest version but asks if you want to reload it anyway. Do that and it will clear root and relock. Good Luck.
---------- Post added at 07:50 AM ---------- Previous post was at 07:43 AM ----------
I thought so also but after restoring to stock using the Moto Automatic Update tool, I rooted and tried to restore an old backup using CWM. It was giving me an error that my bootloader was locked. It no longer had the unlocked text at startup but I though it was still unlocked. Went through the unlock process again and then it let me use CWM again. Based upon this, I now assume that you can relock the bootloader.
Click to expand...
Click to collapse
I've used the auto update tool and it tells me I'm current but doesn't give me the option to reinstall. If I have the zip from moto, can I just load it using clockwork mod? I went back to stock using a fruitcake on here, but I'm still unlocked and rooted. If the upcoming soak test is ICS (very doubtful), I want to be able to update
I have set my SuperSU to automatically update. It was all fine and working on the previous versions, but when I checked now it gives me the error below.
"There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Please help.
Gilkauss said:
I have set my SuperSU to automatically update. It was all fine and working on the previous versions, but when I checked now it gives me the error below.
"There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Please help.
Click to expand...
Click to collapse
download this, boot into recovery, then flash it. its the latest supersu binaries http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip
Or simply boot into twrp, reboot it and it's gonna give you the option to do so.
Twrp should have told you that you lost root and gave the option to repair it.
I tried to boot into recovery but it just showed me an android icon with red exclamation.
Also I dont have TWRP installed.
Gilkauss said:
I tried to boot into recovery but it just showed me an android icon with red exclamation.
Also I dont have TWRP installed.
Click to expand...
Click to collapse
So reflash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.4.4.0-mako.img in fastboot and then superSU http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in TWRP.
It seems that many users have had issues with the last few SuperSU updates in one way or another. Some get errors trying to update the binary. Some say Titanium Backup will no longer work unless you use the paid version of SuperSU. The latest installable zip doesn't work on all devices and needs a fix according to the first post on the official SuperSU thread...
http://forum.xda-developers.com/showthread.php?t=1538053
I decided to switch to the new Superuser by Koush.
sos
I tried but seems like i have to get the paid version of supersu in order to continue to use it so. can i go back from the beginning and re-root it with Clockworkmod ?
luubutmucxanh said:
I tried but seems like i have to get the paid version of supersu in order to continue to use it so. can i go back from the beginning and re-root it with Clockworkmod ?
Click to expand...
Click to collapse
flash the supersu su binaries in your recovery and reboot, download it here http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
simms22 said:
flash the supersu su binaries in your recovery and reboot, download it here http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
Click to expand...
Click to collapse
Thank, n sorry wrong section, my phone is htc one m7. But i did flash the 1.34 version, still getting the message that supersu stopped working.
luubutmucxanh said:
Thank, n sorry wrong section, my phone is htc one m7. But i did flash the 1.34 version, still getting the message that supersu stopped working.
Click to expand...
Click to collapse
well, im not familiar with rooting it, heres a link http://www.xda-developers.com/andro...one-m7-and-install-recovery-xda-developer-tv/
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
nickf123654 said:
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Click to expand...
Click to collapse
again.. or just grab the latest supersu and flash it in recovery. thats all.
ALSO.. THE LAST POST IN THIS THREAD IS OVER A YEAR OLD. WHY BRING THIS THREAD BACK? LOOK AT THE DATES BEFORE YOU POST IN A DEAD THREAD.
simms22 said:
again.. or just grab the latest supersu and flash it in recovery. thats all.
ALSO.. THE LAST POST IN THIS THREAD IS OVER A YEAR OLD. WHY BRING THIS THREAD BACK? LOOK AT THE DATES BEFORE YOU POST IN A DEAD THREAD.
Click to expand...
Click to collapse
Yes, it would be nice if that worked ever time, but for me it didn't.
I tried flashing the latest SU many times and still ended up without root.
I am just trying to offer a solution that me be helpful to others experiencing the same issue I did.
If you are interested in the details, you can check out my thread here:
http://forum.xda-developers.com/note-2-tmobile/help/4-3-custom-roms-losing-root-t2817114
To your point of this being an old thread, I just want to make the information easy to find. I searched all over the place and could not find a solution to my problem. Hopefully I can help someone else who is facing the same issue.
nickf123654 said:
Yes, it would be nice if that worked ever time, but for me it didn't.
I tried flashing the latest SU many times and still ended up without root.
I am just trying to offer a solution that me be helpful to others experiencing the same issue I did.
If you are interested in the details, you can check out my thread here:
http://forum.xda-developers.com/note-2-tmobile/help/4-3-custom-roms-losing-root-t2817114
To your point of this being an old thread, I just want to make the information easy to find. I searched all over the place and could not find a solution to my problem. Hopefully I can help someone else who is facing the same issue.
Click to expand...
Click to collapse
you are also missing that its a completely different device. of all my time ive spent in the nexus 4 and nexus 5 forums here, not once has an issue like that been reported. this would better be posted in the note 2 forums.
Thank u very much
gee2012 said:
So reflash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.4.4.0-mako.img in fastboot and then superSU http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in TWRP.
Click to expand...
Click to collapse
Thanks a lot.........your suggestions helped me a lot...... :good:
Recently released is the ONE-CLICK root and temporary custom CWM recovery for Asus Zenfone 2 ZE551ML & ZE550ML & ZE500CL
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
and to the maker of the original Intel temporary CWM: @social-design-concepts Thread
Method 1: ONE-CLICK root
Download the Asus Zenfone quick one-click root package
Unzip the package
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to download and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'Root_zenfone.bat'
To unroot, use 'xoa_root' or unroot through SuperSU in Android
Bam, done.
------------------------------
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
Download the Asus Zenfone temporary CWM package
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to download and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Easy, thanks!!!! :laugh:
with it, is possible run Asus update without bootloop?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
Working
working perfectly.
Getting more than 3GB RAM after removing preinstalled bloatware on the latest 2.17.40.12 ROM.
jaganathsamal said:
working perfectly.
Getting more than 3GB RAM after removing preinstalled bloatware on the latest 2.17.40.12 ROM.
Click to expand...
Click to collapse
great:good:! what is your software for uninstall that?
Used system app remover for removing preinstalled apps
Sent from my ASUS_Z00AD using XDA Free mobile app
Back in business.
Note, if you root and do OTA update after the root, you may end up in a boot loop/soft bricked. Unroot prior to OTA and reroot again after OTA may avoid this issue, but haven't tested yet.
Is this method working for ze500cl also ?
Hi, i have a zenofone 2 ze500cl, will this method work also on my device ?
Neemia86 said:
Hi, i have a zenofone 2 ze500cl, will this method work also on my device ?
Click to expand...
Click to collapse
Hello man. I'd read through this thread: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and see if anyone's ran into any serious complications. If it were me, I'd try it. But be prepared for it to not work out.
Chinaphonearena said:
Note, if you root and do OTA update after the root, you may end up in a boot loop/soft bricked. Unroot prior to OTA and reroot again after OTA may avoid this issue, but haven't tested yet.
Click to expand...
Click to collapse
If you update SuperSU binaries, yes you will bootloop on OTA.
You have two options to update:
1: Unroot > Take OTA > Root
2: Flash Pre-Rooted system.img > Keep root with no unroot needed
Harfainx said:
If you update SuperSU binaries, yes you will bootloop on OTA.
You have two options to update:
1: Unroot > Take OTA > Root
2: Flash Pre-Rooted system.img > Keep root with no unroot needed
Click to expand...
Click to collapse
Even if using the latest SU binaries via this method and then OTA, will end up soft-bricked. The 2nd method can't update binaries. Need to stick with the binaries in the pre-rooted ROM. Either way (1. Unroot, OTA, reroot or 2. Pre-rooted ROM and never update SU) are both solid methods.
Chinaphonearena said:
Even if using the latest SU binaries via this method and then OTA, will end up soft-bricked. The 2nd method can't update binaries. Need to stick with the binaries in the pre-rooted ROM. Either way (1. Unroot, OTA, reroot or 2. Pre-rooted ROM and never update SU) are both solid methods.
Click to expand...
Click to collapse
I have updated my SuperSU and flashed the Pre-Rooted over my current without any problem. No bootloop at all.
The simple method is just like all other devices. If you're rooted, don't take an OTA. Wait for a rooted build.
Harfainx said:
I have updated my SuperSU and flashed the Pre-Rooted over my current without any problem. No bootloop at all.
The simple method is just like all other devices. If you're rooted, don't take an OTA. Wait for a rooted build.
Click to expand...
Click to collapse
You misunderstood, yes if you flash the entire pre-rooted system over it, you will be fine. I was referring to OTA.
Whats simple for some may be a chore for others. You download and flash 1gb to update. If that works best for you, by all means it's a fine way to go.
This one didn't work for me, nor did the other one. The same thing happened as with the other, I get to where I type "T4" and it won't take it. I have already done all the OTAs if that makes a difference.
Anyone know if this method will also work on Asus Memo Pad 7?
kanagawaben said:
Anyone know if this method will also work on Asus Memo Pad 7?
Click to expand...
Click to collapse
I would suggest searching/asking that here: http://forum.xda-developers.com/android/help/qa-intel-android-devices-root-temp-cwm-t2975462
That's the QA thread for the CWM stuff.
Trotter516 said:
This one didn't work for me, nor did the other one. The same thing happened as with the other, I get to where I type "T4" and it won't take it. I have already done all the OTAs if that makes a difference.
Click to expand...
Click to collapse
User error. My bad. I am good now.
This root worked for me!
this method, temporary CWM, can it be used to flash other zip file? such as viper4android-lollipop or gapps flashable zip file?
BTW guys who rooted and in 2.19.40.18, I think you will get bootloop even after update is successfully complete... Please verify if you updated and successfully booted from 2.19.40.18 to 2.19.40.20... I seen 2 of them got bootloop
ansebovi said:
BTW guys who rooted and in 2.19.40.18, I think you will get bootloop even after update is successfully complete... Please verify if you updated and successfully booted from 2.19.40.18 to 2.19.40.20... I seen 2 of them got bootloop
Click to expand...
Click to collapse
I updated mine successfully.
AaronICK said:
I updated mine successfully.
Click to expand...
Click to collapse
So did you rooted and tried?
If yes then thanks.. Now I can confirm them not becoz of the 2.19.40.18..
i'm in bootloop with the circle under asus that continue s running but with adb sideload update was successful.is the same after factory reset too.
ansebovi said:
So did you rooted and tried?
If yes then thanks.. Now I can confirm them not becoz of the 2.19.40.18..
Click to expand...
Click to collapse
Yup. I am rooted before. I just unfreeze system apps and bloatware first, then remove xposed (no need to remove the xposed modules; they will not work if xposed is not installed), then unroot via SuperSU, and finally performed system update. After the update, I root my phone again, then install xposed again, then finally freeze system apps and bloatwares again.
delete Xposed and unroot
Then sideload OTA
working fine
29y6145 said:
delete Xposed and unroot
Then sideload OTA
working fine
Click to expand...
Click to collapse
i uninstalled root,busybox but i forgot to uninstall xposed and i stuck in bootloop.i think i have to reflesh pre root 2.19.40.18.
for my fortune i had twrp and i did a backup of whaat twrp calls "data" in microsd and then i copied in my pc.save files of games are in ?
NOTE NOTE:
I update ok 2.19.40.20
BUT then i flash twrp and flash super suV2.46 ..........hic hic bootllop
i dont understand
i dont understand... Everywhere people are saying to un-root first....As i remember last time we got a new one click root tool which allowed us to update via OTA without un-rooting... Will confirm if un-rooting is necessary or root can survive the OTA.
FW 2.19.40.20
Use TWRP flash super SU =>>> zenfone 2 bootlop
Use tools http://forum.xda-developers.com/zenfone2/general/zenfone-2-root-easy-t3114003
Root okie and work very good
Okay guys i updated to the latest fw NOW I CAN CONFIRM UN-ROOTING BEFORE APPLYING OTA IS NOT NECESSARY... here is what i did:
NOTE: ROOT SURVIVES OTA AND THERE ARE NO BOOTLOOPS ... BUT REMEMBER I USED THE LATEST 1 CLICK ROOT TOOL WHICH ALLOWS US TO APPLY OTA WITHOUT UN-ROOTING...IF U HAVE ROOTED YOUR PHONE VIA DIFFERENT METHOD U HAVE TO UN-ROOT FIRST......
1) Unfrozed all the frozen apps
2) Un-installed Xposed....
3) Un-installed BusyBox
4) Applied OTA
5) And Voila i was on the latest firmware...
Hi there
mhp1995 said:
Okay guys i updated to the latest fw NOW I CAN CONFIRM UN-ROOTING BEFORE APPLYING OTA IS NOT NECESSARY... here is what i did:
NOTE: ROOT SURVIVES OTA AND THERE ARE NO BOOTLOOPS ... BUT REMEMBER I USED THE LATEST 1 CLICK ROOT TOOL WHICH ALLOWS US TO APPLY OTA WITHOUT UN-ROOTING...IF U HAVE ROOTED YOUR PHONE VIA DIFFERENT METHOD U HAVE TO UN-ROOT FIRST......
1) Unfrozed all the frozen apps
2) Un-installed Xposed....
3) Un-installed BusyBox
4) Applied OTA
5) And Voila i was on the latest firmware...
Click to expand...
Click to collapse
Exactly what I did. But gave me an error while flashing.
After reboot there was a message and still on .18. :-/
I rooted with the latest root tool (3rd option). I did apply OTA withouth unfreezing apps and I had no problem with my phone. Everything is working and took no more than 2-3 minutes to complete.
hardwarechaos said:
Hi there
Exactly what I did. But gave me an error while flashing.
After reboot there was a message and still on .18. :-/
Click to expand...
Click to collapse
did u modify some system files? Un-installed any bloatware by any chance?
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
gurusux said:
I rooted with the latest root tool (3rd option). I did apply OTA withouth unfreezing apps and I had no problem with my phone. Everything is working and took no more than 2-3 minutes to complete.
Click to expand...
Click to collapse
Without UN-FREEZING you got no bootloops or anything rite? This is nice :good: finally this is what i was looking for... i hate un-freezing bloatware regularly as Asus has been providing regular updates it just adds to the steps for updating...
Hi
just xposed, but removed before ota.
bloatware was just frozen and unfrozen before.
But I think the whole thing is a bit f*cked up now. Tried to clear cache in recovery and now am in bootloop
mhp1995 said:
did u modify some system files? Un-installed any bloatware by any chance?
Click to expand...
Click to collapse
mhp1995 said:
did u modify some system files? Un-installed any bloatware by any chance?
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
Without UN-FREEZING you got no bootloops or anything rite? This is nice :good: finally this is what i was looking for... i hate un-freezing bloatware regularly as Asus has been providing regular updates it just adds to the steps for updating...
Click to expand...
Click to collapse
No i didnt. I have to say that I didnt freeze everything Asus put on my phone but just what I dont use. I could give you a list but I'm pretty sure its not gonna make a difference. 3rd root tool works with OTA w/o unfreezing bloatware. At least for me.
hardwarechaos said:
Hi
just xposed, but removed before ota.
bloatware was just frozen and unfrozen before.
But I think the whole thing is a bit f*cked up now. Tried to clear cache in recovery and now am in bootloop
Click to expand...
Click to collapse
I am not sure but maybe it happened because of busybox... There are some applets or sumthing which modify/add files to the system and system/bin folder....
---------- Post added at 07:19 PM ---------- Previous post was at 07:16 PM ----------
gurusux said:
No i didnt. I have to say that I didnt freeze everything Asus put on my phone but just what I dont use. I could give you a list but I'm pretty sure its not gonna make a difference. 3rd root tool works with OTA w/o unfreezing bloatware. At least for me.
Click to expand...
Click to collapse
:good: i am sorry but this is off-topic....did u or someone install Xposed framework latest build (official alpha3 version)... i am having issues with installation... can someone help me with xposed latest build (official alpha3)
Sorry guys,
I lied. :-/
Fastboot flashed the recovery after bootloop, rebooted into it. Cleared cache again (which now worked) and sideloaded the update an that complains by verify.
Turns out I did indeed turn on sw navbar in the build....prop.
Gonna revert the changes there and try again to update.
THX & MEA CULPA
what i've done :
i Left on my phone : busybox and frozen apps
just :
removed xposed
removed supersu
apply OTA
install Root
install xposed
also my bootloader still unlocked
Done.
So is it a little bit lottery to flash ota, any one tried to download ota file to phone and flash it from recovery automatically?
Wysłane z mojego ASUS_Z00AD przy użyciu Tapatalka
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Mlight123 said:
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Click to expand...
Click to collapse
Sadly, I just joined your club!! lol I wanted to comment here incase anyone else can help us or if I manage to figure it out myself I can find this thread easily. I got it rooted with newest version of Kingroot too, then I used Supersume to update to SuperSU and everything was working fine. When I tried rebooting, same thing as you I presume, I get kernel is not se enforcing I think it said and got the dreaded Unauthorized software was found running on this device, please take to att for service.
Sorry I can't help with your current problem. But, did you ever try to reboot with the kingroot SU?
This is definitely a slippery slope with no installation image.
moonbutt74 said:
Reboot to recovery, connect to pc and via adb shell , do a manual unroot.
that usually consists of
adb shell mount /system
adb shell rm /system/xbin/su
adb shell rm -fr /system/bin/.ext <----.ext is a directory
adb shell ls -al /system/bin/app_*
lrwxrwxrwx root root 2014-06-30 09:42 app_process -> /system/xbin/daemonsu
lrwxrwxrwx root root 2014-06-30 09:42 app_process32 -> /system/xbin/daemonsu <---remove this symlink
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process32_original <---- rename to app_process32
-rwxr-xr-x root shell 73508 2008-08-01 08:00 app_process32_xposed <------ not there if you don't have xposed
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process_init
Then search /data/app /system/app and /system/priv-app and remove the offending apk's base directory.
m
Click to expand...
Click to collapse
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Mlight123 said:
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Click to expand...
Click to collapse
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Shocked...
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Mlight123 said:
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Click to expand...
Click to collapse
Glad to hear it worked for you mate! Sadly, it didnt for me. I do have good news of my own though, I was able to have my wife take it by the local Best buy store and after they tried the normal factory reset and such, he must have had an Odin flashable 5.1.1 file or something because the tab is back to working order.
That is how I knew I was in trouble after I rebooted the first time after installing Kingroot and Supersume Pro. I also got the red lettered "Kernel is not SEandroid enforcing in top left corner too, but the next thing I saw was the " Unauthorized software detected, please power off and take to ATT ". I don't think I ever even made it to the samsung screen if my memory is correct (It might not be! lol) It sounds like either kingroot or SuperSU left something behind after install maybe? If you go to Settings > About tablet > Status and scroll all the way to bottom, the last entry says custom as well correct? The unlocked padlock on boot just means Syscope is detecting something not official installed somewhere it normally shouldn't be.
I just kept to odin folder and boot(LP_fix).tar on my pc because despite getting stuck in a boot loop you lose root after you fix it so it's kind of like a tethered root lol
Guys Iam having this same problem but I don't speak computer lingo can another walk be though step by step so I can fix my tablet?
Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
I had this same problem, I just ended up giving up, exchanging tablet for a new one. :c
Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
That's exactly the problem i had. But when i took it to best buy, they said that, their software cannot read my tablet, because of "an abnormal software has been found on this device" its probably because my tablet is custom...Any Fixes?
Can't you guys boot to download mode and flash the stock files via odin?
wp4jot said:
Can't you guys boot to download mode and flash the stock files via odin?
Click to expand...
Click to collapse
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
How about this?
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
wp4jot said:
How about this?
http://forum.xda-developers.com/showpost.php?p=65481346&postcount=606
Click to expand...
Click to collapse
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Definitely worth trying. It's a bricked phone and there's nothing to loose.
thisisapoorusernamechoice said:
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Click to expand...
Click to collapse
wp4jot said:
Definitely worth trying. It's a bricked phone and there's nothing to loose.
Click to expand...
Click to collapse
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
thisisapoorusernamechoice said:
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Click to expand...
Click to collapse
wp4jot said:
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
Click to expand...
Click to collapse
I figured, no worries, just didn't want to confuse anyone else :good:
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.