Hi all...
I just got my first Android phone... is an X10i...
I have version 2.1-update1 on it, and i tried 2 custom roms (2.2) with the install from SDcard.
After installing first rom (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip) the result you can see it here: 220.ro/documentare/MOV01113/AVtgAccdjh/
After this, i instaled the 2nd rom (FreeX10-beta4.zip + gapps_FreeX10.zip); the result was: it work perfectly but after 30 seconds it was rebooting. it never stops.. the phone start again, and after 30 seconds , again reboot... and so on.
I must mention that the phone is SIM locked, and to work in my network i must unlock it... can this be a problem? if not can any one help me to fix this?
Or can anyone tell me where to find a custom rom that can be flashed with x10flasher? because when i install the rom from SDcard, is loading normally untill 50%, but when it reach 50%, he instantly go to 100%
Some info about my phone:
model: x10i
firmware: 2.1-update1
baseband: 2.1.54
kernel: 2.6.29
Can anyone tell me what is the problem and advice me what to do?
Thanks in advance.
SE-X10i said:
Hi all...
I just got my first Android phone... is an X10i...
I have version 2.1-update1 on it, and i tried 2 custom roms (2.2) with the install from SDcard.
After installing first rom (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip) the result you can see it here: 220.ro/documentare/MOV01113/AVtgAccdjh/
After this, i instaled the 2nd rom (FreeX10-beta4.zip + gapps_FreeX10.zip); the result was: it work perfectly but after 30 seconds it was rebooting. it never stops.. the phone start again, and after 30 seconds , again reboot... and so on.
I must mention that the phone is SIM locked, and to work in my network i must unlock it... can this be a problem? if not can any one help me to fix this?
Or can anyone tell me where to find a custom rom that can be flashed with x10flasher? because when i install the rom from SDcard, is loading normally untill 50%, but when it reach 50%, he instantly go to 100%
Some info about my phone:
model: x10i
firmware: 2.1-update1
baseband: 2.1.54
kernel: 2.6.29
Can anyone tell me what is the problem and advice me what to do?
Thanks in advance.
Click to expand...
Click to collapse
For now you can only flash stock 2.1 roms using the flashtool, everything else you have to use xrecovery.
As far as your phone being sim locked, I really don't think that's related to any of the issues you've mentioned.
Here's what I suggest:
- use the flashtool to flash it back to stock 2.1
- root
- install xrecovery
- try Wolfbreak's custom 2.2 rom from here
http://forum.xda-developers.com/showthread.php?t=945264
the instructions on the first post are kinda confusing but let me know if you have any other questions. Make sure to use the thanks button if any of this helps.
To install custom ROMs, your phone needs to be rooted and then install the ROMs via xrecovery.
Also for Trip's Froyo or Gingerbread ROM, it is preferable to on bb49..
GUIDES:
For changing BB: http://forum.xda-developers.com/showthread.php?t=960527
For Trip's 2.2 ROM: http://forum.xda-developers.com/showthread.php?t=1013210
Instruction for Flashtool : http://forum.xda-developers.com/showthread.php?t=928343
thanks to both for fast answer...
***********************************
@Lockon Stratos
this rom is working good, is only rom that installs properly and work without reboot, but SDcard is not working, and when i applyed the hotfix, it enter into a reboot loop
@regencyhood
i tried MIUI... same problem... reboot loop
***********************************
i tried again all roms that i have downloaded until now from here, but unsuccessfully
I do not understand why, but ROMs are not installed correctly (i have root and xrecovery installed, i made factory restore, wipe cache, format cache, wipe dalvik cache).
so i think i will stay on 2.1
I was very enthusiastic when i got it, but i see that is not such a great phone with no official update for 2.2, and is low on internal memory (only 465MB data memory and 280MB RAM).
SE-X10i said:
thanks to both for fast answer...
***********************************
@Lockon Stratos
this rom is working good, is only rom that installs properly and work without reboot, but SDcard is not working, and when i applyed the hotfix, it enter into a reboot loop
@regencyhood
i tried MIUI... same problem... reboot loop
***********************************
i tried again all roms that i have downloaded until now from here, but unsuccessfully
I do not understand why, but ROMs are not installed correctly (i have root and xrecovery installed, i made factory restore, wipe cache, format cache, wipe dalvik cache).
so i think i will stay on 2.1
I was very enthusiastic when i got it, but i see that is not such a great phone with no official update for 2.2, and is low on internal memory (only 465MB data memory and 280MB RAM).
Click to expand...
Click to collapse
Reason for Reboot on MIUI is because you are on baseband 54 (i.e 2.1.54)....
Recommended baseband is 49, either you flash and change your bb or you can apply a patch... all the necessary help regarding bb is given in the link in my above post...
hope i was helpful
So which one do you want to use trip's froyo or Z's froyo? I hate to say this but I have a feeling it's something you're doing in between installs that could be causing the problem. I say pick one that you want to use/test, flash back to stock 2.1 using je flashtool, root, install xrecovery then flash just one of the custom froyo roms using xrecovery.
Sent from my X10i using XDA App
Patch BB 54 or rollback BB 52
Lockon Stratos said:
So which one do you want to use trip's froyo or Z's froyo? I hate to say this but I have a feeling it's something you're doing in between installs that could be causing the problem. I say pick one that you want to use/test, flash back to stock 2.1 using je flashtool, root, install xrecovery then flash just one of the custom froyo roms using xrecovery.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
what i want is a version of froyo that look like official one...
something like the ROM from TripNRaVeR (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip)
sorry for the link from my first post... i hope this is working : youtube.com/watch?v=iV408mrlWqA
this is how is working the Rom from TripNRaVeR (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip) on my phone
edited:
regencyhood said:
Reason for Reboot on MIUI is because you are on baseband 54 (i.e 2.1.54)....
Recommended baseband is 49, either you flash and change your bb or you can apply a patch... all the necessary help regarding bb is given in the link in my above post...
hope i was helpful
Click to expand...
Click to collapse
so... if i downgrade baseband to 2.1.49, the rom from TripNRaVeR will work to?
and i want to know if appeared any fix for camera for the rom from TripNRaVeR?
so... if i downgrade baseband to 2.1.49, the rom from TripNRaVeR will work to?
and i want to know if appeared any fix for camera for the rom from TripNRaVeR?[/QUOTE]
Yes, it will work.
Regarding the camera I am using "TripNMiUI FINAL 1.0.63" ROM, and the camera is working a-OK. (Pic and Vid included)
Zoom results in FC for me in the stock and MIUI camera app, because of which I use Vignette....
Was adding another post, but thought it was not helpful..now i dont know how to delete a post
Related
Did anyone find out why we keep getting them. I know tjeres been a few threads but not an actual solution. My phone has been doing it. Since .24 update. Ony when im using.data and its in my hand.
Sent from my X10i using XDA App
Could jit have adverse effects.?
Sent from my X10i using XDA App
My X10 usually reboots when I use multiple apps(around3+).Ex.data+poweramp. I'm pretty sure it has to do with JIT. X10a 2.1.1.A.0.6 JIT V2
-PiLoT- said:
Did anyone find out why we keep getting them. I know tjeres been a few threads but not an actual solution. My phone has been doing it. Since .24 update. Ony when im using.data and its in my hand.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
which rom are u using?
i am guessing se stock 2.1? which baseband?
http://forum.xda-developers.com/showthread.php?t=920746
Bottom of the first post:
IMPORTANT:
- You should always wipe userdata if you switch between Android versions (1.6 <-> 2.1). If not your phone will keep restarting all the time. This is the same for some providerbrandings even if you flash between same Android versions. So if you have this restarting problem, flash again with Wipe Userdata. If you don't want to loose your apps you have to backup them with Titanium or some other backup tool!
Regards
Androxyde
Yeah that what i did. i never wiped userdata when i first used flash tool 1.6 branded orange uk -> 2.1 Global Generic
for some reason though the restarts have got worse as of late.
one thing though its been a while since i used flash-tool is the option to wipe user-data there? i know its in xrecovery
and if b wipe user data you mean like a master reset didn't everyone do this when they went to 2.1
Yeah, it's in the latest flash tool. When I first flashed from 1.6 to 2.1 Nordic, my phone would randomly freeze and then reboot. It was really annoying. However, when I upgraded to the newest 2.1 firmware(s) using the new flash tools it doesn't happen to me anymore. I guess it could be considered a master wipe, but I never factory reset my phone before doing it. Flash to the newest firmware and see if it fixes the problem.
Good Luck!
well after reflashing and doing everything by the book its still doing it so im getting another one
I don`t complete get it but i guess you`re on 2.1. Right?
I found that`s really strange.
I switch frequently to/from and vice-versa between 2.1/2.2/2.3x and between different basebands and never had any issue (apart when all this rom thing started a few months ago, cause they`re all instable at the time).
Try with latest flashtool available if you didn`t already.
Check on flashtool thread or on my how-to for firmwares.
Like i said. There`s no reason for that happen and even less if we`re talking of SE ones.
rendeiro2005 said:
I don`t complete get it but i guess you`re on 2.1. Right?
I found that`s really strange.
I switch frequently to/from and vice-versa between 2.1/2.2/2.3x and between different basebands and never had any issue (apart when all this rom thing started a few months ago, cause they`re all instable at the time).
Try with latest flashtool available if you didn`t already.
Check on flashtool thread or on my how-to for firmwares.
Like i said. There`s no reason for that happen and even less if we`re talking of SE ones.
Click to expand...
Click to collapse
Yeah i am on 2.1 latest 435 i reflashed phne while wiping userdata and when i set it all back up it started random rebooting again going as far as doing it while i was texting which was a first
im assuming the phone overheated
Pilot, I believe there was some mention awhile back, possible short / connection problem on sum of the boards, my first x10 battery would heat up and restart over n over.. swapped it at at&t and the new one has worked perfectly for 4 months n 7 diffrent roms!!
Sent from my X10i TripNMiUI using XDA App
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I have a bell Galaxy S2. Today I rooted it and after hours of confusion, I finally managed to install resurrection remix 4.04 ICS on my phone.
So far I've run into tons of issues:
1) No GPS
2) No wifi (stuck on 'obtaining IP address, unlikely that this is my network's fault)
3) No software buttons, so I can't multitask (have to use task killer to kill unused apps right now)
4) Rom Control crashes everytime I go into the Navigation bar page
The phone in it's current state is useable, but I will go back to stock settings if I can't fix these problems. Maybe there is a better ROM out there? Though I heard resurrection remix is the best one. Also, could it be that I installed the wrong kernel? The one I installed is:
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Can somebody help me out? Any tips would be appreciated.
EDIT: I just realized that USB connectivity (file transfer) doesn't work either - not even in clockwork menu!
anthraxcp said:
I have a bell Galaxy S2. Today I rooted it and after hours of confusion, I finally managed to install resurrection remix 4.04 ICS on my phone.
So far I've run into tons of issues:
1) No GPS
2) No wifi (stuck on 'obtaining IP address, unlikely that this is my network's fault)
3) No software buttons, so I can't multitask (have to use task killer to kill unused apps right now)
4) Rom Control crashes everytime I go into the Navigation bar page
The phone in it's current state is useable, but I will go back to stock settings if I can't fix these problems. Maybe there is a better ROM out there? Though I heard resurrection remix is the best one. Also, could it be that I installed the wrong kernel? The one I installed is:
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Can somebody help me out? Any tips would be appreciated.
EDIT: I just realized that USB connectivity (file transfer) doesn't work either - not even in clockwork menu!
Click to expand...
Click to collapse
Sounds like you might have flashed the wrong kernel for your phone.
did you first check what was the original kernel on your phone? acutally, run me through your root process so i can figure where you went wrong, because the Resurrection remix rom is just about perfect
I know it was KG2 kernel originally. Don't remember the other numbers.
I'm now on a different kernel because when I used KG2, the phone wouldn't work at all (the buttons were screwy).
The process went something like this:
1. Rooted KG2 kernel installed
>Phone still works like before, but rooted
2. Put Res remix rom on my phone's storage
3. Go into clockwork recovery
4. Flash/Recovery
Format /system
Wipe Cache
5. Install ROM from SD card - twice (since the video I was watching told me to do it twice)
>Phone turns on but the buttons don't work so I can't navigate menus
6. Install CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
>Buttons sort of work now but lots of problems
>All of my old files/music are still on the phone despite all that format/recovery stuff. Is that normal?
Now when I try to install KG2 kernel phone doesn't even turn on. If it helps, the phone currently tells me the baseband is I9100MUGKG2
k, yep you missed the gapps install. did you make a backup in CMW recovery before you flashed remix?
Mv101 said:
k, yep you missed the gapps install. did you make a backup in CMW recovery before you flashed remix?
Click to expand...
Click to collapse
*lowers head in shame*
Nope. But if I understand correctly gapps is just the google stuff (maps, gmail, etc) but that all works fine for me.
anthraxcp said:
5. Install ROM from SD card - twice (since the video I was watching told me to do it twice)
>Phone turns on but the buttons don't work so I can't navigate menus
6. Install CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
......
Now when I try to install KG2 kernel phone doesn't even turn on. If it helps, the phone currently tells me the baseband is I9100MUGKG2
Click to expand...
Click to collapse
whats wrong with you brother? installing CF-root on an AOKP rom???? CF-root is matched with the Kernel not with the Baseband.
Yourself dont know what is being flased on what.....did you make sure of your model before flashing there are many S2s I9100 /I9100G / I9100M / 9100T many more...
please read all the instrction first before attempting anything my friend...There is no substitute for reading and learning for comprehension .it is not like that any thing can be applied on anything.
I have a bell s2 and i did this
Google: how to root galaxy s2 kg2. Use the one that comes up. Will show the right cf root.tar to flash through odin
Follow these steps to the T
http://androidforums.com/galaxy-s2-...ock-root-bell-galaxy-s2-step-step-guide.html
Sent from my GT-I9100 using XDA
ooh you messed up real good! think you need to flash the insecure kg2 kernel through odin again
ZACQ8 said:
whats wrong with you brother? installing CF-root on an AOKP rom???? CF-root is matched with the Kernel not with the Baseband.
Yourself dont know what is being flased on what.....did you make sure of your model before flashing there are many S2s I9100 /I9100G / I9100M / 9100T many more...
please read all the instrction first before attempting anything my friend...There is no substitute for reading and learning for comprehension .it is not like that any thing can be applied on anything.
Click to expand...
Click to collapse
It's the I9100M (bell) and the Kernel before I started was KG2. I already mentioned this.
@kilometers4 that's the exact kernel I tried the first time (from that tutorial) but it didn't work.
anthraxcp said:
It's the I9100M (bell) and the Kernel before I started was KG2. I already mentioned this.
@kilometers4 that's the exact kernel I tried the first time (from that tutorial) but it didn't work.
Click to expand...
Click to collapse
yes it was before, but when you flashed Reserection Remix you got Cyanogenmod Kernel...
ZACQ8 said:
yes it was before, but when you flashed Reserection Remix you got Cyanogenmod Kernel...
Click to expand...
Click to collapse
Ok, some good news.
I installed the CF-ROOT KG2 kernel.
I went into recovery, formatted/wiped everything that needs to be done. (Then USB connectivity began to work!) so I put a 2.3 Cyanogen Mod on there and now everything seems to work (USB, WIFI) except for the home button. I still can't exit out of applications.
anthraxcp said:
Ok, some good news.
I installed the CF-ROOT KG2 kernel.
I went into recovery, formatted/wiped everything that needs to be done. (Then USB connectivity began to work!) so I put a 2.3 Cyanogen Mod on there and now everything seems to work (USB, WIFI) except for the home button. I still can't exit out of applications.
Click to expand...
Click to collapse
I dont understand what are you doing, it is your phone and up to you...do any experiments you want...
but dont ask for support when you get into deep treble with your stupidity doing without reading and knowing.
CF-root will not work with AOKP roms.
ZACQ8 said:
I dont understand what are you doing, it is your phone and up to you...do any experiments you want...
but dont ask for support when you get into deep treble with your stupidity doing without reading and knowing.
CF-root will not work with AOKP roms.
Click to expand...
Click to collapse
Yes but I can't find any other rooted kernels out there that will work for my phone. I've googled it but all the GS2 rood/mod tutorials I've seen use CF-Root.
If you can let me know what kernel or rom to install that would be great. I'm not going to touch my phone until I figure out what to do.
anthraxcp said:
Yes but I can't find any other rooted kernels out there that will work for my phone. I've googled it but all the GS2 rood/mod tutorials I've seen use CF-Root.
If you can let me know what kernel or rom to install that would be great. I'm not going to touch my phone until I figure out what to do.
Click to expand...
Click to collapse
Why not start with a working phone + a nandroid backup before you start playing with roms .
Stock rom + CWM and root kernel = Nandroid backup .
If CM does not work then read the CM thread faqs and instructions .
jje
first of all get into reserection remix thread and ask whether this ROM supported for I9100M or not, if yes ask somebody can provide CWM flashable CM9 kernel (if it is the original kernel of your rom) then flash from CWM and try..
ZACQ8 said:
first of all get into reserection remix thread and ask whether this ROM supported for I9100M or not, if yes ask somebody can provide CWM flashable CM9 kernel (if it is the original kernel of your rom) then flash from CWM and try..
Click to expand...
Click to collapse
It does work with 9100M.. I have the same phone and am running v1.4 flawlessly
Sent from my GT-I9100 using XDA
I was previously using MIUI latest ROM and NightElf kernel for stock (my mistake). Due to instability and lag I wanted to move to CM9. So today I downloaded mt11i BB72, NightElf kernel for fxp and latest (126) fxp ROM. First I installed the BB using flashtool, then installed the kernel using fastboot and at last installed the ROM via CWM. But after that I am unable to boot into OS. I can boot into recovery, but not into OS. The phone just reboots.
As recovery still loads, I think the device is not yet lost. Will anyone help me out please?
Flash the original .431 ftf using flashtool,then install new kernel and after that flash the CM9 rom.
It was, just that I was searching a shorter route. But it seems that the long way is to go. I am not even sure if Sony has released 4.0.4 with new baseband for my handset in India.
Another thing: did you wiped cache and dalvik cache? If no,wipe them and make a factory reset from cwm.
sbcontt said:
It was, just that I was searching a shorter route. But it seems that the long way is to go. I am not even sure if Sony has released 4.0.4 with new baseband for my handset in India.
Click to expand...
Click to collapse
About India 4.0.4: http://forum.xda-developers.com/showpost.php?p=27269800&postcount=231
And about your problem in OP, if by "NightElf kernel for fxp" you mean on this: http://forum.xda-developers.com/showthread.php?t=1468043 you are using kernel for GB.
yes I have done all the wiping and resetting. I remembered that I had not mentioned those in the post after I had hit the post button.
Madfysh yes I was using that one. So, is that the error that is causing this bootloop? Can you provide link of a proper kernel for me?
This one?
OK solved
I installed the proper kernel and now device boots into OS. Thank you Madfysh for pointing out the error.
CM9 is so smooth!
Update: And now wifi does not work!
They just keep telling me to flash kernel in instructions [- new wifi init (if you dont flash kernel and wipe wifi will not work properly)], but sorry to be a noob: which kernel?
Found kernel: inside ROM zip. LoL. Madfysh you knew that?
Much ado about nothing. I kept weaving a tale of wrong kernels when the proper one was always there hiding inside the zip.
I recently picked up an Xperia X10 to use with my straight talk service. I rooted and unlocked the bootloader just fine using flashtool; edited the APN settings and have a functional phone. But, whenever I try flashing a new ROM, I get into some trouble. First, my wifi never works. I read that's a common thing and tried flashing the zip to fix it; no go. Secondly, I lose service with the new ROM; again, common thing, and I've found fixes. I'd try the kill services command through terminal emulator, but that brings me to my third issue. I lose access to my SD Card; it won't mount it at all with the new ROM, except for when I'm in xRecovery. I have an Xperia X10a from AT&T, running official Android 2.1. Firmware is 2.1.A.0.492 and baseband 2.1.65. I've tried various ROMs that are compatible with this baseband, including FreeXperia from Achotjan; all with the same results. Is it necessary to flash your baseband even if the ROM is verified for your current baseband? Am I missing some critical step here? Sorry if this is in the FAQs somewhere; I've read the stickies in here and the development section 3 or 4 times each (I get bored at work ), and didn't see it anywhere. TIA
RadRacer said:
I recently picked up an Xperia X10 to use with my straight talk service. I rooted and unlocked the bootloader just fine using flashtool; edited the APN settings and have a functional phone. But, whenever I try flashing a new ROM, I get into some trouble. First, my wifi never works. I read that's a common thing and tried flashing the zip to fix it; no go. Secondly, I lose service with the new ROM; again, common thing, and I've found fixes. I'd try the kill services command through terminal emulator, but that brings me to my third issue. I lose access to my SD Card; it won't mount it at all with the new ROM, except for when I'm in xRecovery. I have an Xperia X10a from AT&T, running official Android 2.1. Firmware is 2.1.A.0.492 and baseband 2.1.65. I've tried various ROMs that are compatible with this baseband, including FreeXperia from Achotjan; all with the same results. Is it necessary to flash your baseband even if the ROM is verified for your current baseband? Am I missing some critical step here? Sorry if this is in the FAQs somewhere; I've read the stickies in here and the development section 3 or 4 times each (I get bored at work ), and didn't see it anywhere. TIA
Click to expand...
Click to collapse
I would suggest you upgrading 2.3.3.
You can find ftf files for 2.3.3 in my signature. unzip the files to get ftf.
You can flash american generic or global generic version. All will work for you.
flash the ftf using flashtool.
Here's a guide to use flashtool : http://forum.xda-developers.com/showthread.php?t=928343
RadRacer said:
I recently picked up an Xperia X10 to use with my straight talk service. I rooted and unlocked the bootloader just fine using flashtool; edited the APN settings and have a functional phone. But, whenever I try flashing a new ROM, I get into some trouble. First, my wifi never works. I read that's a common thing and tried flashing the zip to fix it; no go. Secondly, I lose service with the new ROM; again, common thing, and I've found fixes. I'd try the kill services command through terminal emulator, but that brings me to my third issue. I lose access to my SD Card; it won't mount it at all with the new ROM, except for when I'm in xRecovery. I have an Xperia X10a from AT&T, running official Android 2.1. Firmware is 2.1.A.0.492 and baseband 2.1.65. I've tried various ROMs that are compatible with this baseband, including FreeXperia from Achotjan; all with the same results. Is it necessary to flash your baseband even if the ROM is verified for your current baseband? Am I missing some critical step here? Sorry if this is in the FAQs somewhere; I've read the stickies in here and the development section 3 or 4 times each (I get bored at work ), and didn't see it anywhere. TIA
Click to expand...
Click to collapse
Download SEUS and upgrade your phone to stock gingerbread2.3.. it has the baseband required... then use flashtool to root and unlock....
Remember every custom ROM has different kernel... for example FDP ROMs run on FDP kernel.. x10s runs on doomlords modified kernel... feralab kernel is for feralab ROMs.. so you need to be careful.. good luck...
Sent from my Transformer TF101 using xda app-developers app
OK, I flashed the American gingerbread ftf. Everything appears to work except my SD card. I tried mounting through terminal, tries formatting from both the phone (xRecovery) and computer (USB adapter) and nothing. Suggestions?
RadRacer said:
OK, I flashed the American gingerbread ftf. Everything appears to work except my SD card. I tried mounting through terminal, tries formatting from both the phone (xRecovery) and computer (USB adapter) and nothing. Suggestions?
Click to expand...
Click to collapse
did you try another sd card?
does usb tranfer work by connecting to pc?
THeLogiC said:
did you try another sd card?
does usb tranfer work by connecting to pc?
Click to expand...
Click to collapse
Don't have another SD card, but it did this before. Once I restore to 2.1 it works fine. It does USB mode through xRecovery, haven't tried while Android is running.
RadRacer said:
Don't have another SD card, but it did this before. Once I restore to 2.1 it works fine. It does USB mode through xRecovery, haven't tried while Android is running.
Click to expand...
Click to collapse
thats strange. if it works in 2.1 it should in 2.3.3 too
RadRacer said:
Don't have another SD card, but it did this before. Once I restore to 2.1 it works fine. It does USB mode through xRecovery, haven't tried while Android is running.
Click to expand...
Click to collapse
I had the same issue when I upgraded to 2.3.3 from 2.1 I had to buy new SD card... but my old one worked just fine with other.. sometimes these things happen..
Sent from my Transformer TF101 using xda app-developers app
Reformatted again and now it works:good:
RadRacer said:
Reformatted again and now it works:good:
Click to expand...
Click to collapse
glad to hear that