Phone: Atrix 4g, 4.5.141 ATT, Andriod Version: 2.3.6 Kernal 2.6.32.9, Unlocked, rooted, in USA running ROM manager, titanium backup pro, and ROMRACER. I have run Moto stock with updates until now.
Lurked here forever, haven't had to post until now. Since Moto has end of serviced the atrix I figure I would try my hand at CM7 and maybe CM10 once the big boys get all the drivers working.
I am trying to flash CM7 and I keep getting stuck when re-booting at Red Moto emblem with the quad core screen. I have left it run for 30 minutes. The only way out is to pull battery re-boot to CWM and re-flash ATT.GB236_45141_PureStock_v21.5_xanadu_upndwn4par and start again. I can back up upndwn4's ROM while it's running with ROMRACER, but I can't restore it. I get a system error from CWM when I try to re-flash it.
Tried:
Reset/Wipe cache/wipe davilik every time
multiple different ROMs including Ba2tF, CM-10-20121010-unofficial-olympus, MROM all downloaded a couple of times
Tenfar's CWM instead of ROMRACER
Flashing off of internal
Flashing off of external
When I flash the CM7 or CM10 ROM it takes about a minute to flash before CWM says it's completed. But when I flash back to stock it takes 4-6 min. to flash.
Can't figure out why I can't flash anything other than the stock ROM. Any assistance would be much appreciated.
Binarysailor said:
Phone: Atrix 4g, 4.5.141 ATT, Andriod Version: 2.3.6 Kernal 2.6.32.9, Unlocked, rooted, in USA running ROM manager, titanium backup pro, and ROMRACER. I have run Moto stock with updates until now.
Lurked here forever, haven't had to post until now. Since Moto has end of serviced the atrix I figure I would try my hand at CM7 and maybe CM10 once the big boys get all the drivers working.
I am trying to flash CM7 and I keep getting stuck when re-booting at Red Moto emblem with the quad core screen. I have left it run for 30 minutes. The only way out is to pull battery re-boot to CWM and re-flash ATT.GB236_45141_PureStock_v21.5_xanadu_upndwn4par and start again. I can back up upndwn4's ROM while it's running with ROMRACER, but I can't restore it. I get a system error from CWM when I try to re-flash it.
Tried:
Reset/Wipe cache/wipe davilik every time
multiple different ROMs including Ba2tF, CM-10-20121010-unofficial-olympus, MROM all downloaded a couple of times
Tenfar's CWM instead of ROMRACER
Flashing off of internal
Flashing off of external
When I flash the CM7 or CM10 ROM it takes about a minute to flash before CWM says it's completed. But when I flash back to stock it takes 4-6 min. to flash.
Can't figure out why I can't flash anything other than the stock ROM. Any assistance would be much appreciated.
Click to expand...
Click to collapse
Lol. Quad core screen? You have a powerful atrix!
Anyways, try a fastboot erase system and fastboot erase userdata before flashing CM7/10.
matthew5025 said:
Lol. Quad core screen? You have a powerful atrix!
Anyways, try a fastboot erase system and fastboot erase userdata before flashing CM7/10.
Click to expand...
Click to collapse
Yep my dual core is gonna become a quad if I can't figure this out.
Tried fastboot erase system and userdata, then restore/wipe/wipe install from SD (internal)...nope, sitting here looking at the same dang M
Thanks for the suggestion...got any more?
i have exactly the same problem with my atrix, i have 4.5.141 ATT en.US with android 2.3.6 NottachTrix 1.3.1 (this is the only custom rom that works after flash) i want to install cm9 or jb so baddd !! i hope someone know how to get this over :-/
Don't forget, you need to clear userdata (fastboot -w) AND cache (fastboot erase cache). You could also do that through recovery. I recommend TWRP 2.3.0.0. You can install it via Goo Manager or download the image from here and install it via fastboot (fastboot erase recovery and then fastboot flash recovery #filename#.img)
Haven't tried TWRP yet. Thanks for the suggestion. I will try that next.
Ok some sucess. Re-flashed based on the 5th post here http://forum.xda-developers.com/showthread.php?t=1525804&highlight=moto-fastboot+stock except for the OEM part because I am all ready unlocked.
Rooted again using auto unlock 4.2 instead of Pete's tools because the link was dead.
Updated recovery to touch recovery 5.8.1.8
Made another backup existing functioning stock ROM
Tried to flash a new Faux123 CM7 Kernel downloaded from ROM manager - fail when to boot loop re-booting constantly
Recovery to CWM and restored from backup WORKING NOW yippie! At least I can recover without having to re-flash stock each time
Downloaded MIUI 2.10.12 from ROM Manager and installed....error in downloaded Miui ROM (status 7) installation aborted.
Rebooting...will restore again if necessary...sigh more research ahead of me a fear.
I win
Big thanks to vladeco,. Since fastboot -w and fastboot erase worked so well getting ROM Manager to restore it tried them again before flashing CM7. Done and done.
Now I have backups of Stock, CM7 and am moving on to CM10 epinter's.
Flashed Epinter's CM10 - now running chrome, no isses heck even the video camcorder works!
Done and DONE!
Related
Ok so before my Atrix was stock on Gingerbread 2.3.4 OTA update. I then sbf flashed the pudding ROM, and it flashed correctly but my Atrix said boot error 0X1000 and that it detected no OS. It gave me the options regularly seen on the boot screen (including recovery, bp bypass nv flash, etc). To remedy this I did fast boot oem unlock and then fast boot reboot. The phone was unlocked, and at first it was stuck on the dual core screen, but on second boot it booted into the new ROM. I then flashed a custom recovery (tenfar's) and installed the pre release CM7 ROM. I'm now rooted and unlocked running CM7. My question is, do I ever need to use sbf flash again or can I always just install through my custom clockwork mod recovery. Also, when I do install a ROM through cwm recovery, is it just like sbf flash, as in does it overwrite all previous data and I'm starting fresh with my new ROM (after cache and data wipes of course)? And if I ever do sbf flash to something higher than 1.8.3 (my fuse has already been burned since I did the OTA to 2.3.4, will it be safe)?
Lastly, an important question I need to ask pertains to the cwm recovery. Whenever I try to use a function on ROM Manager, it says I need to flash clockwork mod recovery, even though I already have Tenfar's cwm recovery flashed into my phone. Is it safe to flash cwm recovery that ROM Manager is asking me to flash even while I have Tenfar's custom recovery flashed on my phone?
Yes, threw cwm a full rom if you wipe all your data, it will be like a fresh install.
But it won't erase recovery or mess with bootloader
You can skip flash sbf's by using cwm zips, since every custom rom is in cwm and none in sbf.
If you update to a higher who knows?
You are already in gb. The sure if you downgrade with ota sbf you will hard brick!
In an upgrade, mmm let's say ICS, as they promised to unlock the BP, may they finally do it..
If they dont, or its not safe etc,
Don't worry . Devs will make again a safe cwm zip.
For rom manager.
Yes, it is safe, but..
It doesn't support sdcard-ext.. Only the internal.. So stay with tenfars or with the new one, of another guy in dev section.
ofcourse you can install eg rom managers recovery, and after that install using fastboot tenfars or the other one..
Its safe. If you know what you are doing.
One recovery will be installed each time..
Its up too you..
BlackKnight12 said:
Ok so before my Atrix was stock on Gingerbread 2.3.4 OTA update. I then sbf flashed the pudding ROM, and it flashed correctly but my Atrix said boot error 0X1000 and that it detected no OS. It gave me the options regularly seen on the boot screen (including recovery, bp bypass nv flash, etc). To remedy this I did fast boot oem unlock and then fast boot reboot. The phone was unlocked, and at first it was stuck on the dual core screen, but on second boot it booted into the new ROM. I then flashed a custom recovery (tenfar's) and installed the pre release CM7 ROM. I'm now rooted and unlocked running CM7. My question is, do I ever need to use sbf flash again or can I always just install through my custom clockwork mod recovery. Also, when I do install a ROM through cwm recovery, is it just like sbf flash, as in does it overwrite all previous data and I'm starting fresh with my new ROM (after cache and data wipes of course)? And if I ever do sbf flash to something higher than 1.8.3 (my fuse has already been burned since I did the OTA to 2.3.4, will it be safe)?
Lastly, an important question I need to ask pertains to the cwm recovery. Whenever I try to use a function on ROM Manager, it says I need to flash clockwork mod recovery, even though I already have Tenfar's cwm recovery flashed into my phone. Is it safe to flash cwm recovery that ROM Manager is asking me to flash even while I have Tenfar's custom recovery flashed on my phone?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Danger!
To be honest...
you can use clockworkmod and take advantage of your unlocked bootloader, but the second that you brick (soft/hard) your device, you are in trouble. You wont be able to reflash it back to stock because the only SBFs that exist are for 4.5.57, and 4.5.52. Reflashing either of these downgrades WILL BREAK YOUR DEVICE FOR GOOD.
If you are lucky, you might be able to use fastboot to restore stock images, but if I were you, I would head on over to:
direct.motorola.com/hellomoto/motosupport/source/softwareupdate.asp
and use the update software to return your phone to factory ROM. With an OTA updated Atrix, there is too much chance that your phone will be rendered useless.
Do what you wish, but be mindful of the consequences.
This is all very confusing. There is a 4.5.91 SBF. It isn't a downgrade. It should only be flashed as a last resort though. It will remove the word "unlocked" from your boot screen, but it can't un-burn the fuse.
The far safer option is to use CWM for everything. This is the recommended approach.
Sent from my Alienated Atrix
As to your CWM question, I believe romracer's CWM is the new standard. I thought the CM7 instructions even said to use it to install CM7.
Sent from my Alienated Atrix
im on hboot 1.5 and i just bought BM (so boot manager noob) and had success (or so i thought) installing a slot 1 rom.. my phone rom is the latest MIUI, and i made the latest Joelz CM9 my slot 1. the rom installed (wiped all 3), and the gapps installed (wiped nothing) but but when i went to boot into the slot 1 (joelz CM9) my phone went into a boot loop and was pushed to CWM recovery. im restoring my nandroid as we speak. any ideas on what i did wrong or what could case this?
I did extensive research prior to buying and trying this app but Im obviously doing something wrong.. maybe its a kernel issue? but i was under the assumption that they both were using miui kernel.. lost plz help, or ill be forced to request a refund
...........edit..........
i am still in boot loop with restoring my nandroid!! wtf?!
Different ROMS require different procedures, with s-on, Meanrom, my personal favorite is easily flashable with .zip files, With other ROMS you will have to unzip the ROM and take the boot.img and place it in SDK tools and push ADB. from usb fastboot through the terminal. zedomax on youtube is super helpful with 3d rooting.
* Make sure to us CWM 4.0.1.4
Because you have 1.5, I think that you should flash the boot.img file via flash gui or fastboot before switching ROM's, that should take care of the situation.
Ohai!
I have a Galaxy Player 5.0 USA (YP-G70), and a few days ago I installed Entropy512's kernel via the `dd` method. Everything worked nicely, until I decided to boot into ClockworkMod Recovery by holding the volume up key while booting. It booted into the recovery menu, and everything worked nice, but when I hit 'reboot' or 'shutdown', it booted right back into recovery (after seeing the SAMSUNG screen for about 5 seconds).
I've done pretty much everything I can think of. I've reflashed the kernel, flashed CM7 and CM9, and I tried flashing a stock ROM that I found. Flashing the kernel from the stock ROM causes my device to instead go into "Android System Recovery" rather than ClockworkMod Recovery, but I'm able to get back into CWM by flashing Entropy's kernel with heimdall.
I'm capable of getting root access with `adb shell`. I've wiped almost everything on the device (used the 'wipe data/factory reset' option and 'wipe cache partition' option) but still continues to boot into CWM recovery.
I'm not too interested in simply fixing the device so it's back to stock, as I *really* want CM9. I have a Droid X to keep me busy for now, so I found that my Galaxy Player has been just sitting there, collecting dust. If I can get it to run CM9, I'd have more use for it.
I apologize if I left out some important information. Any help would be appreciated!
Thanks in advance,
- Ben
Just an update, I tried an exitrecovery.zip, which did not help. I also extracted the exitrecovery.sh from the zip and executed the one command it had inside it manually in a root shell. Still stuck. Is my device bricked in some form? I'm pretty sure there is some bootflag that tells it to boot into recovery, even if everything is fine.
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
East gsstert
Mevordel said:
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
Click to expand...
Click to collapse
Thanks for the reply. I actually ended up trying so, and CM7 as well, to no avail. I also tried flashing stock, as I said in the post (I think, maybe I forgot to mention it) and it failed. (I used heimdall to flash stock)
I ended up giving up and replacing the device since it was under warranty, but I regret doing such as I *really* wanted to know why this happened in the first place. I'm anxious to get CM9 on it. Should I just put the device into download mode and use heimdall to flash CM9?
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Mevordel said:
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Apologies for the late reply.
That is what I did last time. I actually got stuck in CWM before even trying to flash CM9 or anything. I just booted into recovery, and then instantly clicked on 'reboot'.
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Mevordel said:
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Yeah, seems to be probably what happened. I actually ended up trying again on the new Galaxy Player, and things went swimmingly. I am now happily running CM9 on this device. However, I am scared to even think about booting into recovery again. (I only went into recovery to flash the kernel, and wipe the data partition)
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
basti_b24 said:
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
Click to expand...
Click to collapse
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
TheKryptonite said:
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
Click to expand...
Click to collapse
Forgot to mention that: I tried various ways: first wipe data/cache, then flash ROM; first flash ROM, then wipe cache; wipe cache, flash ROM, wipe again...
In order to get CWM recovery and being able to flash a zip I flashed the Kernel first. For CM9 I followed this http://forum.xda-developers.com/showthread.php?t=2213152
As I couldn't flash any of the pre-flash zip from stock, I thought it's necessary to flash a kernel including CWM first. It was done in the same way in some youtube tutorial I watched, where the guy already had the terrasilent kernel on his device.
For odin, I will check if it works with first flashin the ROM and afterwards the kernel.
Cheers for your fast reply!