Database Info

[Q] Scoured the net with no luck... issue with revolutionary and flashing rom. Evo 4g

Hey all,
Recently used revolutionary to gain S-Off and root on an Evo 4g that was running GB. I am now not able to flash any roms. Have tried 4 different CM's and a Sense Rom.
I am also not able to restore my backup. I wipe data/cache/dalvik before every try.
The specific message I am getting is
assert failed: write_raw_image("/tmp/boot.img, "boot")
E:Error in /sdcard/update-cm-7.0.3.1-SUpersonic-signed.zip
(Status 7)
Installation aborted
Right now my phone is basically worthless as I cannot boot into anything...
Anyone?
Thanks

NM Problem solved
Got it. Thanks

Any way to reinstall the OS from scratch on the phone????

So I was trying to get Wallet on my phone, complete mess, the phone went fubar, I can get the phone to work on stock 2.3.4 but can't update to 2.3.6 nor I can install any ROM, and yes, the phone is rooted.
If I try on updating to 2.3.6 I get >>>
assert failed: less_than_int(1303507835,getprop("ro.build.date.utc")
Status 7
If I try to install any Rom I get >>>
assert failed: getprop("ro.product.device") == "crespo" ll
getprop("ro.build.product") == "crespo"
And trying to restore will simply give me system.img not found.......
So if nothing works towards, then I will simply and rather prefer to do a clean install so it will wipe everything, but, is there a way to "Wipe" everything and reinstall?
And yes, I already tried the "Wipe data/factory reset", no good at all.
Upd: I can install kernels.....go figure.....

If this is a NS4G you can use OneClickStock

tylerwatt12 said:
If this is a NS4G you can use OneClickStock
Click to expand...
Click to collapse
Thx Mate but I have a i9023 (NS 3G+ if u can say), I was able to downgrade using the guide from TheUnlockr and it was a PITA since the file somehow is not really the best to work on the NS but I was able to update to 2.3.6.
And since now I'm updated and found a way to mess the phone even more it is time to try the Wallet again!!!

please help with my phone: can't update ROM, keep getting error msgs!

Hi all, I recently rooted my NS4G and flashed my rom to the Brainmaster's MIUI 10.14.11. It worked great for a while and then I started having issues with it so I tried to update it to the 10.28.11 version and it wouldn't let me. I was finally able to reflash to GRJ06D, but no other custom rom would work. I'm using CWM 5.0.2.0. ROM Manager won't work either after it gets into recovery. I get the error message...
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo 4g"
E: Error in /sdcard/
(Status 7)
Even trying to do an OTA system update via Sprint freezes and gives me the Android error message (triangle with exclamation). I've tried many many times to reflash and no success.
What do I need to do?

This issue has been reported a few times and there are a few ways to fix it;
1) Make sure you downloaded the right ROM; ie, the ROMs from the Nexus 4G Development section
2) If you're installing ROMs through ROM Manager, don't. Reboot into recovery mode, do a full data, cache and dalvik wipe and then flash the ROM zip while still in the CWM recovery mode
3) Else; try a different version of CWM, make sure it's compatible with your device and then do step 2 again.
Good luck.
Greetz

I think you should flash CWM again then wipe data, cache, dalvik, boot, then flash rom again and report your findings back to us.

I had this issue last week.. You've probably tried to flash the incorrect ROM originally or something..
The only way I could fix it was to boot into download mode, and flash the PDA, phone and modem via Odin. You can get the firmware from samfirmware.com

Thanks for the responses, its funny because I flashed the 4.0.1.0 CWM, which was for the GSM version and then reflashed to 5.0.2.0 (NS4G) in order for the MIUI rom to work. It was after flashing that and running MIUI for a while that I started having issues so I reflashed a new 5.0.2.0 and its still the same.
I haven't been able to flash back to the CWM 3 that it originally came with because I lost my micro USB cable. I hope to get this fixed soon! Thanks again, will keep you guys posted.

[Q] E:signature verification failed?

Hello and thank you ahead of time,
I have been trying to load my first ROM onto my Nexus S after finding the ICS "update" that Google gave me was a load of troublesome crap.
Through this forum I successfully rooted my phone and installed Super User app. However after wiping date/factory reset and wiping the cache, I tried to install Cyanogen and get the following lines:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
Your guidance is greatly appreciated!

The recovery on your phone, does it say Clockworkmod recovery at the top? It sounds like you may still be using the stock recovery.

Yes it says Android system recovery <3e> at the top.
I installed Clockwork Mod recovery before I rooted my phone. I guess with the wiping of my device it is gone.

MC Pono said:
Yes it says Android system recovery <3e> at the top.
I installed Clockwork Mod recovery before I rooted my phone. I guess with the wiping of my device it is gone.
Click to expand...
Click to collapse
That does happen. You'll need to install clockworkmod again as the stock recovery cannot flash unofficial roms.

Does anyone have a link to Clockwork mod that I can download right to my phone? I'm having issues in general with my computer's internet and in China I apparently can't find or download directly through the marketplace.

i know the link but i cannot leave reply
Sent from my Nexus S using XDA App

..

Election Day said:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
Click to expand...
Click to collapse
pardon my ignorance.
will this apply for SGT P1000 also? if so, how to use this "img" file?
i had been running back and forth with this rom flashing for a week now. i just can't get through the signature verification failed part.
help will be highly appreciated.

i already installed clock work mode, but it's still show recovery e3, what should i do?

After you instal the cwm flash the recovery from cwm and reboot into recovery,this is a cwm option. From the recovery flash your favourite rom.
Sent from my Nexus S using xda app-developers app

[Q] STUCK ON CM 9.1 r13/CANT FLASH OTHER ROMS

Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.

Use TWRP instead of CWM. This should fix the issue.

Tried it thru the twrp app and it just launches into cwm recovery and does same status 4 error
Thanks for replying though!
Sent from my XT1032 using xda app-developers app

'Cwm-based recovery v6.0.4.6
--Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /storage/sdcard0/MikTouch-0.7-signed. Zip
(Status 4)
Installation aborted
Sent from my XT1032 using xda app-developers app

I didn't mean the app found on Play Store. I meant the actual TWRP recovery.
You'll have to connect your phone to your PC, boot into bootloader, and flash the TWRP recovery, which will replace the existing CWM recovery.

Moto g looks like a great phone for the price, but I would want to fix my double shot too.
First off, the getprop errors you were getting were saying you were trying to flash a ROM for sensation on your doubleshot, not a good idea, don't delete getprop from updater-script no matter what the internet says, this is a good warning
Don't use an app for flashing, use recovery
But before you proceed any further I would suggest to boot into bootloader and write down every thing from that screen here, word for word
Then you will be sure to get the exact links and info, I wouldn't do anything until then, not to say @abe5 is having you bad info, he is correct, but I have a feeling there may be more info needed here
Sent from my Nexus 7 using XDA Premium 4 mobile app

Bootloader info
Hi,
OK thanks to both of you for your help! ...I guess I would rather check/be sure than do something worse to my phone.
Your right Moto G is great phone..I am pretty impressed so far...for the price. Only let down is the camera....I miss the doubleshot great camera...but you cant have it all....well not for £130
OK SO INTO BOOTLOADER..... (front screen reads as follows - hope this is what you mean?!)
***UNLOCKED***
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
NOV 21 2011,20:20:47
FASTBOOT
VOL UP.... ETC ETC
.....

fickleama said:
Hi,
I need some help. Firstly I'm quite a noob so please go easy on me, have only flashed/rooted a couple of phones before this...both with pretty much no issues.
I flashed the CM 9.1 A while back to improve it, and decided I wanted to change it due to few bugs annoying me too much...such as the restarts, crazy battery life and most annoyingly of all calls only being able to be heard on loudspeaker! Buts can't seem to get any other rom to flash - tried 2 - samsation v6.0 kerneldev101 & MikTouch- 0.7-signed.
When trying to flash firstly 'samsation v6.0' i encountered an error code '"assert failed: getprop("ro.product.device") == "pyramid"
E:\Error in /storage/sdcard0/samsation v6.0.zip
(status 7)
Installation aborted.
and to try and overcome this I opened the updater script from rom zip and deleted the line 'assert(getprop("ro.product.device") == "pyramid" || getprop("ro.build.product") == "pyramid");'.....after reading in forums it could be this. After this line is deleted the flash attempt is 'opening update package...installing update...installation aborted'
I then tried MikTouch 0.7 and it came up with the 'status 7' error, so I deleted the first line of the updater script and now I am getting a 'status 4' error...even if I try to flash thru rom manager - CWM app.
Driving me crazy! Any help much appreciated.
even tried a different SD card to see if that makes a difference....and nope
installed new CWM - V6.0.4.6 after reading that may be the prob. no difference
To be honest it all P'd me off so much just went and bought myself the Moto G instead...but would still like to fix this one and get it even back to a stock like ROM so at least it functions properly but without all the bloatware.
Click to expand...
Click to collapse
Don't use CWM above 6.0.2.5 for flashing an older ROM. 6.0.4.6 is designed for KitKat and will fail older ROMs.

everything looks good on bootloader so the issue is with recovery or rom.zip
personally i think its the rom.zip, but I also recommend TWRP recovery
so i would download twrp (without dumblock) from HERE
and flash with fastboot, also do some erasing in fastboot for good mesure
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
the md5sum for recovery is listed next to download, be sure it matches use command line on linux or this for windows
but what i really think is the problem is the roms, bad download or whatever, the status 4 and status 7 are related to updater script, so either you playing with them messed them up or they were corrupt from the start
md5sum for MikTouch-0.7-signed.zip should be BAE9153946B02251621547DBFB537387
if not re download
now it is possible that the newer recoveries f\wont flash older roms, like Fuzi0719 said, but in theory they should and i have not had issues myself
but if need be weekends has posted older recoveries HERE be sure to thank him
flash with fastboot if you TWRP fails you
also when i see this --Installing: /storage/sdcard0/MikTouch-0.7-signed.zip
make me wonder, if i am correct the path on this phone is just /sdcard/MikTouch-0.7-signed.zip
but i cant recall as it has been months since i used my doubleshot, its just how i remember even the newer recoveries find sdcard path here
so maybe for good measure take everything important off sdcard and format to fat32
then put new rom on the root freshly formatted sdcard (not in any folders) before you flash
hope it all works out, if there is an issue let us know!

well I spent the whole evening mucking about with it and I have conquered it. Thanks guys for all the help...couldn't have done it without you!
After firstly having to switch to an older laptop as win 8.1 not compatible with htc drivers ...
I flashed TWRP and tried to flash new rom (miktouch 0.7) again through that, said failed. then tried to install the current ROM CM9.1 just out of interest which it also 'failed'
then considered the cwm comment about version, so flashed cwm 5.5.0.4. thru Hasoon 2000's ALL in 1 kit I still had. I then tried to reflash the current CM9.1 again, and it went through.....At the same time it occurred to me about me having 'messed' with the script files of MikTouch 0.7 ...maybe being the cause, so luckily, I had an original copy of the rom zip (kept justin kase lol) and then tried this method.
I now don't know if it was the script file or the cwm version number but hallelujah it WORKED. I honestly thought I was stuck on cm9.1 forever, I've spent so much time reading/trying to flash anything else!
Can't thank you all enough, whatever it was, I think I have overcome it now! phew.
:cyclops: :victory: