Custom roms - no mobile network - Xperia Play Q&A, Help & Troubleshooting

Hi,
I cant get any mobile network on any custom rom. It does work on the ICS beta but its not a great rom imo. I have flashed jellybean, xpress ics rom, dark ics rom, and ICS 4.04 all from Shadowsnipers tutorials on youtube. Roms work perfect but never any signal - im with Meteor in Ireland. I tinker with the settings GSM only etc or wcdma or both but I get error when looking for mobile networks. Another problem I have is any custom kernel I use to flash a rom ( Lupus, Doomlord ). It installs the rom, but instead of rebooting, It always boots into recovery. The only way I can install a rom is by using the boot.img that came with the stock beta gapps addon on ics beta. When the rom is flashed, I have to flash boot.img again without recovery ( from stock ics beta )...then the rom loads perfect apart from the NETWORK...Main problems is why cant my device reboot normally in the first place after i install a zip from sd card through lupus/doomlord/cwm auto. I have followed the instructions 100%. wipe cache , dalvic, system restore and advanced settings - but no change..would that be the cause.??... looks like stuck on stock 2.3.4 ...

tommyforest123 said:
Hi,
I cant get any mobile network on any custom rom. It does work on the ICS beta but its not a great rom imo. I have flashed jellybean, xpress ics rom, dark ics rom, and ICS 4.04 all from Shadowsnipers tutorials on youtube. Roms work perfect but never any signal - im with Meteor in Ireland. I tinker with the settings GSM only etc or wcdma or both but I get error when looking for mobile networks. Another problem I have is any custom kernel I use to flash a rom ( Lupus, Doomlord ). It installs the rom, but instead of rebooting, It always boots into recovery. The only way I can install a rom is by using the boot.img that came with the stock beta gapps addon on ics beta. When the rom is flashed, I have to flash boot.img again without recovery ( from stock ics beta )...then the rom loads perfect apart from the NETWORK...Main problems is why cant my device reboot normally in the first place after i install a zip from sd card through lupus/doomlord/cwm auto. I have followed the instructions 100%. wipe cache , dalvic, system restore and advanced settings - but no change..would that be the cause.??... looks like stuck on stock 2.3.4 ...
Click to expand...
Click to collapse
Im on the same network with no problems. What kernel of mine are you using (gb, gb/ics, ics beta, or jb) Did u flash the recommended ftf. Try wipe all partitions in cwm → advanced→ mounts.. then format system and do your wipes. or
sudo fastboot erase userdata && sudo fastboot erase system then wipe you caches and flash ROM.

Related

[Q] Cannot install Miui port.

http://forum.xda-developers.com/showthread.php?t=1719746
Original Thread.
For those that want information I've a GSM model and I flashed this upon
.58 Enhanced v2
-Firstly Flash DooMLoRDs ICS Beta Kernel via fastboot OK!
-Boot the phone into recovery OK!
-Perform a Factory Reset OK!
-Wipe cache and dalvik-cache OK!
-Flash the Zip from SD Card in recovery OK
-REBOOT and Enjoy! - Stuck On Kernel Screen / DoomLord Kernel ICS Beta
I'm unsure what to do, all the other roms seem to work well for me.
This rom is built based on KA14 Test Play which does not work for me either, and Cyanogen 9 RC2 is sluggish at games at least for me.
Cyanogen 7 is slow on the menu and all apps always stay in memory.
I just want to add this rom to my collection I.E I make a backup of each Rom and Kernel so I can switch without using a laptop.
sewer56lol said:
http://forum.xda-developers.com/showthread.php?t=1719746
Original Thread.
For those that want information I've a GSM model and I flashed this upon
.58 Enhanced v2
-Firstly Flash DooMLoRDs ICS Beta Kernel via fastboot OK!
-Boot the phone into recovery OK!
-Perform a Factory Reset OK!
-Wipe cache and dalvik-cache OK!
-Flash the Zip from SD Card in recovery OK
-REBOOT and Enjoy! - Stuck On Kernel Screen / DoomLord Kernel ICS Beta
I'm unsure what to do, all the other roms seem to work well for me.
This rom is built based on KA14 Test Play which does not work for me either, and Cyanogen 9 RC2 is sluggish at games at least for me.
Cyanogen 7 is slow on the menu and all apps always stay in memory.
I just want to add this rom to my collection I.E I make a backup of each Rom and Kernel so I can switch without using a laptop.
Click to expand...
Click to collapse
Hi , what was your rom before trying to install miui?
It seems so I had two recoveries at that point of which one being the leftover and which is terminated upon forst boot and one in the IcsBeta Kernel. What have I done is used the leftover CWM and that was the error. Anyway I found out this by accident when trying to enter flashmode and I didn't realise the kernel booted. I've flashed this rom using the kernel's touchscreen recovery and that worked for me. Anyway to answer your question it was 2.3.4 stock (.58) Enhanced version v2 anyway considering this is as an ICS ROM I should be able to get to it with any Gingerbread version.
Sent from my R800i using xda app-developers app and Miui v4 - Which IS installed.

[Q] About flashing ICS ROM

In the days of GB, we have to wipe cache/system/dalvik cache/etc and flash a ROM from zip, but now if we have to flash ICS ROM, I saw the instructions always require user to flash the original ICS fw by flashtool, then start flashing the custom ROM.
As what I know, after wiping all the stuff, the phone became empty and ready for new ROM. So what is the use of flashing the original fw? May someone explains because I'm facing some difficulties in flashing custom ICS ROM. I don't know the reason is I haven't flash original ICS fw first or due to other reasons...
For example, in my case after flashing custom ROM my mobile model shows Xperia Arc s instead of Xperia Arc.
But Actually i own Xperia Arc. The problem is after flashing custom ROM, some sytem information will get lost or change.
So when flashing the custom ROMs we get errors (status 7 installation aborted, etc.,).
So we are flashing the stock ROM to restore the system information and installing the Custom ROM.
Really? Never had that problem...
Sent from my LT18 using xda app-developers app
As much as I have done ROM testing, I never installed original ICS in the first place.
KartzXDA said:
So when flashing the custom ROMs we get errors (status 7 installation aborted, etc.,).
Click to expand...
Click to collapse
The error appears on ROMs, that check the phone's files first, to make sure you are installing correct ROM on correct phone (and not installing Neo ROM on Arc).
yes i also agree tried almost all ics Xperia arc roms in dev section never had problems like that . make shure you flash the rom for arc on arc and not any other make. i genrally make a cwm backup and then wipe/factory reset,clear cache and then flash the rom. you must follow the devs instruction on OP properly i mean point to point if you dont want any problems you have.
best luck modding :good:
In Custom ROM, u have to wipe things in case some files still be on system from installed ROM.
In CWM mode;
1. Wipe data/factory reset and wipe cache partition
2. format system & format data and format cache
3. wipe dalvik cache and battery stats
4. Install rom choosing SD card.
As far as i know, Xperia Arc and Xperia Arc S are quite smilar except processor. Most of the ROM's and Kernel's should be worked both.
It isn'n necessary to go in an official ICS stock ROM , you can flash new rom from another rom wich has the same build that Rom you are going to flash . However , i recommend you to flash ALWAYS original ics firmware , and follow next instructions , i promise you that you NEVER will have a bootloop . I always do on CWM : 3 wipes and format system , 0 BOOTLOOPS
Not every rom needs a fresh flash of the fw. But some roms need the fresh fw because sometimes the kernel and the build version cause issues with the new rom.
Why waste time on reinstalling ICS, if custom ROM deletes it (or whatever ROM you had earlier) automatically anyway?

[Q] Can I return to stock Koodo?

Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).
Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!

[Q] Help with installing custom rom

Hey guys,
I'm new to the Xperia Arc development and need some help with installing a custom rom. I've done quite a bit of reading but still can't figure out what is wrong and why it's simply not working.
So from what I gathered the steps to ensure a successful flash are:
Firstly flash a stock rom via flashtool ie LT18i_4.1.B.0.587.ftf
flash LT18i_4.1.A.0.562_Kernel > root the device > flash back to LT15a_4.1.B.0.587_Kernel
Then now that the device is rooted, I need to install a recovery such as CWM via RecoverX
So, so far so good as I can access CWM, stock rom works fine as well
So then next step is to unlock the bootloader
pretty sure this worked, as when i tried to unlock it again, it said it failed as it was already unlocked
Now flash a custom kernel, in this case i flashed the 146 FXP CM kernel
This also seemed successful as I was presented with a custom splash screen
So then after custom kernel is installed I enter recovery, wipe the cache and reset factory settings, format the data system and cache as well as wiping the dalvik and battery stats.
After, I installed the custom rom zip file, in this case it was aokp_anzu-ota-eng.kxp_build5 and then google apps and then reboot.
So my problems begin here.
My phone seems to be stuck in the boot process (sometimes), on the "initiating swagger" splash screen and it goes crazy. I've tried flashing this rom with other kernels (fusion 3.9) and sometimes it actually loads up into the rom. But the rom is extremely laggy, applications freeze and close and the wifi never works
So my question is, is there any steps or procedures that I am missing, not doing right or in the correct order?
I don't think it's any hardware issues as wifi works in the stock rom, and it's fairly smooth and fluid.
Also, is there a better way to flash roms so that I don't need to do this entire process of flashing a stock rom, rooting, unlocking bootloader, installing recovery every time I want to flash a new rom? And when I flash a custom kernel first, then flash a custom rom that has a kernel inbuilt (cm10) does the custom rom's kernel replace the one i just flashed, reason for asking is that the instructions say to flash the custom kernels and then the roms, but yeh just hasn't been working for me so not really sure how to do what.
I'd really appreciated any help or insight!
Thanks
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
XperienceD said:
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
Click to expand...
Click to collapse
Thanks! I've read your guide (what I based my flashing on) and it seems consistent with what I have done, on the surface of it anyway. If you think I missed or overlooked something, would it be possible to point it out?
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
XperienceD said:
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
Click to expand...
Click to collapse
As ExpirienceD says,just one more thing flash kernel modules if you need to.
So:
1.Flash kernel
2.Full wipe data/cach...etc...
3.Flash ROM
4.Flash kernel modules
Sent from my LT15i using xda premium

Xperia Play boot loops every time something is flashed via CWM

Hi, I've been having some problems with my Xperia Play getting stuck in a boot loop after flashing anything, or restoring a backup in CWM. This includes mods, like Adrenoboost, and the NXT Lockscreen, to themes. I have the Xperia Play R800x with an unlocked bootloader (via unlock code from Sony) and I'm using stock 2.3.3 Gingerbread, with the stock Kernel. I boot CWM by hotBooting LuPuS with Fastboot. I'm not really sure what to do because I really want to install these mods, and because restoring my nandroid backups also gets it stuck in a bootloop, I have to reflash the stock .ftf with FlashTool and reroot it every time.
x2110311x said:
Hi, I've been having some problems with my Xperia Play getting stuck in a boot loop after flashing anything, or restoring a backup in CWM. This includes mods, like Adrenoboost, and the NXT Lockscreen, to themes. I have the Xperia Play R800x with an unlocked bootloader (via unlock code from Sony) and I'm using stock 2.3.3 Gingerbread, with the stock Kernel. I boot CWM by hotBooting LuPuS with Fastboot. I'm not really sure what to do because I really want to install these mods, and because restoring my nandroid backups also gets it stuck in a bootloop, I have to reflash the stock .ftf with FlashTool and reroot it every time.
Click to expand...
Click to collapse
Hi. Not all mods are 100% compatible with stock ROM so you should use a custom one. Many custom ROMs are better than the stock one.
WhiteWashed said:
Hi. Not all mods are 100% compatible with stock ROM so you should use a custom one. Many custom ROMs are better than the stock one.
Click to expand...
Click to collapse
My only problem is, when I flash other ROMs they don't work, unless I also flash a custom Kernel. Anytime I flash a custom kernel, WiFi never connects, even if I flash the WiFi modules. It gets stuck at Obtaining IP Address, then stops.
x2110311x said:
My only problem is, when I flash other ROMs they don't work, unless I also flash a custom Kernel. Anytime I flash a custom kernel, WiFi never connects, even if I flash the WiFi modules. It gets stuck at Obtaining IP Address, then stops.
Click to expand...
Click to collapse
There's are some Gingerbread based roms that work also with the stock kernel and won't give you any problem with wifi (personal experience).
Try the gbx_play v3-rebuild here: http://forum.xda-developers.com/showthread.php?t=1897634
Or the Gin2kitkat here: http://forum.xda-developers.com/showthread.php?t=1631144
Try to flash one of these and let us know
Remember that before you flash a ROM you MUST make a wipe data/factory reset, wipe cache and wipe Dalvik Cache (in advanced options).
WhiteWashed said:
There's are some Gingerbread based roms that work also with the stock kernel and won't give you any problem with wifi (personal experience).
Try the gbx_play v3-rebuild here: http://forum.xda-developers.com/showthread.php?t=1897634
Or the Gin2kitkat here: http://forum.xda-developers.com/showthread.php?t=1631144
Try to flash one of these and let us know
Remember that before you flash a ROM you MUST make a wipe data/factory reset, wipe cache and wipe Dalvik Cache (in advanced options).
Click to expand...
Click to collapse
I do wipe the data and cache. I know how to install ROMs, I've done it with TWRP on my Kindle Fire, but I get stuck in a boot loop every time. I'll try these ROMs and see how they go.
WhiteWashed said:
There's are some Gingerbread based roms that work also with the stock kernel and won't give you any problem with wifi (personal experience).
Try the gbx_play v3-rebuild here: http://forum.xda-developers.com/showthread.php?t=1897634
Or the Gin2kitkat here: http://forum.xda-developers.com/showthread.php?t=1631144
Try to flash one of these and let us know
Remember that before you flash a ROM you MUST make a wipe data/factory reset, wipe cache and wipe Dalvik Cache (in advanced options).
Click to expand...
Click to collapse
I did a Factory Reset on CWM, then flashed Gin2KitKat, and wiped the cache and dalvik cache and it's stuck on the Android boot animation. It's been sitting there for like 10 minutes or so now. Flashtool does recognize it though.
Connected Device: R800
Installed version of busybox: BusyBox x1.21.1-Stericson (2013-09-26 14:33:26 BST) multi-call binary
Android Version: 2.3.7 / kernel version 2.6.32.9-perf / Build number: 4.0.2.A.0.79
Click to expand...
Click to collapse
It worked fine as soon as I hotBooted it with LuPus. I'm gonna try installing the other ROM I wanted and hotBooting LuPus
Strange, I have the opposite problem: lupus doesn't boot any ROM for me, excepting ICs ones.
In fact, to install a GB ROM I always have to flash first the stock rom and fw, and then flash the ROM with a custom recovery. Anyway by "hot booting" you mean custom recovery right?
Sent from my R800i using xda app-developers app
No, what I'm doing is using Fastboot to boot the phone with the kernel, without flashing it, to test it out. As soon as you shut the phone off, and turn it back on, it boots with whatever kernel is flashed on it
Sent from my R800x using xda app-developers app
x2110311x said:
No, what I'm doing is using Fastboot to boot the phone with the kernel, without flashing it, to test it out. As soon as you shut the phone off, and turn it back on, it boots with whatever kernel is flashed on it
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
That's what I mean with custom recovery :laugh: (don't confuse with custom kernel).
When I had stock kernel I would boot LuPuS just for CWM, but I'll hotboot kernels to see how well they run
Sent from my R800x using xda-developers app
x2110311x said:
When I had stock kernel I would boot LuPuS just for CWM, but I'll hotboot kernels to see how well they run
Sent from my R800x using xda-developers app
Click to expand...
Click to collapse
So here's what you need to do, since you want stock and and fastbootalot for recoveries y don't you download xperia play clockwork mod app? It's version 4 or something like that don't use xparts it don't work with our Verizon plays since you have root this will install recovery for you to flash Roms mods etc
I'll edit later with a link to the thread that has the clockwork mod app install that MAKE A NANDROID before you flash anything it helps worse case you hotboot lupus to restore your nandroid you have then reboot and guess what stock 2.3.3 Rom and kernel
Sent from my ADR6300 using xda app-developers app
No I got everything to work fine. I have LuPuS flashed on, and I'm using the xElite Gamer ROM with no problem.
Sent from my R800x using xda-developers app

Categories

Resources