Hi everyone,
This is the first time I am rooting and modding a phone since my G1, and I am stuck. I downloaded the rom from here:
http://forum.xda-developers.com/showthread.php?t=1221832
When I put the rom in my sdcard, at first it was a *.0_Stable File, and recovery mode did not see it. Then I renamed the extension to .zip and recovery mode saw the file, but installation aborted due to a can't open message.
Any help will be really appreciated and thank you in advance.
edit: I think I had a corrupt download. Now I am re-downloading and it seems to be downloading as .zip. Apologize for this thread.
Related
Hey guys, trying to return my HTC Hero 2.1 stock
anyone have instructions to how to remove amon-ra?
i tried to install via RUU exe file but it doesn't detect my phone and asks if its turned on.
so far i have managed to get a packed.zip file with stock 1.5 flashed but when it goes OTA for updates, it reboots to amon-ra instead of doing the update through the HTC loader. hence why i want it removed.
any help will be appreciated
thank you
blah just fixed my issue
zip file i downloaded won't open with windows decompressor so i used 7zip to grab the recovery image out
then followed
http://android-dls.com/wiki/index.php?title=Replace_Recovery_Partition
http://forum.xda-developers.com/showthread.php?p=7010639#post7010639
http://forum.sdx-developers.com/index.php?topic=7108.0
On the original post by inxane he says to 2. Download the recovery and put it in C:\Program Files (Program Files (x86) if you are on 64 bit)\Samsung Electronics\SWUpgrade\Models\Binary. DELETE THE FILE ALREADY IN THERE OR YOU MAY PERMA-BRICK YOUR INTERCEPT...
Is the recovery just the cm01 tar file at the top because this link >http://www.sdx-downloads.com/devs/inxane/intercept/recoveryv14.tar can no longer be found.
sorry first time working with the intercept, i was going to try adb method but i heard the recovery goes away after you reboot.
From my experience, the CM01.tar file needs the recovery.rfs extracted. When you download SWUpgrade, you want to delete the file inside the Binary Folder and replace it with the recovery.rfs which happens to be Inxane's CM Recovery. The latest should be 2.5.1.0.
The reason it exists as a .tar file is becuse CM Recovery recognizes system files as .tar extensions. So if there was a case you wanted to reflash CM Recovery for some reason, you can do it inside CM Recovery so long as it's in the .tar container. Otherwise, you need the recovery.rfs file on the PC side.
From my experience, If you move CM01.tar to the Binary folder and run SWUpgrade, the upgrade won't start and it'll just hang.
alpha-niner64 said:
...the upgrade won't start and it'll just hang.
Click to expand...
Click to collapse
THANK YOU!!! I was wondering why it was hanging/just rebooting...
[Wrong link! My bad!]
I read that the Intercept can re-install it's stock recovery after rebooting the phone.
Recovery
Read this too
Basically someone is suggesting to just flash a root kernel (SlapKernel) with SW Upgrade. I'm going to try it out right now.
[EDIT] Flashing SlapKernel worked fine (and I wasn't rooted before...), and it's way more responsive so far. I suggest you follow these instructions
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
normankev said:
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
Click to expand...
Click to collapse
Try toggling script asserts, or re-download the file.
Also, I suggest updating your recovery to 2.5.1.8.
Thanks for the quick reply!
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
I've tried redownloading the file multiple times, even getting earlier versions of the rom to try.
How would I go about updating recovery? I don't have a functional usb cable at the moment unfortunately but if absolutely neccessary I can hack one up.
normankev said:
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
Click to expand...
Click to collapse
I think you should have the asserts disabled to get past the error. (use the extracted zip, which gave you the error 7)
If this does not help, probably best way to go forward is to get a usb cable and try flashing using fastboot
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
droidzen10 said:
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
Click to expand...
Click to collapse
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
OmniRom flashing question
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
Click to expand...
Click to collapse
Thanks for your answer and suggestion regarding flashing a recovery. I've been doing a lot of reading here on XDA and quite a few have suggested using Flashify to flash recoveries....
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
Click to expand...
Click to collapse
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Riiquiem said:
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Click to expand...
Click to collapse
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
AngryHapposai said:
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
Click to expand...
Click to collapse
That explains why mine always reports an error as well. *fixes all future build md5's
Having the same problem MD5 not found while flashing ROM. lemme try renaming. Will say again, if its work
Hi guys, am new here and to the whole custom rom thing too. I found this page by anand more on installing a custom rom
https://forum.xda-developers.com/redmi-2/how-to/ultimate-guide-redmi-2-users-rooting-to-t3294212
The problem is after making stock recovery when i follow this step..tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.. i cannot locate any .img files anywhere. Tried to install a recovery.img file online and flashify could not detect that either. Please help me on how to proceed and if there is a post with newer/simpler way to do this please provide the link.