Related
I bought an Atrix locally. It has superuser since it was rooted, BUT the seller removed the SD card, so the root isn't working right now.
I tried to upgrade Superuserand I'm not allowed to do so... it says the following: "An error ocurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary"
I already inserted my own SD card, but I don't know what to do in fear of bricking my new phone.
Any help would be GREATLY appreciated, thanks!!
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.
hey guys and girls, hopefully you can help me out.
I'm using a t-mobile galaxy S, trying to flash a new rom after I rooted it. I followed the instructions, and I have CWM able to load. when I got into select the install from the SD card, I'm able to select the file (trying bionix frost), it tries to load it, but then comes back telling me 'Can't mount /sdcard' and any subsquent attempts to even browse for the install zip give me the same error. I can boot the phone into the rooted stock image, access anything on the SD card there fine, copy files to it, etc, but CWM will not install the ROM's or keep the /sdcard mounted.
anyone here run into this issue? I'm using CwM Voodoo lagfix Recovery 3.0.2.8x
It's been awhile since I flashed that ROM...
Did you change the mounts manually? Does the OP say to change mounts? Back then we had to change the mounts ourselves in CWM to UMMU.
I'm at work and just sending a quick reply..check the OP to see what your mounts should be
to clarify a bit, this isn't just on a specific ROM, this is for ANY rom I try, after I access any ZIP file through CWM, it unmounts the SD Card and won't let me get back to it unless I reboot, and the cycle repeats.
Ok. Sorry I can't help you with that. I'm still kinda new.
I'm sure you'll get the help you need soon especially with your last reply.
Good luck and sorry I couldn't be of help.
I'm backing up and will format my SD card to see if this is the problem, saw this fixed a couple of errors like this for other peeps.
So since I couldn't get CWM to install the rom, I used ODIN and flashed to gingerbread. that's installed and working (had it fail the first time, but the 2nd installed and was up inside 10 minutes)
Got a Samsung Epic 4g with gingerbread. I downloaded this file "update-cm-9-20120606-SNAPSHOT-epicmtd-beta4-sig" on my computer and put it in the included micro sd card(I have to unmount sd card then put it in my pc). I then tried to install the CM9 file, it loads about a quarter of the bar then gives my an error message "E:failed to verify whole-file signature". Did I do anything wrong? I followed QBKING77's instructions and "Cyanogenmod Epic 4G: CM9 Install Guide" instructions but kept getting the same message. I thought it was just a corrupted file so I downloaded it 3 more times and failed 3 times as well. Any help would be appreciated.
p.s. I've searched here and google for any solutions but couldn't find any.
I too am having this issue on my One S on t-mobile while trying to apply their latest update. It may be an issue with the verification that the package looks for before install that clockwork cannot give because it is in the way of the Android bootloader. Or maybe I don't understand clockwork properly. The latter is more likely. If anyone could provide assistance, that would be excellent
Found out that my cable is the culprit so I used an aftermarket ipad adapter w/ a male micro usb and two female mini usb. I thought I was the one making the mistake.
Hello. I have rooted, stock, tab. OTA's would never install right. I tried downgrade to.30 to reroot JB. I tried several times. Didn't work. Then, somehow, I'm stuck on boot screen. I tried the soft brick recovery options, didn't work. I can access stock recovery, but when I rename file and put on SD card, it says file not found. Any help or suggestions would be very appreciated.
redheadplantguy said:
Hello. I have rooted, stock, tab. OTA's would never install right. I tried downgrade to.30 to reroot JB. I tried several times. Didn't work. Then, somehow, I'm stuck on boot screen. I tried the soft brick recovery options, didn't work. I can access stock recovery, but when I rename file and put on SD card, it says file not found. Any help or suggestions would be very appreciated.
Click to expand...
Click to collapse
Most likely you are doing something wrong if the recovery said that no file is found.First make sure your MicroSD is formatted in FAT32 and then check the filename and keep in mind that if you use Windows usually you don't need to use the .zip file extension. Also make sure that you extract the zip from the file you download from Asus site.
Pretoriano80 said:
Most likely you are doing something wrong if the recovery said that no file is found.First make sure your MicroSD is formatted in FAT32 and then check the filename and keep in mind that if you use Windows usually you don't need to use the .zip file extension. Also make sure that you extract the zip from the file you download from Asus site.
Click to expand...
Click to collapse
did everything again. Reformated SD. Still nothing. Here's what it tells me
Finding update package
E: failed to mount /SD card (no such file or directory)
E: can't mount /sdcard/ASUS_BUNDLE.zip
E: failed to mount /sdcard (no such file or directory)
E: can't mount SD card
Installing update...
Finding update package...
E: failed to mount /sdcard (no such file or directory)
E: can't mount /sdcard/EP201_768_SDUPDATE.zip
SD installation aborted
redheadplantguy said:
did everything again. Reformated SD. Still nothing. Here's what it tells me
Finding update package
E: failed to mount /SD card (no such file or directory)
E: can't mount /sdcard/ASUS_BUNDLE.zip
E: failed to mount /sdcard (no such file or directory)
E: can't mount SD card
Installing update...
Finding update package...
E: failed to mount /sdcard (no such file or directory)
E: can't mount /sdcard/EP201_768_SDUPDATE.zip
SD installation aborted
Click to expand...
Click to collapse
This is odd, i heard that with the new JB bootloader the fastboot mode can be accessed even with locked bootloader, can you boot in fastboot mode (USB ICON) when pressing Volume Down +Power?
Pretoriano80 said:
This is odd, i heard that with the new JB bootloader the fastboot mode can be accessed even with locked bootloader, can you boot in fastboot mode (USB ICON) when pressing Volume Down +Power?
Click to expand...
Click to collapse
Not on JB. was trying to go back to ICS to root it again. I went from .30 to JB and back down 3 times trying to keep root. Didn't work cause OTA's would never install. Finally left it at ICS .30. Everything was fine for about an hour, then I rebooted. It never came back alive. Spinning circle.
redheadplantguy said:
Not on JB. was trying to go back to ICS to root it again. I went from .30 to JB and back down 3 times trying to keep root. Didn't work cause OTA's would never install. Finally left it at ICS .30. Everything was fine for about an hour, then I rebooted. It never came back alive. Spinning circle.
Click to expand...
Click to collapse
In this case you can't do anything to restore it if the recovery doesn't work. Try to Wipe Data and then check the recovery again, if still doesn't work ask a RMA ticket from Asus.
Just to be clear, what are you renaming your file to? It needs to be renamed to "EP201_768_SDUPDATE.zip" and on an SD card formatted to FAT32. Also, if you're working with a .zip you downloaded from ASUS, you need to extract that zip and rename the EXTRACTED zip file and place that one on the SD.
I'd also try a different SD card if that's not doing it for you. "E: failed to mount /SD card (no such file or directory)" already sounds like it's just not liking that particular SD card right now.
You could also try to download JB from ASUS and flash that file instead of ICS. That way, you will have your fastboot option back so that you can send ICS via fastboot, re-root, and upgrade. That's what I did when I was going through this yesterday trying to reroot after I was bricked.
Once you've over come that part, on to the rooting (and keeping root). It wasn't working with the JB from the ASUS site. I was able to flash it, but I kept losing root. I had to use the dlpkgfile method from my OTA to upgrade to JB in order to keep root. If you don't have that file, you can find one somewhere here or I can provide you with mine.
Good luck!
Alitheia said:
Just to be clear, what are you renaming your file to? It needs to be renamed to "EP201_768_SDUPDATE.zip" and on an SD card formatted to FAT32. Also, if you're working with a .zip you downloaded from ASUS, you need to extract that zip and rename the EXTRACTED zip file and place that one on the SD.
I'd also try a different SD card if that's not doing it for you. "E: failed to mount /SD card (no such file or directory)" already sounds like it's just not liking that particular SD card right now.
You could also try to download JB from ASUS and flash that file instead of ICS. That way, you will have your fastboot option back so that you can send ICS via fastboot, re-root, and upgrade. That's what I did when I was going through this yesterday trying to reroot after I was bricked.
Once you've over come that part, on to the rooting (and keeping root). It wasn't working with the JB from the ASUS site. I was able to flash it, but I kept losing root. I had to use the dlpkgfile method from my OTA to upgrade to JB in order to keep root. If you don't have that file, you can find one somewhere here or I can provide you with mine.
Good luck!
Click to expand...
Click to collapse
I tried all of those things. I stayed up all night trying everything I could think of. Nothing. I might just have to trip and drop it off a balcony and use best buy replacement warranty. I took it back several days ago cause of glitches. They wouldn't do anything cause they said my warranty covers breakage, not software.
redheadplantguy said:
I tried all of those things. I stayed up all night trying everything I could think of. Nothing. I might just have to trip and drop it off a balcony and use best buy replacement warranty. I took it back several days ago cause of glitches. They wouldn't do anything cause they said my warranty covers breakage, not software.
Click to expand...
Click to collapse
If you still can get to recovery mode, can you take about all your sd card(s), do a factory reset (data wipe) and see if boot up?
buhohitr said:
If you still can get to recovery mode, can you take about all your sd card(s), do a factory reset (data wipe) and see if boot up?
Click to expand...
Click to collapse
Thanks for those that tried to help, but that tablet overheated and melted down. burned my fingers. best buy exchanged it under factory defect. New one is rooted JB.
this thread can be closed now, thanks.
That would qualify as a 'terminal failure', indeed. Did you help it a bit? ; )
(This is just me having a sick mind, and a background in (bio)chemistry -- all (bio)chem guys/girls I know, including myself, are pyromaniacs -- when reading your last post, I cannot help but see large, now-empty bottles of easily combustible liquids and you swaying back and forth while on your knees, hands high up in the air, chanting "burn, m*****f*****, BURN!" Imagine the surprised faces at BB -- "overheated... oh, I see..." <takes over small, charred metal pancake>)
Haha, no.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2
redheadplantguy said:
Thanks for those that tried to help, but that tablet overheated and melted down. burned my fingers. best buy exchanged it under factory defect. New one is rooted JB.
this thread can be closed now, thanks.
Click to expand...
Click to collapse
Ya, they do that when you take a torch to them