[Completed] Asus ZenPad S 8 Bricked. Have CWM. Need ADB RSA Authentication, but can't access OS. - XDA Assist

Hello!
I just got an Asus ZenPad 8.0 about 6 hours ago, and now I broke it. I rooted it successfully using this guide, but then I updated the firmware, and now it's bricked. I can probably return it with all of the holiday returns policies, but I'd rather keep it. Anyways, here's the problem, and what I've tried.
I found the script in the link above that lets me access CWM recovery. My plan was to format everything, then copy the zip using adb, and install it through CWM recovery. The script temporarily flashes CWM. I can't find another version of CWM for my device, so this is all I've got to work with (I think). This backfired on me because I also deleted my RSA keys. I never thought I needed them in my recovery, and I've done this pleanty of times on my Nexus 6, without the need for keys when working with my TWRP recovery. TL;DR: I can't copy the factory image zip to my tablet.
Here's what I've tried
-------------------------------------------
Using ADB to copy the file (Doesn't work, need RSA Authorizations)
Find a new recovery, then flash it via fastboot, and then use ADB via that recovery (Couldn't find another recovery. Checked CWM and TWRP pages, but couldn't find my device)
Put the zip on my SD card & extract the zip from the card (Error mounting the card. I used another device to format the sd card. No luck. Tried this article and this article)
Booting into safe mode (Still bricked... still didn't work)
Cursing at it
If I can get past the "Permission Denied" and "unauthorized" stuff with ADB, that would be great! I just don't know how to do that.
Let me know if I'm missing anything and what my options are before I return it in a few days. Cheers!

I figured it out. CWM needed a SD card with a capacity of 32gb or less. Since I was using a 64gb card, I couldn't mount it. I stuck in my 8gb card from my Raspberry Pi, put it in, and now it's mounted. I installed it, and now I just have to wait on that.

Related

[Q] Help: bricked and read only

Hello,
I rooted my tf101, all went well. Put clockworkmod recovery on it and still no problems. Now I wiped all partitions by mistake of my tf101. The only thing left is the recovery image (cwr) but if i try adb tool to push a file on the system it says the system is readonly. If i try nvflash tool is also says error onable to write and it disconnect the tf101.
Can any body help me, or do i have to put it back to repair
thanks Ernst
Well, if you have a microSD card, and a CWM that can read from it, you could just hook the card up to your PC (using a phone with microsd slot, or a cardreader, etc) and place the new image on the card.
Also, have you tried running 'adb root' to make sure ADB is running as root?
@Goatshocker
I tryed to insert a microSD card, but cwr does not recognize it, at least it does not appear in the menu structure.
Also tryed adb root, it sayed hat it is already in root.
ernst99999 said:
@Goatshocker
I tryed to insert a microSD card, but cwr does not recognize it, at least it does not appear in the menu structure.
Also tryed adb root, it sayed hat it is already in root.
Click to expand...
Click to collapse
If you are using cwm 5.5.0.4, go to the following link.
http://forum.xda-developers.com/showthread.php?p=23256536
@kokopopz
I have indeed version 5.5.04, have read the tread you mentioned, but no solution. My problem is that if i try to push a file to the TF than it says "read-only file-system". Tryed in cwr to fix permisions, but no help.
Problem stays the same.
@kokopopz Thanks for your link.
I Found the solution !!!! My TF is UNBricked. YES YES YES.
For the record: "adb push rom.zip /data/media/rom.zip" will do the trick, after that reboot to cwr and do install zip from sdcard.

[Q] TF300T, TWRP and ROM issues

Hola banditos, I am new here, and not really that big into android, so forgive me if I do not refer to something correctly. I am currently having multiple problems with my Asus Transformer pad. A few months ago I purchased said product and rooted it. I had a few minor issues but eventually got it working. Flash forward to yesterday night at around 10 PM, and I had wiped the system and removed the Operating system. "No problem" I thought "I can just download the Jellybean firmware from the asus website" ( I had done this before.)
I downloaded the firmware, put it on my SD card and flashed it. The only problem was that I had flashed the Japanese version of the firmware onto it.
At this point, TWRP apparently thought it would be hilarious to stop working. Upon downloading the US version of the software and loading it onto my SD card, TWRP was no longer able to mount the SD card. That my friends is the major problem.
I have checked on my computer, and the SD card is still functioning. I have went into the Japanese OS on the Android and it is still accessible and functioning. I have downloaded multiple versions of TWRP, different recovery kernels and tried multiple solutions through other threads. I have tried reformatting my SD card to EXFAT, Fat32, NTFS and regular FAT. I have tried putting the firmware on the internal SD card and loading it from there. It recognizes that the firmware is there, but fails to install it. ADB also fails to recognize the device (I have everything set up correctly on the PC but it still fails). Fastboot is working fine though.
I have crawled through web page to web page looking for a fix. About 7 hours in total, and I am yet to find one that works.
Help me out here.
My gear:
64 GB sandisk SD card
Asus tf300t running a japanese Jellybean 4.2.1
TWRP 2.6
You're my last hope
There is another way! Inside the us software zip there is another zip inside that zip is a .blob file extract it to the directory where adb and fastboot are on your pc open up command prompt and cd to your fastboot directory: now type: fastboot flash system blob
This will take some time!
Then flash twrp and open it then wipe data system cache dalvik cache and then flash the firmware via twrp reboot!
Sent from my sensational HTC Desire C
I have grabbed the blob file from the US firmware. Upon using the "fastboot flash system blob" command, I get the message < waiting for device > I have waited a half hour, and it is still there. am I doing something wrong?
Edit-
I have since got the fastboot to work after some research. When I went to wipe the data system cache and dalvik cache, TWRP said that it had failed. TWRP still failed to recognize my SD card
Edit Edit-
Again after more searching, I have found a TWRP version that has recognized my SD card. However, One problem still remains before I am finished. I am still unable to flash the stock firmware. I navigate to my External SD card in TWRP, select the firmware zip file. Almost instantly it says that the install failed. Any ideas?
Lord Cyan said:
I have grabbed the blob file from the US firmware. Upon using the "fastboot flash system blob" command, I get the message < waiting for device > I have waited a half hour, and it is still there. am I doing something wrong?
Edit-
I have since got the fastboot to work after some research. When I went to wipe the data system cache and dalvik cache, TWRP said that it had failed. TWRP still failed to recognize my SD card
Edit Edit-
Again after more searching, I have found a TWRP version that has recognized my SD card. However, One problem still remains before I am finished. I am still unable to flash the stock firmware. I navigate to my External SD card in TWRP, select the firmware zip file. Almost instantly it says that the install failed. Any ideas?
Click to expand...
Click to collapse
cant you use fastboot to flash the stock firmware?

[Q] Can't flash from SD Card

Good evening, XDA :cyclops:
I am having issues flashing from recovery!
Some device info: Motorola Xoom WiFi, fully stock and fully updated, unrooted, bootloader unlocked today, device wiped multiple times. This is my first day trying anything custom on this device.
I decided today that i wanted to go custom on my Xoom today and update it to KitKat via this method.
I have downloaded all the required files per the mentioned guide. While in recovery i go to apply update from USB drive, but it is not finding any of the downloaded files from the guide.
What I see is
Code:
Android system recovery <3e>
Choose a package to install:
/sdcard
../
The ../ is my only option to click and it obviously returns me to the main recovery menu.
All the zip files are on the root of the SD card, not in sub folders. I have confirmed via PC and another phone that the files are indeed there. I tried with a different, fresh, formatted (fat32) SD card, but I'm getting the same results.
The Xoom is indeed reading the SD card, confirmed via settings>storage.
I've tried using adb, but it's telling me the image isn't correct, but it's certainly possible I'm missing a step with adb.
Code:
C:\Xoom bootloader unlocker2>adb reboot bootloader
C:\Xoom bootloader unlocker2>fastboot flash R.A.H._TWRPv2.6.3_BigPart_selinux.zip
unknown partition 'R.A.H._TWRPv2.6.3_BigPart_selinux.zip'
error: cannot determine image filename for 'R.A.H._TWRPv2.6.3_BigPart_selinux.zip'
Yes, the zip is in that folder. I thought maybe I'd root first, so I tried that method with the root zip, but I'm getting the same error.
Is there something I can do to repartition this device and get it rommed, or am I doomed to use it stock?
Thank you for your time!
I found some information stating that I need to enable the SD card, but since I'm running up to date SW, and I can see the SD card from settings, I'm assuming that this isn't the case, correct?
I'm still stuck. Anyone around who could give me some advice?
scubab said:
I'm still stuck. Anyone around who could give me some advice?
Click to expand...
Click to collapse
It appears the XOOM does not like SD Cards that were formatted using Windows
(or perhaps Quick Formatted using Windows).
Using a 4GB FlashDrive formatted as Fat32 using Linux (i.e. Linux Mint 17.3 Cinnamon 64 bit boot CD)
resolved the issue.

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]
Did you ever find a fix? I'm having a similar problem.
Try to use fastboot restore everything.
I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device
Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.
If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.

Help! Asus SL101 stuck in CWM, can't mount /sdcard, error mounting /data :(

Hi all.
I've been searching the net for hours for a solution to this issue, to no avail.
I have an Asus Slider SL101 that I wanted to upgrade to KatKiss so here's what I've done...
- Root successfully (1-click transformer root 1.1 from here: https://forum.xda-developers.com/showthread.php?t=1689193)
- Installed CWM Recovery (6.0.1.3) successfully (also using above)
- put all the relevant zips (katkiss, gapps, slider comp pack) on the sd card ready for flash
- booted into recovery...
Next I went to wipe data/factory reset... but it froze so I did a hard boot and tried again: same thing.
So I went to install the rom zip from sdcard and I get error message 'can't mount /sdcard/'
Also getting 'error mounting /data' and 'unknown volume for path [/sdcard/].
I can't get back to my original Android settings at all, I'm assuming it's all gone or something. Maybe the reset did work.
The big issue is I can't access the damn zip files on the sd card to install a rom.
I have these ADB tools (with adb and all these random executables and various files scattered about) but if I can't start Android then I can't use them can I?
It's a bit of a mess really. I'm thinking if I can just get the slider to mount the sd card then I can install the rom and I should be back in.
I'm not sure how to go back to stock recovery (whatever that means) so if you advise that I should 'flash' then I'm afraid I'm going to need some clear instruction.
Stupidly, I forgot to do a backup, which is probably half the reason I'm here, although that still doesn't account for the sdcard error...
Anyway, please help a moron out?
sliderfan said:
Hi all.
I've been searching the net for hours for a solution to this issue, to no avail.
I have an Asus Slider SL101 that I wanted to upgrade to KatKiss so here's what I've done...
- Root successfully (1-click transformer root 1.1 from here: https://forum.xda-developers.com/showthread.php?t=1689193)
- Installed CWM Recovery (6.0.1.3) successfully (also using above)
- put all the relevant zips (katkiss, gapps, slider comp pack) on the sd card ready for flash
- booted into recovery...
Next I went to wipe data/factory reset... but it froze so I did a hard boot and tried again: same thing.
So I went to install the rom zip from sdcard and I get error message 'can't mount /sdcard/'
Also getting 'error mounting /data' and 'unknown volume for path [/sdcard/].
I can't get back to my original Android settings at all, I'm assuming it's all gone or something. Maybe the reset did work.
The big issue is I can't access the damn zip files on the sd card to install a rom.
I have these ADB tools (with adb and all these random executables and various files scattered about) but if I can't start Android then I can't use them can I?
It's a bit of a mess really. I'm thinking if I can just get the slider to mount the sd card then I can install the rom and I should be back in.
I'm not sure how to go back to stock recovery (whatever that means) so if you advise that I should 'flash' then I'm afraid I'm going to need some clear instruction.
Stupidly, I forgot to do a backup, which is probably half the reason I'm here, although that still doesn't account for the sdcard error...
Anyway, please help a moron out?
Click to expand...
Click to collapse
))
Ive got the same problem. CWM cant mount the sd card. Ive been searching for days, but all the links in any solution i did find are outdated. I did read somewhere that it means that the CWM version isnt compitable with the Sl101. I can't find any other/older versions then the Manager i downloaded from Playstore. I want to flash the Twrp Recovery and then the kisskat ROM, compability pack.. Gapps
.etc but i cant seem to get any of that done if CWM can't mount the damn sdcard. (Sorry i got a bit frustrated over this). Ive never rooted anything before so im new to this. Did anyone find a solution for this? Or has an link to some other version of CWM that is compitable to mount the sdcard? Thank you very much in advance)
Probably not what you wanna hear, but I didn't find a solution and had to throw my beloved slider away!

Categories

Resources