Hello everyone this is my first time posting here and i have an atrix 4g and i am currently running th3 bills beanstalk jb 4.2.2 and i also have mrom cm7 in recovery and i was wondering if i can dual boot between the two, would boot emperiem work if i replace the boot images or anyplace to start would be a great help. Oh and i have a little experience with my atrix so not a complete noob lol. Thanks for anyones rtime and help
I do believe i tried boot emperium before and i got stuck at boot screen and i dont know if this would cause an issue to what i am trying to do but beanstalk was missing something and i had to flash epinters cm10.1 first then beanstalk to get it to boot properly. The reason for wanting dual boot is there are certain things that work on cm7 that doesnt work properly on ics and jb, i like miren browser alot i have used it for over a year but there are some issues with it on jb,ex: force close due to multiple pages or will also fc when you back page a few times
Related
I have the HTC g2 tmobile phone. I have just gotten into the flashing/modding scene, and am having a blast tweaking the phone. I have been trying a lot of roms in the past days trying new ones I like or may not like. Anyway I had the Cyanogen nightly rom on there before I flashed with the virtuous sense v2.0. Everything seemed good until I tried unlocking the phone after the looong reboot. Now when I unlock it I get a lot of force closes. Specifically for messages, and media, then the phone just reboots. Keeps doing the same thing over and over? Any help? If I could just figuire out a way to reboot into recovery and flash w a diff rom, or is there something missing since Im getting the FC from a few things? Thanks a lot!!
hi wtfd00d, if u new to flashing rom and wanna flash a stable rom, try keep yourself away of any custom with name "Nightly/Nightly build" because Nightly build, although is kinda ahead of time, is still in development build and merely for testing. try flashing other rom if you would.
[Q] What kind of "loop" do i have? Happens with AOKP devil and glitch ICS and CM10
First I know the phone is not bricked. I can and have repeatedly ODINed to stock EH03, remembering to atlas and repartition as per droidstyle's guide. The problems begin when I go through the rest of the guide section 4, to get and ICS AOKP rom running. (This is staging for my question to be complete. Question at bottom.)
For whatever reason the phone was stuck to only boot into (red) recovery. I had the AOKP rom MS6-devil before and I think flashed another different devil kernel over that. The phone has been completely stable for months now. I tried data wipe/reset and wipe cache, and dalvik too. It still only rebooted to red recovery (sorry don't recall the exact version). This is when i decided to ODIN and start fresh.
Maybe some side questions. Is it ok to flash different devil kernels on the devil kernel rom? I assume yes but I just needed to run through my check list. When I ODINed back to stock did that automatically restore the phone to a stock kernel as well?
So the phone ODINs fine every time and ODINing cmw4 for CW7 and GB bootloaders too. (BTW when i flashed ICS rom several month back i dont think the guild had anything about ODINing bootloaders. Is this new?). 3 finger works and I'm in blue recovery 4, i wipe data and dalvik (I've done this more than 5 times some i also tried a cache wipe with same results).
What kind of boot loop is this?
I flash the ICS rom zip that i want and it starts but the status bar on the phone make a small amount of progress then goes black, reboots to the flash the Samsung logo then goes to some splash screen that shows Icy Glitch Kernel V14 if i try the AOKP M6 official, or a splash screen of Devil Kernel if i flash AOKP M6-devil or even with CM10 i see the splash screen of cyanogenmod. If i let the phone sit on the screens for a long while all i see is a continual booting to these splash screens.
I have mucked something up with the kernel and i thought ODIN would reset that each time. If I can know what kind of boot loop i face i can go to find the right threads or make a post in the right place to get this resolved.
Actually it's normal for that to happen, after you start the install it should reboot the phone to an updated recovery and continue the installation from there. At least that's what it did for me when coming from stock. How long did you wait? Are you getting any errors? If you're still using the stock sd card that could be your problem right there. Also, I highly recommend trying a JB rom, ICS is pretty stale at this point. AOKP just released JB Milestone 1
Good tips. I didn't know that's what it should look like. I was flashing for many hours and waited 20-30 minutes. The only happenings on screen were the splash screens flashing occasionally as if the phone were looping. Im guessing now that's normal in the flashing process. I've flashed the same roms before months ago and probably the process on screen I just forgot. Ill try again later when I have time and try some jb action and report back.
When going from stock to ics are you first flashing ths build 2? There are many versions of devil available some are built for ics and aome for jb only. It's important to know which one you are dashing cause the jb devil kernels have a specific partition layout needed to get jb to run on the fascinate. I could be wrong but anything higher than 1.5.xx is jb specific.
The devil rode a unicorn named jelly bean
forsakenone said:
When going from stock to ics are you first flashing ths build 2?
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
You know I think that is it. I just blanked on doing that. I have build 1 and 2, b/c sometimes one works and one doesn't. I think I used 1 this time, but the first time I flashed ics i used build 2. Any way thanks. I am checkin out jb now too. cm10 is working great.
You didn't miss the step (to flash Build2 between EH03 & AOKP/CM10), the step was missing (temporarily) from the guide because some have found it to be unnecessary. I had the same bootloop as you when I didn't go through Build2 on the way to AOKP. Seems like the phone attempts to boot normally rather than into recovery to finish the installation of AOKP/CM10, and can't because it is midway through the installation. So did you state you had the problem when flashing CM10 as well? That's interesting, since some can skip going through Build2 and some can't. I thought maybe AOKP required it and CM10 did not... still trying to figure out what is different between phones that require it and those that don't.
Yeah I had it happen on cm10 too. I tried again but only flashed cm10 and no strange looping like I described. But I didn't flash any build before cm10.
Not too long ago I bought a XT910 from rogers used off a person. It had a problem,it wouldn't boot pass the rogers screen, well I got it once or twice, just to root it and it always booted fine in BP hardware + AP boot but no other way. After tinkering I got BMM installed, and was able to install any non stock based ROMS (AOKP types iirc).
I was wondering if anyone else has had a similar problem and if there is a way to get stock based roms like catalyst and Artmod to boot properly.
Or do you think there is some hardware problems on it? Like I said, non stock based roms seem to work fine, well some have a small lag issue on touching the screen and actions but so far Carbon 4.3 JB rom I have installed with the JBX kernel seems to be going fine (Even have GPS working fine too)
I just wanted to know anyones opinion on the matter. (oh, I bought the phone for only $80 CDN, figured it was a deal)
EDIT: BMM shows a Red LED when attempting to boot stock roms
This never looks like a hardware problem!
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
NOTE: Most, if not all of these ROMs are designed for ATT.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
I had the same problem and switched to Philz Touch instead of TWRP, I like TWRP a lot more and most people say its more stable, but that's what fixed it for me.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Umm... Don't reboot
Sent from my SCH-I545 using xda app-developers app
I have read, on CM's site somewhere I believe, they recommend using CWM for a recovery. I use 6.0.4.4 and have no issues with getting stuck at the boot logo. There was an issue with that but CM addressed it in one of the nightlies about two weeks ago.
I had that issue when I had a newer twrp recovery I have the .2 whatever one and I havnt had it since.