Hello I am trying to revert to the CWM Gobstopper Stock 2.2.2 for bell found here:
http://forum.xda-developers.com/showthread.php?t=1185171
Using Tenfars latest CWM recovery. After getting into recovery mode and starting to install the .zip file I linked to above the installation is aborted.
This is what it says:
assert failed: package_extract_file("app.bin", "/internal/app.bin")
E:Error in /sdcard/Bell_2.2.2.stock.zip
(Status 7)
Installation aborted.
Any suggestions?
Edit: I also followed the steps in this post: http://forum.xda-developers.com/showpost.php?p=17084503&postcount=64
However, while using fastboot I can erase only userdata and cache, nothing else.
I am rooted, not unlocked.
I didn't find this answer definitively but I read for the new gobstopper 2.3.4 you need to have an unlocked bootloader (I am guessing that was why 2.2.2 didn't work), I just finished doing that, once I am done downloading the new 2.3.4 bell version I will try using that and will see if it works.
Related
hi there!
i just flashed the official rom to my htc hero to get the latest radio.
T-Mobile DE
RUU_Hero_T-Mobile_DE_2.73.111.26_release_signed_NoDriver.exe
from here: showthread.php?t=559622
now im trying to flash the latest villian rom 12.
if i boot the phone via home-and-power into recovery mode i just get the orange/white warning triangle. if i hold home-and-power again i have three options: reboot the system, apply the update, and wipe data/factory reset. if i try to flash the rom i just get
e: cant't open /cache/recovery/command
-- install from sd card
...
e: no signature (785 files)
e: verification failed
installation aborted.
im trying to flash via the bootloader (back-and-power) and access the phone via fastboot my device will be recognized but i can load any recovery rom.
i entered:
"fastboot-windows boot recovery-RA-heroc-v1.5.2.img"
i also tried the latest recovery rom from here: showthread.php?t=561124... and others, that i found on different sites and threads.
this is the message i get:
"downloading boot.img ... FAILED (remote: not allow)
i also tried to flashing the recovery rom via flashrec.
these are the versions i used:
flashrec-1.1.2-20090909
flashrec-1.1.3-20091107-2
flashrec-20090815
but i cant backup and therefore flash a recovery-rom.
so are all my hopes to flash a custom rom to my phone gone because i flashed the official update or is there any way to maybe downgrade again?
im new to the rom scene, any help would be much appreciated.
cheers.
For now you are essentially up the creek without a paddle.
I'm not aware of a way to reverse this issue
Goes to show you should never flash anything that comes from HTC...
http://villainrom.co.uk/viewtopic.php?f=43&t=28 explains why this shouldn't be done. Not much help though
Mod. edit: not dev related, moved to q&a
gl though
I've followed the steps listed in that thread but when I try to get into recovery mode with CWM (after I've already flashed it with Odin), it won't let me apply the update.zip due to the signature verification error thus preventing me from using CWM. (It only shows me the stock recovery menu)
I then started the process over from the start but this time, I installed CWM immediately after reverting back to DL09 and successfully updated it and was able to get into the CWM recovery menu - but now I can't apply the EA28 update.zip because of the following error:
assert failed: getprop("ro.product.device") == " SCH-1500" || getprop("ro.build.product") == "SCH-1500"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Am I doing something wrong and can anyone help me figure this out?
Any help would be greatly appreciated.
I should probably mention that I have the Samsung Galaxy S (Fascinate)
Disable signature verificaition in recovey and then flash
Sent from my HTC Desire using XDA Premium App
I'm assuming you're talking about my first attempt in which I meant to explain that I was never able to toggle the signature verification because I wasn't able to get into CWM recovery mode in the first place. The stock recovery menu doesn't allow the toggling of the signature verification.
I'm somewhat new at this so I might be missing something obvious here. If so, please let me know.
If you're following that thread, why are you installing CWM? The update.zip files that are posted there are the official update.zip files and are signed, so you can flash them just fine in stock recovery. Flash transfer the EA28 update.zip file to your SD Card, then flash DL09 via Odin. After flashing DL09, boot your phone to recovery and apply the update.zip. After that, start up your phone and transfer the ED01 update.zip to your SD card, reboot into recovery and apply the update.zip again. There is nothing in the entire process where you should be flashing CWM.
Thanks for the reply, imnuts, but the reason I'm installing CWM is because I want to flash one of the roms, i.e. Evil, and I don't know how to do it without CWM. I've successfully updated it to ED01 twice now, but afterwards, I can't go back into the CWM recovery mode - it only shows me the blue stock recovery mode and I don't know how to get back into the red CWM mode to flash one of the roms that are on the front page of the development page.
You need to flash CWM in Odin, then boot straight to recovery after you go to start you phone. If you allow the phone to boot normally after flashing, it will re-write the stock recovery over CWM. After you boot into CWM, flash a custom kernel and then you can boot up normally once, or also flash the ROM you want as well.
Hi, I'm hoping somebody might be able to shed some light. My phone isn't rooted or unlocked and last night I did the OTA update. Upon the first reboot, the phone is stuck at the "Dual Core Technology" screen and won't go any further. I can hold volume down and power to get to Fastboot, a bunch of other things, and Android Recovery.
Within Android Recovery, I've tried the wipe options as well as the apply sdcard update.zip but the wipes don't help anything and the apply update resutls in a signature error.
I feel like if I could just get the .zip update onto the internal SD storage, the apply update would work (maybe the OTA download was corrupted somehow). Is there anyway to use Fastboot or Moto-Fastboot to copy files to the internal SD storage?
Any help would be much appreciated.
hi
Try putting the OTA on a micro SD card (thats where it looks for it anyways) rename it to update.zip and try to flash that update.
y2whisper said:
hi
Try putting the OTA on a micro SD card (thats where it looks for it anyways) rename it to update.zip and try to flash that update.
Click to expand...
Click to collapse
Thanks for the reply.
Tried and this is what happened (which is more than before):
Install from SDCARD
Finding update package
opening update package
Verifying update package
...installing update
Verifying current system
.....assert failed: apply_patch_check("preinstall/app/gameloft_3games.zip","5428aeff....."
Not sure what that means, but I'll google and search here for a bit.
Edit: Just noticed that there was more to the output:
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
either you removed some apps before or the install updated some of the files and now doesn't pass the verification check.
search on here for a bit possibly flash cwm recovery and then the 2.2 gobbstopper. or you could try to go through bell as everything you have done is through official methods.
Okay thanks a lot for the help. I have since Unlocked using the Pudding IHOP thread and next will install Gobstopper 2.3.4 Bell (http://forum.xda-developers.com/showthread.php?t=1195922), though the CWM (tenfar's) post only shows that it's only for AT&T, which is odd since it's linked from the Gobstopper Bell thread).
Any idea if I can safely use Tenfar's CWM Recovery from here?:http://forum.xda-developers.com/showthread.php?t=1138541
Actually i would recommend only using that one for gobstopper purposes.
Although I would either wait until the 2.3.4 version is updated or get the 2.2.2 version and upgrade your device with the official rom as there have been changes since the 2.3.4 leak
Would you recommend another recovery instead of Tenfar's CWM? I'm currently now using the one that came in the CWM_INT_Recovery.zip (recover-d00.img).
Seems really hard to find a recovery that is definitely safe with Bell Atrix, and I'm never sure if just "moto-fastboot flash recovery %recoveryfile.img% is all I need to do now that it's unlocked. I might have to find another ROM since the download isn't working so well.
to install the gobstopper? no only use the latest tenfar cwm for that. after which, you could go with romracer and it will be fine
Okay great, thanks. The latest Tenfar CWM says at the top of the thread that it's only for Unlocked ATT users in bold red text so I was hesitant to use it.
I have the same issue. I have tried EVERYTHING I can think of to get it to boot.
The only difference in my case is I have run the update multiple times all finishing successfully with no errors.
This is really bugging me, any help would be appreciated.
Thanks
Jeff53765 said:
I have the same issue. I have tried EVERYTHING I can think of to get it to boot.
The only difference in my case is I have run the update multiple times all finishing successfully with no errors.
This is really bugging me, any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I'm an extreme novice Android/Atrix user but I would recommend doing what I did:
Use the Pudding IHOP instructions to RSDLite flash the unlocker SBF for Bell
Use moto-fastboot to flash recovery with Tenfar's latest CWM recovery (updated June 30)
Use Tenfar's CWM recovery to mount your USB storage, download the GobStopper 2.3.4 zip to your sdcard, then again using CWM, update from the zip.
See the GobStopper 2.2.2 thread for some pre-cleanup steps before trying to update with the 2.3.4 zip, all using Moto-Fastboot or regular fastboot from the Android sdk.
Thank you
You saved my life
Woot woot!
ive tried everything to get my tablet back to stock. as of now i am on overcome ROM. ive followed every guide i could fiund to get back to stock and nothing works. wheni try to flash anything i get 2 errors.
when i try to flash the hc-3.1_ota-full_sam_tab_10.1.zip i get this error:
assert failed: getprop("ro.bootloader") == "P7100BUKB7"
E:Error in sdcard/hc-3.1_ota-full_sam_tab_10.1.zip
(Status 7)
Installation aborted.
when i try to flash anything else, i get this error:
assert failed: getprop("ro.bootloader") == "P7100BUKB7" || assert failed: getprop("ro.bootloader") == "P7100BUKB8"
any help on this is greatly appreciated. i mean any help. thank you.
so, i tried again this morning and have still got the same results. has ANYONE else had this issue? or something simular? i am at my end. this is what ive tried so far:
flash the stock
flash another rom
factory reset
flash restock from overcome
nothing is working. someone has to have some information on this.
thanks!!
SOLVED!!!
this is what i did to get back to stock after getting the errors above.
first thing, i re-rooted my tab.
once re-rooted, i flashed the hc-3.1_ota-full_sam_tab_10.1.zip
then i did used ODIN to flash the stockrecovery file. (everything you need is ont the files for dummies zip
on the tab re-booted, it was stuck in a bootloop.
so i got back into recovery and did a factory/data reset/wipe.
tab rebooted and everything is working fine. back on stock.
android version 3.1
kernel 2.6.36.3
[email protected]#1
build number
hmj37.uekf3 p7510uekf3
hope this helps anyone having the same problem.
Which method to re-root did you use? I have the same issue.
EDIT: Nevermind! Got it! Thanks
jcporter80 said:
Which method to re-root did you use? I have the same issue.
EDIT: Nevermind! Got it! Thanks
Click to expand...
Click to collapse
Ack! Which method did you use to re-root? I'm getting the same error. I'm trying to root by flashing the root zip file in CWM. It flashes fine, but then I still get the same error. Is there another way to do it?
The problem seems to be the CWM version. I was on 5.x that came with one of the ROMs. So I used ODIN to flash the older CWM 4.0.0.4. Then I was able to flash the stock hc-3.1_ota-full_sam_tab_10.1.zip file.
I have an Optimus T, P509, with the latest stock firmware 2.2.2. I want to flash it to mik_os's CM7, version 6.5.8.
1) I rooted the machine using Gingerbreak.
2) I used the ROM Manager to install CWM.
3) I put cyanogen_thunderg-ota-eng.mik-6.5.8.zip onto my SD card and verified the md5sum.
4) I booted into CWM, which reports v5.0.2.7.
5) I did a wipe data/factory reset.
6) I proceeded to "install zip from sdcard" and selected the file.
7) This is the error that I see:
Code:
assert failed: getprop("ro.product.device") == "thunderg" || getprop("ro.build.product") == "thunderg" || getprop("ro.product.board") == "thunderg"
E:Error in /sdcard/cyanogen_thunderg-ota-eng.mik-6.5.8.zip (Status 7)
Installation aborted.
So I proceeded to search for this error message, and I came across the following suggestions in various threads:
* Toggle image verification and script assert
* Update to CWM v5 (I'm already using 5.0.2.7)
* Format /system
I've tried all of these suggestions, and I still get the exact same error...
Dont verify md5sum / signature or anything. Just wipe everything and flash!!
As I indicated in my OP, I did wipe everything. And I did try turning off signature verification. As for the md5sum check, that was something that I manually did when I copied the file to the card, before I even booted into recovery mode, so verify that the file was not corrupt.
In any case, when I created this thread, I was not aware that there was an "official" CM7 build for the Optimus (it wasn't mentioned in the FAQ, and I'm new to all this...),but after I found that there is an official CM7.2 stable build, I tried flashing that zip instead, and it went ahead without a hitch. So I guess there was something wrong with the mik_os CM7? But i checked the hashes again, and there wasn't any corruption. Oh well, all's well that ends well...
Maybe it was because your on new baseband?
Virusbetax said:
Maybe it was because your on new baseband?
Click to expand...
Click to collapse
No, I'm on the old baseband; a new baseband was never released for the Optimus T, and as I understand it, the new baseband does not support the AWS frequencies that T-Mobile uses, so I mustn't upgrade to the new baseband anyway (I had to apply the baseband fix to allow CM7.2 to use the old baseband).
Actually I've been using v20g baseband on tmobile for almost a year now and it does work perfectly with tmobile... I'm also in NY and 3g, mms, text, all work. Even signal is better
Try updating baseband with lgmdp, I used tht and it worked flawlessly :thumbup: tht should solve problems cuz of new baseband
Sent from my LG-P500 using xda premium