Related
I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?
Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.
Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.
solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S
Hi,
I'm about to install CM11 (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip) on my Nexus 5, but wanted to be sure I'm not about do something obviously stupid. I tried using the CM Installer, but it said 'firmware not supported'.
I have
- Minimal experience.
- LG Nexus 5, hammerhead
- unlocked and rooted. (it did a factory reset on unlocking)
- Fresh Android 5.1.1 with bootloader version HHZ12h.
- TWRP 2.8.7.1 (took a backup and copied the whole TWRP folder to my laptop), flashed manually using fastboot flash recovery twrp.img.
- Latest TWRP manager installed from Play Store.
- standalone adb and fastboot installed on my Windows 7 laptop. No SDK. 'adb devices' lists the phone when connected.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip is also present in same folder as adb.exe and fastboot.exe.
Questions are:
- Hope this build of CM is compatible with my Nexus 5 & the bootloader version and whatever else there might be compatibility issues.
- How should I do this: According to "official CM installation on Nexus 5 guide" on wiki.cyanogenmod.org it seems like I'm supposed to push the zip file to /sdcard/0, but /sdcard seems to be a link to /sdcard/emulated/legacy, which contains no folder named '0'. Should I create it and put it there?
If you're coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/
Click to expand...
Click to collapse
OR
Given that "cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/", can I just: boot to recovery, click on Install, select the zip file and swipe to flash?
Finally a general query: Is there any reason I have to connect the phone to my laptop and run any adb, fastboot commands except to transfer the zip file from laptop to phone and to boot into bootloader or recovery with fastboot command? I already have TWRP running.
Thanks
Kashyap
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
I don't use cm, but that sounds like the right file. It doesn't matter which location the zip file is on your sdcard as far as I know, I think they've just said /sdcard/0 to make it easy to find from within twrp. Sounds to me like you've covered all your bases, nice to see someone manually flashing a nexus as a start. I'd go ahead and flash the zip, don't forget to factory reset if you're coming from stock. Also, you may want to find a gapps package if you haven't already. Since you seem to have taught yourself the right way, and your PC is setup for fastboot already, it should be easy to flash back to stock/restore under twrp. You don't even need adb to push files to your phone, you can just download them straight to the device. I generally only use my PC for fastboot flashing to stock,or transferring large amounts of data. Good luck, enjoy your nexus - first boot will generally take just long enough that you'll start wondering if its broken.
Thanks for the quick response.
scissors_cut_paper said:
don't forget to factory reset if you're coming from stock.
Click to expand...
Click to collapse
Just curious why?
If i do a factory reset, will it not delete /sdcard/cm-11-20141008-SNAPSHOT-M11-hammerhead.zip? Do I just copy it from laptop to phone after reset and proceed to flashing? Or there is some way to not wipe 'sdcard' during factory reset?
scissors_cut_paper said:
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
Click to expand...
Click to collapse
I did do a TWRP backup, but selected what to backup in the TWRP manager app, there is no option called EFS. Anyway, I'm creating a new using the recovery UI, where there is a check box called EFS. Thanks!
scissors_cut_paper said:
nice to see someone manually flashing a nexus as a start.
Click to expand...
Click to collapse
Didn't know there was any other more automated option/way. , is there? Only thing I knew was the CM Installer, which said the firmware isn't supported. .
scissors_cut_paper said:
Also, you may want to find a gapps package if you haven't already.
Click to expand...
Click to collapse
Yes, I was planning to, but taking it step at a time. .
I was planning to get gapps-kk-20140606-signed.zip from cyanogenmod.org, but lets see. I'll probably post another question here asking which is the compatible one.
Factory reset just wipes data/cache/dalvik, it should leave your sdcard storage intact. Just out of interest,why cm11? KitKat is pretty long in the tooth, and I've always found aosp based ROMs to perform better than cm on nexus 5. The problem with having no gapps will be no access to play store/google account services, so you'll have to get apps from less trustworthy sources.
Worked
Thanks.
It worked fine. Though it was totally useless without either the play store or basic CM apps. Couple of notes:
- After wipe/factory-reset (from TWRP Recovery UI) /sdcard was untouched.
- Installed the ROM using TWRP Recovery UI -> Install -> Select the zip file from /sdcard and swipe.
- CM Installer on Windows 7 laptop worked fine once the CM was installed. But it downgraded the build from Nov to Aug-2014.
- Also CM Installer removed my TWRP and replaced it with CWM. Not happy.
So actually all that's needed is:
- Unlock the bootloader and root.
- Install TWRP Manager
- Try to use the TWRP Manager's "Install TWRP" to install the TWRP Custom Recovery. If that doesn't work then do it manually. Download twrp.img
- Install ADB and fastboot, you don't need the whole 1GB Android SDK. Just search for "ADB Fastboot without SDK".- Enable USB debug, connect the phone and ensure that 'adb.exe devices' prints a device.- fastboot flash recovery twrp.img- Download the ROM zip file you wanna install on the phone itself, no need to involve the laptop.
- Boot into recovery (e.g. using TWRP Manager -> Reboot options) and do what I did above.
Once you've installed Cyanogenmod, DO NOT use CM Installer. This is written in July'2015. May be things would improve in future.
Hi all,
First off, I am not familiar with alot of the technical wording in these forums so I hope that I am able to communicate properly with my issue.
I was not happy with how slow the stock version of this tablet was so I decided to install a custom rom, however, I managed to get to the point of unlocking it but that's about as far as I got out of being overwhelmed with what came next! Here is where I am at:
I am currently on Android version 4.2.1 and my laptop is running Windows 10.
I have downloaded latest TWRP image file and renamed that twrp.img and it is stored in the main root folder of my tablet (SD Card aka Internal Storage). USB debugging has been enabled after I activated the Developer Options.
The custom rom I am looking at is CyanogenMod version 11 which I have downloaded, however it should be noted that on the download page it says that there is no recovery available for this build?? whatever this means? I also downloaded Minimal ADB and Fastboot but when I connect the tablet to the laptop (the tablet connects fine) I type in the command prompt "fastboot devices" but nothing happens.
I am at a point now where do I try to continue with the custom rom? or go back to stock?
Can anyone help with basic instructions please?
Thanks in advance.
Head to the General section and read the Beginners Guide. It's the first sticky, so it's easy to find.
It's your decision which rom you run, but you should give Katkiss LP or Katshmallow a good look.
The latter is the only rom for this tablet that is still under active development.
Sent from my Nexus 5X using Tapatalk
Can I ask questions in this thread with reference to the beginner guide?
Sure. Ask away
Sent from my Nexus 5X using Tapatalk
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
binx77 said:
I managed to now Root the device and when I turn on the device in recovery mode it says the following:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.3.1.14.10-20130601" A03
Starting Fastboot USB download protocol
then it has 3 options - RCK, Android, Wipe Data
I am trying to install 6.0.1 KatKiss Custom Rom (it's downloaded onto the device already)
Thanks
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2688891
As many times as it takes to understand it. :laugh:
In the meantime I will update post #2 a little.
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
binx77 said:
I am not understanding about the installing a recovery. RCK is the stock recovery according to the beginners guide, however it also mentions TWRP.
In order to get KatKiss, what steps do I actually need to do? given where I am currently at?
Click to expand...
Click to collapse
It's all in my Beginner's Guide - you just have to read it:
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery
Click to expand...
Click to collapse
And I gave you the remaining steps in my last post....
Now it's up to you to read and read again. And google terms you do understand. Then read again
After installing a recovery you have to:
Format data
Convert /data to f2fs http://forum.xda-developers.com/tran...p-2-8-t3073471
flash Katkiss, gapps and SuperSU in the same session (follow instructions in the OP of the Katkiss thread)
Click to expand...
Click to collapse
This is where I am up to now as per the beginners guide
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
the error I get says "cannot open twrp" (I renamed the TWRP file that I downloaded) even though this image file has been moved into the fastboot directory on my PC (I downloaded and installed the ADB, Fastboot and Drivers tool)
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
berndblb said:
How did you rename the file? Enable file extensions in Windows Explorer and make sure you did not add a double extension
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I renamed the file just in windows explorer and I can confirm that the file name is twrp.img
That's with file extensions enabled? Do you see the extensions for all the files in that folder or just for TWRP?
BTW, which TWRP version do you try to flash? Downloaded from where?
Sent from my Nexus 5X using Tapatalk
Ok I got past this point, I hadn't added .img to the command prompt.
Now I am in TWRP and attempted to install KatKiss but it came up with "Zip Signature Verification Failed!" Error installing zip file '/sdcard/download/katkiss-6.0_TF700T_026.zip".
It did say that it could not find MD5 file?
I now have 2 options
1 - Wipe Cache/Dalvik
2- Reboot System
Just hit the Home button in TWRP, go back to Install and this time uncheck the box that says "verify zip signature" then flash the rom. It always checks if you have a md5 checksum file, but it doesn't matter if you don't. The flash goes through anyway
Sent from my TF700T using Tapatalk
Excellent, I successfully installed KatKiss 6.0.1!
Thanks for your help mate!
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
binx77 said:
well, I thought I was in the clear until I realised that I hadn't formatted the data (which apparently is why I don't have file manager and other apps).
I have gone back into recovery to format data and re-flash relevant zip files but now the tablet has frozen during formatting with "unable to mount /data/media/TWRP/.twrps" and also "Failed to Mount '/data' (invalid argument)
Click to expand...
Click to collapse
You got it resolved?
Katkiss Marshmallow - Can't run Goggle Services/Play
I converted my TF7000T from 4.2.1 to KatKiss Marshmallow, using TWRP Manager on the installation end. Steps included boot access, rooting, wiping/formatting and flashing. Marshmallow functions fine. My problem is that I can't get Google Play or Google Services to run. I tried one installation that was a 'moderate' Gapps installation. It was completely unstable despite some of the apps actually updating. I then repeated the wipe and reinstall of KatKiss-026 and Android 6.0.1 with a minimal Gapps installation - just Google Play Store and Google Play Services. Google Play Services flashes constantly that it is not working. I am also not able to log into my Google Play Store account. I'm afraid I have an outdated version of Google Play. However, I cannot figure out a way to update Play Store or Play Services. Does anyone have a solution to this problem? If I could download a minimal Gapps zip that contained either the current, or update-able version of these two apps, I would also be in business. Help!!
You are running the wrong gapps package I think. You need to install the pico gapps and only the pico gapps package that is linked in the KatKiss OP.
And you have to flash rom, gapps and Supersu(if you want root) in the same recovery session together in that order. Every time. You cannot just flash a gapps package on MM rom anymore.
ROM, pico gapps, supersu - reboot
Oh - and to start out with I'd highly recommend you wipe, better format data before flashing. Wiping of cache and Dalvik goes without saying right?
Sent from my TF700T using Tapatalk
Yes I did thanks, I haven't played around too much with it though - I did experience it to be very slow when trying to install Facebook app though. I do plan to start using it more often so time will tell.
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 ://
Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.
start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008
Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.
Try using sp flash tools flashing the boot.img