Problem with new GingerStreak 2.4.4 - Streak 5 Q&A, Help & Troubleshooting

i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?

raptoid said:
i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
Click to expand...
Click to collapse
Honestly honestly what I suggest is you back up to a more stable build. GB2..4.4 is a beta just like all the Gingerbread builds and upcoming ICS builds will be betas because there are no official releases,
If something like a boot loop hangs you up, you definitely shouldn't be running Gingerbread or anything beyond Froyo as those problems will always exist with these builds....
But to answer your question, you need to boot into recover, clear your cache, your dalvik cache, flash the ROM again and then do a factory reset

raptoid said:
i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
Click to expand...
Click to collapse
cdzo72 said:
Honestly honestly what I suggest is you back up to a more stable build. GB2..4.4 is a beta just like all the Gingerbread builds and upcoming ICS builds will be betas because there are no official releases,
If something like a boot loop hangs you up, you definitely shouldn't be running Gingerbread or anything beyond Froyo as those problems will always exist with these builds....
But to answer your question, you need to boot into recover, clear your cache, your dalvik cache, flash the ROM again and then do a factory reset
Click to expand...
Click to collapse
The latest GingerStreak build is stable for most people using it, but it is not a final release yet
The boot loop problems are most likely related to not doing a factory reset of the phone or not following the install instructions to the letter. Another possibility is over clocking the CPU too high, some Streaks can not be over clocked.
If you can get into recovery do a reset from the first screen.

ADW
Just to add......I had the same problem after flashing 2.3.3. In fact, mine went Bricked and couldn't even get back to stock with streakflash. Luckily, I've had BB's Geek warranty, so I got a replacement.
Couldn't stand stock ROM, so tried SD 2.4.4. All went well until I started updating restored apps from the market, then phone would go into reboot loops, requiring a factory reset each time.
Then I tried without overclocking, still crashed into the reboot loops.
Finally, went to a different launcher (Go, rather than ADW) and so far it's stayed stable. No FCs, nothing. I'm thinking ADW didn't like something.

raptoid said:
i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
Click to expand...
Click to collapse
I think is md5 checksum problem, try to verify it before flash, and flash rom only if you're sure of that

Just try dsc rom. I got no random reboot, no sod or any major bug.

power_rom is rapid, stable and smooth.

Related

[Q] All soft buttons stopped working on CM7

I installed Cyanogenmod 7 a week ago, and everything was pretty much working fine.
Randomly today, all 4 of the soft buttons stopped working in the middle of me using my phone. I believe I was checking scores on an NFL app. Regardless, reapplying the CM7 zip didn't fix it. I tried factory reset, wipe cache, wipe dalvik cache. Nothing.
Decided to try to reroot. Reapplied ED05, which is what I did before I installed CM7. Got back to essentially factory... soft buttons still don't work. Reinstalled CM7... took, but soft buttons won't work.
I thought I read somewhere that this is an issue with gapps, but I can't seem to find that page or people discussing it again. Installing gapps again didn't work.
I'm willing to get my phone back to it's most basic level, and even erase the SD card if I need to, but not sure how to clear my phone moreso than my reverting back to ED05.
Thanks for your input guys.
Also, I had reinstalled my apps using Titanium, but not the app data. Again, everything was just fine for a week.
Also, having done a bunch of flashing and what not, I dont' know what happened, but now when I long press the power button, the menu comes up. When I try to use volume up/down to navigate to power off, all I get is volume going up and down
So, i know this thread is sort of dead, but this happened to my fascinate a while back with a version of CM7 mtd (55 maybe?)... I'm fairly convinced that the sensors for the buttons (and the lights for that matter) are completely shot, but I can't really test that. I have flashed back to stock, re-rooted it,and done everything I can think of to fix it.
You probably messed the phone up for good... my advice (if you haven't already done it): get a new phone.
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Will try this out
JJ5150 said:
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Click to expand...
Click to collapse
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Charcaroth said:
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1488976
If you are already on ICS just wipe cache and dalvik cache and flash. If not just flash up to ICS and flash kernel with ROM (same cwm session). You may want to do some reading in that thread first to make sure you get right version for your ROM.
Sent from my SCH-I500 using xda premium

[Q] Cyanogenmod 7.1 Galaxy SII?

I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?

[Q] P7510 (p4wifi) tab freezing all the time

Hi all,
Lately my tab is freezing at random moments. When opening gmail, youtube, browsing, settings, .. I can't use it longer than 5min or it will crash.
I'm running CM 10.1 nightly 20130118, Kernel 3.1.10-cyanogenmod (never upgraded this).
I have also tried older CM versions (CM 10, older CM10.1's, CM9) and AOKP -> same problem.
When I install a new rom I always wipe cache partition, wipe data/factory reset, wipe dalvik cache first.
I'm running CMW Recovery v6.0.2.7. Today I also installed a new bootloader (US_LPL_4.0.4_bootloader) but still the same issue.
Any ideas? Is it possible to do a harder reset than I already do? Should I maybe install a kernel update?
Thanks!
either you are overclocking and not stable, keep installing back the same bad app which is wreaking havoc, restoring from an old TB backup which is not playing nice on current stuff, installing some hack/mod which is wreaking havoc, or you have a hardware issue.
odin back to stock ics (this will completly wipe the whole tab out) and observe for a few days.
pershoot said:
either you are overclocking and not stable, keep installing back the same bad app which is wreaking havoc, restoring from an old TB backup which is not playing nice on current stuff, installing some hack/mod which is wreaking havoc, or you have a hardware issue.
odin back to stock ics (this will completly wipe the whole tab out) and observe for a few days.
Click to expand...
Click to collapse
Never overclocked so I'm afraid it's a HW issue.
Just installed stock ics and it still freezes after a few minutes (without installing any apps).
Guess I'm gonna try to put everything default again (I still have those 0/0/0 folders from JB) and return it to the shop..
lolsnorz said:
Never overclocked so I'm afraid it's a HW issue.
Just installed stock ics and it still freezes after a few minutes (without installing any apps).
Guess I'm gonna try to put everything default again (I still have those 0/0/0 folders from JB) and return it to the shop..
Click to expand...
Click to collapse
Jeps... Sounds like a hw issue if it is still causing the crashes on stock, how long do you use your tab now? maybe it has nothing to do with time, but just want to know..
DefQoN_BE said:
Jeps... Sounds like a hw issue if it is still causing the crashes on stock, how long do you use your tab now? maybe it has nothing to do with time, but just want to know..
Click to expand...
Click to collapse
I have it for about 9 months now but never really used it alot. I think in total maybe 40-50hours (watching movies on holidays etc).
I did leave it on the table once while the sun was shining through the window so that might have overheated the tab a bit.. Not sure if the issues started right after that. I could still watch a movie on it etc, now it crashes after 5min max.
lolsnorz said:
Hi all,
Lately my tab is freezing at random moments. When opening gmail, youtube, browsing, settings, .. I can't use it longer than 5min or it will crash.
I'm running CM 10.1 nightly 20130118, Kernel 3.1.10-cyanogenmod (never upgraded this).
I have also tried older CM versions (CM 10, older CM10.1's, CM9) and AOKP -> same problem.
When I install a new rom I always wipe cache partition, wipe data/factory reset, wipe dalvik cache first.
I'm running CMW Recovery v6.0.2.7. Today I also installed a new bootloader (US_LPL_4.0.4_bootloader) but still the same issue.
Any ideas? Is it possible to do a harder reset than I already do? Should I maybe install a kernel update?
Thanks!
Click to expand...
Click to collapse
I have the same setup as you and my tablet starts to crash this week. Gmail won't stay for 2 mins
Try this!
You need to wipe it clean and make sure your 16G is not getting full. You can use any file manager ap to start your clean up, which is all you need if the hardware is not damaged. Ok, so go to root and remove any excess file you might have, this will eliminate memory issues. Next, reboot into recovery, hope you are rooted, then wipe everything including delvic. Install your ROM [INFAMOUS_2.2], the best I have tested, and reboot your system. If you can't do this you need to reinstall CWM, I use 5.5.1.7, and then reflash your rom. If this doesn't get you back in the clouds contact me.

Phone freezes after boot

hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.

[Q] ROM: Hellybean Problem: won't reboot

Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?

Categories

Resources