Related
getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
exzacklyright said:
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartition and wipe out every bit of data I had. The posts about howto fix CWM bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OP, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
wizayne said:
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartitions and wipe out every bit of data in had. The posts about howto fix cwm bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OPEN, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
Click to expand...
Click to collapse
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
mkuehl06 said:
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
Click to expand...
Click to collapse
The problem started after using ics from alphalulz v1 on around build 3 team hacksung IMMEDIATELY AFTER flashing glitch kernel v14 build 4...I have since kept away from glitch on ics, and the problem remains.
Lately it hasn't been as bad though and it seems by hitting random buttons during boot that it will eventually start but reading tells me glitch v14 build 5 is still recovery bootloop ridden and I haven't seen a word about it in the OP for ANY ics components be it team hacksung roms or glitch kernel, and an issue like this which from reading is seemingly widespread *should* be mentioned.
Any suggestions?
In your op you said e120, what phone are you using. E120 isn't a fascinate build.
Sent from my SCH-I500 using XDA App
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
wizayne said:
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
Click to expand...
Click to collapse
That makes more sense to me now I know what phone your on. Try rootzwiki they have a mesmorize section, they can help ya out more than I can. I have fassy so idk much about mes
Sent from my SCH-I500 using XDA App
I'm not new to android customization so i know what unlocking the bootloader entails, but my question is, is it worth it? There doesn't seem to be that much development going on for the TF201. My main issue with the Prime is that it seems a bit sluggish and unstable at times, which seems to imply a software issue rather than a hardware issue. If i unlock and flash a custom rom and kernel, would i see significant improvement in speeds or stability. I don't want to void warranty if i don't get a tangible benefit from it.
sputnik767 said:
I'm not new to android customization so i know what unlocking the bootloader entails, but my question is, is it worth it? There doesn't seem to be that much development going on for the TF201. My main issue with the Prime is that it seems a bit sluggish and unstable at times, which seems to imply a software issue rather than a hardware issue. If i unlock and flash a custom rom and kernel, would i see significant improvement in speeds or stability. I don't want to void warranty if i don't get a tangible benefit from it.
Click to expand...
Click to collapse
I unlocked my bootloader because of the unstability and the asus crap. I have now installed on my prime AOKP and motleys kernel (1,6ghz). I think it is worth it, but thats my opinion.
It was worth it to me...I'm currently running Primalicious Odexed Final version and the performance has been way better. Battery life is also way better...wiping cache and dalvik would definitely help with the sluggish performance, but as you know, you'd need CWM or any other custom recovery...hence, unlocking the bootloader is def worth it.
Thank you guys, that's exactly what I wanted to hear. Last question before I unlock, is flashing roms and kernels as simple as wiping data and caches through recovery and flashing the .zip file, or is it more involved? I remember reading a thread that talks about .blob files or something like that. I'm just trying to get as much info as I can before I do this, so I don't mess anything up. There doesn't seem to be much information available unfortunately. And I guess everyone is running the latest CWM recovery which is the touch recovery, right? Any problems with that? I know that TWRP 2.0 hard-bricked my Evo and that he CWM Touch recovery has bricked a few Samsung Epic 4G Touch phones when flashing between GB and ICS kernels. But this was likely a Samsung ICS kernel issue that wasn't playing well with the recovery.
sputnik767 said:
Thank you guys, that's exactly what I wanted to hear. Last question before I unlock, is flashing roms and kernels as simple as wiping data and caches through recovery and flashing the .zip file, or is it more involved? I remember reading a thread that talks about .blob files or something like that. I'm just trying to get as much info as I can before I do this, so I don't mess anything up. There doesn't seem to be much information available unfortunately. And I guess everyone is running the latest CWM recovery which is the touch recovery, right? Any problems with that? I know that TWRP 2.0 hard-bricked my Evo and that he CWM Touch recovery has bricked a few Samsung Epic 4G Touch phones when flashing between GB and ICS kernels. But this was likely a Samsung ICS kernel issue that wasn't playing well with the recovery.
Click to expand...
Click to collapse
Yes, you can flash roms and kernels just over the recovery (zip).
And there are no problems with the cwm touch recovery, the how to for that and the blob file can you see here. But i would flash the twrp recovery, i use it because it is more comfortable. I dont know about hard bricks because of that.
dom2215 said:
Yes, you can flash roms and kernels just over the recovery (zip).
And there are no problems with the cwm touch recovery, the how to for that and the blob file can you see here. But i would flash the twrp recovery, i use it because it is more comfortable. I dont know about hard bricks because of that.
Click to expand...
Click to collapse
Thanks, that's all I need. The TWRP 2.0 issue I had was only related to the HTC Evo and no other device as far as I know. But it did kill my phone and many others, so as you can imagine I'm weary of using it. But don't think that I'm trying to say anything negative about TWRP in general, it was just the Evo that it had issues with.
Hi guys,
I've had an S2 for a few months now, and although I've managed to root the phone I'm still pretty green and need help.
I've had an OTA update from Gingerbread to ICS which I only installed as it popped up when I was using the phone.
The battery died earlier than expected and now it's stuck in a bootloop.
I don't want to have to ROM it as frankly I'm still in the "full theory" stage. I've heard of Odin and SamMobile.com, I've seen hours of vids on Youtube but I'm hoping there's another way to get around it. My confidence levels are improving but not there yet.
I have a Titanium backup on the phone from 2.3.4, if I wipe the phone from recovery will it work? Is there anything I can do apart from a new ROM?
If you had my lack of experience with this, what would you do? Thanks.
Can you get into download mode?
If so, you may have to bite the bullet and use Odin to flash the original firmware. You will be able to find it on these forums.
Don't sweat it, just download the Orange ICS ROM and put it in PDA on Odin and flash it, it'll take just a couple of minutes and you are done.
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
FourQ said:
Thanks guys. It sounds so simple when you don't have a bootlocked phone to panic about.
Click to expand...
Click to collapse
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Warren.D said:
Thats because it is simple! Ive never rooted because it looks confusing. But I've used odin many times to flash stock firmwares.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nothing confusing about rooting either.
Download one of chainfires cfroot kernels or siyah kernel and flash via Odin.
That's it you're rooted.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
if ya have a look around the forum, theres plenty of pre-rooted roms to flash via odin that wont increase ya binary counter, nothing hard about that.
Read the links in my signature
Sent from my GT-I9100 using XDA
I'm still reletively new to it
and I've had a couple of bootloops. A bit of a panic and then I figured out what I'd done wrong. As long as you follow instructions to the letter you'll be fine.
Edit: *Relatively, damn it.
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
FourQ said:
Rooting it was easy enough. I went to unlockroot.com and a download later I was rooted. It's the ROMs that terrify me.
Click to expand...
Click to collapse
getting a custom rom isn't something you should be afraid of
getting a custom rom (or kernel) can improve your battery life (some of them).. but just be sure that getting a custom rom, it should be for whatever you're running (Gingerbread or ICS) usually, roms are flashable via CWM
take a leap, when you get into bootloop or get some problems along the process, just flash a stock firmware with odin..
@saywhatt
A mate (who's been doing this for years) has installed CWM7. It's odd how the things I liked about Gingerbread were added by Samsung, not Google.
I suspect I'll run with CWM7 for a week or so and decide then. First impressions aren't always correct (especially if you saw my face!) but after a week I should have a pretty good impression of the new ROM. I'm hesitant about ICS as the official version killed the phone but ultimately I may end up there.
It's good to watch the Youtube vids on how to flash stock ROMs with Odin. It's something I may try next week if CWM7 falls from favour.
Ultimately I'm sort of glad it happened. It's given me new confidence to try these things as I know there's a good chance it can all be recovered.
Q
I've never been too afraid of rooting or flashing. My first android device was a cheap piece of rubbish (an LG GTsomething i think), so I built up confidence in rooting and flashing because I didn't care if i damaged my phone.
I would recommend anyone who's not too confident to go out and get a cheap phone, it's a pretty significant investment but if your unsure about what your doing and just want to experiment, it's definitely worth the peace of mind.
...
I'm hesitant about ICS as the official version killed the phone
Click to expand...
Click to collapse
no m8 it didn't, your battery dying while you were updating killed your phone
It had finished a while before that. I was selecting a new font when it died.
You can't stuff up your phone anymore - its already in bootloop, what do you have to lose?
Odin is indeed very easy. Just make sure F.Partition is unchecked. Put the ROM in PDA and flash! Of course, after your phone has been put into download mode and connected to pc via usb and one of the Odin blocks have turned yellow.
Your phone is already rooted? If you made a backup in CWM (NOT Titanium Backup, this won't help you right now, as it's only for apps) you should restore that in CWM. A wipe and factory reset wouldn't help you right bow.
I understand you are a bit skeptic of ICS stock ROM right now, but remember you probably got pushed an early version,.the latest versions are very stable! Though Custom ROM's are the way to go eventually. Try the latest stable Cyanogen ROM.
Sent from my GT-I9100 using Tapatalk 2
@FreeStanler
Good point.
The stock ICS ROM was 4.0.3 if memory serves. It wasn't there for long but I was curious to see which version I'd been upgraded to.
I'm planning to see how this CWM7 ROM sits with me. If I can find out which app is causing this: http://t.co/9GfdXmD I'll probably be happy with it. I need to have a good play about with it to give it a fair chance. May end up with ICS/Stock ICS but for now we'll see how it goes.
Why on earth would you use Cm7 when Cm9 is far better, plus to flash a fw & then root with SuperOneClickRoot, or use the cf root kernel. The whole process takes 5 mins. Honestly M8 there's nothing to worry about. One thing I will say tho, Google Nandroid back up & once you know how to use etc, use it & make it your best friend coz that's the only thing that will fix the bootloop in the future
Sent from my GT-I9100 using xda premium
@blade30p
I didn't. A friend who's been doing this for years did it for me. I was hoping to get something resembling the stock Gingerbread on the phone, instead I got CWM7.
I have had a Bad ESN Fascinate for a while that I was playing around with, trying to get it to work on Sprint... No go. Anyway, it was rooted with a stock GB ROM and I decided I wanted to try out some of the ICS or Jellybean offerings that XDA has in its forums.
To be honest, I am no noob, but I didn't do enough research to begin with. First I installed GeeWiz 2.9 Kernel, System, and 2.8 Recovery. I didn't like the 2.8 Recovery, so I tried to flash something else, but nothing would replace it. Then I tried to install Baked CM10 from the GeeWiz recovery, and it went downhill from there.
Long story short, I have ODIN'd back to stock EH03 and tried to update to a couple of CM10 ROMs using the guides I have found here and on a few other forums. I have a working install of Hacksungs CM9 build 5 as of right now, but I can't get any further.
After using ODIN to get to Stock EH03, I ODIN the CWM4 for CM7. 3-fingering brings me to CWM4 where I begin the install of CM9. When it examines the partition BML/MTD it reboots the recovery (took me a while to figure that out) in to CWM 5.5.0.4 where it finishes the CM9 install. When I soft reboot into recovery, I get CWM 5.5.0.4. According to the guides, this is where I would flash CM10. It runs the update, but when I go to reboot the system, it reboots into a recovery of CWM 6.0.1.4. Also, if I reboot the system from CWM5 without installing anything, it boots back into CM9 just fine.
I am pretty sure I installed CWM 6.0.1.4 sometime in the past, but to be honest I have no recollection of when.
My question is multi-part: How do I get rid of CWM6; why is it still there after all the repartitioning with ODIN (with and without PIT file), MTD partition formatting, etc; why can't I get CM10 to install?
While this is a fairly wordy post, I have to say, I do have a working Fascinate with CM9 that I am enjoying playing with. I just thought if nothing else, people might get a laugh out of my struggles with this phone, that is basically a web browser and toy.
FWIW I have seriously ODIN'd back to stock about 5 or 6 times today alone.
Thanks for any help or suggestions in advance.
Unlike Gingerbread and earlier, with ICS and JB kernels they include whatever version of recovery the developer wants to include.
Is there a reason you don't want the latest CWM?
Sent from my SCH-I500 using xda app-developers app
Its been awhile for me since I had to go back to stock, but unless something has changed the three finger reboot into cwm caused some problems when flashing. Try rebooting to recovery through power menu.
Some ROMs are requiring to be installed a second time to "stick" due to partition layout changes.
Sent from my SCH-I500 using xda app-developers app
Thanks for the info on the ICS and JB attached recoveries. I was unaware of that. Maybe that's where the CWM6 came from.
And it isn't that I don't want to most current, it just didn't seem to want to play nice with the ICS and JB Roms I was trying to installed.
Now my problem is that the phone won't boot when powered down from ICS. Glad this isn't my main phone.
Sent from my EVO using xda app-developers app
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
From my limited knowledge,,,
I know the fixed cwm is what you need to get out of a 3 finger boot loop,,, I've had to do that...
Cwm 6 is what runs and works with cm10/jb roms,,,
Causes no errors that I'm aware of...
No more 3 finger,, always use power button/reboot
Once you have started an install of say cm10 ... Let it run its course , so to speak,,, if it comes up with cwm5 or cwm6 then that is the one the developer designed it to work with,,,
Let it come all the way up,, and then reboot through the power button method always,,,, you'll get used to that quick enough , as i remember the old gb froyo stuff didn't offer this method
I keep a copy of the fixed cwm just in case i happen to accidentally 3 finger ever again...
Sent from my swagger
spikeekips said:
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Not sure if you are still looking for advice but here is a little guide that has not failed me at all. If you follow this then you should come to the latest JB rom that you want.
Click here
Hi all,
I have a friend with an AT&T Atrix 4G. I've had a Droid X and current have a Galaxy Nexus & Nexus 7. I did everything you could do to the X and know my way around the Nexus very well; the atrix is a little confusing to me. moto-fastboot and the idea that SBFing is bad are new concepts to me. On the Droid X, if you were in trouble, you just SBF'd.
My friend had some trouble with his Atrix the other day, he was stuck at the splash screen, we got it half way fixed and he was in a bootloop, and eventually we got a version of CM9 on there: 9.0.0-rco-atrix-kang. The phone is running now but the ROM is unstable. I'd like to know how to safely downgrade to a CM7 ROM. Is it as simple as booting into recovery, wiping, and flashing the earlier rom? Something blur based would be ideal at this point as he's just looking to have a stable phone back. He got into rooting/ roming on his own so I'm not sure what updates, if any, were on there before he started. Is there an easy way to check and see which bootloader version he's on, find out which SBF we can safely use, etc? He does have it unlocked, so that should make things easier (or maybe harder, this Atrix really is a mystery to me...).
TL;DR - How do you safely downgrade an Atrix 4G from CM9 to CM7 and which recovery is the best to be using?
I used to switch between CM10 and CM7 all the time, if the phone is rooted and bootloader is unlocked, it's as simple as wiping data/cache, wiping dalvik, format system, install ROM, boot, reboot, install gapps.
Did your friend follow directions and make a nandroid of original before wiping? That would be the simplest way.
エイトリックス から 送ります
He said he had a backup but that when he restored it it was bootlooping. I'm assuming it was some kind of issue with switching recoveries or something like that. With the Droid X there was a recovery for 2nd-init roms and a recovery for blur roms. With the Nexuses it's mostly TWRP or CWM but as long as you're on the latest you can flash anything. Is there any reason to downgrade recoveries on the Atrix? Is there one "up to date" recovery? I see a lot of posts that point to a 2011 thread with the "latest CWM based recovery" but that seems kind of old...
Alright so I think I have this sorted out for the most part, and my understanding is that RomRacer made a version of CWM that we should be using on the Atrix. I just can't find a link to download the thing, is there a thread in development? When I search all I find is a ton of threads telling me to use it and no one linking it.
Edit: http://forum.xda-developers.com/showthread.php?t=1204500 Right?
Or is TWRP better?
http://teamw.in/project/twrp2/72
Lot of people love TWRP, but I'm one of the few that still uses RomRacers CWM 5.0.2.7 (I think) and no issues flashing CM10.1 (android 4.2.1) Had it for over a year, and works great every time. If it's not broken, don't fix it.
As for the boot loop, those are usually fixed with a wipe. Try wiping everything and restoring.
Edit: Yeah, that seems like the proper thread. Sorry, haven't looked at it since I first rooted my phone. Try TWRP, most people swear by it. The touch does add a nice feature, but I'm too lazy to make the switch.
エイトリックス から 送ります
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
You can flash to stock rom and then install CM7 :laugh:
ravilov said:
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
Click to expand...
Click to collapse
Thanks for the help, I'm glad I checked in. On the Droid X whenever anything went wrong and someone posted a thread like this the first ten replies were "Just SBF" - that used to be safe, until they rolled out .621, but that was end-of-life anyway.
I digress; next time I see him we'll iron this out and he'll be off to the races. Thanks again.