Related
Need Help!
I've installed 2 roms Chrack's and Crash's LRK404 successfully But afterwards I can't Install from zip anything, this includes themes, boot anims. kernels. All freeze for awhile then reboots. So I have to use odinPC to flash an FM kernel then install from zip the Abyss kernel, then wipe factory reset + dalvik and cache, also tried the jBroid_Kernel_Cleaning_Script_Ed-1.zip. And Fix Permissions inside the
CWM v.5.5.0.4
I did get a log file after trying Crash Red theme. (I've attached it in a zip) it's like the permissions get locked once the rom is installed.
By the way if anyone has a (Abyss touch kernel in tar format) I would be thankful.
Any help would be greatly appreciated.
here you go, used this one when I was with stock GB.. not sure about stock ICS though but I guess it'll work still.... :good:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.
Sorry, I didn't understand your last post.
YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance
Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...
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...
i have installed twrp revovery to install a lollipop rom but it failed and i wasn't able to boot into my system again so i flashed the souce kernel of the rom for the first time and it worked and when i tried again to install the rom i had the same issue exept that after reflashing that kernel i'm stuck on bootstall help me plz i'm a neewbie btw :'( :crying:
dettol123 said:
i have installed twrp revovery to install a lollipop rom but it failed and i wasn't able to boot into my system again so i flashed the souce kernel of the rom for the first time and it worked and when i tried again to install the rom i had the same issue exept that after reflashing that kernel i'm stuck on bootstall help me plz i'm a neewbie btw :'( :crying:
Click to expand...
Click to collapse
1)Make sure you bootloader are unlocked.
2) Make sure that the kernel match the software, You have to have an AOSP kernel for a AOSP build, for that you will need to read the instuction that are provided by a particular developer, Usually kernel are provided and it can be recognised by .sin ; .img you may need to flash it first using flashtool then boot to recovery and flash the rest of the system. You may provide better description of the build that your are using , for the better help. I suspect that you have not unlocked the boot-loader
Hello
I have made a dirty flash of my current rom then xposed modules stopped working. I have reflashed the framework. And It seems installed with no issues . but the modules itself is not working. I have tried to format the whole system and install it fresh then xposed zip but the same issue .
I don't really know how it's related.
Tried several ways but all failed .
Phones is oneplus one . running cm12s
Any suggestions ?