Ok, here's official clockworkmod and ROM Manager support
For a full/better How To, click here: http://forum.xda-developers.com/showthread.php?t=788099
This thread is a quick rundown, as well as a primer on how to create a proper clockwork compatible kernel.
First, use odin or redbend_ua to flash this kernel:
http://koush.tandtgaming.com//samsung/fascinate/zImage (you will need to package it accordingly for odin, I am lazy and did not do so, see the other thread)
Then, open up ROM Manager and flash recovery (choose Fascinate!).
All done!
Note, using reboot recovery or adb reboot recovery will take you to a "stock" recovery. Simply apply the update.zip on your SD card and clockworkmod will start up. (This method is better known as fakeflash)
Starting up recovery through ROM Manager will take you directly into clockworkmod.
How this works for those that want to develop on this further and create kernels that are ALSO clockworkmod compatible:
I extracted a initramfs from a stock recovery. I modified recovery.rc and fota.rc to allow adbd (and other small fixups). I modified default.prop to enable adbd and root shell. I replaced /res/keys with a test signed version to allow applying update.zip files.
Here is my fascinate initramfs:
http://github.com/koush/fascinate_initramfs
One can build clockwork directly into the kernel if they so choose. Simply take the update.zip on your SD card and pack those files into the initramfs as well. I chose not to do this because I am lazy.
i know this is irrelevant but i hope you can help
i flashed the CMWrecovery file --- i followed the steps to the dot .. and now my phone can't get signal and is rebooting insanely ... help!!!
i did not uninstall the ext2 lag fix - i did not see that in the steps --
i even booted into standard recovery and completed a master reset -- same issue ---
masri1987 said:
i know this is irrelevant but i hope you can help
i flashed the CMWrecovery file --- i followed the steps to the dot .. and now my phone can't get signal and is rebooting insanely ... help!!!
i did not uninstall the ext2 lag fix - i did not see that in the steps --
i even booted into standard recovery and completed a master reset -- same issue ---
Click to expand...
Click to collapse
join the freenode #samsung-fascinate channel... i will try to help you.
Has anyone else tested this? I've yet to get it to boot, so I would caution those looking to install CWM to use the files found in the other thread until we can sort out what's up with this zImage..
i have this up and running with root and cw the only problems im having is my market wont load and it only gives me the "top free" tab and the "just in" tabs on the market...i can not see the top paid tab. i did a odin full restore (everything back to stock) then i rooted and flashed this anyone give me a had to why my market is funny? or how i have bad serves now?thanks to everyone for getting us cw!!
ruthlessbeatle said:
i have this up and running with root and cw the only problems im having is my market wont load and it only gives me the "top free" tab and the "just in" tabs on the market...i can not see the top paid tab. i did a odin full restore (everything back to stock) then i rooted and flashed this anyone give me a had to why my market is funny? or how i have bad serves now?thanks to everyone for getting us cw!!
Click to expand...
Click to collapse
So you're saying you downloaded this specific zImage2 file, then tar'd it, then flashed it over your kernel and it worked? Did you use odin, or redbend?
Or did you just post for help on the bottom of this thread?
namebrandon said:
So you're saying you downloaded this specific zImage2 file, then tar'd it, then flashed it over your kernel and it worked? Did you use odin, or redbend?
Or did you just post for help on the bottom of this thread?
Click to expand...
Click to collapse
lol nahh i flashed it last night with odin but it was zimage not zimage2 is there a difference? i can boot into recovery and even installed zips off my sd card like i said the only real problems i have is serves and market
ruthlessbeatle said:
lol nahh i flashed it last night with odin but it was zimage not zimage2 is there a difference? i can boot into recovery and even installed zips off my sd card like i said the only real problems i have is serves and market
Click to expand...
Click to collapse
Yes, there's a difference. When I posted asking if anyone had gotten this to work, I meant the kernel Koush specifically provided above, in this post. I know in general CWM recovery works.
I would try posting in the thread where you obtained your files for help. That way there are people who are using the same kernel that might help.
namebrandon said:
Yes, there's a difference. When I posted asking if anyone had gotten this to work, I meant the kernel Koush specifically provided above, in this post. I know in general CWM recovery works.
I would try posting in the thread where you obtained your files for help. That way there are people who are using the same kernel that might help.
Click to expand...
Click to collapse
turee that sorry. im noticing more and more problems like i dont have maps and missing apps here and there. thisis my fist time using odin and samsung...should i just odin back to stock everything and then try this recovery?
Alright...so I am confused now and I am not an Android noob....I see all the threads with how to flash the recovery and then this one....but I think we should have ONE thread that walks thru Rooting, flashing recovery etc....AND, in the first post, the instructions tell people how to pack files and etc., but a lot of people have no clue what that means...therefore, we need to have a "packed-ready" files for noobs. There are just a few too many botched phones.
As a noob myself, I think that sounds like a great plan.
Look closer my friend.
Clockworkmod installation how to
namebrandon said:
Look closer my friend.
Clockworkmod installation how to
Click to expand...
Click to collapse
Thanks, I saw that thread....but what I meant was, for a new person to see the following can be extremely confusing:
http://forum.xda-developers.com/showthread.php?t=787834
http://forum.xda-developers.com/showthread.php?t=788099
http://forum.xda-developers.com/showthread.php?t=787168
http://forum.xda-developers.com/showthread.php?t=788256
You know what I mean?
Can someone post a link on how to backup the original stock kernel via ODIN (or some other application) before I go ahead with this? I'd like to just be able to go back to the unmodified kernel if I want to. After a five minute search I couldn't even find a tutorial on ODIN.
Related
I, an ignorant vibrant user eager to break into the world of ROMS, finally and successfully rooted my phone with the one click root.
One Click Lagfix from the marketplace immediately thereafter. Phone was blazing fast.
I decided to push my stupid limits. I tried to download and install Eugene's Vibrant Hybrid final ROM that would give me glorious, stock android. I followed the instructions I found for "installing a ROM":
Copy the zip to the root.
Boot into recovery.
Go into clockwork recovery.
factory reset.
install zip from sd card.
after that's done, reboot.
I got a little chimy, should-be-startup noise, (not the standard vibrant start-up noise, but what I expect would be the new ROM start-up noise I downloaded) and then nothing. Just the Vibrant screen.
I can boot into recovery mode, but I don't know what to do next. I tried to find the backup I made on Clockwork, but it was NOT THERE. I am now panicking and trying not to do anything stupid to my phone.
read on Eugene's site that it could be that I don't have the correct kernel flashed to support the ROM...? At this point, I kind of just want my phone back while having to lose the least amount of data. Please Help.
and before I tried installing the ROM, I used the one-click lag fix from the market on my already rooted phone.
Thanks!
james
Did you disable the lag fix before flashing?
Sent from my SGH-T959 using XDA App
no, didn't realize that it would be an issue until after flashing the ROM. I think I'm stuck in a boot loop... and I have access to a mac only at the moment. Tomorrow I'll have access to a PC if ODIN could help at all...
Search for "froyo that doesnt brick your phone" flash if with odin and after that flash back to stock.
Sent from my SGH-T959 using XDA App
Will this restore my data and settings...?? What will I lose?
In a weird. Everything. Unless you made an external backup. Eugene's will wipe the phone.
Sorry bud
Gl.
Sent from my SGH-T959 using XDA App
jamespwolpert said:
I, an ignorant vibrant user eager to break into the world of ROMS, finally and successfully rooted my phone with the one click root.
One Click Lagfix from the marketplace immediately thereafter. Phone was blazing fast.
I decided to push my stupid limits. I tried to download and install Eugene's Vibrant Hybrid final ROM that would give me glorious, stock android. I followed the instructions I found for "installing a ROM":
Copy the zip to the root.
Boot into recovery.
Go into clockwork recovery.
factory reset.
install zip from sd card.
after that's done, reboot.
I got a little chimy, should-be-startup noise, (not the standard vibrant start-up noise, but what I expect would be the new ROM start-up noise I downloaded) and then nothing. Just the Vibrant screen.
I can boot into recovery mode, but I don't know what to do next. I tried to find the backup I made on Clockwork, but it was NOT THERE. I am now panicking and trying not to do anything stupid to my phone.
read on Eugene's site that it could be that I don't have the correct kernel flashed to support the ROM...? At this point, I kind of just want my phone back while having to lose the least amount of data. Please Help.
and before I tried installing the ROM, I used the one-click lag fix from the market on my already rooted phone.
Thanks!
james
Click to expand...
Click to collapse
its just a simple user error. Honestly imo opinion, if you are using the lagfix option found on the market, flashing to other roms reformats /data and /system and such undoing it. So thats not where your issue came from the flashing. Before the flash, if you were on stock jdf, the flashing the hybrid final rom didnt update your baseband/modem.bin and i am pretty sure that would put you in your situation. Possible situation number 2. You had the ota update on your phone already. Meaning you were running ji6 then the rom update.zip may have been corrupted or incomplete.
to fix either one of these situations is simple. As long as the answer to my next question is a hell no. Did you flash jacs xmod voodoo kernel after you flash the hybrid rom?? The faster you reply to this the faster i can get to to a solution. You will also need a computer that has adb installed and properly recognizing your phone.
IF YOU DID FLASH THE VOODOO LAGFIX YOU WILL NEED ACCESS TO A COMPUTER WITH ODIN AND ANDROID SDK!! WETHER IT BE A MAC WITH PARRELLS OR A VM OR LINIX OR WINDOWS.
a4 moda said:
In a weird. Everything. Unless you made an external backup. Eugene's will wipe the phone.
Sorry bud
Gl.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That is not true. Anything on his internal memory will be perfectly intact. And if he can still get into cwm recovery, he adb push a few files to the root of his sd card and boot right up depending the cause
jumaaneface said:
its just a simple user error. Honestly imo opinion, if you are using the lagfix option found on the market, flashing to other roms reformats /data and /system and such undoing it. So thats not where your issue came from the flashing. Before the flash, if you were on stock jdf, the flashing the hybrid final rom didnt update your baseband/modem.bin and i am pretty sure that would put you in your situation. Possible situation number 2. You had the ota update on your phone already. Meaning you were running ji6 then the rom update.zip may have been corrupted or incomplete.
to fix either one of these situations is simple. As long as the answer to my next question is a hell no. Did you flash jacs xmod voodoo kernel after you flash the hybrid rom?? The faster you reply to this the faster i can get to to a solution. You will also need a computer that has adb installed and properly recognizing your phone.
IF YOU DID FLASH THE VOODOO LAGFIX YOU WILL NEED ACCESS TO A COMPUTER WITH ODIN AND ANDROID SDK!! WETHER IT BE A MAC WITH PARRELLS OR A VM OR LINIX OR WINDOWS.
Click to expand...
Click to collapse
I didn't flash **** after that. Just the Hybrid mod, then I was stuck. The steps I mentioned in my process were the only things that ever ever happened.
also, yes, I (was) running JI6 as well. Until this fiasco.
Eugene's thread for the hybrid mod also has files posted for, quote, "reboots and freezes" with the file name JFDkernanmodemji2.zip. All things that have been mentioned positively at one point or another in this thread. Since I am pretty sure I don't have the appropriate kernel to run the ROM, do I simply push the JFDkernanmodemji2.zip file to my root, flash it, then flash the ROM again and life will be good?
jamespwolpert said:
Eugene's thread for the hybrid mod also has files posted for, quote, "reboots and freezes" with the file name JFDkernanmodemji2.zip. All things that have been mentioned positively at one point or another in this thread. Since I am pretty sure I don't have the appropriate kernel to run the ROM, do I simply push the JFDkernanmodemji2.zip file to my root, flash it, then flash the ROM again and life will be good?
Click to expand...
Click to collapse
Indeed. If it doesn't work. U had a messed up download. At that point redownload and push to sd root
jumaaneface said:
Indeed. If it doesn't work. U had a messed up download. At that point redownload and push to sd root
Click to expand...
Click to collapse
how do I push files to my vibrant? Where do I start?
jamespwolpert said:
how do I push files to my vibrant? Where do I start?
Click to expand...
Click to collapse
Do you have android sdk on your pc?
jumaaneface said:
Do you have android sdk on your pc?
Click to expand...
Click to collapse
I think. When I open it, it the app is called Java and the titlebar says Android SDK and AVD Manager
jamespwolpert said:
how do I push files to my vibrant? Where do I start?
Click to expand...
Click to collapse
jamespwolpert said:
I think. When I open it, it the app is called Java and the titlebar says Android SDK and AVD Manager
Click to expand...
Click to collapse
boot your phone into clockwork recovery and plug in to computer. Then open a command prompt window. you can type in cmd into search bar in windows to open it up. Then type adb devices into the little black window. tell me what happens when you do this. Do you have gtalk or aim? This will go by faster If you have one
jumaaneface said:
boot your phone into clockwork recovery and plug in to computer. Then open a command prompt window. you can type in cmd into search bar in windows to open it up. Then type adb devices into the little black window. tell me what happens when you do this. Do you have gtalk or aim? This will go by faster If you have one
Click to expand...
Click to collapse
yeah, I've got gtalk.
gmail is [email protected]
Personal assist, wow that's awesome.
So what came if this? What's the outcome?
I'm curious, please update.
Sent from my SGH-T959 using XDA App
Push pppuuuuush..baby deliveried yet?? An update on steps by steps?
Can I just flash back some how. I'm running 3.0
Same thing happened to me when I first rooted my Fascinate. There were many conflicting guides on how to get CWR on my phone and I ended up using ROM manager which put 3.0 on.
This link below:
http://forum.xda-developers.com/showthread.php?t=942021
...will get you to the "red" CWR or CWR "all" as it is called in this thread.
I used the ODIN option.
Quick and easy. Plug phone in, put phone in to download mode *yellow triangle* (NOT RECOVERY), use the PDA option in odin, select the file, send it over, wait for it all to reboot, profit.
Hope that can point you in a better direction... I am by no means a dev, just went through the same thing!
are there any working links on this site? they all lead to dropbox and are broken.
Man... someone really needs to sticky a thread in the dev section with the essential files..... update.zip .... red cwm... etc.
yes, it's a real PITA trying to keep up with where to download them, and most of the links are broken. it would be much easier to manage in one thread.
You can find one about a third of the way through this post over on Android Central.
It doesn't actually say the version, but due to the name I'm (reasonably) certain it's the one you're looking for.
thanks, but that requires odin, which requires windows
m91-30 said:
thanks, but that requires odin, which requires windows
Click to expand...
Click to collapse
I don't think the .zip would work either in that case? (which I haven't found a working link for anyway at this point)
Edit: and I was actually trying to help the OP. (surely the percentage of Mac-only owners isn't that high )
From what I recall, the red CWM could be installed from any other version of CWM if you download it in zip format and install it from the zip file within your current version of CWM. However, I'm not sure if that trick works with 3.0, now that they dropped support for the older scripting language. If you can use Rom Manager to revert back to an old green version of CWM, you should then be able to install the red version from a zip file on your SD card.
Sent from XDA Premium on my Super Clean Fascinate
I use linux, I've "downgraded" cwr before from orange to red with the .zip. it was the only way I could get my eb01 installed. then the damn thing "upgraded" on me again.
m91-30 said:
I use linux, I've "downgraded" cwr before from orange to red with the .zip. it was the only way I could get my eb01 installed. then the damn thing "upgraded" on me again.
Click to expand...
Click to collapse
So don't you have the .zip saved somewhere?
Btw, I would highly recommend not using Rom Manager at all, as it does not work with the custom red version of CWM necessary rom work with the Fascinate.
Sent from XDA Premium on my Super Clean Fascinate
Hi guys, I was trying to flash new ROM via CWM. However, cwm wasn't able to read the zip file saying something about script is not supported blah blah blah... Browsing thru xda forum, I found out that this problem has caused due to the cwm version(recently updated to cwm3.0.0.8) , or at least I want to believe it this way. So lastnight I ended up finding a thread started by jt1134 which I basically helped out lots of ppl who were struggling with similar problem as mine. But the thing is when I was trying to download the files, cwm-recovery-ALL.zip and cwm-recovery-ALL odin. The download links were broken giving me an error message. So guys, if anyone has the files I beg of you to share it pleaseeeeeeeee.
to shorten it down, the link is broken, I think. So if anyone has the files I beg of you to share it thank you..............
Hello jjalhjy
I will make this easy for the both of us!
Direct your browser to this link:http://forum.xda-developers.com/showthread.php?t=999802
Once there scroll down to the 5th post (#5) where I linked both the page you referenced (broken links) and a link to a working download of the ".tar" file (was earlier! ).
If you need the .zip file scroll down to post 9 (#9) where I have linked it.
A quick guide to getting you flashed.
*note* I am assuming you cannot use .zip files due to the incompatible script error! This is for using odin.
1. Put phone in download mode via the power menu if on superclean. If not turn off the power, pull battery, plug into computer, hold "down" on the volume rocker till the yellow triangle "download" screen appears
2. download the ".tar" version of cwr all
3. Launch odin
4. Click the PDA button and search for the ".tar" file and select it -> then hit "ok"
5. Run the file in odin, wait for the phone to reboot.
6. put your battery back in and test recovery mode to see how it looks!
*whew*
good luck!
Wow that was a fast reply! Thank you! A quick question tho, 1. Do you know if I have to uninstall ROMmanager and delete update.zip file in my sd card before I even start flashing via using odin. 2. After following your instruction step by step, and let's say if it works. Do I still need to download ROMmanager? 3. I remember reading someone's thread in xda saying it is always necessary to flash new cwm after flashing a ROM (I always have it done using ROMmanager but now things have changed, obvisouly. So yea, how would I flash new CWM after flashing a ROM from now?
Sorry if these questions sound so newbyyyy hehe and thanks again!
jjalhjy said:
1. Do you know if I have to uninstall ROMmanager and delete update.zip file in my sd card before I even start flashing via using odin.
Click to expand...
Click to collapse
It is advised (so I have read) that you should not use ROM manager with the Fascinate. While it is a powerful tool, it is just not 100% Fascinate friendly yet. Also I have never had to remove/mess with the update.zip on my SD card. Heck as far as I know you can delete it after using ODIN with the new cwr-all.
jjalhjy said:
2. After following your instruction step by step, and let's say if it works. Do I still need to download ROMmanager?
Click to expand...
Click to collapse
No. I would use the Development Thread here in the fascinate section for your ROMS. ROM manager is just not made for us.....yet!
jjalhjy said:
3. I remember reading someone's thread in xda saying it is always necessary to flash new cwm after flashing a ROM (I always have it done using ROMmanager but now things have changed, obvisouly. So yea, how would I flash new CWM after flashing a ROM from now?
Click to expand...
Click to collapse
I personally have never done this. To the best of my knowledge (and real life experience) cwr-all (red version) is the current and most up-to-date version (for the Fascinate). Once I ODIN-ed over the cwr-all I have not updated it once. You should be fine to flash it and flash ROMs as you please!
Dude, thanks A LOTTTTTT
Yesterday I updated my S2 i777 to KitKat with OmniRom, but I did something really dumb. Omni rom does not come with root so i tried to install root and used a kernel from jellybean. While I was mucking around with CWM i also turned on signature verification. The result was my phone was bricked, which i fixed, but now i am stuck on ginger bread (rooted) and when I try to launch CWM it says it failed to verify the whole-file signature and stays in stock recovery mode. When I try to install CWM or any other package in stock recovery I also get the signature error. Because it is in stock recovery and not CWM I am not able to change the setting either. Does anyone know how I fix this or get around it? Maybe by somehow manually changing the setting in a file?
Thanks.
Stock recovery will not install any unsigned firmware. You will need to follow one of many guides available here, that will walk you through the process of going from stock to custom firmware.
Your shortest path to omni is using the "mobile Odin method" listed in the notes of the omni OP. But I seriously suggest familiarizing yourself with the process -othermark has an up to date guide in the "General" section.
cyril279 said:
Stock recovery will not install any unsigned firmware. You will need to follow one of many guides available here, that will walk you through the process of going from stock to custom firmware.
Your shortest path to omni is using the "mobile Odin method" listed in the notes of the omni OP. But I seriously suggest familiarizing yourself with the process -othermark has an up to date guide in the "General" section.
Click to expand...
Click to collapse
The problem with mobile odin is that it costs money, which i would rather not pay. On top of that, I am using the same steps on the same firmware that i used to have to upgrade my phone. I am allready rooted too, and have clockwork mod, but when I try and boot into clockwork it also gives me that error and goes to stock recovery. For somereason launching clockwork mod is installing a package on stock recovery. I am launching clockwork mod from rom manager btw.
ConnorBP said:
The problem with mobile odin is that it costs money, which i would rather not pay
Click to expand...
Click to collapse
There is a free version that gets the job done just as well as the paid version. That free version is available here on XDA.
I am using the same steps on the same firmware that i used to have to upgrade my phone.
Click to expand...
Click to collapse
You haven't described those steps, so I cannot say whether they are useful or not. I suggest trying a different method, as the one you are following doesn't seem to be achieving the desired result.
I am already rooted too, and have clockwork mod, but when I try and boot into clockwork it also gives me that error and goes to stock recovery. For somereason launching clockwork mod is installing a package on stock recovery. I am launching clockwork mod from rom manager btw.
Click to expand...
Click to collapse
ROM MANAGER is known to cause issues with these phones. You should avoid using it from here on.
Whenever you are ready, the advice in my first response will get you where you want to be (free of charge)
Happy flashing
-Cyril
@ConnorBP,
I don't think cyril279's warning about Rom Manager is strong enough. Rom Manager is not only known to cause problems, it has in some cases caused damage to the low level firmware which is very difficult to recover from. There is a sticky right at the top of this forum.
creepyncrawly said:
@ConnorBP,
I don't think cyril279's warning about Rom Manager is strong enough. Rom Manager is not only known to cause problems, it has in some cases caused damage to the low level firmware which is very difficult to recover from. There is a sticky right at the top of this forum.
Click to expand...
Click to collapse
I saw that sticky, but it has worked for me so far, and I only use it to boot into clockwork mod and sometimes install clockwork. I can't seem to get into clockwork by doing the key combinations so i use that.
cyril279 said:
There is a free version that gets the job done just as well as the paid version. That free version is available here on XDA.
You haven't described those steps, so I cannot say whether they are useful or not. I suggest trying a different method, as the one you are following doesn't seem to be achieving the desired result.
ROM MANAGER is known to cause issues with these phones. You should avoid using it from here on.
Whenever you are ready, the advice in my first response will get you where you want to be (free of charge)
Happy flashing
-Cyril
Click to expand...
Click to collapse
I got the free mobile odin, but it does not let me do anything except flash the kernel. What I need to do is update to a new version :/ (I can allready flash kernels with heimdall or odin)
Once you decide to follow the instructions provided, you'll be a happy camper. If you do it your own way, or take short cuts, then this session may continue for much longer than it needs to.
MobileOdin Install:
(procedure verified working from stock rooted AT&T firmware by @cyril279):
With your phone on fully booted into (whatever ROM)
1) Gather all necessary flash files onto internal sdcard before performing these steps.
---a) Boot.IMG (extracted from omni-4.4.x-latesti777-nightly.zip)
---b) MrCook's ROM wipe.zip
---c) Omni-nightly.zip
---d) PA GApps (optional)
---e) SuperSU (optional)
2)Mobile-odin flash Omni's boot.img
>>the phone will try to reboot, but will likely fail. Three-finger salute (with the USB cable UNPLUGGED), until you are in TWRP recovery<<
3) [install] > [COOK'S ROM WIPE.zip] > [add more zips] > [omni-4.4.x-latesti777-nightly.zip] > [add more zips as desired] >>swipe to confirm flash>> [reboot system]
Click to expand...
Click to collapse
ConnorBP said:
I got the free mobile odin, but it does not let me do anything except flash the kernel. What I need to do is update to a new version :/ (I can allready flash kernels with heimdall or odin)
Click to expand...
Click to collapse
cyril279 said:
Once you decide to follow the instructions provided, you'll be a happy camper. If you do it your own way, or take short cuts, then this session may continue for much longer than it needs to.
Click to expand...
Click to collapse
I ended up finding a kernel with CWM installed and using odin to flash it, and I used it to flash a new version of clockwork mod and then install the latest omni rom. So all is resolved. Thanks for your help! :good::laugh:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.