Develop Bugs

Trouble flashing wimaxx

Ok first off new to this business........ Just rooted yesterday. All seemed to go well. i used the simpleroot tool. I'm pretty sure I got full acess since I get the # in a shell.
Anyway here is the issue. new radio, new rom ( I have tried both CM and Fresh) currently have Fresh installed and working. However I have not been able to flash the new wimaxx.
I have tried with both Clockwork and Amon_Ra recovery.
Flash radio - Successful
Flash rom - Successful
Flash wimax - get this error E: Multiple firmware images, E: Can't store zip image, Installation Aborted
Any help here would be appriciated.
The only question I might have is with RA recovery when I tried to wipe the SD ext partition it told me I need to do that with adb.
Thanks
Noel

N_Jones said:
Ok first off new to this business........ Just rooted yesterday. All seemed to go well. i used the simpleroot tool. I'm pretty sure I got full acess since I get the # in a shell.
Anyway here is the issue. new radio, new rom ( I have tried both CM and Fresh) currently have Fresh installed and working. However I have not been able to flash the new wimaxx.
I have tried with both Clockwork and Amon_Ra recovery.
Flash radio - Successful
Flash rom - Successful
Flash wimax - get this error E: Multiple firmware images, E: Can't store zip image, Installation Aborted
Any help here would be appriciated.
The only question I might have is with RA recovery when I tried to wipe the SD ext partition it told me I need to do that with adb.
Thanks
Noel
Click to expand...
Click to collapse
After flashing rom. Reboot. It will then install the RADIO. Radio installation requires one more extra step after flashing. Once thats done. Load into Android. Then go back in recovery then flash the WIMAX.

+1 the above I use Ra and flashed both just fine.

[Q] Cannot flash to other roms (boot image issue??)

I'm fairly new to rooting and flashing, but I can figure things out usually after a bit of research. This has me completely stumped though because I have no idea what to attribute my problem to:
I rooted my Evo a few weeks ago and flashed CM7. The problems I had after flashing CM7 was my GPS and I had 1x instead of 3G. Note: I have also updated my CM7 with the recent updates.
I researched some fixes for the GPS/1x issue, which meant I needed to flash to a sense-based rom. I tried flashing a sense-based rom (several different ones) on several occasions via Clockwork/Rom Manager and I had no luck- it would just reboot to the white screen over and over.
The problem I'd like to resolve in this thread is how to figure out why I am unable to flash to *any* rom. I just attempted flashing KingsRom (via Rom Manager) and everything seemed to be going quite well until the very end where it scrolled so fast I could barely catch what the error was- and it seemed to be something with the "boot image."
Side note: During one of my previous attempts at flashing a different rom, which of course was unsuccessful, I was unable to flash a restore of my CM7 backup and I received this error: "error while flashing to boot image." However after just going at it over and over again I managed to flash a fresh CM7
I'd really appreciate any help as it seems a simple flash is giving me a lot of trouble. If any details about my phone are needed to help resolve this please let me know (I don't know what would be necessary to post).

Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk

plainjane said:
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
+1 on what Jane said. You can use rom manager to flash RA recovery (alternate recovery) but don't use it for flashing roms. Just wipe like she said and flash the zip manually through RA.
Sent from "The EVO" using XDA Premium

I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?

subjectdelta said:
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
Click to expand...
Click to collapse
Are you wiping fully between installs? It seems like your boot partition may be corrupt... or getting there, if that's possible. Try wiping everything, boot included, and flashing again. The only other thing I can think to do is unroot & go back to stock, then reroot & try again...?

[Q] Can't make a back-up: Signature failing

Ok. So I've rooted using Zedomax's Kernal.
I'm not trying to make a back-up of my stock ROM, but there is an issue.
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
[COLOR="Red"]E:failed to verify whole-file signature
E:signature verification failed[/COLOR]
Installation aborted.
[code]
I'm having some weird verification issue. I'm trying to make a back-up of my Stock ROM since that is VERY important. :p, but as you can see, I can't. Any ideas?
I've been searching, but I've seen things on where people are trying to flash a ROM and having this issue. It was solved by renaming the ROM to update.zip. As you can see, I'm not trying to flash a ROM, I'm trying to make a back-up, so that's not going to work for me.
Thanks for any help. Finally got my phone back from that guy over on mobiletechvideos, and I'm not trying to get it bricked again. Taking precautions. :cool:

FIXED (I think): So All I did was flash CWM using Odin instead of using ROM Manager, and it gave me CWM instead of the Stock Recovery. So now I was able to make a back-up.
I think I lost my Root, but since I have a back-up I don't really care anymore. I'll just flash the Kernal again and then just flash Starburst.

Hanging on Clockwork Mod
I did exactly what you did, and then reflashed ZedoMax's ROM, but think it did not work right. When I reboot into recovery, I get the exclamation point inside a triangle with little green android guy, and have to hold down power button long time and _then_ it reboots into clockwork mod. That’s not right, is it? It's a SGS2, Sprint, rooted, and then ran into same trouble as you: Recovery 3e requires signature verification for flashing external files, so it balked, throws error can't read file signature, hard stop. Replaced CWM with this: acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar to try to get around rebooting issue, but I am not good to go yet, am I? Do I have to go back to stock and start over?

Same problem. Anyone?

pdaddy said:
Same problem. Anyone?
Click to expand...
Click to collapse
If you want a kernel that overclocks, I say go with Rogue Desperado. Zedomax hasn't been updated in a long time and you will get a lot more user support because most people overclocking are either using Rogue with SETCPU or repacked stock with Tegrak app. I honestly don't remember if Zedomax even has the latest version of CWM which is 5.0.2.7. If you want to play it safer, go with one of the kernels I mentioned and you wont have any issues with backups or restoring them
Sent from my SPH-D710 using xda premium

assert failed when applying most recent OTA update

I've got the ATT S3 and have been trying to apply the most recent OTA patch, but am unable to at this point. My phone is rooted. I had the Google wallet fix installed - so I tried flashing my nandroid backup from before I did that, still unable to apply. I get the following error in CWM when applying the .zip.
I searched but was unable to find anyone else with this problem.
Code:
Verifying current system...
assert failed: apply_patch_check("/system/app/Nfc.apk", "b0f957f4bc320ba9be0473306f89c1a336d7cbc7", "59e610a76e01241e0a9de36e0ea3c47f144cf0ef") E:Error in /cache/fota/2400258.cfg
(Status 7)
Installation aborted.
I'm thinking maybe just doing a factory reset and then applying and starting from scratch might do it, but want to avoid that option if possible.

thefightforgood said:
I've got the ATT S3 and have been trying to apply the most recent OTA patch, but am unable to at this point. My phone is rooted. I had the Google wallet fix installed - so I tried flashing my nandroid backup from before I did that, still unable to apply. I get the following error in CWM when applying the .zip.
I searched but was unable to find anyone else with this problem.
Code:
Verifying current system...
assert failed: apply_patch_check("/system/app/Nfc.apk", "b0f957f4bc320ba9be0473306f89c1a336d7cbc7", "59e610a76e01241e0a9de36e0ea3c47f144cf0ef") E:Error in /cache/fota/2400258.cfg
(Status 7)
Installation aborted.
I'm thinking maybe just doing a factory reset and then applying and starting from scratch might do it, but want to avoid that option if possible.
Click to expand...
Click to collapse
You may be better off doing a Odin restore to factory.

These ota updates look at the files being updated / replaced . If throse files were different than the original files then update will fail.

http://forum.xda-developers.com/showthread.php?t=1902178
That post has a CWM-flashable complete version of LH9. It does not patch the existing files so you can flash it regardless of which mods you've applied (although you'll lose them all).

As drothenberger has stated he himself created a guide & flashable CWM zips to get from LG1 to LH9. Since you are rooted with LG1 you will run into some problems upgrading. I have made a very detailed guide on how to upgrade to the latest. Just visit my post below and start from step 16. Please be sure to read above the step to be fully informed on what it is your about to do. You will be flashing 4 different files starting with the ROM, then the Modem, followed by the Bootloader and finally the Kernel. Once again this is for people who are rooted on LG1. All credit for these files go to drotheberger I take no credit for it whatsoever I simply just wrote a detailed guide to help those with troubles. Here's the link.
http://forum.xda-developers.com/showthread.php?t=1912335
Sent from my T&K Blessed SGH-I747

[Q] Help Please

I am not exactly sure where things started to go wrong. I just recently installed the latest ROM of Task650's Jellybean 4.2.2
I have been trying to update to the latest ROM and I recieve:
[assert failed: getprop("ro.product.device") == "E: Error in /external_sd/ROMs and Gapps /aokp_JB_4.2.2_d2att-ota-eng.task650-4.26.2013.zip
(Status 7)]
I have looked up the issue and updated the Kernel and updated to the latest CWM and still get the same error.
Another thing I have noticed is that I cannot flash any other ROMs like CyanogenMod or anything
I also noticed in my devices folders, that I basically have mulitple of the same folders in multiple directories... I am not sure if this is from flashing too many times... I have never had this many problems with my device before. I like to have everything updated, which I have been able to do before, but now I can't do anything.
Can I get some advice on what to do?

if you have an i747 (d2att), was that a d2att cwm update you applied? it will say in the updater-script (in the recovery zip) what model it's for.
each time you flash a 4.2.2 ROM you're likely adding the multiple folders. a known issue. follow the link in my signature for some more details on this down in post #2 of that thread. essentially, back everything up (either to a micro sd card or your PC) and perform a full wipe before flash (including /system and /data + /media) to avoid this problem. we'll work on that once you've got this first issue fixed.

Fixed my issue!
I'm guessing I had flashed the wrong CWM:good: for my phone.