Database Info

[HOWTO] INSTALL STOCK FIRMWARE USING CWM/TWRP even w/a DEAD USB Port

GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES ​
THIS METHOD APPLYS TO:
ONLY FOR PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES

This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

chasama said:
This really work. Can you write one for unlocking also?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10

Samsugn galaxy s2 GT-I9100 help!!
vincom said:
you have to buy unlock code, and you have to be on stock when entering code, read this http://forum.xda-developers.com/showpost.php?p=28439204&postcount=10
Click to expand...
Click to collapse
i am running on RR Jelly bean rom 3.0.6, suddenly my comp stopped detecting my phone nd now its not detected by any comp!!
wen i connect it only charges but the phone is not recognised!! i want to install stock ics firmware plz help me!

Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.

zgibbyson said:
Hey thanks for the comprehensive list. One question. I can't boot, but I can access recovery. I can access USB, however, I don't have an external sd card. What are my options, besides buying one.
Click to expand...
Click to collapse
use internal if you have usb access to it

thanks

the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.

Re: [HOWTO] INSTALL STOCK ICS USING CWM/TWRP even w/a DEAD USB Port
PhoneTay11 said:
the SD card from my other phone has some folders:.android secure, data; LOST.DIR; DCIM; LGsys.....which folder should I put TWRP2.2.0 & stock firmware in ? which folder is considered A ROOT of the external SD card ? so I can boot the device.I couldn't boot it. I am newbi. please help. Thankss.
Click to expand...
Click to collapse
Don't put it in any folder, just copy to the SD card.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)

PhoneTay11 said:
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
Click to expand...
Click to collapse
that screen is also odin/download mode
try flashing again
check odin troubleshooting section in the "install cwm/twrp" link in my sig

vincom said:
GUIDE TO FLASHING STOCK FIRMWARE FOR ATT AND ROGERS I727 SKYROCKET PHONES WITHOUT USING ODIN OR KIES ​
THIS METHOD APPLYS TO:
PHONES THAT CAN BOOT INTO A CUSTOM RECOVERY CWM/TWRP
USERS WHO CANT USE ODIN AND/OR KIES FOR WHATEVER REASON
PHONES WITH A BAD USB PORT
HAVE USB CONNECTIVITY ISSUES
MAC USERS WITH A CUSTOM RECOVERY ALREADY INSTALLED.
YOU ARE ON A CUSTOM ROM WITH USB PROBLEMS AND NEED TO RETURN TO STOCK FOR WARRANTY REPAIRS
NOTE: USING THIS GUIDE TO RETURN TO STOCK WILL PERMANENTLY UNROOT THE PHONE, BUT CAN BE REROOTED AFTER IF NEEDED.
Disclaimer: I am not responsible for your devices, follow guide at your own risk!
READ THE WHOLE POST
HOW TO ENTER INTO RECOVERY MODE, INSTRUCTIONS HERE STEP #4
GUIDE PRESUMES YOU ALREADY KNOW HOW TO INSTALL/FLASH FILES FROM RECOVERY
YOU NEED TO HAVE ONE OF THE RECOMMENDED CUSTOM RECOVERIES ALREADY INSTALLED ON THE PHONE SUCH AS CWM OR TWRP, LINKS IN THE DOWNLOAD SECTION BELOW
IN THIS GUIDE YOU WILL BE INSTALLING THE STOCK FIRMWARE ZIP FILE
OPTIONAL: INSTALLING THE STOCK RECOVERY ZIP FILE ONLY IF YOU NEED TO RETURN FOR WARRANTY, OTHERWISE NOT RECOMMENDED TO INSTALL
GETTING THE STOCK FIRMWARE TO YOUR PHONE
OPTION 1: IF YOUR ABLE TO BOOT INTO ANY ROM:
YOU HAVE A WORKING USB CONNECTION:
Download the files and transfer the files from your computer to your internal or external sdcard
YOU DONT HAVE A WORKING USB CONNECTION: USE EITHER METHOD "A" OR "B" OR "C":
METHOD A: From the phone use xda app or browser and navigate to this page and download the files directly to your device from the links provided below, then move them to the root of your internal or external sdcard, it will make it easier to find.
METHOD B: Use airdroid wirelwss appor kies air to transfer your files from your computer to your phone through your wifi connection and place them in the root of your internal or external sdcard
METHOD C: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
OPTION 2: YOUR NOT ABLE TO BOOT BUT CAN GET INTO A CUSTOM RECOVERY: USE EITHER METHOD "A" OR "B":
METHOD A: If usb port works: enable usb mount in custom recovery and transfer files to the root of your sdcard
METHOD B: If usb port doesnt work: use an external sdcard reader/writer or another phone that has a micro sdcard slot and transfer files from your computer to the root of the external sdcard, then insert the sdcard back into the phone.
FLASHING THE FILES
FIRMWARE
ENTER INTO RECOVERY MODE
PERFORM A RESET AND WIPE BOTH CACHES
INSTALL THE STOCK FIRMWARE ZIP FILE
ONLY INSTALL THE STOCK FIRMWARE(NOT THE STOCK RECOVERY ZIP FILE) THEN REBOOT THE PHONE INTO ANDROID TO CHECK IF IT BOOTS PROPERLY
YOUR GOOD LIKE THIS IF YOU JUST WANTED STOCK BACK ON YOUR PHONE
STOCK RECOVERY: ONLY RECOMMENDED IF RETURNING FOR WARRANTY REPAIR AND NEED TO SHOW FULL STOCK
TO GET THE STOCK RECOVERY ZIP FILE ONTO THE SDCARD FOLLOW THE INSTRUCTIONS FOR THE FIRMWARE GUIDE ABOVE
ENTER INTO RECOVERY MODE
INSTALL THE STOCK RECOVERY ZIP FILE, ONCE YOU DO THIS YOU WILL LOSE THE CUSTOM RECOVERY
IF YOU CANT USE ODIN THERE IS NO WAY TO REINSTALL A CUSTOM RECOVERY ON THE SKYROCKET ONCE THE STOCK RECOVERY HAS BEEN INSTALLED.
REBOOT PHONE INTO RECOVERY TO SEE IF THE STOCK RECOVERY FLASHED PROPERLY.
DOWNLOADS
MOVED TO THE 1STOP STICKY
USE CWM/TWRP FLASHABLE FIRMWARES
Click to expand...
Click to collapse
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.

ntd0626 said:
Do you have the Stock ROM for GB 2.3.6 (SkyRocket) which i can flash using TWRP? My PC doesn't recognize my Skyrocket. The only way for me is to flash using TWRP but I can't find the GB ROM for it. There's a lot of ROM of GB but it is for ODIN (with extension .tar.md5) instead.
Click to expand...
Click to collapse
no, why do u need gb, just flash the ics or jb roms, or if your usb is not dead go through the odin trouble shooting section in the restore to stock sticky to try to solve the connection issue, link to restore to stock is in my sig

Stock Rom Android M.
Hi, could you help me i have TWRP Custom recovery and cm12.1 android lollipop, i want to
Flash Stock Rom Android Marshmallow using TWRP is it possible using this method ,
my Device is Galaxy Tab S 8.4 wi-fi.

invalid zip
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.

champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
AFAIK all devhosts files are bad/fake, i cant even dl my own files.
if i find them all reup to androidfilehost

Stock Rom
champagne_problems said:
I am a mac user without access to a PC (no odin). I have TWRP recovery installed. I used android file transfer to move the stock firmware zip in the download section to the internal SD (root folder). I wiped the system and cache, then install zip - but it fails every time with "invalid zip file format". I have tried a half dozen other versions of the stock ROM from various sources and they all fail with the same error. ZIP signature verification is disabled. Just when I thought that i was doing something completely dumb and not flashing correctly at all - I tried re-flashing the lineageOS ROM i have and that worked fine. I've read a bit about unpacking and re-zipping these zips to get them to work, but that requires 7zip (which I don't have on mac). Help! am I doing something dumb or do I not have the correct zip files? I really need to get back to stock so I can activate my cellular service.
Click to expand...
Click to collapse
Just use "Flashfire" and do everything from your phone no need for a computer.

Using this to flash 1.7 gb file
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?

ParaSpl01t said:
I have a moto g5s plus (sanders) and have installed unofficial lineage 15.0 build. before installation , I didn't took backup in TWRP. Now i am downloading stock firmware zip file. can that be installed using TWRP?
Click to expand...
Click to collapse
you mean this zip file when you unzip it show you 5 files that you can use with Odin?

I tried and says fail , why would tarp fail to flash a stock firm ?

Can I flash twrp from goomanager?

I have a 8013. I need to put in a different recovery and I like twrp. has anyone flashed it from goomanager? I see that there is one on there I just dont want to mess something up.
Already rooted.
I would search for this but I cant find a search button. Really not in the app or on the website.
Sent from my GT-N8013 using xda app-developers app

Let me see...
eggwardo said:
I have a 8013. I need to put in a different recovery and I like twrp. has anyone flashed it from goomanager? I see that there is one on there I just dont want to mess something up.
Already rooted.
I would search for this but I cant find a search button. Really not in the app or on the website.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Hmm... When I read here: Goomanager so there is function for flash recovery. But if I don't get wrong, so this recovery files must be on www.goo.im server. Theoretically all ROMs, MODs and RECOVERY files lying on goo.im server
you can download to your device and flash it!
But for me and if I want to flash something, the best way is: Flashify
Here is it TOP 11:
1 - Flash boot and recovery .img without even needing to go to recovery.
2 - Flash zip files. Option to wipe cache, dalvik and data when using TWRP or Philz recovery.
3 - Download and flash CWM, Philz, TWRP, Gapps, Franco Kernel, Stock Nexus Kernel (premium), and Stock Nexus Recovery (premium).
4 - Automatic Loki Patch when needed.
5 - Full nandroid backups/restores when using TWRP or Philz recovery.
6 - Backup/Restore kernel and recovery using Sdcard or cloud (Dropbox, Box (premium) or Google Drive (premium)).
7 - Automatic cloud synchronisation of backups between devices and desktops.
8 - Keep track of recently flashed items.
9 - Flash multiple files and build your flash queue.
11 - Flash from anywhere! Do you want to flash from your favorite File Explorer or Email app? No biggie, that also works together with Flashify.
More at links above!
Have great Flashing :victory: Peter

I have an 8013 as well that I acquired used. it was pre-rooted, but the custom recovery on it didn't work for newer roms. I looked into installing TWRP and found that although the official TWRP instructions said you could install it from GooManager, when I tried to, it didn't find a recovery for the device.
I did successfully get TWRP installed quite easily using their alternate instructions, though. here's a quick breakdown, especially since their instructions are a bit vague.
1. download the .img file for the recovery from here: http ://teamw.in /project/ twrp2/110 (remove the spaces; I can't post outside links yet.)
2. in either terminal emultor or through adb shell, run the command shown below, replacing the bracketed sections with the path and filename of the .img file:
dd if=/<File path>/<filename>.img of=/dev/block/mmcblk0p6
For example, say you save it in your downloads folder on the internal sd card. The path is probably something along the lines of /storage/sdcard0/Download/openrecovery-twrp-2.7.0.0-gt-n8013.img
If you get the path or filename wrong when you runthis command, it will just tell you that it could not find the file you told it to write. if you get the second part wrong, however, you could brick your device, so make sure you double and triple check that part.
Another good check to do before running the command is to ensure that your download is not corrupt by checking the md5 checksum. To do this, make sure you copy that when you download the file and then check using a file browser that supports it. I use Explorer (by Speed Software) to check the md5. To see it, long press the file and click properties. If the one given when you downloaded it and and the one you get from the file do not match, your download likely got corrupted and you should try again until they do match. It's rare, but you don't want to flash a corrupted recovery, so do check it.
The command itself can either be run from an app like terminal emulator or over adb (android debug bridge) from your computer using the command:
adb shell <command>
I followed this basic procedure and now have a fully functioning TWRP recovery on my 8013. Best of luck to you in getting yours working. :good:

Newb Warning - I softbricked my P3110

I started experimenting with my old P3113 last night and ran into a bit of a problem. I successfully rooted using Odin 3.09, verified with root checker. I also successfully flashed TWRP 2.8.7.0 via Odin. All root and TWRP install/flashes were successful via Odin.
Following these instructions: http://forum.xda-developers.com/gal...m-dhollmen-lollipop-5-0-2-2015-02-02-t3020849
I downloaded the Dhollmen-P31xx-Kernel_20150215.zip and saved to the Download folder on the tab. From TWRP I ran a wipe and installed the .zip. I reboot the device and I am returned to TWRP recovery. TWRP tells me that the installation was successful however the log says "no MD5 file found". Does this have anything to do with why my device isn't booting properly? I've rooted other devices and flashed ROM's before but I don't understand what I missed on this one. Do I just need to try a different ROM? For reference I am still able to access download menu.
Any help would be appreciated!

Well, the "no MD5 file found" just means TWRP cannot verify the MD5 hash of the ZIP file - that's actually a security meassure to ensure the ZIP file didn't get damaged during download or transfer onto the tab.
Now ... once you flashed TWRP (which you obviously already successfully did) and flashed the Kernel (which you obviously also already successfully did) it would be about time to flash the actual Dhollmen ROM that goes along with the Kernel ... I doubt the Kernel will boot up your vanilla Samsung stock ROM.
In short (haven't read the ROM thread nor did I ever use Dhollmen, so check back to make sure it's about right): Download the ROM, download the GApps package for the ROM and download the Superuser package (if not already included in the ROM) of your choice. Put the files onto either a FAT32 formatted SD card (if you can't put them into the NAND "SD card" partition at the moment) or onto a FAT32 formatted USB stick (given you have a USB-OTG cable), plug it in (if you use a USB stick make sure your tablet is CHARGED!), boot into recovery and flash the files in one go ... ROM, Gapps, SU.
Run a wipe (Data and Cache) when everything is flashed to nuke any left-overs from the Stock ROM and reboot to system.
Keep in mind the first boot can take quite some time ... don't panic if the boot animation "just sits there" for 5<->15 minutes.
Easiest way would be to actually use a ROM that doesn't require a extra Kernel ... like Android-Andi's CyanogenMod 12.1 or Omni ROM 5.1 (use the 3110 versions for your 3113).

Best Method to Re-flash & Re-root Plus Have Internal Storage Working

Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!

bzowk said:
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
Click to expand...
Click to collapse
First off, this isn't Development.
Secondly, I explained to you how to fix this in the very root thread you linked several times.
Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).
Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.
Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).

OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!

bzowk said:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
Click to expand...
Click to collapse
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.
And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.
P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.

Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks

bzowk said:
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
Click to expand...
Click to collapse
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?

Captain_Throwback said:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Click to expand...
Click to collapse
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!

bzowk said:
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
Click to expand...
Click to collapse
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.

Captain_Throwback said:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Click to expand...
Click to collapse
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
4. Flash SuperSU 2.76 zip
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
9. Flash newly packed boot.img to phone using fastboot
10. Enjoy
I really appreciate your help and patience with me!

bzowk said:
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
Click to expand...
Click to collapse
Good so far . . .
bzowk said:
4. Flash SuperSU 2.76 zip
Click to expand...
Click to collapse
I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).
bzowk said:
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
Click to expand...
Click to collapse
Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).
bzowk said:
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
Click to expand...
Click to collapse
Looks good . . .
bzowk said:
9. Flash newly packed boot.img to phone using fastboot
Click to expand...
Click to collapse
TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.
bzowk said:
10. Enjoy
Click to expand...
Click to collapse
Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.
bzowk said:
I really appreciate your help and patience with me!
Click to expand...
Click to collapse
Guess we'll see if it all works out . . .

Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!

bzowk said:
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
Click to expand...
Click to collapse
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.

Captain_Throwback said:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Click to expand...
Click to collapse
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!

bzowk said:
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
Click to expand...
Click to collapse
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go .

bad topic

[ROM] Debloated Asus Zenpad S 8.0 (Z580C/Z580CA) WW Firmware Rom

This is a modded and signed ZIP of the latest Asus rom with all bloatware/junkware removed, dropping the ZIP size from 1.4 GB to only 920MB! It has no added applications/bloatware and has NOT been rooted (can root with SuperSu though). This rom will more than likely not work with OTA updates, but newer versions of the rom will be posted should Asus provide updates, and those should will be dirty flash-able. Picture of the app drawer with clean install: https://i.imgur.com/8xsZj8F.jpg
This modded ROM works fine with both the Z580C and Z5680CA (ROMs are the same ZIP). Currently only the WW firmware is supported, and will ONLY work on devices that already have a WW firmware. Flashing an incorrect firmware that does not match what your device originally had (WW, JP, TW, or CN) will NOT work, and may brick your device. Use caution. Only WW is available at this time.
Note: The ROM is currently stuck at 5.0. It will be unless Asus provides a 6 ROM or and an unlocked bootloader. Don't ask for Marshmallow, I can't do anything about it yet.
Requirements:
Asus Zenpad S 8.0 - Z580CA or Z580C with WW (World Wide) Firmware ONLY.
Micro SDCard - FAT32 Formatted, <= 32GB Size (Larger cards have issues with ClockWorkMod)
Intel Android Devices Root / Temp Recovery Session (Windows or Linux Version)
Latest ZIP file from thread
(Optionally) Latest SuperSU ZIP
(Optionally) Latest XposedFramework ZIP
Full Backups of your data, unless you want to lose it all.
Screenshots: https://i.imgur.com/8xsZj8F.jpg
https://i.imgur.com/4MTCqwo.jpg
https://i.imgur.com/eek03Te.jpg
Links:
Modded Stock Rom: https://drive.google.com/file/d/0B0af6CkRQIYWV3pCbHZnY09zamM/view?usp=sharing (sha1sum: 3cbdd3bc52bc486c24d1c2573ac924eb33f9f891)
Intel Android Root Tools:
Windows: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Linux: http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Latest SuperSU Stable: http://forum.xda-developers.com/showthread.php?t=1538053
Latest XposedFramework (sdk22, x86 Version): http://forum.xda-developers.com/showthread.php?t=3034811
Instructions:
Steps:
1.) Place all flashable ZIP files on the FAT32 formatted SDCard (Rom ZIP, SuperSU, and Xposed). Leave the card on your desk/table for now, do not install into tablet yet.
Note: If you have the tablet encrypted, you should factory reset it using stock recovery before moving on to step two. CWM doesn't do a good job of erasing encrypted /data and claimed it was still encrypted after the clean install, and required another reset.
2.) Use the Intel Boot/Recovery tools to boot CWM. Follow the instructions at their pages to do this. You must use Method #2.
3.) Completely format /cache /system, and /data. /cache make take some time, it took nearly 15 minutes, /system took about 2 minutes, and /data about 1 minute. DO NOT CLOSE CWM OR REBOOT.
4.) Pug in Micro SDCard, and install your flashable ZIPs from your external SDCard.
5.) WIPE CACHE AGAIN. Just /cache. It shouldn't take as long as the first time, but this MUST be done, or else you will get issues and/or bootloops.
6.) Done. Reboot to system.
I have only modded the stock rom. Credit for the tools and links goes to their respective creators and/or maintainers. I'm just sharing this with others.

lolihunter said:
This is a modded and signed ZIP of the latest Asus rom with all bloatware/junkware removed, dropping the ZIP size from 1.4 GB to only 920MB! It has no added applications/bloatware and has NOT been rooted (can root with SuperSu though). This rom will more than likely not work with OTA updates, but newer versions of the rom will be posted should Asus provide updates, and those should will be dirty flash-able.
It is not compatible with the Z580C at this time. That requires a separate ROM, and I don't have a device to test with. If someone feels like being a little adventurous, I can make a test build for you to play with, and once its good I can upload that as well.
Note: The ROM is currently stuck at 5.0.1. It will be unless Asus provides a 6 ROM or and an unlocked bootloader. Don't ask for Marshmallow, I can't do anything about it yet.
Requirements:
Asus Zenpad S 8.0 64GB/4GB Edition - Z580CA (Not for the Z580C)
Micro SDCard - FAT32 Formatted, <= 32GB Size
Intel Android Devices Root / Temp Recovery Session (Windows or Linux Version)
Latest ZIP file from thread
(Optionally) Latest SuperSU ZIP
(Optionally) Latest XposedFramework ZIP
Full Backups of your data, unless you want to lose it all.
Screenshots: https://i.imgur.com/8xsZj8F.jpg
https://i.imgur.com/4MTCqwo.jpg
https://i.imgur.com/eek03Te.jpg
Links:
Modded Stock Rom: https://drive.google.com/file/d/0B0af6CkRQIYWV3pCbHZnY09zamM/view?usp=sharing (sha1sum: 3cbdd3bc52bc486c24d1c2573ac924eb33f9f891)
Intel Android Root Tools:
Windows: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Linux: http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Latest SuperSU Stable: http://forum.xda-developers.com/showthread.php?t=1538053
Latest XposedFramework (sdk22, x86 Version): http://forum.xda-developers.com/showthread.php?t=3034811
Instructions:
Steps:
1.) Place all flashable ZIP files on the FAT32 formatted SDCard (Rom ZIP, SuperSU, and Xposed). Leave the card on your desk/table for now, do not install into tablet yet.
Note: If you have the tablet encrypted, you should factory reset it using stock recovery before moving on to step two. CWM doesn't do a good job of erasing encrypted /data and claimed it was still encrypted after the clean install, and required another reset.
2.) Use the Intel Boot/Recovery tools to boot CWM. Follow the instructions at their pages to do this. You must use Method #2.
3.) Completely format /cache /system, and /data. /cache make take some time, it took nearly 15 minutes, /system took about 2 minutes, and /data about 1 minute. DO NOT CLOSE CWM OR REBOOT.
4.) Pug in Micro SDCard, and install your flashable ZIPs from your external SDCard.
5.) WIPE CACHE AGAIN. Just /cache. It shouldn't take as long as the first time, but this MUST be done, or else you will get issues and/or bootloops.
6.) Done. Reboot to system.
I have only modded the stock rom. Credit for the tools and links goes to their respective creators and/or maintainers. I'm just sharing this with others.
Click to expand...
Click to collapse
I can test I have the 32gb variant

I just finished installing it and everything seems to be running smoothly. Great job!

I am mighty sure that this is just plain 'ole 5.0 and not 5.0.1 as mentioned. Just to be clear, Cheers and good job!
Edit: Another thought, there are different versions or SKU's of this tablet (WW, JP, TW, CN etc.) that according to ASUS, you cannot install a rom from one SKU to another...... @lolihunter, what SKU version rom did you use? and IMHO, a warning should be added to the OP.

mad4some said:
I am mighty sure that this is just plain 'ole 5.0 and not 5.0.1 as mentioned. Just to be clear, Cheers and good job!
Edit: Another thought, there are different versions or SKU's of this tablet (WW, JP, TW, CN etc.) that according to ASUS, you cannot install a rom from one SKU to another...... @lolihunter, what SKU version rom did you use? and IMHO, a warning should be added to the OP.
Click to expand...
Click to collapse
You are indeed correct. I have edited the post to reflect the correct data. I shouldn't make such an important post when low on sleep.
Also, I am working on a version for Z580C. I actually noticed the file sizes, ZIP names, and descriptions of the stock ROMs for both devices are the same on the Asus website, but have slightly different links. If luck is in favor, the one I am downloading will match the original stock ROM for the Z580CA, meaning they are one and the same. Will update later today with either an edited post or a new separate modded ROM.
If there ends up being enough demand for the other firmwares, I may edit and add those as well.

Cannot connect via ADB and cannot pull files from ExtSD
(Issue Resolved, see below)
Hello,
While attempting to flash my tablet, my CWM session did not seem to recognize my SD card with the files needed to flash.
So, right now, my tablet is:
-In a CWM session (somewhat afraid to restart)
-Unable to read SD cards for some reason (tried two separate SD cards, 4GB and 16GB, both formatted FAT32)
-Without an operating system (/System, /Data, /Cache wiped)
-Is unauthorized by ADB.
Is there anything I can do to fix my tablet? Restart into stock bootloader maybe? Authorize ADB to sideload files (somehow)?
Any help is appreciated,
-Pjb0521
(Forgot to mention, I have the Z580C)

pjb0521 said:
Hello,
While attempting to flash my tablet, my CWM session did not seem to recognize my SD card with the files needed to flash.
So, right now, my tablet is:
-In a CWM session (somewhat afraid to restart)
-Unable to read SD cards for some reason (tried two separate SD cards, 4GB and 16GB, both formatted FAT32)
-Without an operating system (/System, /Data, /Cache wiped)
-Is unauthorized by ADB.
Is there anything I can do to fix my tablet? Restart into stock bootloader maybe? Authorize ADB to sideload files (somehow)?
Any help is appreciated,
-Pjb0521
(Forgot to mention, I have the Z580C)
Click to expand...
Click to collapse
If CWM is failing to detect an SDCard, I would suspect the card itself as being the problem. What OS are you using to format the SDCard? If your are using Windows, try to use disk management to make sure the card is using the GPT partition table instead of MBR. If it is already, use it to initialize it to MBR then back to GPT, and use it to create a single nameless fat32 partition across the whole SDCard.
CWM should automatically mount the card. I didn't need to mount it with mounts and storage, I just plugged it in and tried to install from it, and it automatically showed the files I had copied to it.
This tablet does not allow for pushing or pulling of files with adb, it is always unauthorized. I would imagine this has to do with the locked bootloader, as even in Linux I cannot push the files to it, which is why the guide uses the SDCard.

Nevermind, issue is resolved. Just rebooted into fastboot, restarted the CWM session and installed the ROM. Thanks anyways for your help!

Do you think you can port marshmallow rom for zenfone 2 to zenpad s Z580CA? same hardware

lolihunter said:
This is a modded and signed ZIP of the latest Asus rom with all bloatware/junkware removed, dropping the ZIP size from 1.4 GB to only 920MB! It has no added applications/bloatware and has NOT been rooted (can root with SuperSu though). This rom will more than likely not work with OTA updates, but newer versions of the rom will be posted should Asus provide updates, and those should will be dirty flash-able. Picture of the app drawer with clean install: https://i.imgur.com/8xsZj8F.jpg
This modded ROM works fine with both the Z580C and Z5680CA (ROMs are the same ZIP). Currently only the WW firmware is supported, and will ONLY work on devices that already have a WW firmware. Flashing an incorrect firmware that does not match what your device originally had (WW, JP, TW, or CN) will NOT work, and may brick your device. Use caution. Only WW is available at this time. ....
.....I have only modded the stock rom. Credit for the tools and links goes to their respective creators and/or maintainers. I'm just sharing this with others.
Click to expand...
Click to collapse
Excellent work - much appreciated!
One question - after installing this ROM is it possible to return it back to stock at a later time?

@glaudrem it might be possible to get a marshmallow build ported, but unless we actually get an unlocked bootloader for the device it's really gonna be too much work.
@Angus66 yes, you can just flash the latest stock rom zip from the Asus website in the same way you flashed the modded one. In fact, the only thing I have done to the modded rom is just removed the bloatware from /system/ and repacked it, making clean installs or reinstalls much easier. Just make sure to do a full wipe with CMW should you decide to go back.

Hi, Thanks for your work on this. I have the Z580C and can you tell me the version of superSU that you have verified to work with this rom? I have had problems with older devices and "the latest version of SuperSU" causing bootloops. I currently use version 2.65 which works.
jfoss

Where can I find what firmware version I currently have on my Zenpad S???

Official Marshmallow rom for Z580C/CA is UP!
It has just been discovered that the Portuguese Z580C/CA web page has version 5.4.3 available for download!
This Android version for these ROMs is 6.0, and is for the JP and WW SKUs.
http://www.asus.com/pt/Tablets/ASUS_ZenPad_S_80_Z580C/HelpDesk_Download/

hheeyyy it's the same on the US webpage
ASUS ZenPad S 8.0 (Z580C) Firmware: V5.4.3.0 (for WW SKU version only)
***This version is only for download manually, device wouldn't receive FOTA notification***
Notice：
Note1: Software update to Android 6.0 Marshmallow. Internal storage will decrease slightly after update, suggest backing up data and relocating media file (pictures & video clip) to SD card to reserve enough storage before starting the software update.
Note2: The battery life of device has to be more that 50%. It suggest plug ASUS adapter in order to avoid upgrading failed.
* OS upgrade from Lollipop to Marshmallow
http://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580C/HelpDesk_Download/
gimmie smores

Hey guys,
everything went fine, except that I forgot to erase the cache before rebooting. Now I am stuck in droidboot and I can't get out of there. The only thing that detects the tablet is fastboot, but i can't execute any commands, as it says
Code:
FAILED (remote: command not allowed in this device state)
So I can't start a new temporary CWM session.
Wiping cache or anything else with fastboot does not work either, as it's the same error...
Any suggestions?

Hi!
I have a question:
During this week Asus updated to mm.
Can i do the upgrade if i have installed the debloated version of the firmware? If yes, how? If not, how Can i roll back and get mm?
Thank you very much in Advance.

4k7 said:
Hey guys,
everything went fine, except that I forgot to erase the cache before rebooting. Now I am stuck in droidboot and I can't get out of there. The only thing that detects the tablet is fastboot, but i can't execute any commands, as it says
Code:
FAILED (remote: command not allowed in this device state)
So I can't start a new temporary CWM session.
Wiping cache or anything else with fastboot does not work either, as it's the same error...
Any suggestions?
Click to expand...
Click to collapse
If you installed the MM update, from the tethered recovery, that is the cause of your problem and no one has found a solution, at this point. You can find more discussion on this issue, in the rooting your Zenpad S tablet discussion.
http://forum.xda-developers.com/showthread.php?t=3160422
Sent from my Nexus 6P using Tapatalk

S. Prime said:
If you installed the MM update, from the tethered recovery, that is the cause of your problem and no one has found a solution, at this point. You can find more discussion on this issue, in the rooting your Zenpad S tablet discussion.
http://forum.xda-developers.com/showthread.php?t=3160422
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ah okay, I've just seen the thread. Well, as I still have warranty I handed it back to the store today and they will send it to Asus, so it will either be repaired or I will get a new one.
Thanks anyways.

lolihunter said:
@glaudrem it might be possible to get a marshmallow build ported, but unless we actually get an unlocked bootloader for the device it's really gonna be too much work.
@Angus66 yes, you can just flash the latest stock rom zip from the Asus website in the same way you flashed the modded one. In fact, the only thing I have done to the modded rom is just removed the bloatware from /system/ and repacked it, making clean installs or reinstalls much easier. Just make sure to do a full wipe with CMW should you decide to go back.
Click to expand...
Click to collapse
There is now an official Marshmallow Update from ASUS I am currently running it but its full of bloat, if you could remove bloat again that would be awesome, I just want an AOSP version for this tablet but I don't think I will ever get that. Here is a link to the actual download from the ASUS website: http ://dlcdnetDOTasus.com/pub/ASUS/EeePAD/Zenpad/Z580C/UL-P01M-WW-5.5.0.0-user.zip?_ga=1.264638607.1670638117.1483822798 This is for the Z580C.
I just signed up so I can't post links :crying: but just replace the 'DOT' with a . and the space between the http and ://