I have two identical xooms. The model number lists as "Xoom". Android version is 4 .1.2 , build JZ054K, kernal version 2.6.39.4-g4e32b94 . I've been trying for days to update at least one of them. I'm using a Linux Mint 17 desktop. No Windows available.
I've tried everything I found on these forums, and nothing has worked. I have 32gb external sd cards in both of them. My first trak was to do it from the SD card but I found that recovery cannot see my SD card. I also tried putting " BigPart" in a directory called downloads, but that didn't help. I also tried loading it onto the internal card. Can't see it either way.
I downloaded the Linux android files and plugged in the USB cable. I could talk to the Xoom, and tell it to reboot the bootlooder into fastboot or recovery, and the Xoom would reboot but lock up at the "loading fastboot" screen. I tried sideloading the BigPart file, but the install would fail on validation. If I try to enter fastboot by rebooting it locks on the loading screen. If I load recovery on boot it appears to come up but It can't see the SD cards or accept the files from the computer (From adb).
One of these Xoom's I gedfied and the other was a google device when I bought it. Both got all of their last bunch of updates thru Google, until Google dropped them. Could the google updates have left something needed out??
As I understand the process getting Big part on the device is the first step. I have all needed files for the upgrade,on my SD cards and on my Linux machine. I just can't use them. Anyone have any ideas? Does anyone know where and what the OS is looking for during that attempted USB update??
Ok turning of Developer options
GreyBeard51 said:
I have two identical xooms. The model number lists as "Xoom". Android version is 4 .1.2 , build JZ054K, kernal version 2.6.39.4-g4e32b94 . I've been trying for days to update at least one of them. I'm using a Linux Mint 17 desktop. No Windows available.
I've tried everything I found on these forums, and nothing has worked. I have 32gb external sd cards in both of them. My first trak was to do it from the SD card but I found that recovery cannot see my SD card. I also tried putting " BigPart" in a directory called downloads, but that didn't help. I also tried loading it onto the internal card. Can't see it either way.
I downloaded the Linux android files and plugged in the USB cable. I could talk to the Xoom, and tell it to reboot the bootlooder into fastboot or recovery, and the Xoom would reboot but lock up at the "loading fastboot" screen. I tried sideloading the BigPart file, but the install would fail on validation. If I try to enter fastboot by rebooting it locks on the loading screen. If I load recovery on boot it appears to come up but It can't see the SD cards or accept the files from the computer (From adb).
One of these Xoom's I gedfied and the other was a google device when I bought it. Both got all of their last bunch of updates thru Google, until Google dropped them. Could the google updates have left something needed out??
As I understand the process getting Big part on the device is the first step. I have all needed files for the upgrade,on my SD cards and on my Linux machine. I just can't use them. Anyone have any ideas? Does anyone know where and what the OS is looking for during that attempted USB update??
Click to expand...
Click to collapse
Ok after 70 views and no responses, I'm giving up for now. Turn off deleloper options, and letting Google have their way with my Xoom android 4.1.2 . "I think" part of the problem is my Xooms will NOT boot into Fastboot. For what ever reason I do not know. The bootloader is still locked because I can't get to it to unlock it (using my Linux box) I know they can be unlocked because I did it a few years ago with my XP box (long gone). Is JellyBean the end for my Xooms?
Related
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?
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.
I got a Xoom for free a couple days ago, I decided I wanted to put KitKat on it, I didn't really like how 4.1 looked. I installed ClockworkMod Recovery on it to, but I can't push any files to it using 'adb push 'filename'', this is because adb does not recognize my device. I believe this is because there is no driver installed. In Device Manager it shows up as "Xoom" in the "Other Devices" dropdown. I've downloaded and installed the drivers previously from this link (can't post links because I'm new, the name of the program is Motorola Device Manager ), but while in recovery, they don't seem to work. When I try to run the driver installer while in recovery, it does not install any drivers, and Windows cannot find any drivers. So, any suggestions?
Edit: I booted back to the factory OS and tried installing the driver there through Motorola Device Manager, but it says to switch the device into "Media Device" mode (MTP), which it is already in.
xBenjio said:
I got a Xoom for free a couple days ago, I decided I wanted to put KitKat on it, I didn't really like how 4.1 looked. I installed ClockworkMod Recovery on it to, but I can't push any files to it using 'adb push 'filename'', this is because adb does not recognize my device. I believe this is because there is no driver installed. In Device Manager it shows up as "Xoom" in the "Other Devices" dropdown. I've downloaded and installed the drivers previously from this link (can't post links because I'm new, the name of the program is Motorola Device Manager ), but while in recovery, they don't seem to work. When I try to run the driver installer while in recovery, it does not install any drivers, and Windows cannot find any drivers. So, any suggestions?
Edit: I booted back to the factory OS and tried installing the driver there through Motorola Device Manager, but it says to switch the device into "Media Device" mode (MTP), which it is already in.
Click to expand...
Click to collapse
Are you using the correct cable? Have you tried using another USB port?
I'm assuming you have a memory card. So if you had a custom recovery already installed why not pull the SD card out of the xoom and move the files required for custom os onto that directly from computer.
getyroks said:
Are you using the correct cable? Have you tried using another USB port?
I'm assuming you have a memory card. So if you had a custom recovery already installed why not pull the SD card out of the xoom and move the files required for custom os onto that directly from computer.
Click to expand...
Click to collapse
I don't have the factory cable, I believe I have already tried two separate cables though. I have tried front and back USB ports on my PC. I've been trying to do it without a micro SD card, as the only one I have is in my phone. I assume if I use that it would mess up the formatting on my phone though?
xBenjio said:
I don't have the factory cable, I believe I have already tried two separate cables though. I have tried front and back USB ports on my PC. I've been trying to do it without a micro SD card, as the only one I have is in my phone. I assume if I use that it would mess up the formatting on my phone though?
Click to expand...
Click to collapse
No. If you have recovery already loaded, then place the rom of choice on the card insert in xoom and install from SD card. No formatting required on card.
getyroks said:
No. If you have recovery already loaded, then place the rom of choice on the card insert in xoom and install from SD card. No formatting required on card.
Click to expand...
Click to collapse
I was worried about my SD card, which is in my phone, getting messed up and not work properly with my phone. I'll probably go ahead and try it and not worry about my phone. I'll let you know how it goes.
xBenjio said:
I was worried about my SD card, which is in my phone, getting messed up and not work properly with my phone. I'll probably go ahead and try it and not worry about my phone. I'll let you know how it goes.
Click to expand...
Click to collapse
Copy all files to computer from SD card to be safe. Then if you do lose something. No worries![emoji16]
A510 has encryption unsuccessful--
Have gone to acercom/ac/en/US/content/drivers under the OS tab and have tried several of their update files under ICS and JB. I have no idea what my ID number is.
Reset with hole-unsuccessful
Reset with Power/Vol Up-Vol down/Reset--unsuccessful
Various update.zip files tried via sd card unsuccessful
After it verifies the OS it then tells me check.partition.size=[__PROP_UNDEFINED__]
Tablet has never been rooted, cannot be seen through windows 8(thinking root or adb not an option), makes noise on connect and reconnect, was watching movies on sd card when it crashed.
Any guidance or should I just throw it away?
Thanks
Any advice please?
skilmer said:
A510 has encryption unsuccessful--
Have gone to acercom/ac/en/US/content/drivers under the OS tab and have tried several of their update files under ICS and JB. I have no idea what my ID number is.
Reset with hole-unsuccessful
Reset with Power/Vol Up-Vol down/Reset--unsuccessful
Various update.zip files tried via sd card unsuccessful
After it verifies the OS it then tells me check.partition.size=[__PROP_UNDEFINED__]
Tablet has never been rooted, cannot be seen through windows 8(thinking root or adb not an option), makes noise on connect and reconnect, was watching movies on sd card when it crashed.
Any guidance or should I just throw it away?
Thanks
Click to expand...
Click to collapse
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.