Related
MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.
irobbie said:
MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.
Click to expand...
Click to collapse
So, just to clarify, you are rooted and attempting ti install the Moray Rom, and your Xoom is giving you an error that it can't access the sdcard to flash the Moray file.
My first question is, what version of CWM recovery are you using and is your Moray file on your external micro sdcard which is inserted in your Xoom?
It sounds like you are trying to flash from the Xoom's internal "sdcard" which doesn't work (unless you have the Rogue recovery installed).
Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie
irobbie said:
Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie
Click to expand...
Click to collapse
Ok, Sounds like you should be set regarding recovery. I'm pretty sure that you should be able to go right to Moray 2.2.1.
First, confirm that your sdcard is good and working properly by inserting it into a phone or a card reader. It could be as simple as a bad card. Also, you could redownload the file, but I think it's most likely your sdcard.
Thanks for getting back to me.
I replaced the SD card with another from my mp3 player and checked it out by loading up a song and playing it. No problems. So then I moved the zip file for the rom (which I had previously re-downloaded) over to the root of the sd card from my PC and proceeded through the steps again. Failed again. The message sequence reads:
--Installing: /sdcard/Tiamat-Xoom-rom-2.2.1-Moray.zip
Finding update package... (So its gone looking)
Opening update package... (And it is found?)
E:Can't open /sdcard/Tiamat-Xoom-Rom-2.2.1.Moray.zip
(bad)
Installation aborted
Hmmm. Just to check that the sd card is still viable, after reboot went back to "files", sdcard, music and selected a song and it played as normal. Also checked that the Tiamat rom zip file is on the card and yep, it is. So tomorrow morning I will download the zip file once again and retry. If you can think of anything else it will be much appreciated.
Irobbie.
If you can check to make sure the downloaded file is the right size that will be great. also make sure that you don't add another.zip file extension on the end, somehow. Some pcs are set up to hide file extensions and that's been a problem a few have encountered.
The mystery deepens! Well, for me at least.
Re: zip file extra extension, have show extensions switched on, and there is no extra extension.
So on to file size, it looks the same to me on each download so I went a bit further. I noticed the link to the file has a MD5sum check noted. So I downloaded an open source file "Sigma Informatics Checksum calculator", pointed it to the rom zip file and ran the check, and then cut and pasted the original number from the thread and got the calculator to do a check. Bingo - exactly the same!
So then copied the file from the Xoom back to the PC, ran the same checks and got different answer!
OK, I deleted the rom zip file from the Xoom, copied another over from the PC, then recopied it back to the PC to a different location, ran the check sum, got the correct answer, so now I knew I had a correct file on the Xoom.
Next, reran the installation of the Rom - failed again with the same results and messages as before.
Then copied the Rom zip file back to the PC to another location, ran the checksum and different answer popped out again. Well, could it be that the zip file is being corrupted during the install and that is why it fails? I've never heard of that sort of thing happening before but I suppose it is possible.
Your continued support is much appreciated.
It seems like I have heard of this happening, but why? What would cause that? Can you use a different method to copy the Rom file to the sd card? Using an adapter, and inserting the card directly into the sd slot of the pc? Download right onto the card?
Thanks for the reply and suggestions again.
To make absolutely sure I eliminated everything possible; I went out and bought a new micro sd card, and card reader with a micro sd card slot. Plugged it altogether into the pc and copied over a copy of the rom zip file.
Then did a checksum check on the file on the sd card and it was fine.
So, holding breath, puff, puff, puff, started the procedure all over again.
SUCCESS! It all went as smooth as silk! Thanks for your help and suggestions. But now I am left with a concern about where the problem really was - was it in the copying of the file onto the card through the Xoom, or was it, in fact, a bad card? I don't want to discard the card because it seems to be o.k. in every other respect so I think a little play around is in order. I think in all probability you are right in questioning the process I was using before, and recommending that the file be copied directly to the sd card.
But in the meantime I'm off to explore the new rom and in particular USB hosting.
Yes! I love success!
Enjoy.
What happened to me? I testig new settings Buildprop file and I was stuck.
TF 700 not boot
______________________________________
Wipping/factor reset
POWER off
VOL down
VOL up to recovery
Wipe/Factor reset
Boot
but
Not boot I cry almost :crying:
______________________________________
I wonder.....
Download ASUS.com your Factor version Asus update
Open zip file Unzip first Zip file (WW_epad-user-9.4.5.22.zip)
Re name (WW_epad-user-9.4.5.22.zip) EP201_768_SDUPDATE.zip
And put zip file External Sdcard root
POWER off
VOL down
VOL up to recovery
Now auto starting full factory reset/update and TF700 :fingers-crossed: boot normal.
if anyone benefited from that I'm happy
Zeus :good:
I had the same problem and used (+described here) the same solution a few days ago, but thanks for this. Glad it worked for you too ]:>
http://forum.xda-developers.com/showpost.php?p=28597763&postcount=17
To clear up possible ambivalence on file location: the firmware file should be placed in the root directory of the microSD card. When you get an error message saying that some directory couldn't be mounted or some file couldn't be found, check if it hasn't been put on the SD card's root accidentally. :highfive:
To answer what actually happened, a factory reset only touches the data partition. Since the build.prop is on the system partition, its not wiped and so whatever prevented it form booting before is still there. Until we get an unlocked bootloader AND a custom recovery, I'd stay away from build.prop changes and any other mod that could potentially prevent booting unless you know completely what you are doing.
Jotokun said:
To answer what actually happened, a factory reset only touches the data partition. Since the build.prop is on the system partition, its not wiped and so whatever prevented it form booting before is still there. Until we get an unlocked bootloader AND a custom recovery, I'd stay away from build.prop changes and any other mod that could potentially prevent booting unless you know completely what you are doing.
Click to expand...
Click to collapse
Factor reset only return data partion default
if using sd card option Recovery return system partition. (But not touch data partition settings etc..)
I've restored the system partition twice.
Will this get rid of root? I am going to exchange my tf700 because the volume rocker is mushy and seems defective (I went to the store to check out the tf201's/etc asus tabs to compare) and I am sending back to amazon to exchange - so want it factory fresh.
It won't, apart from wiping data you need to remove su from /system/bin/ or xbin, wherever it is, and uninstall busybox (if installed)
You may reflash firmware as well, should do the trick.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
d14b0ll0s said:
It won't, apart from wiping data you need to remove su from /system/bin/ or xbin, wherever it is, and uninstall busybox (if installed)
You may reflash firmware as well, should do the trick.
Click to expand...
Click to collapse
Thanks - found it there in xbin
I'm trying to figure out why after downloading any file to my sd it goes into storage/sd0, and when I move the file it appears to move just fine to sd/downloads. However, when I go into TWRP recovery the files are not there. I have been troubleshooting this all morning and afternoon and it appears as though since flashing bb7 when it first dropped and then two days ago I flashed CROMI and now I'm apparently stuck here. Any help is appreciated.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
It's because you updated to a 4.2.1 rom and then downgraded to 4.1.1 again.
Unfortunately 4.2.1 reorganised your internal sdcard without asking as well as setting some folder links and now they are incompatible with your recovery and android 4.1.1
Best fix is to copy everything some where safe, make sure you have a flashable rom or a Nandroid Backup on external sd, wipe internal from recovery, reflash cromi and then rebuild your file structure manually.
Sorry. The BB7 guys should warn you imo.
I wanted to go the data2sd route and tried installing by formatting the 64mb class 10 microsd with minitool partition. After installing everything , the tablet stuck at "encryption error" only option was to reset. It did that everytime i started it. So i did a factory reset, format system and it threw a error saying cannot format sdcard android secure. So i then reinstalled cleanrom using the unters rom at the bottom selection and deleted cache then dalvick took sd card out and rebooted. Finally no encyption error.
Looked in es file explorer cleanrom installed to the /data, ilooked in sdcard/ and there is a file that data2sd installed called !microSD and i cannot delete it. I opened /sdcard in root explorer and the !microSD isnt there, i tried "show hidden files" in settings but it still wont show. I booted clockworkmodand chose installfrom internal sd and the !microSD shows. I click on it and it just opens another !microSD, i can keep clicking it and at the top if the screen it will look like this /!microSD/!microSd/!microSD/ and on and on. I want to delete it or format the internal sd but i am scared to format it, i have heard horror stories of bricking when choosing format emmc or format sdcard. I have tried format system to startfresh but it will format system,then data but it will say cannot format android secure skipping format. I dont mind wiping /sdcard since i backed up a few pics and movies.
I did format the 64gb with gparted. I want to try data2sd again but imicrosd file needs to be removed most likely. I tried to rename it too but es file explorer wont let me.
mescalinedreamz said:
I wanted to go the data2sd route and tried installing by formatting the 64mb class 10 microsd with minitool partition. After installing everything , the tablet stuck at "encryption error" only option was to reset. It did that everytime i started it. So i did a factory reset, format system and it threw a error saying cannot format sdcard android secure. So i then reinstalled cleanrom using the unters rom at the bottom selection and deleted cache then dalvick took sd card out and rebooted. Finally no encyption error.
Looked in es file explorer cleanrom installed to the /data, ilooked in sdcard/ and there is a file that data2sd installed called !microSD and i cannot delete it. I opened /sdcard in root explorer and the !microSD isnt there, i tried "show hidden files" in settings but it still wont show. I booted clockworkmodand chose installfrom internal sd and the !microSD shows. I click on it and it just opens another !microSD, i can keep clicking it and at the top if the screen it will look like this /!microSD/!microSd/!microSD/ and on and on. I want to delete it or format the internal sd but i am scared to format it, i have heard horror stories of bricking when choosing format emmc or format sdcard. I have tried format system to startfresh but it will format system,then data but it will say cannot format android secure skipping format. I dont mind wiping /sdcard since i backed up a few pics and movies.
I did format the 64gb with gparted. I want to try data2sd again but imicrosd file needs to be removed most likely. I tried to rename it too but es file explorer wont let me.
Click to expand...
Click to collapse
Nevermind, i decided to bite the bullet and install cleanrom 3.0.3 and followed directions for data2sd. It installed without encryption error and the imicrosd file was gone. But from what i have eread about data2sd it didnt install correctly because the file system should have showed sdcardi which it didnt. I tried downloading a torrent movie and the tablet became unuseable,freezing. Also moving files from the ext4 to fat32 were sloooow. I decided to flash a kernal from the t700t forum on the data2sd subject. That resulted in the encryption scenario. So i factory wiped in clockwork and installed the newest cleanrom 3.3 and the 3.2 chromidata2sd file then the mount2sd file and then the kernal pack and used the 10.4.20 tf300 kernal. Rebooted fine. The tablet is real fast but i havent tried a torrent download. I also had two weird half reboots with each one when i tried deleting a file in file manager and then in es file. I do have a folder called internal sdcard which has the usual files on it. Didnt have that with the old 3.03. I did but it was empty.
Anyone know why it reboots when deleting a file? I did disable fsync though.
Don't use minitool to partition the card. It corrupts and causes reboots, etc. Even though the d2sd thread recommended it, don't.
Use gparted instead and all will be well.
sbdags said:
Don't use minitool to partition the card. Corrupts and causes reboots, etc. Even though the d2sd thread recommended it, don't.
Use gparted instead and all will be well..
Click to expand...
Click to collapse
I figured that out after the first encryption Error. I then spent all for one day trying to figure out how to partition the card in gparted. I should have deleted both partitions and then format them, instead I moved them in gparted and that took 4 hours. Then i found a write up on exactly what to do.
mescalinedreamz said:
I figured that out after the first encryption Error. I then spent all for one day trying to figure out how to partition the card in gparted. I should have deleted both partitions and then format them, instead I moved them in gparted and that took 4 hours. Then i found a write up on exactly what to do.
Click to expand...
Click to collapse
Well i just went through 4 hours of being terrified that I bricked my tablet. I kept getting reboots, i installed androbench and when i clicked on the benchmark button the tablet rebooted. Tried to run the benchmark again and rebooted again. I then tried to uninstall it which rebooted the tablet again. I went to clockwork recovery and wiped /factory reset i then proceded to reinstall cleanrom 3.3 with stock kernal,then format cache, installed chromi.3.2data2sd,wiped cache,started the kernal installer and chose unters 10.4.4.20 ,wiped cache,flashed mountdata2sd.zip, factory reset. I restarted to a bootloop. I then wiped and factoryreset again and installed cleanrom again this time choosing no kernal and wentthrough the steps and had a bootloop again. I started worrying and did another factory reset but installed stock kernal and didnt install data2sd, rebooted to a the asus screen with blue loading bar, that screenflashed black and then stuck on asus screen.
I then freaked outa bit because i dont save backups. I then did a horrible thing, i formatted emmc. I had read a few posts about installing a fresh rom for thepurpous of selling. A few posts mentioned that it was safe to format emmc but to be careful since it might format an external card too. I rremoved the sd card beforehand. I then did a factory reset in clockwork and proceded to install cleanrom . Install went fine and i clicked on reboot system. BOOTLOOP! I was really freaking out now. So i looked up format emmc some more and the horror stories started appear. I downloaded peri one click root+recovery/fix-bootloops+softbricks. I had android phones listed in system properties but no adb. While searching for a work around i came across how to reinstall stock firmware over a rom. I downloaded the tf300t firmwware 2013.01.18 up date unzipped it and threw it ona microsd. In clockworkmod i chose install zip from sdcard and boom fixed!!!!!!!!!! I was sooooo happy. So i now have a locked tf300t unrooted factory fresh. But there is one problem, in file manager on /sdcard/ there is that file that mountdata2sd.zip installed called !microSD that shows 0.0bytes and i cannot delete it. It doesnt show up in windows 7 though. I have show hidden files checked too. My plan is to reinstall clockworkmod and try data2sd one more time but i want to delete that !microsd file first. I need to make a few more posts until i can ask in developer forum.
mescalinedreamz said:
Well i just went through 4 hours of being terrified that I bricked my tablet. I kept getting reboots, i installed androbench and when i clicked on the benchmark button the tablet rebooted. Tried to run the benchmark again and rebooted again. I then tried to uninstall it which rebooted the tablet again. I went to clockwork recovery and wiped /factory reset i then proceded to reinstall cleanrom 3.3 with stock kernal,then format cache, installed chromi.3.2data2sd,wiped cache,started the kernal installer and chose unters 10.4.4.20 ,wiped cache,flashed mountdata2sd.zip, factory reset. I restarted to a bootloop. I then wiped and factoryreset again and installed cleanrom again this time choosing no kernal and wentthrough the steps and had a bootloop again. I started worrying and did another factory reset but installed stock kernal and didnt install data2sd, rebooted to a the asus screen with blue loading bar, that screenflashed black and then stuck on asus screen.
I then freaked outa bit because i dont save backups. I then did a horrible thing, i formatted emmc. I had read a few posts about installing a fresh rom for thepurpous of selling. A few posts mentioned that it was safe to format emmc but to be careful since it might format an external card too. I rremoved the sd card beforehand. I then did a factory reset in clockwork and proceded to install cleanrom . Install went fine and i clicked on reboot system. BOOTLOOP! I was really freaking out now. So i looked up format emmc some more and the horror stories started appear. I downloaded peri one click root+recovery/fix-bootloops+softbricks. I had android phones listed in system properties but no adb. While searching for a work around i came across how to reinstall stock firmware over a rom. I downloaded the tf300t firmwware 2013.01.18 up date unzipped it and threw it ona microsd. In clockworkmod i chose install zip from sdcard and boom fixed!!!!!!!!!! I was sooooo happy. So i now have a locked tf300t unrooted factory fresh. But there is one problem, in file manager on /sdcard/ there is that file that mountdata2sd.zip installed called !microSD that shows 0.0bytes and i cannot delete it. It doesnt show up in windows 7 though. I have show hidden files checked too. My plan is to reinstall clockworkmod and try data2sd one more time but i want to delete that !microsd file first. I need to make a few more posts until i can ask in developer forum.
Click to expand...
Click to collapse
I just need one more post so i can reply in developers
+1 I have the same problem as you.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
i am same problem
So ever since I got my Asus back from RMA and I am waiting for them to fix my (unable to) unlock issues, I though I might try the official 4.2 but not without having root first.
So I downloaded the appropriate WW SKU .30 firmware .zip (MD5 matched), extracted it, renamed the extracted file and put it on my micro sd (like I should)
Unfortunately, every time I boot into stock recovery to perform the downgrade, it just shows me the annoying red triangle, which means that it was no success.
I really want my root access
Does anyone have an idea how to fix this?
With the .30 firmware I got from the asus downloads, I had to extract twice to get to the file and then rename.
wassup said:
With the .30 firmware I got from the asus downloads, I had to extract twice to get to the file and then rename.
Click to expand...
Click to collapse
Maybe that is what you have to do. The uploader may have downloaded it, and zipped it again, giving it two layers to be unzipped instead of one.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.7 Odex AND That's UltraCleanRom(7 sec boot )
Kernal: _That's Stock V6 Kernal
Theme: Timberwolf's Blues & Jazz Theme V2.1
UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE http://forum.xda-developers.com/showthread.php?t=2204100
Yes they are zipped twice. Zip in a zip.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
adelancker said:
So ever since I got my Asus back from RMA and I am waiting for them to fix my (unable to) unlock issues, I though I might try the official 4.2 but not without having root first.
So I downloaded the appropriate WW SKU .30 firmware .zip (MD5 matched), extracted it, renamed the extracted file and put it on my micro sd (like I should)
Unfortunately, every time I boot into stock recovery to perform the downgrade, it just shows me the annoying red triangle, which means that it was no success.
I really want my root access
Does anyone have an idea how to fix this?
Click to expand...
Click to collapse
A locked tablet should just see the zip file as an OTA notification after booting back to the launcher.
Installing from recovery wouldn't be necessary in most situations.
Tylorw1 said:
Maybe that is what you have to do. The uploader may have downloaded it, and zipped it again, giving it two layers to be unzipped instead of one.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.7 Odex AND That's UltraCleanRom(7 sec boot )
Kernal: _That's Stock V6 Kernal
Theme: Timberwolf's Blues & Jazz Theme V2.1
UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE http://forum.xda-developers.com/showthread.php?t=2204100
Click to expand...
Click to collapse
wassup said:
With the .30 firmware I got from the asus downloads, I had to extract twice to get to the file and then rename.
Click to expand...
Click to collapse
elfaure said:
Yes they are zipped twice. Zip in a zip.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advice.
The sad part is: I know their double zips, so I did everything right.
The tablet also recognises the update. And then, ... I click on it, it shows the working android icon for two or three seconds, before showing the belly up red triangle android.
This sucks...
Any further ideas?
Have to try to wipe data (factory reset) then do the update? (make sure you have a full backup with Titanium backup).
adelancker said:
Thanks for the advice.
The sad part is: I know their double zips, so I did everything right.
The tablet also recognises the update. And then, ... I click on it, it shows the working android icon for two or three seconds, before showing the belly up red triangle android.
This sucks...
Any further ideas?
Click to expand...
Click to collapse
Check the filesystem of your SD card -- from my experience it needs to be FAT32. NTFS for sure doesn't work, exFAT may not work either (haven't tested).
becomingx said:
Check the filesystem of your SD card -- from my experience it needs to be FAT32. NTFS for sure doesn't work, exFAT may not work either (haven't tested).
Click to expand...
Click to collapse
Only FAT32 works for recovery. Both NTFS and exFAT formats will not work. For SDXC cards the default (Sandisk) format is exFAT so you have to format them FAT32 if you want to use them for recovery, but this will typically only show you 32GB max available for a 64GB and larger SD. So the largest SD you can practically use for recovery is 32GB FAT32.
buhohitr said:
Have to try to wipe data (factory reset) then do the update? (make sure you have a full backup with Titanium backup).
Click to expand...
Click to collapse
What is the difference between a Titanium and a Nandroid backup? Do they both restore all apps, data, and /system files?
elfaure said:
What is the difference between a Titanium and a Nandroid backup? Do they both restore all apps, data, and /system files?
Click to expand...
Click to collapse
No, big differences, Nandroid backup (done through TWRP) will create a backup of your entire OS (everything, sys apps, users' apps, system settings, kernel, rom..etc.), but the downside is you have to restore the entire image (can't pick and choose). While Titanium only can backup your system apps and users apps with data. The advantage of Titanium is you can choose what app you want to restore with or without data when you restore an app. Usually anadroid backup is useful when you want to test out a new rom, you first make a nandroid backup and if for some reasons you don't like the new rom or your device crashed, you can just restore the nandroid backup and you're back to the same exact setup as before you upgrade/crashed.
Had to do a factory reset and use fat32 in order to downgrade... Gonna root as soon as downgrade complete