[Q] Odd boot up problem with Roms - Galaxy S II Q&A, Help & Troubleshooting

ok the problem I have is when I install any Rom from recovery mode they all hang on the boot screen, I have waited 40 mins as devs do say that they can take time on first boot.
The only roms that seem to work are CM or roms that install via odin.
What I have tried to fix the problem is installing stock roms via odin then trying the recovery mode installation, just same thing happens stuck on rom logo/wallpaper.
What irritates me the most is I used to be able to install roms without any problems, so i must off done something, I am thinking when using Odin I have maybe ticked the partition option but really I just don't know...
Any help or even a way to take it right back to the day i got it would be greatly appreciated.
Thanks

Are you using the correct or recommended kernels?
Sent from my LT26i using xda premium

Recommended every time, not sure if its important but when installing via odin roms work perfectly.

Related

[Q] trouble flashing roms

gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Did you try to wipe data/factory reset/ wip cachd and wipe dalvik?
all of it. follow directions for each rom exactly. i always end up in the same spot
burnitdown said:
all of it. follow directions for each rom exactly. i always end up in the same spot
Click to expand...
Click to collapse
How much you wait? After I flashed the Galaxy Task 14 room earlier this day it took several minutes to load.
Certain ROMS require an older version of CWM, such as CM9. If that is the latest version you have installed it may not work. Maybe try using ODIN to flash the recommended version (you can easily find that in the CM9 Nightly threads or simply by searching around)?
bar_rodoy
Click to expand...
Click to collapse
i let it sit long enough.
this_is_nick6
Click to expand...
Click to collapse
i'm using the most up to date cwm. right now i'm trying to flash aokp m4
burnitdown said:
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Click to expand...
Click to collapse
Can you link us to the CWM 5.8.3.1 recovery your using???
As far as I know this is the latest version of CWM http://droidbasement.com/db-blog/?p=2655 as of 6/30 and it's only 5.5.0.4.
As far as Googling is telling me...
1. It may be a touch recovery?
2. I couldn't find a many search returns that mentioned it being for Tab10.1s
3. The search returns I did find that mentioned Galaxy Tabs were in languages I don't read.
Just curious don't ya know...
Sent From My Galaxy10.1 Class Starship....
Questions go in the Q&A section
my recovery is listed on the cwm site under rom manager. it's not touch
now i'm curious as to what version everyone else is using
okay. so i flashed 5.5.0.4 through odin then flashed aokp m4 plus gapps. all seemed to go well until boot time. i've been sitting at the samsung screen for a full 20 minutes now. i suppose my next course of action would be to revert to stock via odin and start the process over? i'd really like to use this thing but absolutely can't stand tw
you may have gotten a corrupt partition somewhere. I'd odin back to stock and start fresh. fwiw, I wouldn't trust ROM Manager for the latest recovery, it doesn't always have the correct file for your device. For example, for may particular phone Rom Manager had never worked properly and soft-bricks the phone every time.
Always check here on XDA for the proper recovery files for this device first.
that's all i needed to hear. now, can anyone point me in the direction of the file i need? my searches all point to S0ckM0nk3y's link which results in a 404 error
disregard my last post. i flashed sam's ics via odin. i'll play with it and try to like it. thank you sir
huh. still can't flash a custom rom...
Well, I don't know what I did but i was able to get MapleSyrup's CM10 preview to run. I'm happy for now
Are you doing a factory reset and wiping the cache in CWM before you flash? I always do that and then use titanium backup to restore my apps.
Also, what version of recovery are you using? I'm on CWM 5.5.0.4 which I've used to flash a couple of different roms, including the latest stock ICS from Toldo I think.
you can get it here and use ODIN to flash. Just make sure you download the correct version for your device:
http://droidbasement.com/db-blog/?p=2668
i had the same problem. i flash stock ics rom for my 7510. at first it looks fine until i try to reboot my tab. it starts to hang at the bootscreen. i try to reflash the rom via recovery but fail. try to install nandroid backup and also fail. the last resort is to do clean flash from odin. this thing happened 5 times in 3 days. one time after i install all the apps and try to restart my tab then it happened again, stuck at bootcscreen.

When trying to flash ROM... It is stuck on the Reboot Screen...HELP!

Hi there,
I tried to flash a new rom and it some how is stuck on the reboot screen.
Any help in what to do, would be great!
Thanks!
Pull the battery, put it back. Hold button combo to boot to recovery. Flash the ROM again but do not wipe. Reboot and you should be good.
FFR please list which ROM you are coming from and the ROM you are flashing.
Sent from my SCH-I535 using xda premium
Thanks, for your help!
I ended up taking out the battery, and then rebooting it, and it went to the Recovery mode.
I actually did wiped everything all over again, like you were doing it from the start originally, and it seemed to work fine.
I cant even remember what I was coming from, I had it on my Phone for almost two years, and it was old and the battery life was terrible.
I tried RemlCS-JB its not bad, but I think I am going to try another one. Any suggestions? I have been away from this forum for over a year, so anything recent with good battery life and good GPS is ideal.
The rom did not seem to come with an app downloader such as google play, or Clockwork manager.
Anyone know how to get into reboot recovery mode without clockworkmanager?
When I try to download clockworkmanager online it does not let me really download it.
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
molson24 said:
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
Click to expand...
Click to collapse
Did you Odin back to stock before trying to flash a ROM that is a previous version of android? It could cause a lot of problems if you don't Odin back to stock first!
Did you flash gapps on the ROM that you said was missing apps etc?
Gapps is a package of Google apps that devas can't include in the ROM.
I wouldn't use ROM manager, in most ROMs, there is an option to reboot to recovery in power menu. You can also power down and use button combo to boot to recovery.
I highly suggest reading through some of the dev threads for any ROMs you are interested in. It will answer most of your questions and prevent future issues.
Sent from my GT-P5113 using xda premium
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
molson24 said:
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
Click to expand...
Click to collapse
You can get the gapps from the op of the ROM thread or go to www.goo.im/gapps
As far as Odin etc
If you are on an ICS or JB ROM and want to go back to a froyo or GB ROM, you need to odin to stock first.
General rule of thumb, you can flash up but to flash down, Odin to stock first.
Sent from my SCH-I535 using xda premium

[Q] Question regarding TWRP/CWM when flashing CM 10.1

So I was pretty determined to get Cm 10.1 running on my Galaxy Note 2 for Verizon. Before hand, I was using TWRP to do all my ROM flashings but when I tried to use CM 10.1, I was told I must use CWM for it to work properly.
Here's my issue, I tried using CWM but it kept on giving me an error and after searching for awhile, it said its because I'm trying to use TWRP instead of CWM. So I flashed CWM and it gave me the same error. Tried both Touch and regular, downgraded and upgraded to the latest CWM but still same error. So I said **** it and installed the lastest TWRP. Then all the ROMs that were giving me issues started to install flawlessly. Then I went to CWM and it gave me the same error.
Am I doing something wrong when I flash CWM? I tried both Odin and APP Update way and both with same results. After using TWRP for awhile, I actually am starting to like the CWM Touch a lot better and I want to switch but not if its going to be giving me problems every flash.
Any insight would be helpful,
and as always to everyone on this forum, thanks
Just make sure you are using the latest version of TWRP 2.5 and you will be fine. You also may need to re-download your ROM file.
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
wythyntime said:
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
Click to expand...
Click to collapse
That is the way I have always gone about getting CWM on my phone back when I wanted it. I would just flash over TWRP in TWRP and then reboot system and then reboot back into recovery and it would always be CWM. If it doesnt work for you that way then see if they have a Odin tar and if so follow the instructions to flash it in Odin. They may not have an Odin flashable though, its been a long time since I have used it and on a different phone so....
Sent from my SCH-I605 using XDA Premium HD app
Let me actually rephrase this. (My bad for any confusion)
So if I try to flash a rom using TWRP, it goes through without any issues, even the CM rom. But when I flash CWM and try flashing, it gives me the getdevice-"(t0vzwte)"-not exact".. When researching, I was kept on told its because it is running TWRP. I tell them its CWM and they told me to update my CWM. I actually like CWM a bit better, idk why. but I was just trying to get my phone 100% the way I want it.

[Q] Possible brick after CWM recovery update.

Here goes, hopefully someone can help!
Ive installed a fair few roms on my phone and never had any issue, maybe this explains the complacency.
After updating to CWM recovery -6.0.4.7 I get stuck on my bootscreen, only seeing "Samsung galaxy I9100P" , ive been putting I9100 roms on it and losing NFC functionality for a while.
I went to update to the newest CM-11 nightly and read I needed to update CWM-recovery first. So did that, rebooted phone as instructed after installing new CWMr and nothing. Just stuck on I9100 screen.
No way to get into recovery mode, the only bright side I have found is I can boot into ODIN download mode. So what would be my next steps anyone?
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
andrewwright said:
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
From a dig through the forums it sounds like NAND rw corruption?
I wouldn't be calling it that just yet. Unless you'd like to pay for a motherboard replacement ? Most of these are recoverable.
Used ODIN and flashed a new kernel, still on the boot screen, except now I have the yellow exclamation mark. Now to, Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.. this day is not going well..
Fingers crossed, flashed 3 or 4 kernels before one worked and allowed me into recovery mode. Trying to restore back to my backup from this morning. Heres hoping! :good:
Worked perfectly, the first thing I did was retry the initial task which was what got me stuck, currently waiting on CM-11's initial boot up after a successful install Thanks for the calming responses!

Stuck on asop??

I'm having a bit of an issue with my phone.
I was running alliance ROM build 30 since it was released. A week or so ago i wanted to try cm12. So I flashed octos.
It flashed fine and it runs fine, but I still can't seem to "get into" asop. Just seem to keep wanting touch whiz again.
So I went to restore my backup of alliance and it fails right away. I'm using philz recovery. I've also tried twrp and no change.
So I went to do a clean install of alliance and it flashed fine, but it won't boot. It hangs at the boot screen.
So I tried to flash another touch whiz ROM and it did the same thing. Just won't boot.
But it does not boot loop, it justs gets to the boot animation and stays there until I take out the battery.
So far I'm able to get any asop ROM to work fine, but only one touchwhiz. And even then the touchwhiz ROM was really slow and force closed apps a lot (maybe the ROM, maybe not, I'm not sure).
So any help is greatly appreciated.
Odin back to stock?
Haven't tried that yet.
I assume I would have to use the MC3 file right?
So I can re root and unlock again.
It appears that there isnt any files that I can download.
Everything I can find is no longer available
Well I found the odin file.
Ran it now my phone is really screwed. It said it ran successfully but when it went to boot, it just flashes the galaxy note 2 screen.
Now every time I try to flash it in Odin it fails right away.
Bump. I tried to run the odin file again and it still fails.
Im back om my old phone for now so i have some time to figure this out.
Sent from my DROIDX using XDA Free mobile app
droidx2.3.3 said:
Bump. I tried to run the odin file again and it still fails.
Im back om my old phone for now so i have some time to figure this out.
Sent from my DROIDX using XDA Free mobile app
Click to expand...
Click to collapse
have you tried to boot into stock recovery and wipe data/cache?
I tried but it wont boot into recovery. The only thing kt will so is flash the boot screen or go into download mode
Sent from my DROIDX using XDA Free mobile app
You should have just used a custom kernel. It would boot with AGNI fine. My phone is doing the same thing yours was, IE not booting touchwiz roms. AGNI always works to have it boot correctly. Now, though, you have a different problem which is you probably flashed the wrong ODIN file and might have bricked the phone.
I've used this odin file before with success though.
I couldn't find any files to download at first, but then I remembered that I had them on my computer still from a long time ago.
I figured out if you load MochaDrizzle ROM, then after booted, download the app called FOLDERMOUNT. Run it with root access and it will 'fix' a broken permission. Next load Int-SDCard Writer and hit the Download (extra fix) button and then Fix Me buttons. THen reboot. Now you should be able to re-load stock roms and have them boot.
SHEESH!

Categories

Resources