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!
Related
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?!
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
octagonPerfectionist said:
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
Click to expand...
Click to collapse
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
livinginavacuum said:
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
Click to expand...
Click to collapse
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
download this: https://android.googleapis.com/packa...L.5cb0c625.zip
install ADB: https://developer.android.com/sdk/index.html (scroll down and download SDK tools only)
and sideload it by following these instructions: http://www.androidcentral.com/how-ma...r-nexus#slide2
note that these instructions were assuming you are on a mac, instead of doing a ./fastboot or ./adb command just type fastboot or adb, no need for the ./
also, you're sideloading the OTA, not flashing the factory image so don't unlock the bootloader and skip the part that talks about flashing the factory images. also iirc once you see the recovery screen with the error looking message, you should press volume-up first then power to bring up the menu? i remember running into a bit of a snag there when i did this last since it says to do it the other way around. anyway hopefully this will update it. if not, you're probably gonna have to flash the factory images, which would need an unlocked bootloader. SO, in case if you do need to unlock the bootloader (which will wipe the device), be absolutely sure to flip that little switch in developer options that allows OEM unlock, otherwise you might be left with a bricked device.
Click to expand...
Click to collapse
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
livinginavacuum said:
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
Click to expand...
Click to collapse
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
octagonPerfectionist said:
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
Click to expand...
Click to collapse
Your first and third link don't seem to work.
doitright said:
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Easier said than done for someone who has no clue. Is there a good youtube video?
livinginavacuum said:
Your first and third link don't seem to work.
Click to expand...
Click to collapse
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
octagonPerfectionist said:
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
Click to expand...
Click to collapse
First one doesn't work! LOL. I'm sure it's not you.
livinginavacuum said:
First one doesn't work! LOL. I'm sure it's not you.
Click to expand...
Click to collapse
haha fml apparently google doesn't like links to the ota zip well anyway just google "nexus 9 ota zip" and it's pretty easy to find.
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
YOU CAN FIND THE FULL G930AUCU8CSA3 FIRMWARE HERE:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
G930AUCU4CRE4 to G930AUCS4CRG5:
Download link: https://drive.google.com/file/d/1MoJ0be2exLMoji2ZURR6tbEiHCqWSszG/view
G930AUCS4CRG5 to G930AUCU4CRI2:
Download link: https://drive.google.com/file/d/1Fdrcy4m49Qtl-__dUE0Etuqmyn8UhYbe/view
G930AUCU4CRI2 to G930AUCS8CRJ2
Download link: https://drive.google.com/file/d/1bhVx5Rt_CTXmG5YQrY5azS10RO3lWj1r/view
G930AUCS8CRJ2 to G930AUCS8CRK1
Download link: https://drive.google.com/file/d/1lepPXVZIiZM4i_VMOUOvDvVHvGY4ifwv/view
G930AUCS8CRK1 to G930AUCS8CRL1
Download link: https://drive.google.com/file/d/1CUJOVWnDsk3LL378vxLO0vp8y3AdQjmr/view
If i helped you don't forget to hit thanks button
G930aucu4cri2
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Juliowwwe said:
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Click to expand...
Click to collapse
Link is UP
thank you very much
thank you very much
New October update is UP
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
lahlah said:
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
Click to expand...
Click to collapse
1.) Turn off the phone. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
2.) Select "Apply update from ADB". You can scroll using the volume buttons and select using the power button.
3.) Make sure you have ADB and the proper drivers installed on your PC:
http://dl.adbdriver.com/upload/adbdriver.zip
4.)Put the firmware in the ADB folder. You can rename it to anything easy to remember like "FIRMWARE".
5.) In the ADB folder, hold SHIFT + right mouse click and choose "Open command window here". Then type the command "adb sideload FIRMWARE" (where FIRMWARE is how you named your file).
6.) Wait patiently.
7.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
samhnky said:
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
Click to expand...
Click to collapse
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
stek-kravari said:
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
Click to expand...
Click to collapse
Awesome! Thank you, thank you!
I actually really like Oreo, just trying to get Oreo and WiFi calling working on my phone (My Office at work fights all day for 1 bar of cell signal), I had hoped that WiFi calling worked in the SM-G930U variant since everyone talked about it running so much better, but alas, it still doesn't support WiFi Calling (Stupid me for thinking it might have had support added recently).
Thank you again
(My Wife is sure to get upset with me once again working on my phone again today... whoops)
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
bnn0 said:
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
Click to expand...
Click to collapse
You mean about G930AUCS8CRJ2 sideload with adb? Im just pulling the update from AT&T servers and uploading it here. I don't know how to make sideload zip. And for the rooting part I don't know if its possible now because the bootloader binary was updated to 8, try to search here on xda and see if you can find root methods for this firmware
new update, check first post
----
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Maury Yarik said:
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Click to expand...
Click to collapse
First you need to install this:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871 (G930AUCS8CRJ2)
Then you need to go from G930AUCS8CRJ2 to G930AUCS8CRK1, G930AUCS8CRK1 to G930AUCS8CRL1 and you will have the latest update.
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Josh13400 said:
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Click to expand...
Click to collapse
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
stek-kravari said:
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
Click to expand...
Click to collapse
I was thinking something like that was possible. I have baseband version G930AUCU4CRB5 Android 8.0.0 on the AT&T Gal S7 as mentioned, I never saw any updates from this version to go up to a newer version or get into regular updates from OTA. 2 issues I would like to also fixed, that came with the manual update to 8.0 oreo on my phone was the HR heart rate sensor on the back by your flash(red LED) always goes off.. And have tried to go to Samsung health and do some settings to turn it off, but seems to show back up eventually. Also, the issue of not having a working LED indicator, works fine when the phone is POWERED off. and charges. But in OS, it won't work, screen off or on bc of the update. If anyone knows how those issues could be fixed and if there is a possible newer update from my baseband mentioned below. And thanks for the response.
HI, Help needed
Hi,
I wanted to check if it is possible to flash the latest Oreo firmware you have here for downloading dirrectly to my samsung s7 that is currently running on 7.0? Current BaseBand is G930AUCU4BQK2
Basically what happened was that i lost all my contacts on my phone, I ended up download Dr.Phone to my laptop, which i used to try and recover my numbers. What i didnt know was that dr.phone rooted my device which has caused me nothing but headaches.
I now want to flash my phone and get updated to oreo and have my phone working normally again. Since dr.phone did whatever it did to my phone I lost use of my finger print scanner, had to disable samsung health as it kept trying to open on its own, my phone is lagging and freezing constantly..
I just want my phone to be normal again and unrooted and updated.
Lastly my phone is an AT&T device, that i bought second hand in Dubai, if i flash stock firmware is it going to carrier lock my device to AT&T again?
Any advice and help with this matter would be greatly appreciated.
TESTED IN INDIAN AND BRAZILIAN DEVICES
https://motoota.lolinet.com/index.p...&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE
FOR MEXICAN USERS
https://motoota.lolinet.com/index.p...&carrier=amxmx&sn=SERIAL_NUMBER_NOT_AVAILABLE
Pre-requisites:
1. Battery 50+%
2. Locked bootloader
How to install ?
Step 1: Place the downloaded zip in internal storage and rename it.
( Indian / Brazilian: Blur_Version.29.11.30.albus.retail.en.US.zip or Mexican: Blur_Version.29.11.31.albus.retail.en.US.zip)
Step 2: Go to settings -> apps -> show system apps
and then give storage permission for Motorola update services.
Step 3: Reboot the phone and then check for update in settings app.
#Youtube video tutorial by Rocha Tech
https://youtu.be/xJO31p4GLmU
(Just watch the video without sound if you understand the language )
#FAQ
1. What about my data after i install this update?
Ans: Your data is safe after installing the update. For more safety, you can backup your data as an additional safety measure.
2. Will this work on my bootloader unlocked device ?
Ans: No, it will not work with bootloader unlocked. You need to flash the Oreo stock rom to be able to flash this on your device.
3. Why my country name is not mentioned for updates ?
Ans: You may try Indian update zip file and if it doesn't work then try the Mexican one.
Credits:
Helton Vezzoni @erfanoabdi
Any info about the build, software channel, etc?
XBrav said:
Any info about the build, software channel, etc?
Click to expand...
Click to collapse
Load it up and tell us.
kewlzter said:
Load it up and tell us.
Click to expand...
Click to collapse
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
XBrav said:
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
Click to expand...
Click to collapse
I tried TWRP (installed) didn't work.
I'll try returning to stock and sideloading tomorrow after work.
Ok, trying the stock way:
1) Reboot into bootloader (Power + Vol Down)
2) Select boot into Recovery.
3) At "No Command" Screen, hold down Power and press Vol Up.
4) Load from SD card, or live dangerously like me and sideload via ADB (Minimal ADB and Fastboot seems to work for me)
Will update once the push is complete.
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Up and running here. Didn't like my original image, but after flushing data, it booted fine. It did say I no longer qualify for updates which seems to be a new thing with Motorola and Pie, but common across other devices too. Either way, it all seems to be working.
victorhbm15 said:
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Click to expand...
Click to collapse
Did it work really..??
Do we need unlocked bootloader or will it work for all..
Currently running Stock Oreo Firmware locked Bootloader.
Trying to sideload via ADB, will post results after completion of process.
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
OldUncle said:
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
My smartphone Model name is XT-1710-10, Dual SIM.
I was successfully able to sideload the Update, with the command
"adb sideload Blur_Version.29.11.30.albus.retail.en.US.zip".
It took around 15 to 18 mins for the sideload process to complete, later the phone restarted and showed the usual Moto loading screen for another 12mins or so, for a moment i thought it was stuck, but no, it successfully completed the update process.
Everything is functioning as usual, i noticed that the placement of signal bar, wifi icons, and battery icons on the top right corner of the screen seem to be not proper.
Same is the case with the arrangement of signal and wifi icons on top right portion inside notification drop down menu, seems to be too close to the screen edge.
Additional features I saw after the update are, 3 finger screenshot, Screenshot editor, Media controls provision inside 'Moto Actions'; Attentive display inside 'Moto display'.
Also the addition of "Digital Wellbeing" inside settings Menu.
---------- Post added at 01:33 PM ---------- Previous post was at 01:17 PM ----------
OldUncle said:
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
It took around 3hrs for me to solve the problem, I am still not clear, what was I doing wrong.
What worked for me somehow was... I properly uninstalled the old ADB installations first vis control panel and then downloaded the latest version of adb i.e adb-setup-1.4.6.exe, and repeated the normal procedure of adb sideload, this time it worked.
I couldn't find an option to enable Android Pie navigation gestures, even in System>Gestures, there is no option.
Do existing TWRP and Magisk root work?
Thanks to everyone who replied with advices :good:
It is my first try to Sidload OTA.
I found out that, I needed the latest OPS27.76-12-25-22/23 stock firmware and I was using OPS27.76-12-25-13.
I fastbooted to the latest but, it didn't work again and I think the reason is that my device is XT1710-11 (Chinese), though I have fastbooted it to RETEU version (Modems preserved) and works fine.
If my guess is correct, that means I need to wait for the fastboot version for Pie
snuk182 said:
Do existing TWRP and Magisk root work?
Click to expand...
Click to collapse
its working great
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
saurav112214 said:
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/albus/official/
Get the firmware you need from that link and then fastboot flash it to your device.
But make sure if this OTA Pie is for your device.
XBrav said:
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
Click to expand...
Click to collapse
I too have an XT1710-09 (Europe, RETEU software channel). Any idea if this firmware will work for me? Thanks!