Database Info

CM9 can't get past welcome screen

Hello,
I appreciate everyone here is from quite a technical background. I'm quite a noob with these things but hopefully this isn't a massive issue.
I have a HTC sensation (I'm in the uk) and I have been using cm7 for many months. I've just decided to download cm9 and install and everything was going smoothly until I get to the welcome screen.
I try to change English (USA) to English (uk) but this freezes the phone and makes it reboot. I go through this motion over and over again. Any ideas please?
When I updated to cm9, I assumed my phone was already s-off (to be honest I still don't know what this means but thought I did it when I installed cm7) so all I did this time was download cm9 and gapps to the root folder of the SD card. Then I opened rom manager, flashed clockwork recovery and went into recovery mode. I then wiped the data on the phone, wiped the cache, installed cm9 and then gapps and now I'm here!
Any ideas anyone? Many thanks in advance.

Repoman123 said:
Hello,
I appreciate everyone here is from quite a technical background. I'm quite a noob with these things but hopefully this isn't a massive issue.
I have a HTC sensation (I'm in the uk) and I have been using cm7 for many months. I've just decided to download cm9 and install and everything was going smoothly until I get to the welcome screen.
I try to change English (USA) to English (uk) but this freezes the phone and makes it reboot. I go through this motion over and over again. Any ideas please?
When I updated to cm9, I assumed my phone was already s-off (to be honest I still don't know what this means but thought I did it when I installed cm7) so all I did this time was download cm9 and gapps to the root folder of the SD card. Then I opened rom manager, flashed clockwork recovery and went into recovery mode. I then wiped the data on the phone, wiped the cache, installed cm9 and then gapps and now I'm here!
Any ideas anyone? Many thanks in advance.
Click to expand...
Click to collapse
Hi,
Once you are s-off,you do not lose it,unless you manually switch it on in fastboot.
Did you update your firmware before installing the new ROM?

malybru said:
Hi,
Once you are s-off,you do not lose it,unless you manually switch it on in fastboot.
Did you update your firmware before installing the new ROM?
Click to expand...
Click to collapse
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)

Repoman123 said:
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Click to expand...
Click to collapse
Hi,
The best guide on firmware update is HERE
Substitute ARHD for CM9.

Repoman123 said:
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Click to expand...
Click to collapse
The post above mine links to the best guide to get CM9 booting.
But in the mean time if you don't have the time to figure all that out (it's not hard, but it can take a little while your first time because you'll be extra careful and read all the instructions 100 times before each step) you can revert back to a Gingerbread ROM. I assume that's where you started, so if you have the Gingerbread firmware you can boo any Gingerbread ROM. That will only take about 5 minutes. So if you're in a rush to get a working phone right now just do that and it'll boot right up.

haha yes i read the instructions several times, although it's quite clear, to a newbie it's still very complicated! managed to get through it though and in hindsight that thread is pure awesomeness.
managed to get cm9 working now so will spend some time messing around with it.
thank you for all of your help.
ps. yes i began using gingerbread (stock) but i didn't have a ROM to hand and I wasn't sure if I can just download and install any rom (stock or not) willy nilly without having to do several different things to my phone so i just tried to get cm9 sorted. hopefully won't have to update rom now for some time.
thanks again!!

Interesting 1st attempt

Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.

uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium

good flashing

uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"

[Q] Error mounting sd card in CWM

Okay so I've been all over this site and linked to many other articles to proceed and hope to fix my issue but nothing seems to be working for me. To get you guys up to speed it's a SGH-T959V and I started out with having jelly bean 4.0 on it then upgraded to 4.2.2 which I occurred an issue with that and had to revert to getting gingerbread flashed back on. It's been a little while since I've done so and kinda forgot how I did it. I've read about using odin and heimdall but no luck getting my phone to connect with either of those programs.
Recently upgraded to 4.4.2 slimkat which was working good (still some bugs, since it's weekly) and had TWRP recovery on it. Problem started as I was starting the process to flash the new update of 4.4.2 and I created a back up and recovery for it prior to flash but now its gone. During the flash of the new update it had occurred some error and now went to Semaphore CWM Recovery v6.0.4.5 and has a bunch of errors to it and I cant even format or mount an sd card. I've tried using a couple different sd cards same issues. I can boot into download mode no issues.
Anyone be able to help me out? I am pretty stumped on this one and have tried many things to get it to work. Also are there any programs I could use besides odin and heimdall to flash a different version of CWM or TWRP via usb?
Thanks guys let me know if I left anything out or if you have questions to help me out better.

Hey guys, here are a couple of pictures of what it looks like while in CWM and what its saying.

Hey guys never mind, I already figured out what I was doing wrong. All I needed to do what open a file I downloaded in this thread to get it back to stock gingerbread. Now I am going to do some more flashing to get it back to 4.4.2 slimkat. Thanks

[Q] Phone Randomly Reboots Itself?!

So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!

Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide

joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!

Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).

5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help

Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.

joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!

Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.

How to back to stock ICS 4.0.4 from OMNIROM 4.4.4 bigpart?

Hi all,
I am using OMNIROM 4.4.4 bigpart in my old EU Wingray XOOM 32GB but I have lots of performance and stability issues (browser crashes, apps freezing, very slow system....). After reinstalling it I still have problems and I want to check if it's due to the device itself...
To test that, I would like to go back to the stock Android 4.0.4 ICS that I was using in my European xoom before the jump to EOS, CM and OMNI.
Could anybody help me on how to go back to stock? Where to download the stock rom? how to remove bigpart? Is it really required to remove bigpart to install the stock rom?
Thanks for any help given.

The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.

valent|n0 said:
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
Click to expand...
Click to collapse
Thanks a lot for answering.
So... I have to download the original Honeycomb software, "reflash it" and update until I get 4.0.4 or 4.1.2 ...
My doubt is ... do I have to "undo" the "bigpart"? Or will the stock firmware install perfectly in my "bigpart" xoom?
Thanks!

the bigpart issue I am not to sure of

Of course you need to undo BigPart. It's well document in Xoom Android development section of this forum.
You need to flash the non-big-part TWRP (2.8.0 or other), wipe everything, reboot intot TWRP, format Data, wipe everything again, reboot into TWRP again. Then you can flash original image using fastboot.

Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)

machina77 said:
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
Click to expand...
Click to collapse
... Sorry

jkd said:
... Sorry
Click to expand...
Click to collapse
Eh?

I didn't find anything in forum, could somebody help me how can i go back from bigpart to stock partition?

I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.

nomadman said:
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
Click to expand...
Click to collapse
I just flashed mine from omni bigpart back to stock 3.1 cause my 1yr old daughter can't keep her hands off my phone...was time consuming researching how to do it. But it works perfectly...I wound up running some script somebody wrote and it pretty much did everything for me... not in front of my PC at the moment but if you are still fighting it PM me and I'll give ya everything you need...