I've been hacking on this on and off for days. Success. Basically the solution is a bait and switch.
I've tried so many things, this is recalled from memory and the following steps may be incomplete. I used the latest of ES File Explorer. SuperSU, etc.
Get angguesss' update.zip here: http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21 . Rename it to update zip and keep it safe.
Make sure you know how to root, get the proper Intel drivers, Phone Flash Tool Lite, etc.
OVERVIEW:
What is being done here is to prime the 7840 for an update by downloading the stagefright fix with a rooted device and swapping out that fix with angguesss' older update.zip. It's like starting over. Upon reboot the 7840 updates to angguesss' older update cleanly, paving the path for the stagefright fix to update successfully.
Special thanks to angguesss, Social Design and everyone who unknowingly provided little pieces of knowledge here and there.
CAUTION:
You might brick, wipe, lose root, lose customizations, void warranty, get frustrated, look at the device hatefully and all the standard caveats, no guarantees. Do at your own and the device's risk.
HERE IT IS:
This is the BAIT part:
1. Root the 7840
2. Download the stagefright patch (DO NOT REBOOT)
3. In an editor: Go To \data\data\com.dell.systemupdateota
4. Copy the patch somewhere safe (extsd, for example, just in case)
5. Review the properties of the update.zip in the com.dell.systemupdateota
6: Note permissions of RW- --- --- and the owner/group "u0_a29"
This is the SWITCH part:
7. Copy over to \data\data\com.dell.systemupdateota angguesss' update.zip here while renaming it update(1).zip
8. Change the permissions and owners of the update(1).zip to match the update.zip
9. Delete the downloaded update.zip (the stagefright download)
10. Rename update(1).zip to update.zip. angguesss' update will now be the update!
11. In \system\app delete the supersu folder (containing the supersu.apk)
12. in \data\data delete the eu.chainfire.supersu data folder
13. Press the on/off button, select reboot
14. Let the 7840 reboot
15. After a few seconds the 7840 will "figure out" there is an unused update and begin to shut down.
16. Wait out the shutdown (mine took about five minutes).
17. The tablet will begin to update in the usual fashion (Andy, the progressing blue line)
18. Let the update finish and allow to boot to completiton.
19. Go to settings->about tablet->update and download (yes, again) the stagefright fix.
20. Install, reboot (wait...) and upon reboot let the update proceed as normal. Should be no errors.
21. Hopefully, you now have a Stagefright updated 7840 5.1
Some steps may be unnecessary, redundant, etc. Now off to check out some things. Update later.
UPDATES:
The Dell Stylus still appears to work.
First attempt at re-rooting failed, TWRP recovery did not load/display.
Second attempt at re-rooting but using CWM worked. SuperSU installed.
There are still low level speaker "clicks" at boot time.
Update and clarifications to instructions steps 6, 12, 13
Hey, thanks for posting this. I am trying to accomplish the same thing you have done.
I followed your guide up through number 16, but the tablet never reboots and there is never any update screen.
If I boot up by pressing the power button I am still on 5.1 and the stagefright update still fails for me...
Is this a problem you encountered?
On step 16 I waited quite awhile and waited and waited. I was tempted to bail out but didn't. It might have been ten minutes.
TonyBigs said:
First attempt at re-rooting failed, TWRP recovery did not load/display.
Second attempt at re-rooting but using CWM worked. SuperSU installed.
There are still low lever speaker "clicks" at boot time.
Click to expand...
Click to collapse
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Mistype in row 12: not /data , its /data/data
Thanks, trying it now
Not worked for me, still error while flashing stagefrigt patch
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
toxic_garden said:
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Click to expand...
Click to collapse
Rerooting using the venue_7840_droidboots using 1-502 then using IntelAndroid-FRBL-07-24-2015 selecting CWM and then T4. That was just my choice after installing the update to see what would happen and how the process would run, if at all. The main goal, however, was to get the stagefright fix installed.
toxic_garden said:
thanks for the informations. But there's one thing i don't understand: how did you root afterwards? For my understanding, the only way to boot CWM is to revert to 5.0.1 boot.img. But then the stagefright update is completely screwed up....
Click to expand...
Click to collapse
olvrick said:
Mistype in row 12: not /data , its /data/data
Thanks, trying it now
Not worked for me, still error while flashing stagefrigt patch
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
Click to expand...
Click to collapse
Thank you for the response, I'm in the process of trying the process all over again. Maybe I missed something.
Successful again. Note changes to steps 6, 12, 13
Today when updating from 5.0.1 to 5.1 I'm not sure what happened but I ended up with the stragefright ota also installed. At least I think it is. System update is no longer finding any available updates. I did lose root. The strangest part was that I was having trouble updating to 5.1 until I booted into tethered TWRP (Have only used cwm on this device in the past when flashing first 5.1 update). First time trying to boot into TWRP I just got a black screen after leaving the bootloader and having the white text populate on screen. Second attempt though TWRP loaded up and immediately began running a script, or flashing the update I suppose. Tablet rebooted automatically and I haven't lost any data. Everything works fine so far. How can I determine if the latest stagefright has been installed?
TonyBigs said:
Rerooting using the venue_7840_droidboots using 1-502 then using IntelAndroid-FRBL-07-24-2015 selecting CWM and then T4. That was just my choice after installing the update to see what would happen and how the process would run, if at all. The main goal, however, was to get the stagefright fix installed.
Click to expand...
Click to collapse
but the stagefright fix also comes with a new boot.img, so only part of the update is installed when you revert to 5.01 boot.img afterwards. :\
toxic_garden said:
but the stagefright fix also comes with a new boot.img, so only part of the update is installed when you revert to 5.01 boot.img afterwards. :\
Click to expand...
Click to collapse
I understand, so don't rerun the rooting process. It's the user's choice of what to do next after returning the 7840 back to a non-rooted state that will accept OTA fixes and updates.
TonyBigs said:
This is the BAIT part:[...]
This is the SWITCH part:
Some steps may be unnecessary, redundant, etc. Now off to check out some things. Update later.
Click to expand...
Click to collapse
i had some time on my hands today and tried it out by myself. You can in fact shorten the process pretty much.
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Obviously, you'll lose root with that and there's no option for the moment to regain it. Using the old method via 5.01 bootimg isn't something i would recommend. But for me, a fully functional and up to date system is more worth than a buggy rooted system.
toxic_garden said:
i had some time on my hands today and tried it out by myself. You can in fact shorten the process pretty much.
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Obviously, you'll lose root with that and there's no option for the moment to regain it. Using the old method via 5.01 bootimg isn't something i would recommend. But for me, a fully functional and up to date system is more worth than a buggy rooted system.
Click to expand...
Click to collapse
Does ambient display or Intel Sensing Assist work on your device? They've stopped working on mine since I updated and rooted. Would be willing to give up root to get that feature back.
jamebarron88 said:
Does ambient display or Intel Sensing Assist work on your device? They've stopped working on mine since I updated and rooted. Would be willing to give up root to get that feature back.
Click to expand...
Click to collapse
They both work fine. I can't say how it was before, because I never used Sensing Assist in the past. But for now, it works.
toxic_garden said:
Just copy the 5.1 update and the stagefright-update images to a local folder on your pc. Then boot to stock recovery and chose "apply update from ADB". Open a command window and use adb to first "adb sideload \path\to\your\update 5.1.img", reboot, again boot to recovery and adb sideload the stagefright fix the same way.
Click to expand...
Click to collapse
Do you have a link to a source for both the update 5.1.img as well as the stagefright image? All I have been able to find is the 5.01 update. I am in the same predicament, currently on 5.1, but even after removing root before my first attempt applying the Stagefright fix, the update fails. I have done a couple factory resets, but now the screen is constantly freezing, making the tablet unusable.
Thanks!
wayne710 said:
Do you have a link to a source for both the update 5.1.img as well as the stagefright image? All I have been able to find is the 5.01 update. I am in the same predicament, currently on 5.1, but even after removing root before my first attempt applying the Stagefright fix, the update fails. I have done a couple factory resets, but now the screen is constantly freezing, making the tablet unusable.
Thanks!
Click to expand...
Click to collapse
Yes where can we find the source. And how do we get to stock recovery if already rooted and used cwm tethered recovery.
first of all, here the links.
stagefright update -> http://forum.xda-developers.com/showpost.php?p=64183381&postcount=9
5.1 update -> http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15
Dell System restore files -> http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
5.01 system.img, boot.img and tools -> http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4
What i've done so far, coming from a complete messed up installation. Just to be sure: if you need some data from your current installation, back it up to external SD first. Obviously, this procedure will wipe everything you got on it.
- copy 5.01 system.img mentioned above to the SD card. Also the stagefright fix and 5.1 update.
- use the Phone Flash Tool to flash flash-DDO_BB.xml from Dell's Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip. This will put the Tablet back in a flashable and clean state. (1)
- boot to CWM (1)
- open adb shell and dd the system.img to the tablet. (1)
- reboot to fastboot (1)
- install the boot.img via fastboot (1)
- boot to Android for getting the system up at least once (don't know if it's neccessary, but i just did it to be sure everything works fine)
- boot to CWM
- via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
- install the 5.1 update via CWM from SD-Card
- boot to Android to see if everything's fine
- now boot to REGULAR recovery. You'll see just the Android robot with no commands or whatever. Don't get confused by that. You'll have to press the power- and volume up button together twice. I always need 5-6 tries, but after some time you'll see the stock recovery menu.
- select "update from ADB sideload"
- for some reason, i had to install the 5.1 update again via sideload to get the stagefright fix working. So open a command window and "adb sideload <name of 5.1 update>.zip" to the device
- right after that, sideload the stagefright fix the same way
- reboot
-voilá
(1) those steps are already described in detail here: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
As much as i love the build quality and overall design of the tablet, keeping it software-sides running really is a pain. But at least for now, i got a running, up to date 5.1 w/ stagefright and for the last few days, no issues like crackling sound or random reboots occoured. Yay!
toxic_garden said:
first of all, here the links.
stagefright update -> http://forum.xda-developers.com/showpost.php?p=64183381&postcount=9
5.1 update -> http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Dell System restore files -> http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
5.01 system.img, boot.img and tools -> http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4
What i've done so far, coming from a complete messed up installation. Just to be sure: if you need some data from your current installation, back it up to external SD first. Obviously, this procedure will wipe everything you got on it.
- copy 5.01 system.img mentioned above to the SD card. Also the stagefright fix and 5.1 update.
- use the Phone Flash Tool to flash flash-DDO_BB.xml from Dell's Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip. This will put the Tablet back in a flashable and clean state. (1)
- boot to CWM (1)
- open adb shell and dd the system.img to the tablet. (1)
- reboot to fastboot (1)
- install the boot.img via fastboot (1)
- boot to Android for getting the system up at least once (don't know if it's neccessary, but i just did it to be sure everything works fine)
- boot to CWM
- via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
- install the 5.1 update via CWM from SD-Card
- boot to Android to see if everything's fine
- now boot to REGULAR recovery. You'll see just the Android robot with no commands or whatever. Don't get confused by that. You'll have to press the power- and volume up button together twice. I always need 5-6 tries, but after some time you'll see the stock recovery menu.
- select "update from ADB sideload"
- for some reason, i had to install the 5.1 update again via sideload to get the stagefright fix working. So open a command window and "adb sideload <name of 5.1 update>.zip" to the device
- right after that, sideload the stagefright fix the same way
- reboot
-voilá
(1) those steps are already described in detail here: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
As much as i love the build quality and overall design of the tablet, keeping it software-sides running really is a pain. But at least for now, i got a running, up to date 5.1 w/ stagefright and for the last few days, no issues like crackling sound or random reboots occoured. Yay!
Click to expand...
Click to collapse
Thanks toxic_garden, as due to your input, I now have an up-to-date tablet that is not constantly freezing as well as the Stagefright update. I simply ADB sideloaded the 5.1 OTA over the messed up 5.1 system already on my tablet. Shortly after rebooting, the Stagefright update downloaded and successfully updated. I did use the 5.1 update posted by xBIGREDDx (Thank you!) at http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15, rather than the link shown in the quoted post above. Unless I messed up somehow, I believe the link shown above for the 5.1 update points to a link for 5.0.1. Anyway, I think I am not going to root this tablet again as long as it is on 5.1.
wayne710 said:
Thanks toxic_garden, as due to your input, I now have an up-to-date tablet that is not constantly freezing as well as the Stagefright update. I simply ADB sideloaded the 5.1 OTA over the messed up 5.1 system already on my tablet. Shortly after rebooting, the Stagefright update downloaded and successfully updated. I did use the 5.1 update posted by xBIGREDDx (Thank you!) at http://forum.xda-developers.com/showpost.php?p=61985130&postcount=15, rather than the link shown in the quoted post above. Unless I messed up somehow, I believe the link shown above for the 5.1 update points to a link for 5.0.1. Anyway, I think I am not going to root this tablet again as long as it is on 5.1.
Click to expand...
Click to collapse
you're right, i should correct that in my description. Glad it worked for you. Personally, i only used root for removing McAffee and installing AdBlock. Well, McAffee is just frozen for now and adblocking happens on the router, so no big loss for the moment. The only thing i might miss is Titanium Backup. Helium does a good job, but is in no way comparable to the mighty power of Titanium. ^^
Link to 5.1 OTA is broken=( Cant open link, just gray circle on the screen
via adb, delete all traces of root (delete /data/data/eu.chainfire.whatever folder as well as /system/app/SuperSU folder)
Seriously? why not make a normal guide for those who havent done it before?
olvrick said:
Link to 5.1 OTA is broken=( Cant open link, just gray circle on the screen
Click to expand...
Click to collapse
seems like mega has some issues at the moment. Just drop me a PM if it's still broken in 1 hour or so, then i'll upload the zip somewhere else
Related
This guide details how to update HDX Nexus ROM from version 1.4.x to 2.0.1.
Please read through this carefully to familiarise yourself with the process before attempting the upgrade.
STEP 0: Requirements / File Downloads
- Download the .3.1.0 stock file for your device
- Get Safestrap 3.75 B02 for your device
- Get Towelroot
- ROM links will be in the usual place
- .3.2.4 update.bin for your device
STEP 1: Introduction
- Use Safestrap to backup your /data partition if you wish to keep you settings from HDX Nexus ROM
- If you already have .3.1.0 installed on stock ROM then go to step 3
- If you are running HDX Nexus ROM in stock then go to step 2
STEP 2: Install .3.1.0
- Flash .3.1.0.zip
- From safestrap perform a Factory reset
STEP 3: Enable updates
- If you have used an OTA update blocker script please undo the changes to re-enable ota updates
- If you installed the .3.1.0.zip from STEP 1 then do the following:
- From safestrap main menu press Mount and select "System"
- From safestrap main menu press Advanced->File Manager
- From safestrap rename /system/etc/security/otacert.old to otacert.zip
- From safestrap rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
- reboot
- The screen will go black for about 10-20 seconds then you should see the grey and orange kindle fire logo
STEP 4: Upgrade to .3.2.4
- When the device has booted select your language settings and press next
- On the wifi settings page, do NOT connect, instead select the complete setup later option
- For Thor copy update-kindle-13.3.2.4_user_324002120.bin to the root of your sdcard
- For Apollo copy update-kindle-14.3.2.4_user_324002120.bin to the root of your sdcard
- On your kindle go to Settings->Device->System Updates
- The screen should show the update is ready to install
- Press the Update button
- The kindle will then validate the update, reboot and install the update
STEP 5: Obtain Root
- Use towel root
- Towel root requires you to be connected to the internet, so as soon as you have obtained root disable your internet connection.
STEP 6: Install Safestrap
- Use Safestrap-Thor-3.75-os3.2.4-B02.apk or Safestrap-Apollo-3.75-os3.2.4-B02.apk
STEP 7: Install HDX Nexus 2.0.1
- Reboot to safestrap
- Flash HDX Nexus ROM 2.01
- Flash Gapps 1.2
- Factory Reset
- Restore your /data partition if you did a backup from STEP 1
- Reboot
- The screen will go black for about 10-20 seconds and then the boot logo will appear
- And finally - Enjoy!
Delete plz
Starting with 13.3.2.2
ggow said:
This guide details how to update HDX Nexus ROM from version 1.4.x to 2.01.
Please read through this carefully to familiarise yourself with the process before attempting the upgrade.
STEP 0: Requirements / File Downloads
- Download the .3.1.0 stock file for your device
- Get Safestrap 3.75 B02 for your device
- Get Towelroot
- ROM links will be in the usual place
STEP 1: Introduction
- Use Safestrap to backup your /data partition if you wish to keep you settings from HDX Nexus ROM
- If you already have .3.1.0 installed on stock ROM then go to step 3
- If you are running HDX Nexus ROM in stock then go to step 2
STEP 2: Install .3.1.0
- Flash 13.3.1.0.zip
- Factory reset
STEP 3: Enable updates
- If you have used an OTA update blocker script please undo the changes to re-enable ota updates
- If you installed the .3.1.0.zip from STEP 1 then do the following:
- From recovery main menu press Mount and select "System"
- From recovery main menu press Advanced->File Manager
- From recovery rename /system/etc/security/otacert.old to otacert.zip
- From recovery rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
- reboot
- The screen will go black for about 10-20 seconds then you should see the grey and orange kindle fire logo
STEP 4: Upgrade to .3.2.4
- When the device has booted select your language settings and press next
- On the wifi settings page, do NOT connect, instead select the complete setup later option
- For Thor copy update-kindle-13.3.2.4_user_324002120.bin to the root of your sdcard
- For Apollo copy update-kindle-14.3.2.4_user_324002120.bin to the root of your sdcard
- On your kindle go to Settings->Device->System Updates
- The screen should show the update is ready to install
- Press the Update button
- The kindle will then validate the update, reboot and install the update
STEP 5: Obtain Root
- Use towel root
- Towel root requires you to be connected to the internet, so as soon as you have obtained root disable your internet connection.
STEP 6: Install Safestrap
- Use Safestrap-Thor-3.75-os3.2.4-B02.apk or Safestrap-Apollo-3.75-os3.2.4-B02.apk
STEP 7: Install HDX Nexus 2.0.1
- Reboot to Safestrap
- Flash HDX Nexus ROM 2.01
- Flash Gapps 1.2
- Factory Reset
- Restore your /data partition if you did a backup from STEP 1
- Reboot
- The screen will go black for about 10-20 seconds and then the boot logo will appear
- And finally - Enjoy!
Click to expand...
Click to collapse
Thanks a bunch for all your fantastic efforts. Just need to know the procedure if I'm starting with 13.3.2.2 (1.4x ROM not installed). Would I start from step 4 (upgrade to 13.3.2.4, etc., and then flash the HDX Nexus 2.01 ROM)? Thanks.
lennV said:
Thanks a bunch for all your fantastic efforts. Just need to know the procedure if I'm starting with 13.3.2.2 (1.4x ROM not installed). Would I start from step 4 (upgrade to 13.3.2.4, etc., and then flash the HDX Nexus 2.01 ROM)? Thanks.
Click to expand...
Click to collapse
Correct, start from Step 4
ggow said:
Correct, start from Step 4
Click to expand...
Click to collapse
im factory resetting in safestrap, correct? Im on nexus 1.4.3 on stock slot.
holeshot77 said:
im factory resetting in safestrap, correct? Im on nexus 1.4.3 on stock slot.
Click to expand...
Click to collapse
Hi holeshot77,
Yes, correct, from Safestrap...
Done! Worked like a charm. All is well again. Nervousness passed. Good Job Ggow.
As for the this website.. the damn ads are horrible..ridiculous on how many there is and all the damn popups..
holeshot77 said:
Done! Worked like a charm. All is well again. Nervousness passed. Good Job Ggow.
As for the this website.. the damn ads are horrible..ridiculous on how many there is and all the damn popups..
Click to expand...
Click to collapse
Excellent, glad you're up and running again
If your running Chrome then try installing the AdBlock extension - generally makes all web pages much better.
ggow said:
Excellent, glad you're up and running again
If your running Chrome then try installing the AdBlock extension - generally makes all web pages much better.
Click to expand...
Click to collapse
Read the upgrade post if I am on 1.4.3 can I just boot into recovery wipe and then install 2.0.1 or do you need to go through all of the upgrade steps. Thanks again for the ROM has been great to finally use my hdx like it was meant to be used.
Sent from my Optimus G using XDA Free mobile app
You need to follow the upgrade guide because it's the only way for locked devices to get onto the newer 3.2.4 kernel.
Sent from my Xperia Z using Tapatalk
Having a little problem
ggow said:
Correct, start from Step 4
Click to expand...
Click to collapse
I had originally rooted my HDX with the rom toolkit v.94 and installed Safestrap 3.75. Created a recovery, etc. Everything worked fine. In order to upgrade from 13.3.2.2 to 13.3.2.4 I did this: (1) turned on OTA using toolkit, (2) turned off wifi, (3) uninstalled recovery, (4) uninstalled safestrap, (5) copied the update rom to the root directory of sdcard, (6) went to "device-system updates" and got the "No Network Connection" message. (Same story after a reboot). Looks like it's not seeing the update rom in the root directory (It's there because I can see it with ROM Toolbox). Please let me know what I'm doing wrong. Thanks.
lennV said:
I had originally rooted my HDX with the rom toolkit v.94 and installed Safestrap 3.75. Created a recovery, etc. Everything worked fine. In order to upgrade from 13.3.2.2 to 13.3.2.4 I did this: (1) turned on OTA using toolkit, (2) turned off wifi, (3) uninstalled recovery, (4) uninstalled safestrap, (5) copied the update rom to the root directory of sdcard, (6) went to "device-system updates" and got the "No Network Connection" message. (Same story after a reboot). Looks like it's not seeing the update rom in the root directory (It's there because I can see it with ROM Toolbox). Please let me know what I'm doing wrong. Thanks.
Click to expand...
Click to collapse
Hi lennV,
1. Did you reboot after enabling OTA?
2. You may also need to do a factory reset if point 1 doesn't work.
ggow said:
Hi lennV,
1. Did you reboot after enabling OTA?
2. You may also need to do a factory reset if point 1 doesn't work.
Click to expand...
Click to collapse
I didn't reboot originally but I did toggle OTA on and off before rebooting after failure. No difference but I'm not sure if I haven't already messed things up by doing that.
Ok, now I've done a factory reset. Btw does a factory reset erase what was in the root directory (where I had copied the update)? If so I guess I'd have to re-root so that I can flash that update rom back in the root?
lennV said:
I didn't reboot originally but I did toggle OTA on and off before rebooting after failure. No difference but I'm not sure if I haven't already messed things up by doing that.
Ok, now I've done a factory reset. Btw does a factory reset erase what was in the root directory (where I had copied the update)? If so I guess I'd have to re-root so that I can flash that update rom back in the root?
Click to expand...
Click to collapse
If I understand correctly: You are still on 3.2.2 and you have factory reset?
If so, no need to root yet, you should copy the 3.2.4 update to the root of your sdcard and check for updates.
ggow said:
If I understand correctly: You are still on 3.2.2 and you have factory reset?
If so, no need to root yet, you should copy the 3.2.4 update to the root of your sdcard and check for updates.
Click to expand...
Click to collapse
That's correct. I'm still on 3.2.2 after factory reset. Ok, I'm a bit of a novice in this environment. I was thinking of "root" as the physical directory called "root" on the HDX. That's why I was wondering if I should re-root so that I can have access to it. But I think you're talking about something else. How do I copy the 3.2.4 update to the HDX? Do I just copy from the PC to any directory on the sdcard?
lennV said:
That's correct. I'm still on 3.2.2 after factory reset. Ok, I'm a bit of a novice in this environment. I was thinking of "root" as the physical directory called "root" on the HDX. That's why I was wondering if I should re-root so that I can have access to it. But I think you're talking about something else. How do I copy the 3.2.4 update to the HDX? Do I just copy from the PC to any directory on the sdcard?
Click to expand...
Click to collapse
copy it from the PC to the root of the sdcard - i.e. /sdcard
ggow said:
copy it from the PC to the root of the sdcard - i.e. /sdcard
Click to expand...
Click to collapse
This is what I did from the PC: adb push update-kindle-13.3.2.4_user_324002120.bin /sdcard/update-kindle-13.3.2.4_user_324002120.bin
I used adb shell to check that the file is there. It is.
However, I'm still getting the "No Network Connection" message. There must be something really basic that I've missed.
lennV said:
This is what I did from the PC: adb push update-kindle-13.3.2.4_user_324002120.bin /sdcard/update-kindle-13.3.2.4_user_324002120.bin
I used adb shell to check that the file is there. It is.
However, I'm still getting the "No Network Connection" message. There must be something really basic that I've missed.
Click to expand...
Click to collapse
I've never experienced that issue so don't know how much help I can be on this, is that error showing up on the software update page?
For manual update it looks like your doing the right things...
Check if /system/etc/security/otacert.zip and /system/app/com.amazon.dcp.apk exist.
ggow said:
I've never experienced that issue so don't know how much help I can be on this, is that error showing up on the software update page?
For manual update it looks like your doing the right things...
Check if /system/etc/security/otacert.zip and /system/app/com.amazon.dcp.apk exist.
Click to expand...
Click to collapse
Yes, it shows up after I go to the "check now" tag from the "System Updates" window. Thanks, anyway. I'll check the other stuff shortly. Much appreciated.
---------- Post added at 05:43 PM ---------- Previous post was at 05:30 PM ----------
ggow said:
I've never experienced that issue so don't know how much help I can be on this, is that error showing up on the software update page?
For manual update it looks like your doing the right things...
Check if /system/etc/security/otacert.zip and /system/app/com.amazon.dcp.apk exist.
Click to expand...
Click to collapse
Hmm! Would this be the problem? The "otacert.zip" file is there but the other one isn't. The file that's there is "com.amazon.dcp.apk.otablock"! Is that supposed to be there?
lennV said:
Yes, it shows up after I go to the "check now" tag from the "System Updates" window. Thanks, anyway. I'll check the other stuff shortly. Much appreciated.
---------- Post added at 05:43 PM ---------- Previous post was at 05:30 PM ----------
Hmm! Would this be the problem? The "otacert.zip" file is there but the other one isn't. The file that's there is "com.amazon.dcp.apk.otablock"! Is that supposed to be there?
Click to expand...
Click to collapse
Yes, rename "com.amazon.dcp.apk.otablock" to "com.amazon.dcp.apk" and reboot
Then try again...
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
It looks like T-Mobile has updated the rom again. Does anyone have an extract which they can upload?
https://support.t-mobile.com/docs/DOC-28482
It appears as if sammobile already has it???
http://www.sammobile.com/firmwares/confirm/99757/G900TUVS1GPI1_G900TTMB1GPI1_TMB/
SurfinMobile77 said:
It looks like T-Mobile has updated the rom again. Does anyone have an extract which they can upload?
https://support.t-mobile.com/docs/DOC-28482
Click to expand...
Click to collapse
Here is an unmodified reupload of the new update straight from sammobile
https://mega.nz/#!5tNjRITJ!tjVgleABN53tmqFwmT9T9mSE_qZ8exIwxpoBVAFNvcw
In the process of updating my encrypted G900T, will post the necessary Odin flashable Protected Partitions once I have extracted them and hopefully not bricked my phone in the update process.
SimLynks said:
Here is an unmodified reupload of the new update straight from sammobile
https://mega.nz/#!5tNjRITJ!tjVgleABN53tmqFwmT9T9mSE_qZ8exIwxpoBVAFNvcw
In the process of updating my encrypted G900T, will post the necessary Odin flashable Protected Partitions once I have extracted them and hopefully not bricked my phone in the update process.
Click to expand...
Click to collapse
Thanks SimLynks, were you able to extract the constituent files and post them (bootloader and modem)?
SurfinMobile77 said:
Thanks SimLynks, were you able to extract the constituent files and post them (bootloader and modem)?
Click to expand...
Click to collapse
Got the files, finally posting them here now. Please go to my AndroidFileHost SM-G900T folder to grab the flashable files. https://www.androidfilehost.com/?w=files&flid=121594
Contains the OTA Update ZIP, and the two Odin Flashable TAR files.
To update your rooted/encrypted G900T to the latest OTA without needing to flash the full ROM update file, download the three files from the link posted above, and follow these steps:
1) Install Chainfire's FlashFire if you dont have it already and grant it root permissions.
Download the OTA Update to YOUR DEVICE ITSELF, Run FlashFire, and Hit the Red "Plus" -> Use either "Flash Firmware package" OR "Flash ZIP or OTA" options, find the OTA ZIP downloaded to your device and let FlashFire do it's thing.
NOTE: DO NOT LET FLASHFIRE UPDATE YOUR BOOTLOADER/MODEM these are the "Protected Partitions" and are Locked while booted into your "Custom" ROM by Samsung after it detects you've been rooted. FlashFire documentation explains this in a bit more detail.
2) Download the TAR files to the computer you will be running Odin from, and Restart your Galaxy S5 in Download Mode (Turn device off -> Hold Power Down + Home + Power)
3) Flash the TAR archives in Odin, standard way is Open Odin, connect phone in download mode (should be detected by Odin) hit the "AP" button and UNCHECK "Auto Reboot" if you want to be able to flash both the Bootloader and the Modem without the Device rebooting automatically after the first flash.
Once you have flashed BOTH the Bootloader and the Modem, go ahead and restart your device, you should now have an updated Kernel (OTA Package in FlashFire, Updated Bootloader/Modem from Odin) and be good to go even with Root/Xposed/Encrypted enabled and TWRP that cannot decrypt the Data partition with Samsung Encryption.
SimLynks said:
Got the files, finally posting them here now. Please go to my AndroidFileHost SM-G900T folder to grab the flashable files. https://www.androidfilehost.com/?w=files&flid=121594
Contains the OTA Update ZIP, and the two Odin Flashable TAR files.
To update your rooted/encrypted G900T to the latest OTA without needing to flash the full ROM update file, download the three files from the link posted above, and follow these steps:
1) Install Chainfire's FlashFire if you dont have it already and grant it root permissions.
.
Click to expand...
Click to collapse
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
tsh said:
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
Click to expand...
Click to collapse
TSH, seems like you did this correctly (or at least you have the same build info I have on my own device) only thing that appears different is my TWRP does not throw the SEANDROID Not Enforcing message, BUT thats somewhat irrelevant anyway as from what i've read from the TWRP Devs, that message is just "hidden" with the newest release of TWRP, so the Recovery is not SEANDROID Enforcing, but they remove the error message on the newest builds.
Also can you confirm what version of TWRP your running? Latest build is 3.0.2-2 (and is what im running without the SEANDROID message you have). At one point I had a "custom" build of TWRP with version I think 3.0.2-3 but the dev of that custom build eventually pulled the files as the official 3.0.2-2 had been updated past the custom build notwithstanding the conflicting build numbers.
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1. The important thing to check for the the Kernel build DATE, which should now be "Mon Sep 12". My Security Patch Level is "July 1, 2016" not May 1 so im not sure how that mismatch has happened. Please try to run the OTA from TWRP and let me know what happens. This is the first time i've ever tried to update using the OTA file directly so might have missed a step or forgotten I flashed with FlashFire then to double ensure I updated correctly updated in TWRP also before using Odin to flash the rest.
Additionally, when I first updated to this OTA a few days ago, ran the Zimperium Stagefright testing and passed 100%, However when I reran the test after reading your post, as has become my expectation with Stagefright and Samsung "patches" it now fails again, because Zimperium is constantly updating the test to include the newest found bugs with Stagefright...so the GPI1 Kernel is patched for any Stagefright bugs as-of Sep 12, but the Zimperium people seem to constantly find new bugs with this damn library...So we need to wait for the next OTA patch to only have the Stagefright testing fail again a week later once Zimperium has updated the tests to include the neverending Stagefright bugs.
I really need to run the Stagefright testing on my friend's Nexus which is running Nougat and was the first device in a while i've seen pass 100%, might have same issues there but I have not checked yet.
Yep, latest TWRP 3.0.2.2... I was able to get the security notification to stop by uninstalling the Samsung security log system app. Still can't pass the stagefright test... I get 12 critical and 45 high vulns testing with Zimperium v5.3
Something definitely not right... Afraid I may just bite the bullet and do a complete wipe and install fresh.
Sent from my SM-G900T using XDA Free mobile app
tsh said:
Yep, latest TWRP 3.0.2.2... I was able to get the security notification to stop by uninstalling the Samsung security log system app. Still can't pass the stagefright test... I get 12 critical and 45 high vulns testing with Zimperium v5.3
Something definitely not right... Afraid I may just bite the bullet and do a complete wipe and install fresh.
Click to expand...
Click to collapse
Right, I mean a full wipe / restore will definitely fix the issue no doubt, but before you try that you can always do the "full" ROM update using the same method as I previously posted, just replace flashing the OTA from FlashFire, with flashing the full ROM Update and follow all the other steps. Also make sure FlashFire has "Everroot" Checked and I entirely disable flashing "Protected Partiions" in settings, so there is no "unchecking" anything, FlashFire does that automatically.
OTA or Full ROM release, FlashFire still cant safely deal with the "protected partitions", but this is how prior to attempting to use the smaller OTA file, I have been updating my rooted/xposed/encrypted G900T from release to release, the downside to the full update is that after flashing everything you get to wait for the ROM to rebuild the cache, reboot to TWRP and reflash SuperSU and if using Xposed reflash that as well and then again wait for the system to rebuild as Xposed does it's thing on the first boot after install.
I also did not think to consider that my heavily "trimmed" System Apps might have an effect on this, I use Titanium Backup & Greenify immediately after install to outright freeze all the bloatware or Greenify things the system needs to function properly, but I don't want running all the time. When I get a chance Im going to update my friend's G900T using my method and try to figure out this discrepancy between what worked for me, and what is clearly giving you some issues. Until then i'd appreciate any further feedback you can give me so I can revise the process to eliminate any potential trouble spots. Sorry to keep spamming you with all this unnecessary info, but until I can post my own thread on this stuff im just kinda throwing everything I've got here so the info is somewhere.
As for the Stagefright issue, I just reran the Zimperium Stagefright testing again on my up-to-date G900T as well as a Galaxy S3 I'm running the latest nightly Exodus ROM release on (Google Release r68, Android Security Patch Date September 6, 2016, Kernel Build Date Oct 6, 2016) and BOTH devices now fail the Stagefright testing again, after previously passing for about a week or so...This is just how it works with Stagefright unfortunately, they patch it until more bugs are found, rinse repeat.
So no matter what it seems, your gonna fail Stagefright even if on an incredibly recent Build/Kernel. My last test for this needs to be if Nougat also now fails as well, because if so, then it's just another round of the Stagefright party as standard, since they first announced this back in July 2015.
tsh said:
I tried your steps, now have Baseband at TUVS1GPL1 but Build is still TUV1GPE1 and the stagefright scans still show the vulns. Also show "Android security patch level: May 1,2016" Here's what I tried:
1. did flashfire using the OTA method, rebooted. Did not update bootloader. Didn't seem like anything happened.
2. Used Odin to flash modem and bootloader. Rebooted.
3. Tried FlashFire again using the "Flash Firmware" method. Booloader items were greyed out, but left the boot.img item checked. This went through an update process.
Rebooted and checked stagefright, still fails the vulns. Just got a notifications pop-up saying "Device Seurity, threat found. Unauthorized actions have been detected, restart to undo changes." I'm assuming this is knox kicking in somehow. Now just get "Recovery is not SEANDROID enforcing" and boots straight into TWRP ... hmm.
Click to expand...
Click to collapse
You need to flash a firmware package containing a system/system.img. stagefright are system libs. If you want that fix you need to just go ahead and flash the entire firmware. Only thing is tho, stagefright has never been 100% fixed
SimLynks said:
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1.
Click to expand...
Click to collapse
I don't believe that is correct, after flashing the complete OTA (without wiping) both my baseband and build are showing GPI1. Baseband is G900T3UVS3GPI1, build is MMB29M.GT900T3UVS3GPI1. Kernel is 3.4.0-7500527. There's no longer any GPG2 reference on my phone.
Flashed the firmware from scratch. I ran a debloater and openvpn don't work. Running Windows and I can't seem to open system.img.ext4. Can someone check this firmware to see if there is a vpndialogs.apk inside? Need this to get vpn working again.
djy said:
Flashed the firmware from scratch. I ran a debloater and openvpn don't work. Running Windows and I can't seem to open system.img.ext4. Can someone check this firmware to see if there is a vpndialogs.apk inside? Need this to get vpn working again.
Click to expand...
Click to collapse
yes, I can find vpndialogs.apk under priv-app
Could you please post it for me, along with the target path? I can't get ext2explore.exe to open the image.
djy said:
Could you please post it for me, along with the target path? I can't get ext2explore.exe to open the image.
Click to expand...
Click to collapse
Please follow the instructions in this thread
http://forum.xda-developers.com/android/help/android-dat-img-file-unpack-repack-2-0-t3309285
SimLynks said:
TSH, seems like you did this correctly (or at least you have the same build info I have on my own device) only thing that appears different is my TWRP does not throw the SEANDROID Not Enforcing message, BUT thats somewhat irrelevant anyway as from what i've read from the TWRP Devs, that message is just "hidden" with the newest release of TWRP, so the Recovery is not SEANDROID Enforcing, but they remove the error message on the newest builds.
Also can you confirm what version of TWRP your running? Latest build is 3.0.2-2 (and is what im running without the SEANDROID message you have). At one point I had a "custom" build of TWRP with version I think 3.0.2-3 but the dev of that custom build eventually pulled the files as the official 3.0.2-2 had been updated past the custom build notwithstanding the conflicting build numbers.
Anyway as to your Build Number still at GPG2 but Baseband at GPI1 that is EXACTLY the same as my device and from what I can tell the correct build numbers you should be seeing. This OTA did not update the "build" it just updated the Kernel/Modem/Bootloader to GPI1. The important thing to check for the the Kernel build DATE, which should now be "Mon Sep 12". My Security Patch Level is "July 1, 2016" not May 1 so im not sure how that mismatch has happened. Please try to run the OTA from TWRP and let me know what happens. This is the first time i've ever tried to update using the OTA file directly so might have missed a step or forgotten I flashed with FlashFire then to double ensure I updated correctly updated in TWRP also before using Odin to flash the rest.
Additionally, when I first updated to this OTA a few days ago, ran the Zimperium Stagefright testing and passed 100%, However when I reran the test after reading your post, as has become my expectation with Stagefright and Samsung "patches" it now fails again, because Zimperium is constantly updating the test to include the newest found bugs with Stagefright...so the GPI1 Kernel is patched for any Stagefright bugs as-of Sep 12, but the Zimperium people seem to constantly find new bugs with this damn library...So we need to wait for the next OTA patch to only have the Stagefright testing fail again a week later once Zimperium has updated the tests to include the neverending Stagefright bugs.
I really need to run the Stagefright testing on my friend's Nexus which is running Nougat and was the first device in a while i've seen pass 100%, might have same issues there but I have not checked yet.
Click to expand...
Click to collapse
Hi!
I think your method fails to update the build. FlashFire doesn't patch anything, (build number still show GPG2)
This is what I do:
Restore original boot from my GPG2 clean install (boot is unpatched)
Restore stock recovery (through ODIN)
(2 previous steps avoid status 7 error while applying OTA updates)
Flash OTA update .zip through stock recovery
Reinstall TWRP custom recovery
Reroot Applying superSU.zip method
Wipe Dalvik / cache
Reboot
After 10 minutes everytihng working!
I'm uploaded a screenshot with the results
I think triyng to apply OTA updates with any workaround is possible whenever system partition is reasonably stock, because OTA updates patch files, not replace files
My system was just rooted and 2 battery stats helpers installed. I think with xposed installed the above steps must work. But with other tweaks more complex OTA updates with no stock system will fail
That's similar to what I did, but without the need to restore data since you flashed the stock recovery without flashing the system by the sound of it. Can you explain exactly which images you flashed for boot & stock recovery? I'm thoroughly confused over what's what, since everybody seems to use different jargon to mean the same thing.
invisiblewave said:
I don't believe that is correct, after flashing the complete OTA (without wiping) both my baseband and build are showing GPI1. Baseband is G900T3UVS3GPI1, build is MMB29M.GT900T3UVS3GPI1. Kernel is 3.4.0-7500527. There's no longer any GPG2 reference on my phone.
Click to expand...
Click to collapse
Was your phone rooted? AFAIK, We cannot apply OTA update with boot or recovery modified
My phone was rooted I restore stock recovery and boot and apply OTA, And I didn't lose my data or installed apps
Reyse said:
Was your phone rooted? AFAIK, We cannot apply OTA update with boot or recovery modified
My phone was rooted I restore stock recovery and boot and apply OTA, And I didn't lose my data or installed apps
Click to expand...
Click to collapse
yes, it was rooted, I restored the entire image, ran the update, then re-rooted & restored /data. Do you have a link to the stock recovery/boot image? I'd like to do it the same way as you next time.
invisiblewave said:
yes, it was rooted, I restored the entire image, ran the update, then re-rooted & restored /data. Do you have a link to the stock recovery/boot image? I'd like to do it the same way as you next time.
Click to expand...
Click to collapse
I extracted both image from the full update from Sammobile
Follow these instructions
Download 7Zip archive manager http://www.7-zip.org/download.html
Download the full image of your phone from SAMMOBILE
For example my previous phone version was G900TUVS1GPG2_G900TTMB1GPG2_TMB.zip
Open that file with 7zip
it contains G900TUVS1GPG2_G900TTMB1GPG2_G900TUVS1GPG2_HOME.tar.md5
double click to extract
these are the files in the archive
Code:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
cache.img.ext4
modem.bin
boot.img => stock boot
recovery.img => stock recovery
extract both files
Now for each of them:
- right click => 7ZIP => Add to archive...
- it suggest the same name (irrelevant)
- Choose archive format => tar (very important)
- Press Ok
- Flash with ODIN
(don't reboot, turn off and turn on for each flash to avoid boot phone and mess versions)
Source of this instructions: http://howto.highonandroid.com/samsung-tutorials/how-to-extract-stock-recovery-from-samsung-firmware/
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
discussion?
Chaosruler said:
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
Click to expand...
Click to collapse
Interesting, was this an issue with the WW-5.17.44.68 update or has this been an ongoing issue? I didn't bother with the previous one because it didn't seem to do a whole lot, but never noticed this issue.
Chaosruler said:
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
Click to expand...
Click to collapse
I hate doing this juggle. Big part of why I don't try to update unless it's significant :/
Chaosruler said:
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
Click to expand...
Click to collapse
Thanks for the heads up on this. I check the release thread often in hopes of Oreo, but they don't bother putting this information on their small updates. I think I'll update just because of that really, although Oreo would have been nice too :silly:
Chaosruler said:
discussion?
Click to expand...
Click to collapse
I feel like there's probably only 2 or 3 people who check these forums often nowadays, which is a shame because the phone is quite nice, and even has the bootloader unlocked as well. But ASUS seems to have too many phones that need updates and we're left in the dust waiting. Both XDA and Zentalk forums have people complaining and talking about this being their last device, which is reasonable and align with my thoughts as well. Really though, I want to go and make my own ROM for this phone, but don't really have the time, resources, or experience to tackle it just yet. Maybe I can use it in the future for practice
Update Impressions
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10 but any computer with fastboot installed will work really) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. /u/Ryder. has pointed out the Zentalk forum has the latest recoveries available, so check there first. At the time of writing, I was pushed to login to view that forum, so instead I just grabbed the latest available from AndroidFileHost, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.2.1* from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img). *3.2.1 is available in the Mega. At the time of writing, I only checked the AndroidFileHost link and didn't check to see if there was an updated build for it. It is Oreo compatible, so when they finally get around to giving us Oreo, you'll have a suitable recovery to go along with it. Thanks to /u/Ryder. for the heads up.
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Error when I try to download.
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
asianflipboy said:
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. I just grabbed the latest available, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.1.1 from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img).
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Click to expand...
Click to collapse
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Chaosruler said:
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Click to expand...
Click to collapse
You're right about that. I've updated my post to reflect it.
Chaosruler said:
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Click to expand...
Click to collapse
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Ryder. said:
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Click to expand...
Click to collapse
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
indiana99 said:
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
Click to expand...
Click to collapse
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
asianflipboy said:
You're right about that. I've updated my post to reflect it.
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
asianflipboy said:
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
No. Thank you very much for asking. I downloaded from a different location.
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Good to hear.
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Hmm, I think I'll do that. I'll make some small zip files for each.
---------- Post added at 09:56 PM ---------- Previous post was at 09:16 PM ----------
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Ryder. said:
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
Click to expand...
Click to collapse
Sorry for re-quoting all of you, but do you guys see the update anymore? It might have been why /u/indiana99 couldn't find it. I went to check while making the zip packs and it's not there... Maybe there was some issue with the build? It's got me a bit shook that it's suddenly not on the website.
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Chaosruler said:
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Chaosruler said:
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
indiana99 said:
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Click to expand...
Click to collapse
That's weird to me though. I just checked again and both variants are missing the current update, 5.17.44.87. Did they pull it for some reason? As far as I can tell, my phone is behaving pretty normally. Anyone that's updated notice anything weird?
I've removed the link. This article claims that we're finally getting the update by the end of March!
https://www.phonearena.com/news/Asu...-ZenFone-3-Deluxe-receive-Oreo-March_id103395
Finally!