I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
b0sanac said:
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
Click to expand...
Click to collapse
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Are you installing from the internal or external sd? try the internal, and check the md5
Glebun said:
Are you installing from the internal or external sd? try the internal, and check the md5
Click to expand...
Click to collapse
Tried both internal and external, I get the same thing. I'm pretty sure that it's not corrupted since this is the same file that my friend used to flash his s3 to miui.
xcly said:
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Click to expand...
Click to collapse
I have not, will try it.
Edit: Flashed an AOSP rom and it worked fine, then MIUI, the install worked but now MIUI is just hanging on the boot screen.
Edit 2: Okay I got it working, I had to do a factory reset and it just started working.
Thanks for your help guys
Related
I am selling my old galaxy s due to having a new phone and I have made it freeze when it boots.
It was flashed onto myICS when I was using it and before handing It over I wanted to wipe everything so it was clean for the new owner. I did this in the phone options and then also in recovery mode to make sure, but after rebooting it is just stuck at the galaxy s boot loader.
I tried flash another Rom onto it and the same thing happened even though odin said it was successful.
I'm not sure what to do now as I am scared of truly bricking the phone so I am asking what should I do to get it up and running again?
Thanks
hmm
it should work after reflashing and whiping data/cash in recovery mode
No luck with it.
I tried wipe data and reboot and had no luck. Then tried reflashing, wiping data and still no luck.
Do you think it might be something with the kernal thatI had installed with the myICS rom, not being compatable with the rom I was flashing to?
steph1389 said:
No luck with it.
I tried wipe data and reboot and had no luck. Then tried reflashing, wiping data and still no luck.
Do you think it might be something with the kernal thatI had installed with the myICS rom, not being compatable with the rom I was flashing to?
Click to expand...
Click to collapse
Didn't you format partitions before flashing? Have you tried doing a fully clean install?
did u try to flash a stock rom via odin
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
pedel said:
Hi,
First time it happened. tried everything but still cant fix it.
after a month or two on MIUI, I wanted to move to AOKP JB.
As I always do when switching ROMs, I backed up everything (efs, pictures, apps with titanium, etc) and format the internal sd card within the os to get rid of all the junk.
Then went into CWM (siyah) and wiped data and cache.
And now for my mistake, I foramt the /system instead of / cache.
So now, when Im trying to install the ROM as a zip file threw CWM I got an error 7.
When trying to do it on ODIN, it stuck on 'factory fs', 'cache', or 'boot'.
After some time, I got the "Firmware upgrade encountered an issue" message.
Then got rid of it after somehow succeeding installing a different cwm (the stock one) but nothing worked there either, exept installing the Siyah kernel zip from there.
What can I do now to get my phone back alive?
THANKS :crying:
Click to expand...
Click to collapse
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
jj92942000 said:
I jumped from S1 to S3, but I'm sure it's applicable. You need to flash via odin stock rom that originally came with your phone. Then root then flash custom rom. Odd tho in past I've done the 5 formats, boot, cache, data, system, sdcard then while still in recovery flash rom. Good luck
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
thanks
The problem is, I really cant remember what was the original ROM version. I bought it end of june 2011.
I cant even remember if it was a UK ROM, or an open europe one, or anything else.
****
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Jussi31 said:
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Click to expand...
Click to collapse
The aokp uses the 4.2 kernal so you will have to instal that. But I'm not sure on the recovery .. maybe it might be worth trying clockwork as if the twrp you are useing is especially for the viper Rom? Have a go at installing the different recovery maybe that will help and double check what you have to do to install on the thread hope this helps
Ilike the viper Rom... But if I get time tomorrow I will try for myself ... If no one else helps you out by the time I do it I will update you on how I done it and any problems I faced maybe I will end up in the same situation.
Sent from my HTC One X+ using xda premium
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Jussi31 said:
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Click to expand...
Click to collapse
TWRP is the ideal solution for our HOX+ - at least as of now.
I hope you are doing the following:
1. Wiping Data & System.
2. Installing boot.img.
The Venom customized TWRP does not have any issues because I also used it for some time (as of now I am back on the official TWRP).
You can download the lastes verison from here:
http://techerrata.com/browse/twrp2/enrc2b
And install it using Hox+ All in one toolkit by hasoon.
Make sure you wipe data & system before you install the ROM.
I also changed from ViperX 1.08 to ARHD, InsertCoin & Elegancia.. no issues
Hmmm. I'll have to putz around with it some more and see what happens. Thanks.
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Jussi31 said:
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Click to expand...
Click to collapse
I guess your recovery is not able to detect that your phone is one x+.. that's why assert failed error.. try changing the recovery( maybe CWM) and try again
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Jussi31 said:
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Click to expand...
Click to collapse
:good::good::good:
that is cool!
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.
A couple months ago I was having problems with my recovery. It kept crashing every time I tried to flash anything. Found out I needed to format my internal storage, once I did that I was able to flash CM but when I tried to flash a TW rom I get stuck in a bootloop. I re-downloaded the same rom 3 times thinking it was a bad download no dice. Tried other TW roms still no dice. But, when I flash a ASOP rom it works just fine. What could of caused this issue?
Anybody Know how to solve this? Been trying to figure this issue out for a whole month!
just a guess but for Note 2/3/4 users with locked bootloaders you cannot flash a kernel. Using safestrap or another vitual rom required it to be TW-based. If you're running true AOSP and was able to flash CM are you sure you're running the stock kernel?
Reilly1812 said:
just a guess but for Note 2/3/4 users with locked bootloaders you cannot flash a kernel. Using safestrap or another vitual rom required it to be TW-based. If you're running true AOSP and was able to flash CM are you sure you're running the stock kernel?
Click to expand...
Click to collapse
My bootloader is unlocked. I was able to flash any rom running AOSP (Liquid smooth CM only 2 I have tried)
DCVR 614 said:
A couple months ago I was having problems with my recovery. It kept crashing every time I tried to flash anything. Found out I needed to format my internal storage, once I did that I was able to flash CM but when I tried to flash a TW rom I get stuck in a bootloop. I re-downloaded the same rom 3 times thinking it was a bad download no dice. Tried other TW roms still no dice. But, when I flash a ASOP rom it works just fine. What could of caused this issue?
Click to expand...
Click to collapse
It's possible that you could have something partially corrupted in your data/cache partitions.
If you don't want to have to ODIN back to 4.1.2... and then start all over again with CASUAL, etc.... then you might check out this thread : http://forum.xda-developers.com/showthread.php?p=53624921
Wiping cache and doing factory reset in the Stock Recovery might correct things... it apparently does a more thorough wipe than the ones done through custom Recoveries like TWRP/Philz... etc... You can just Odin back your preferred custom recovery after completing the wipes in the Stock recovery.
mattnmag said:
It's possible that you could have something partially corrupted in your data/cache partitions.
If you don't want to have to ODIN back to 4.1.2... and then start all over again with CASUAL, etc.... then you might check out this thread : http://forum.xda-developers.com/showthread.php?p=53624921
Wiping cache and doing factory reset in the Stock Recovery might correct things... it apparently does a more thorough wipe than the ones done through custom Recoveries like TWRP/Philz... etc... You can just Odin back your preferred custom recovery after completing the wipes in the Stock recovery.
Click to expand...
Click to collapse
I will try this today and report back!
DCVR 614 said:
I will try this today and report back!
Click to expand...
Click to collapse
This sounds like the same problem I am having in this post: http://forum.xda-developers.com/note-2-verizon/help/assistance-odin-soft-hard-brick-t3093391
Except I can't flash anything. I will also try flashing this stock recovery because it sounds like the only thing I haven't tried doing.
Thanks so much for this thread I hope it can save my phone.