Help, I want to know if theres anyway i can use an SD card to install or use it as a boot for my phone, I have a verykool rs90 and it currently doesnt have a OS, it gets stuck at the logo and its not recognized by my computer so I cant flash it, is there anyway i can do this through an SD card, PLS HELP
Zoulder said:
Help, I want to know if theres anyway i can use an SD card to install or use it as a boot for my phone, I have a verykool rs90 and it currently doesnt have a OS, it gets stuck at the logo and its not recognized by my computer so I cant flash it, is there anyway i can do this through an SD card, PLS HELP
Click to expand...
Click to collapse
In your previous thread you said you can boot the phone into Recovery mode, you further said that you've managed to get the update zip ready on the sd card but when you try to install it it says signature verfication failed and installation aborted . So it's evident that you can install OTA/ROM from external SD-card. BTW: To initiate mounting and booting from external SD-card instead of internal memory would require a heavy mod of Android's kernel ( read: boot.img ) and a specially prepared external SD-card ( replicating eMMC partition table by partitioning SD-card & flashing factory firmware images to these newly created partitions ).
That's what probably happened when you tried to flash
Finding update package...
Opening update package...
Verifying update package...
E:No signature (xxx files)
E:Verification failed
Installation aborted.
FYI:
Basically the ZIP File Signature Verification flag will enable flashing only if the ZIP file is signed properly by the developer. If ZIP isn't properly signed then it's treated as malware.
Advice:
Contact OEM's CS to get an orderly signed update.zip for your 7 years old low-end phone.
Related
I wiped everything, re-partioned sd-card and tried to install a new ROM..
But something have happend..
After i re-patrioned / wiped... and flash the rom (have tried a lot of ROM's now) i get errors..
Install from sdcard
Finding update package...
Opening update package...
E:Can't open /sdcard/Cronos-2-0J_.zip
(bad)
Installation aborted.
Happends now on every rom i install, have already tried again to re-partion.
What is the most basic way to re-partion ? settings i mean?
Anyone know what could be the problem..
The zip files cant be corrupt either.
* I also noticed that if i upload a ROM-file, then re-partion and wipe everything..
The rom is still on the sd-card..
I then deleted the rom from sdcard and re-partion again, and still..even duo i already deleted the file.. its there?
Maybe it is because of the SD Card.. So if you have another one try it
I had this same problem i had to do a full format of the SD card then all worked fine never had the problem again strange
If you ecejt the SD card before its done (or eject it wrong) you may and up with a bad file.
What you could do is:
Format your SD card.
Then put a rom on it.
Then go to my pc, and find ur card, then right click and select eject
Yea something strange with your sdcard.
Try as they stated above. Remove the sdcard from your phone. Insert it back in.
Try to reformat it with a different sdcard setup like: no swap, no ext only fat32.
Then check if the card is still behaving the same if not good. If so maybe the sdcard is just defect?
Good Luck.
Arranmc182 said:
I had this same problem i had to do a full format of the SD card then all worked fine never had the problem again strange
Click to expand...
Click to collapse
+1
same issue here, solved this way.
Did you flash an exotic recovery image by any chance?
You can always reflash 1 back by pushing it to /cache/ and flashing from there.
A radical way to overcome this would be to delete the partition table on your SDcard and let your current rom reformat it.
Im bumping my own thread.. Last time i bought a new sdcard..
Now this **** have happend again.. I get the same error as before!
How should i do this? Is there any other way then whats posted now?
Happens on all Roms
This is quite obvious but you make no mention of what recovery image is on you sd card?
I assume you saved the old image you were using and put it back on your sd card
Yes,maybe you recovery image is damaged.
Try to install again!
It sounds like your sd card is not actually partitioning since the rom is still on the sd card. To partition the sd manually try this:
I'm going to assume the following:
You are using Amon Ra recovery
You have not downloaded Clock Work recovery
You can still get into recovery using Amon Ra
You have SDK and JDK installed
You're using windows
Plug your phone into the computer. Open a command prompt (hit start and type cmd and press enter). Direct it to read from the tools directory of sdk " cd C:\android-sdk-windows\tools" for most people. Now follow the directions from this how-to http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/. Stop after step 4 and type "quit" unless you plan on repartioning your sd card (in which case, choose which partitions you wish to make). Move the new rom you want to boot to the sd card and try again.
I want to run GingerStreak, but my phone will not let me fllash -any- roms. I'm stuck on 1.9. Can anyone help me? And to be more clear, I used to be able to flash roms, but now I get an error. Even if I change the name to update.zip.
We need more information. What recovery are you running? What rom are you trying to flash? What is the error?
lordmorphous said:
We need more information. What recovery are you running? What rom are you trying to flash? What is the error?
Click to expand...
Click to collapse
I have StreakDroid 1.9.0 on my phone...And I was trying to update to 1.9.1. Got the rom on there. Got into recovery. When I hit 'apply sdcard:update.zip, I see the yes, it says 'Yes - Install /sdcard/update.zip'...I click it, and it says
'Installing: SDCARD:update.zip
Finding update package...
E:Can't mount /dev/block/mmcblk1p1
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.'
Have you tried reflashing your recovery? Grab the latest version of MultiRecoveryFlasher and give that a shot.
Sent from my Dell Streak using Tapatalk
Suggestion:
If you are sure you have StreakMod Recovery installed:
Remove you current SD Card
Install another SD Card
Format the card while in the Streak (you will lose any files on the SD Card)
Put the ROM files on it and attempt the upgrade
OR
Remove your sd card.
backup everything on it somewhere
put sd card back in Streak
Format the card (you will lose all files)
Put the files you need to flash ROM on the SD card and attempt upgrade
What ever ROM you install do a factory reset from the first Revovery page.
Copy the files you need back to the Sd Card.
Like I said, I was able to fllash roms before. Yes, I'm sure I have Clockwork on it.
I suggest that you use StreakMod Recovery instead and that you check your SD card as I wrote in my previous post.
It sometimes happens randomly, try powering the device off for a bit and repeating.
If it doesnt work after several tries then try the above, if it doesnt work with a diff card it might be a hardware issue in something, likely the streak
Yeah, it hasn't worked for months. So, I really Don't know.
Yes try updating recovery
Thanks to the help of Lordmorphous, I figured it out. My internal SD card had come unseated slightly. So, I cut off the plastic above the internal sd card, and reseated it.
Hi guys,
My SD card got corrupted before flashing a rom, so I'm a bit stuck (I can access the CWM menu, the kernel is fine).
So I formatted the card to FAT32 (tried other formats) but when I try and flash an update.zip from it I get
E:Can't mount /sdcard/
So I'm thinking, are there some files missing from the SD card that CWM/android need to interact with it? I can imagine these files were wiped when I did a format. Like superuser files or something? You know also, those hidden files beginning with '.'
I've tried all the usual methods like formatting using SDFormatter and stuff - still, CWM can't see it (my computer can if USB is mounted). Am I right in thinking I need some kind of system files on the SD card?
Any help?
Thanks in advance
the best would be paid copy a rom sd card and flash, or flash a rom stock also either ics or gb and see if there cel recognize SD can not think of anything else. :highfive:
Ok, I guess I'll try that if there's nothing else. If I flash an official .ftf with Flashtool will I need to do anything to my bootloader (currently unlocked)?
Edit: I've been reading around and it seems almost certain that my sd card just needs some vital files on it for CWM and android...
Try by simply reflashing any kernel with cwm if your sd card is readable from pc it is not corrupted, it's more likely somethign wrong with cwm, you should be able to fix reflashing kernel which shouldn't be much of a prob since you have unlocked bl
Rudjgaard said:
Try by simply reflashing any kernel with cwm if your sd card is readable from pc it is not corrupted, it's more likely somethign wrong with cwm, you should be able to fix reflashing kernel which shouldn't be much of a prob since you have unlocked bl
Click to expand...
Click to collapse
Hey nice idea, but I tried that earlier and multiple kernels give the same error - it can't be CWM, it must be the SD card (or what's not on the SD card).
Edit: I've tried chkdsk and formatting to a variety of systems using a variety of partition managers, nothings works, my phone just can't mount the SD.
notoxa said:
Hi guys,
My SD card got corrupted before flashing a rom, so I'm a bit stuck (I can access the CWM menu, the kernel is fine).
So I formatted the card to FAT32 (tried other formats) but when I try and flash an update.zip from it I get
E:Can't mount /sdcard/
So I'm thinking, are there some files missing from the SD card that CWM/android need to interact with it? I can imagine these files were wiped when I did a format. Like superuser files or something? You know also, those hidden files beginning with '.'
I've tried all the usual methods like formatting using SDFormatter and stuff - still, CWM can't see it (my computer can if USB is mounted). Am I right in thinking I need some kind of system files on the SD card?
Any help?
Thanks in advance
Click to expand...
Click to collapse
First backup your nandroid backup (if you have one) in a secure place (not the sdcard)
Put your sd card on some other android phone with cwm and format it from the cwm mount/storage option.
if you don't have a nandroid backup skip the next two steps.
mount the sdcard in your computer and create two folders in the sdcard (a folder inside a folder) name the parent folder as "clockworkmod" and child as "backup" .
Put your nandroid backup in /sdcard/clockworkmod/backup/
Now put the Rom zip file you want to flash in the root of the sd card
Power down your phone.
Put the memory card in your phone
Boot into cwm and try to flash the rom.
If the second step fails with "error mounting sd card" try with another memory card or with another phone.
PRESS THANKS IF I HAVE HELPED YOU
sent from my smultron
I'm dealing with a conflict with my Scandisk microsd 32 gb card. I'm running CM 10.1 on an Android 4.2.1 Galaxy s3 i9300, and my phone will not mount my sd card when it's in exfat format, but my phone will also not read my microsd (for installing updates to CM 10.1) when it's in fat32. This means that when I want to add media to my card I have to format it to fat32 and then re-format it to exfat when I want to install updates to CM. Am I missing something? Is there a way around this? Thanks in advance for the help.
Can you be more clear about the updates issue? Why does it require exfat?
PS it's SanDisk
Glebun said:
Can you be more clear about the updates issue? Why does it require exfat?
PS it's SanDisk
Click to expand...
Click to collapse
It's not specifically the updates. When I format my sdcard to fat32 and run recovery mode, the phone does not see the sd card. However, if I change the format to exfat, the phone reads the sdcard in recovery, but then it won't mount the sdcard when I reboot the phone. I get an "sd card damaged" error. Likewise, when I connect phone to PC via USB my PC does not detect the card. Everything is solved by converting to fat32 except the issue of installing updates or flashing ROMs, kernels, etc.
I read another post, though I can't remember where, that said that the size of the card (specifically, if it is greater or less than 32 gb) effects what format theS III will read it in.
What recovery are you using? I'm using TWRP and it's recognizing my 64gb fat32 card just fine
Glebun said:
What recovery are you using? I'm using TWRP and it's recognizing my 64gb fat32 card just fine
Click to expand...
Click to collapse
CWM-based recovery v5.5.0.4 :: CF-v1.5
Update your recovery .
Possible faulty card .
jje
JJEgan said:
Update your recovery .
Possible faulty card .
jje
Click to expand...
Click to collapse
Thanks. Could you provide a link to a thread that could assist in updating the recovery.
Check the first rule of XDA
Glebun said:
Check the first rule of XDA
Click to expand...
Click to collapse
Okay. Looking into the update. In the meantime I thought I'd share the error message I get when I use CM updater to apply a Nightly update.
When I use CM updater, the system reboots and gives me the following error message under "verifying update package...":
E: failed to open /sdcard/0/cmupdater/cm-10.1-20130107-NIGHTLY-i9300.zip (No such file directory) E: Signature verification failed, Installation aborted
If I then pull the update from get.cm, I can access it from external storage, but I get this error message when I try to install it:
E: failed to verify whole-file signature
E: Signature verification failed
I can access the CM updater file from my file manager in-phone, and I can even see the nightly update zip files to be unpacked, but they don't show up in recovery.
Disable signature verification in recovery
Glebun said:
Disable signature verification in recovery
Click to expand...
Click to collapse
I did this but got the same response. I just noticed that when I use CM updater to apply updates, my phone boots into Android 3e recovery and not CWM, which I have. How do I avoid that happening?
Do you have CWM installed? Just boot into it and flash it manually
Glebun said:
Check the first rule of XDA
Click to expand...
Click to collapse
The first rule of XDA is you don't talk about XDA?
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Yhcho said:
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Click to expand...
Click to collapse
I have followed this thread and I got an error message saying failed due to low battery. I will just charge the phone for a while and see if it gives same error.
I have done the fastboot recovery method from here and its keep giving me "failed (remote: not allowed)" messages.
my Legend is already rooted and currently on S-off.
I have solved the problem.
It was memory card problem. my legend works after installing CM7 using different SD card.
I am suspecting if its because I have messed up something with memory card while dividing partitions to install a Jelllybean rom,
However the faulty memory card is still functioning well on my pc which made me think there is no problem with it.