Related
Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
As the title states, is there a way to flash a new rom without being tied down to a PC / laptop?
Bootloader's unlocked, rooted, it's strange how with this phone we're forced to stay locked down to a PC.
Have never flashed anything from the Original Dev section on this phone yet, would that be the same method as normal rom's like monx's and IHackers?
Cheers.
huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.
tomascus said:
huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.
Click to expand...
Click to collapse
FTF's are not just for returning to stock, not at all, they're used to flash rom's too as the kernel and baseband needs to be flashed also.
Check out monx's thread, the instructions for install states to flash the rom and then without allowing a reboot, flash kernel and system (afaik)
Simply flashing the rom wouldn't be enough without flashing those files via flashtool.
What i'm trying to ascertain is do I have to do this every time as it's a pain in the backside.
Quote from Monx
LOCKED & UNLOCKED BOOTLOADER
BACKUP any critical data to microSD
Copy this rom zip package to microSD
Reboot in recovery, (do nandroid backup), do factory reset & install rom until finish
IGNORE RECOVERY INSTALLATION WARNING. SELECT NO & PROCEED AT THE END OF RECOVERY IF USING CWM RECOVERY
Skip (x) steps if u already running same base firmware with latest monxDIFIED base rom. Else, proceed.
(x) Turn off device. (Hold power button + vol up until vibrates 3 times) [or use recovery turn off device option, if any]
(x) Flash latest Sony's firmware (FTF) matching current latest monxDIFIED base rom using latest flashtools. UNCKECK all WIPE options and CHECK only SYSTEM & TA in EXCLUDE options.
(x) Disconnect USB cable & turn on phone. Done.
Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk
tomascus said:
Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.
dladz said:
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.
Click to expand...
Click to collapse
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.
tomascus said:
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.
Click to expand...
Click to collapse
Nice one m8, that's put an end to my misery, cheers for that, makes a lot of sense now, i wasn't aware of how Sony rom's were flashed, it's strange as the bootloader is unlocked? What more is needed lol.
As for the one x, that's the only HTC i skipped and glad i did apparently they had a lot of problems with flashing and stuff, S-OFF.
Anyway, thanks m8.
So toady, I tried to install Cyanogenmod 11 on my Xperia SP, model C5036.
The install worked, but now my phone is missing the IMEI and can't activate Wi-Fi.
I would try to factory reset inside of my recovery, but when I try to enter it (camera button on boot), the phone boots normally and the LED on the bottom flashes red.
Some more info:
-Phone was rooted with Towel Root
-Bootloader is locked
-Phone is locked to Bell Canada, if that helps
-I, as an idiot forgot to wipe factory data and clear cache.
-Phone was previously running Sony 4.3
-The phone now lists the model number as C5303
-Cyanogenmod version: 11-20140528-UNOFFICIAL-huashan
ROM used: http://forum.xda-developers.com/showthread.php?t=2735975&page=51
If you need any more information, I will tell you.
Enter recovery with vol up/down (philz/cwm) buttons.
Missing imei is probably related to the recovery used. Try re-flashing the ROM via cwm, after data/cache/dalvik wipe.
FYI, Newer version of cm11-LBL is available.
mrhnet said:
Enter recovery with vol up/down (philz/cwm) buttons.
Missing imei is probably related to the recovery used. Try re-flashing the ROM via cwm, after data/cache/dalvik wipe.
FYI, Newer version of cm11-LBL is available.
Click to expand...
Click to collapse
I was able to flash the newer version through CWM and now the IMEI is back and my SIM works. The only thing that isn't working now is the Wi-FI; it won't switch on at all. So the only thing I still need help with is the Wi-Fi.
Probably the WiFi module not loading. Have you flashed the .205 kernel? Your model is c5306 and the kernel posted in the OP (of cm 11 thread) is for c5303. I don't know whether flashing that on your phone would be alright (or have you already flashed it?). I don't think it would cause problems...
In any case, try these in a terminal emulator to see whether wifi modules load..
Code:
su
modprobe wlan
Any error? If nothing, run "lsmod" (without quotes) to see which kernel modules are loaded.
mrhnet said:
Probably the WiFi module not loading. Have you flashed the .205 kernel? Your model is c5306 and the kernel posted in the OP (of cm 11 thread) is for c5303. I don't know whether flashing that on your ph[one would be alright (or have you already flashed it?). I don't think it would cause problems...
In any case, try these in a terminal emulator to see whether wifi modules load..
Code:
su
modprobe wlan
Any error? If nothing, run "lsmod" (without quotes) to see which kernel modules are loaded.
Click to expand...
Click to collapse
No, I haven't flashed it yet..
In Terminal Emulator doing the modprobe command gave me this:
Code:
modprobe: 'wlan.ko': unknown symbol in module or invalid parameter
[Code]
After doing lsmod, I get this:
[Code]
cpufreq_wheatley 7320 0 - Live 0x00000000
cpufreq_lionheart 57110 - Live 0x00000000
texfat 124855 0 - Live 0x00000000 (PO)
cfg80211 135928 - Lie 0x00000000
[Code]
I also used "svc wifi enable" but it just said "Killed" after.
Am I supposed to get these?
Looks like wlan.ko is not loading (??symbol mismatch..). The solution I can think of is to flash the given .205 kernel and hope it works!
So I flashed the .205 kernel in Androxyde's flash tool. When I booted up the phone, the phone turned off twice at the boot animation, but I don't think that did anything, as it still works.
The Wi-Fi now says "Turning Wi-Fi on..." but it just stays like that. I also noticed that running lsmod (su command does nothing) it says "cfg80211 135928 1 wlan, Live 0x00000000" instead of "cfg80211 135928 - Live 0x00000000" and new string "wlan 2702117 0 - Live 0x00000000 (0)".
Also, the IMEI is gone again, even after reflashing CM through cwm multiple times.
Should I just use a different ROM other than CM11?
Wlan.ko seems to load with .205 kernel. For the missing imei, the possible "solutions" mentioned by users in other threads are..
* Flashing ROM with a different recovery (TWRP seems to have the least imei problems).
* Do a backup in cwm and restore it (weird of course) - it also fixed Wi-Fi problems for some.
For some people, this imei missing thing is random! If nothing works, may try a different ROM. Maybe can flash/restore a stock based rom to get TWRP recovery, and then flash cm11-LBL via TWRP.
I restored my phone back to Sony 4.3 and re-installed CM11. Wi-Fi now works but no IMEI still.
I also can't access TWRP after installing cm11-LBL; only PhilZ and CWM are accessible. This has happened both times installing it.
Do you have any ROMs that you can recommend to me in case we can't fix this? The reason why I wanted to update to CM11 was because Sony's 4.3 had far too many bugs and lagged too much.
Cm11-lbl doesn't have TWRP. I meant, to use TWRP to flash while on a stock based ROM. Anyway, I'm now using PA rom for LBL : http://forum.xda-developers.com/showthread.php?t=2789320
It's a very nice ROM.
Need to flash it (build #3) via cwm. If no imei, making a cwm backup and restoring it is the working solution.
I flashed PA build #4 in TWRP and IMEI and baseband is still missing like in CM11. I did the backup and restore fix in CWM but it's still missing.
IMEI and baseband does show up normally in Sony 4.3, just not custom roms.
So, I have tried SlimKat, CM11-LBL and PA build #4. All show missing IMEI and basebands.
Strange! Imei missing issue is fixed in build 4. Only old cwm is not compatible. One issue mentioned about TWRP is that, doing a /system format manually before flashing creates problems.
I suggest to go through PA OP carefully and flash build 4 with newest recoveries (Philz confirmed working). Should work!
I already have flashed the newest version of dssmex's recoveries before flashing build 4.
So, this is what I did:
1. Factory reset to 4.3 through Flashtool
2. Re-root with Towelroot
3. Install newest recoveries by dssmex
4. Enter TWRP, factory reset, clear dalvik and cache and flash PA/4.4 ROM and then GApps
5. Power off, enter flashmode (green LED) and flash .205 kernel with Flashtool
6. Reboot, and 4.4 ROM boots up normally with Wi-Fi working, IMEI and baseband missing.
Is there anything that I'm doing wrong?
Steps are correct. Try flashing build #4 with Philz. Many have confirmed it's working with Philz (checkout the responses in PA thread). If still not working, I don't know what's going on .
Edit: just thinking.. whether c5303 kernel is causing an issue on your c5306 phone?? (You got your imei once but Wi-Fi modules didn't load while on stock 4.3 (c5306) kernel + cm-11 ROM no?). Can test this by flashing the given c5303_205 stock kernel (which is meant for cm-11/PA) while on your imei working 4.3 (c5306_205) stock ROM. If imei issue crops up, then we know it's the cause.
OR if you're now on PA/Slim/cm-11-lbl (and no imei), other thing you can do to test is flash a c5306_205 stock kernel while on that custom ROM. If imei appears, it's clear that the different kernel is causing the issue (but, expect Wi-Fi modules not to load!)
*Hope I'm not confusing you.. if you're not fed-up of this issue yet ()and interested on testing things, just save all the .ko files found in /system/lib/modules of your working stock 4.3 ROM to somewhere (sdcard), so can try those later with c5306 kernel + custom ROM. (But I have no idea whether it will work).
But first thing is to make sure that flashing PA build #4 with Philz doesn't solve the issue
@others
Any idea why this strange imei issue??
Yeah, flashing with PhilZ still doesn't fix IMEI.
This isn't confusing for me, so I'll let you know about these tomorrow, but two things:
- I can't find the C5306 kernel, is leaving the kernel the way it is (not flashing C5303) fine?
- To re-install .ko files do I just place them in that same directory with a file manager?
EDIT: Yup, flashing .205 kernel for C5303 on stock 4.3 erases IMEI.
pixielikescandy said:
- I can't find the C5306 kernel, is leaving the kernel the way it is (not flashing C5303) fine?
Click to expand...
Click to collapse
-yes, leave the c5306 kernel as it is (don't flash c5303 kernel after custom ROM flashing, just reboot).
So, what you can do is, flash eg. PA build #4 with Philz, while on c5306_205 kernel/ROM (working imei), and reboot without flashing c5303 kernel. Hope imei not missing!
Then, if Wi-Fi not working, try copying those 4.3 .ko files to the same place (overwrite) and make sure file permissions are 644 (rw-r--r--). Reboot, hope Wi-Fi works! (Not sure about that really.. ). Try modprobe and lsmod commands to see what's happening..
The IMEI appeared when I flashed PA with C5306 kernel, but I haven't done the Wi-Fi fix yet.
pixielikescandy said:
The IMEI appeared when I flashed PA with C5306 kernel, but I haven't done the Wi-Fi fix yet.
Click to expand...
Click to collapse
If you have time, can read the section 6 in the following link, to have an idea why kernel modules won't load if the base kernel is different.
http://www.tldp.org/HOWTO/html_single/Module-HOWTO/
Copy those matching 4.3 .ko files (and set perms) and see what happens..
Thank you so, so much! wlan.ko from 4.3 fixed it. PA is now running with both SIM and Wi-Fi working.
Installed bagyuz's CM11 on locked bl recently. Loving it.
Just set ART, and now dolphin seems to fly instead of swimming.
Issues I need help with:
a. How do one lock the 5 buttons (on homescreen) above the nav bar?
b. the quick launch button (the one you get when you swipe up the home button) - I get the same 3 buttons on locked and unlocked screen. I can't seem to activate the quick launch for locked screen...
Hey guys, seems that the latest builds of CM11 (4.4.4) have the same problems on my phone.
Country: Romania (Europe)
- I have an i9000 with CWM Recovery 6.0.4.7
- I'm trying to flash CM11 4.4.4 (last i tried: cm-11-20140729-NIGHTLY-galaxysmtd) from CM11 4.4.2 (cm-11-2014-02-28--NIGHTLY-galaxysmtd -> XXJVU)
- I did WipeData/FactoryReset, Wipe Cache, Wipe DalvikCache and Format /System, after that I flashed "cm-11-20140729-NIGHTLY-galaxysmtd" (CM11-4.4.4), and flashed GAPPS for 4.4.2 (i tried with 4.4.3 too), and reboot (i get no errors)
- The ROM boots up and everything seems to be okay besides the fact that i have no sim service (no signal bars, or pin code pop-up checker at startup), at "About Phone" i get "Baseband version Unknown", Wi-Fi is grayed and it's freezed ("Turning Wi-Fi on..." forever), Bluetooth it's not grayed out, but once i enable it, the "on" button goes gray and it does nothing, also when i go to "About Phone" -> "Status", the Settings app crashes.
I tried to flash a stock radio/modem (XXJVT, XXJVU) in hope that would fix the problem but no change.
I tried to do another wipedata/factoryreset, wipe cache, wipe dalvik after installing the rom and gapps and cleared the data and cache for "Settings" app and others but still with no succes in fixing something.
I tried the M8 build and other close nightlies, all seem to have the same problem.
If i flash my old rom back, everything is working perfect.
HELP! Any solutions to this?
Thank you guys in advance!
I had the same problem yesterday. Try to re-install the ROM. If it still doesn't work then flash a stock ROM (JW4) with Odin and then install 4.4.4 again. The last one worked for me.
kalpetros said:
I had the same problem yesterday. Try to re-install the ROM. If it still doesn't work then flash a stock ROM (JW4) with Odin and then install 4.4.4 again. The last one worked for me.
Click to expand...
Click to collapse
After you flashed the stock firmware (JW4 aka GingerBread 2.3.6) what and how did you flash a recovery that is able to install CM11 4.4.4 Roms?
EDIT (FIXED IT):
This solved the issues that i talked about in the main post
I was on CM11 4.4.2, entered recovery and did full wipe
- I flashed stock firmware for i9000 Sweden (JW4 Gingerbread 2.3.6) via Odin
- I flashed root for it wich included a cwm recovery 3.0.0.x
- Entered the recovery which the root installed and did a full wipe
- Flashed directly "cm-11-20140729-NIGHTLY-galaxysmtd", after which the phone rebooted in a different cwm recovery (6.0.5.0) and installed the rom and rebooted again
- After reboot, the phone booted directly in the new cwm recovery 6.0.5.0, and i did a full wipe
- Flashed again "cm-11-20140729-NIGHTLY-galaxysmtd" and "gapps-kk-20140606" and now the rom (cm11 4.4.4) works perfect with no more problems
Thanks to kalpetros that initiated me in solving my problem with his solving solution (http://forum.xda-developers.com/member.php?u=5359865)
MihaiDani93 said:
After you flashed the stock firmware (JW4 aka GingerBread 2.3.6) what and how did you flashed a recovery that is able ti install CM11 4.4.4 Roms?
Click to expand...
Click to collapse
CM10.2 contains such recovery. On your place I would flash stock JVU to get for sure last Gingerbread bootloader (JWx don't contain it). As your system and data partitions have been resized you MUST flash together with firmware also the PIT file 512 and enable repartition in Odin, use version 1.82 or 1.83 for that and run it as administrator.
Safer way for not to loose IMEI anymore is to upgrade stepwise (GB,ICS,JB,KK) so first CM9, then CM10.2, then CM11
tetakpatalked from N7100
tetakpatak said:
CM10.2 contains such recovery. On your place I would flash stock JVU to get for sure last Gingerbread bootloader (JWx don't contain it). As your system and data partitions have been resized you MUST flash together with firmware also the PIT file 512 and enable repartition in Odin, use version 1.82 or 1.83 for that and run it as administrator.
Safer way for not to loose IMEI anymore is to upgrade stepwise (GB,ICS,JB,KK) so first CM9, then CM10.2, then CM11
tetakpatalked from N7100
Click to expand...
Click to collapse
I didn't lost the imei (or so i think). I just had no service, no enabled sim. (no "imei lost" warning messages)
Hello,
I have been trying to flash CM12.1, and CM11, and RR ROMs onto my S3 Mini GT-I8190N. The ROMS themselves flash perfectly, but my SIM card is not recognised with any of the ROMS. The SIM card is recognised by the Stock ROM. Now I realise all of the ROMs can not have the same problem, and the problem must be something I am doing. My question is, what am I doing wrong.....
Phone is rooted with TWRP via Odin.
Super User is installed.
I have tried flashing the ROMs via Odin, and TWRP.
And I do a Factory Reset, wipe Dalvik, cache, system, and Data before each flash when using TWRP.
The only thing I can think of is my phone is possibly still SIM locked. Is there any way to check(apart from a foreign SIM)? And is SIM unlocked required for a custom ROM to detect the SIM card?
If SIM unlock is required, does anyone have recommendations on how to unlock my phone?
Thanks for your help.
Got sorted using this link
http://forum.xda-developers.com/showthread.php?t=2548453
Everything working now.