Call me crazy but maybe I'm missing something.
I have a t-mobile Samaung Blaze 4G. I was running stock+root rom and everything was fine. I downloaded Goomanager to check it out and it had an update (pa_t769-ota-eng.thomas.zip) so like a total noob I flashed it (yes I made a back-up) From that I got Paranoid Android 4.1 and its ok if you download the GApps but now it wont take any flashes for 4.0.4 including the back-up. It gets stuck on bootlogo. It seems like anything with a factory stock bootlogo will get stuck and I want to go back to 4.0.4 because the 4.1 is unstable and reboots randomly alot throught the day. any help would be greatly thanked.
EDIT: I am now running Paranoid Android 254v4 and it is working flawless. Goomanager is also running great. People should check it out.
I had that same problem with paranoid. I even did a fresh install just to make sure I didn't forget something. I ended up just flashing a new rom
Sent from my SGH-T679 using xda app-developers app
Related
Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!
Are you sure it is due to CM? I have the same issue with the stock Rom rooted.
Well it only happens on any nightly past the experimental M1.
Have you tried a clean flash? Or have you just been doing dirty flashes over and over?
Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium
Hello Everyone,
I am a new user of XDA and did much reading. I must be honest here, I have been reading quite a bit and love to do some crazy stuff with my Sony Xperia1
I actually had the stock rom for Xperia S which was really slow and problematic. I then loaded the Cyanogenmod 9.1 to try an resolve performance issues. Unfortunately, that was not to be and the system is very slow, unresponsive, and heats the phone up quite significantly even when it is not in use.
Now, when I was loading the Cyanogenmod, I had to copy over the boot.img file along with CWM. I noticed that the boot splash screen now showed "FreeXperia" instead of the regular SONY logo. Also, I was able to get into CWM by tapping the screen upon boot.
Anyhow, due to the poor performance of Cyanogenmod, I decided that I would try MIUI and when I installed, I tried to boot and the phone eventually showed the MIUI splash screen and got stuck on that.
Now, I am trying to get into CWM but that is no longer possible. I want to load another rom and is not working because i can not get into CWM.
Can someone advise to a work around to get back to stock rom so that i can start my hacks again??
Anyone!!??
Not sure if this works on a Sony but you can get it into download mode and flash stock through odin or hemidal
Sent from my YP-G70 using xda app-developers app
Nope that doesn't work on Sony!
Just Samsung recognizes Odin!
And as for the guy, did you flash the boot.img of cm while using cm Rom
But while you switched to miui
Did you flash back stock or stock based kernel?
As the cm kernel won't work on Miui Rom
Sent from my MT11i using xda premium
I recently bought my girlfriend a galaxy s II skyrocket. I own one myself. I updated my phone successfully and easily to jellybean through the official CM10. I am well aware of the different methods to install different custom roms to your phone. I received my girlfriend's phone with stock gingerbread. I proceeded to install the stock ice cream sandwich update to the phone through Odin. It was successful. I also installed ClockWorkMod recovery into her phone, the exact same one I had. I continued to attempt to install the same rom that I had on my phone, to my girlfriends phone, CM10. CWM said it was a successful installation after the careful 3x: Factory reset, Cache, Dalvik Cache. Upon rebooting of the phone however, the phone would fail to successfully turn on. It would stay in boot loop mode forever. One time I even left it for an hour and there it was, the boot screen I so dreadfully began to hate. I gave up on CM10, so i began to look for other prospects of a rom. I discovered slim bean. I installed it into my original phone to test it and found it to be of great quality. After I followed the exact same steps I followed to install slim bean to my original phone, to my girlfriends phone, the same result came about; boot loop. After about 20 tries, seriously, I tried to find yet another prospect of a rom. I also discovered another slimmer version of jelly bean for the Skyrocket. Even after the careful following of the steps, I encountered the same result; boot loop. I am beyond frustrated at this point at the fact that I am holding two phones exactly the same, yet when I attempt to install the rom, it only works on one of them. They are both Samsung Galaxy S II Skyrockets model numbers 1727. Both based off of At&t in the United States. One is white while the other one is black. If it makes any bit of a difference the phone I am having trouble with is white. I need help. I've tried everything with no success. I am trying to update this phone to jellybean but it does not seem to accept it, and I have no idea why
Re: [Q] Stuck on boot loop after several different jb roms
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
TLDR condense give important details that's it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I am not yet familiar with all the terms. It seems like jargon to me at times lol. TLDR Condense?
Re: [Q] Stuck on boot loop after several different jb roms
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Nobody knows what version of cwm you're on.
Nobody knows where you're dl'ing cm10 from.
Quit wiping 3x you only need to do it once.
Don't write novels.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Tldr means to long didn't read
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I've tried installing Official CM10.1 (from XDA) with boot loop result. I've tried installing unofficial 4.2.2 slimbean (from XDA) with boot loop result. I've tried installing Skyjellybean 4.1.2 update 11.4 (from XDA) with boot loop result, and finally I've tried installing Superlite CM10 JB 4.1.2 v8.0 (from XDA) with boot loop result as well. I am currently on stock Ice cream sandwich installed through Odin (links and all found from XDA)
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
lingowistico said:
Agree with mtdew.
Keep it as short as possible and be specific.
Get CM10 (not CM10.1 as it's still unstable) from http://get.cm/?device=skyrocket .
Also try latest CWM http://forum.xda-developers.com/showthread.php?t=1777970 .
Click to expand...
Click to collapse
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
That is good news, i'm glad it worked out for you. Good luck. :good:
Help
s3rgioru3las said:
I discovered the issue! Even if it was the same recovery as my other phone i used to install these updates successfully, it was the recovery that was broken. I installed a different version the latest "touch" version of Clockworkmod and to my surprise, the update was successful. I am running 4.2.2 unofficial slimbean! Thanks guys, for your help.
Click to expand...
Click to collapse
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Cisco408ca said:
I too Have a Bad Recovery . Every time i try to install ANY jellybean rom i get stuck in boot loop . I Tried different recovery's and different rom's and stock jellybean and no success . But any ics or gingerbread installs normally . I have a epic 4g touch galaxy 2 and it's rooted . Any new idea's what it could be or how to fix it ? I feel i'm the only person with this problem since i cant find anyone else with the same situation . Your the closets to my problem
Click to expand...
Click to collapse
Use the latest recovery in your forum
Sent from my HTC One using Tapatalk 4
Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh
Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app
Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium
I've been trying to install Slimsaber on my phone. I've been able to install AOKP 4.4.2 and Beanstalk 4.4.2 fine, however when I follow the instructions on installing Slimsaber the bootscreen seems to linger forever. I've waited longer than 10 minutes and it still remains with a flashing SlimSaber bootscreen. I've tried the 05142014 nightly.
05132014 nightly worked fine.
14 nightly and after has some troubles, with build script mostly as we did some experiments to it. Anw it woukd be back soon after we solve a more important issue named stealing . Sr for this inconvenience.
Sent from my GT-I9300 using Tapatalk