I'm new to rooting and installing custom roms. I used unrevoked 3 to root my ego, then I created an nandroid and wipe my phone. Next, I rebooted the phone to download the free version of ROM manager from the market. I used the ROM manager to download cyanogenmod 6 (stable). After downloading the rom, I did as the screen prompted me and wipe the phone and created a backup. From here the installation process begins and end with
Welcome to Cyanogenmod 6.0.0-supersonic assert failed: getprop ("ro.bootloader")="0.76.2000"//9.000"
E: Error in /sdcard/clockwork/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip
I haven't a clue what to do at this point.
Can someone please help?
"E: Error in /sdcard/clockwork/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip"
Read this link, I think it is about the same problem.
http://www.actuarialoutpost.com/actuarial_discussion_forum/showthread.php?t=195406&page=46
If I still can not post a link cause I am new, then I googled this:
mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip"
I got three hits, read the first one "maybe we need and android tweeking ...."
Also check this out. I am tempted to say you downloaded the link to the actual file that you want and not the file. Here is the link to the actual file.
http://mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
Click that link and then you download the file you need.
Ref:
http://androidforums.com/evo-4g-all-things-root/175655-cyanogen6-link.html
hey,
thanks for trying to help. I'm still having the same problem.
No app2sd partition found. Skipping format of /sd-ext. (is this the problem?????)
--Installing: SDCARD: /clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip
Finding update package...
Opening update package...
Installing update...
Welcome to Cyanogenmod-6.0.0-Supersonic!
assert failed: getprop("ro.bootloader") =="0.76.2000"
getprop("ro.bootloader")=="0.79.0000"
E: Error in /sdcard/clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue
PLEASE HELP....
Hello,
I have Android 2.1(Eclair), when I start my mobile, its show a Android logo with '!' (Recovery Mode)
Its show E:Can't find MiSC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
I am already try to reboot, wide data factory reset option.
please help me - how can I reflash my mobile?
More info please
Before people can help you, you need to give more information.
What is the model for your phone and is it rooted?
If so, what ROM is it running and what custom recovery do you have?
demoneyes905 said:
Before people can help you, you need to give more information.
What is the model for your phone and is it rooted?
If so, what ROM is it running and what custom recovery do you have?
Click to expand...
Click to collapse
Lots of Thanks for reply,
I have Micromax A60, rooted with "SuperOneClick v1.6.5"(http://forum.xda-developers.com/showthread.php?t=803682)
How I know about ROM?
Every time my phone start in recovery mode and show 4 options.
1. Reboot system no
2. Apply sdcard:update.zip (Already try to add update.zip in sdcard but every time show error: Signature )
3. wipe data/factory reset (not useful )
4. wite catche partition..
E:Can't find MISC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
E:Can't find MISC:
Hm....Adb
kunnusingh said:
Lots of Thanks for reply,
I have Micromax A60, rooted with "SuperOneClick v1.6.5"(http://forum.xda-developers.com/showthread.php?t=803682)
How I know about ROM?
Every time my phone start in recovery mode and show 4 options.
1. Reboot system no
2. Apply sdcard:update.zip (Already try to add update.zip in sdcard but every time show error: Signature )
3. wipe data/factory reset (not useful )
4. wite catche partition..
E:Can't find MISC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
E:Can't find MISC:
Click to expand...
Click to collapse
Ok you can't "apply sdcard:update.zip" because even though you rooted your phone, you don't have a custom recovery. You have the stock recovery image that comes with your phone. This means that every zip you try to "apply" or flash will automatically be checked for a signature (to make sure its a valid update from the manufacturer). Since the ROMs usually don't have signatures, it won't work
Never mind about finding out the ROM. since you have a stock recovery, it looks like you haven't put any custom ROM on it. you are running the stock android OS that came with the phone.
It seems your OS got messed up when you tried to root the phone. The One Click root method you used I believe wasn't fully compatible with your phone. You should have used "Universal Root." Anyway, Give me a day or two. I will see If I can find you an official zip belonging to your manufacturer. THAT you can push back onto your phone and get your OS back and in working order.
Cheers!
P.S: Check if there is an option in recovery mode called "Toggle Signature verification" I doubt it but if there is it would DEFINITELY help you.
demoneyes905 said:
Ok you can't "apply sdcard:update.zip" because even though you rooted your phone, you don't have a custom recovery. You have the stock recovery image that comes with your phone. This means that every zip you try to "apply" or flash will automatically be checked for a signature (to make sure its a valid update from the manufacturer). Since the ROMs usually don't have signatures, it won't work
Never mind about finding out the ROM. since you have a stock recovery, it looks like you haven't put any custom ROM on it. you are running the stock android OS that came with the phone.
It seems your OS got messed up when you tried to root the phone. The One Click root method you used I believe wasn't fully compatible with your phone. You should have used "Universal Root." Anyway, Give me a day or two. I will see If I can find you an official zip belonging to your manufacturer. THAT you can push back onto your phone and get your OS back and in working order.
Cheers!
P.S: Check if there is an option in recovery mode called "Toggle Signature verification" I doubt it but if there is it would DEFINITELY help you.
Click to expand...
Click to collapse
I have a Micromax A60 from this company( - http://www.micromaxinfo.com/product.php?cat=Think_Innovative&product=android_A60 )
"Toggle Signature verification" not show in my recovery mode.
If company not release "update.zip" then I can't fix my phone?(dead phone ?)
kunnusingh said:
I have a Micromax A60 from this company( - http://www.micromaxinfo.com/product.php?cat=Think_Innovative&product=android_A60 )
"Toggle Signature verification" not show in my recovery mode.
If company not release "update.zip" then I can't fix my phone?(dead phone ?)
Click to expand...
Click to collapse
I'd recommend changing to CWM recovery via rom manager if you need to toggle verification. Rom manager from the market will flash a recovery for you also.
theimpaler747 said:
I'd recommend changing to CWM recovery via rom manager if you need to toggle verification. Rom manager from the market will flash a recovery for you also.
Click to expand...
Click to collapse
I have no access to USB debugging so I can't use adb command and my phone always start in recovery mode, show only 4 options.
How can I install CWM recovery mode?
It is possible to reinstall whole OS?
Same Problem with HTC Hero, after one click (z4root) root
Hi @ all,
i have the same problem with my hero, and every solution that i can find is using fastboot, but with Eclair i cant´s use it.
So please help.
Here is some dato of my hero:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
Radio-6.35.15.11
1. If your USB debugging is enable then you can fix your problem.
2. official update.zip can fix your problem.
You can't do anything(but your mobile company can help you)
1. Your mobile company not release any update for your device
2. If USB Debugging is disable
I send my Micromax Mobile on 08 Feb, 2011 and Still no info on my device, Micromax = Poor Quality Support, Wastage of money.
@Micromax - Please close your company.... and move your company to your own country....
I tryed to fix it with every update.zip I found in web by
downloading the zip
rename to update.zip
format sd card
copy update.zip to sd card
start in recovery mode
try to start update
... and get a varification failed error
Has somebody a working update.zip, or can say where can I get it and if my steps are right?
1. If your update.zip is not official(signed) then you can't update your device.
Download this and rename this file to update.zip and retry.
Its a signed update.zip
http://www.filecrop.com/40683206/index.html (Link is valid for 30 minute)
If not work then just find your radio update in this list..
http://www.filecrop.com/update-Hero.html
Thank you very much, I will try it tonight.
Damn, now I get a
"failed to verify whole-file signature" error???
What´s wrong now?
Maybe I need a Certificate to put on my sdcard for the whole file?
HTC Hero Problem Solved
I have solved my Problem.
I downloaded the original RUU from shipped-roms.com, swtiched to Fastboot Mode and installed the RUU. And voilà, Hero is new again.
E:Cant mount/cache/recovery/last_log
any one plzz help me..
i have a micromax a60 brought in 2011
i want to update my ph 2.1 to 2.2(Foryo)
but i get a error on recovery mode..
E: Failed to find cache partition to mount at “/cache”
E:Cant mount/cache/recovery/last_log
E:cant open/cache/recovery/last_log
E:Failed to find cache partition to mount at cache.
Then i try to install zip from sd card, choose zip from sd card select Jet 2.1.zip. It ends up at.
assert failed: write_raw_image(“/tmp/boot.img”,”boot”)
E:Error in sdcard/installations/Jet 2.1.zip (status 7).
Installation aborted.
i flesh my phone throw android download toll but he is still showing this message.. plz help me...
I am trying to restore my nexus one to stock. here is the thread I am trying to follow.
http://forum.androidspin.com/showthread.php/4736-GUIDE-Reset-your-Google-Nexus-One-back-to-Stock?
This is what I am getting when I try to install FRG33 renamed to PASSIMG.zip
-- Installing: /sdcard/PASSIMG.zip
Finding update package...
Opening update package...
E:Cant open /sdcard/PASSIMG.zip
(bad)
Installation aborted
On my phone is
ClockworkMod Recovery v3.0.0.5
HBOOT 0.35.0017
RADIO-5.08.00.04
MICROP-0b15
NEXUSONE PVT SHIP S-ON
I have 10 hours into this project and I tried the CM7 but can't get any google apps onto the phone. not even market place.
I'm not sure if this is exactly what you arelooking for or not but i had to rename my .zip folder "PB31IMG.zip" make sure it is placed in the ROOT of your SD card not in any folders!
I think I've just successfully bricked my Photon Q.
Right now I'm stuck with Clockwork recovery (v 6.0.1.3) and my system backed up.
I've tried to install CM12 (cm-12-20150330-NIGHTLY-xt897) but it gives me an error :
Code:
Installing update...
Warning: No file_contextsThis package is for device: xt897asanti_c; this device is asanti.
E: Error in sdcard 0 update zip (Status 7)
Installation aborted.
When trying to recover my system from backup it gives me :
Code:
E: format_volume: make_extf4fs failed on dev block platform msm_sdcc.1 by-name system
Error while formatting system!
Right now I'd like to install ANY CM that would actually work. Please help!
Flash the correct recovery.
Use the one in this: http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-0-photon-q-t3034552
or this thread: http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781
Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?
Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.