I Get a notification about the update to version 4.4 BETA 1 of Paranoid Android rom, after downloaded, i flash it via CWM normaly, then flash gapps, but when the phone reboot it stucked at the Galaxy S2 boot logo, and it can boot into recovery, only download mode, but when i open odin to flash CWM but odin can't access the phone and i can't flash, i tried to install usb driver but not success, so what can i do now, please help!
Sorry for my bad English
1) Your English is better than a lot of native English speakers I know.
2) Hopper8's 'Odin troubleshooting' thread stickied in General has all the info you need to get a successful Odin flash. Find the thread, try as many of the troubleshooting steps as many times as you need to in order to get a successful flash.
However, don't try one or two things from the thread, come back here & say 'But I tried some of the stuff in the thread & it didn't work. That thread covers this issue from every possible angle, and it's often persistence that fixes these. There's no easy fix in this situation because we're not there looking over your shoulder seeing what you're doing/not doing, and there's nothing which isn't in the thread that can be suggested in this situation.
So...I've (and Hopper has) given you the tools to get your phone fixed, up to you to fix it now.
@nguyenducanh did you manage to fix this?
I have been speaking with the dev (ayysir) of ParanoidAndroid, 4.4beta1 for S2 had a bug with the kernel. The ROM wouldn't boot at all with the stock kernel, but would with any compatible custom kernel (Dorimanx, Gustavo, Apolo -correct versions of these).
The dev has uploaded a new build now which fixes the problem, so if you've managed to recover your phone the new build is safe to use (tested by me)
Hopper8 said:
@nguyenducanh did you manage to fix this?
I have been speaking with the dev (ayysir) of ParanoidAndroid, 4.4beta1 for S2 had a bug with the kernel. The ROM wouldn't boot at all with the stock kernel, but would with any compatible custom kernel (Dorimanx, Gustavo, Apolo -correct versions of these).
The dev has uploaded a new build now which fixes the problem, so if you've managed to recover your phone the new build is safe to use (tested by me)
Click to expand...
Click to collapse
Ok, tks u, i fixed my phone via odin, and i'm using c-rom v6.6, i will try newest pa now because i'm a big fan of pa
nguyenducanh said:
Ok, tks u, i fixed my phone via odin, and i'm using c-rom v6.6, i will try newest pa now because i'm a big fan of pa
Click to expand...
Click to collapse
Good job, I like to hear that someone recovered their phone using that guide and odin :good: make sure you re-download the ROM, you need the build on 0605, not 0604. 0604 is busted, but 0605 is good
Hopper8 said:
Good job, I like to hear that someone recovered their phone using that guide and odin :good: make sure you re-download the ROM, you need the build on 0605, not 0604. 0604 is busted, but 0605 is good
Click to expand...
Click to collapse
Ok, using 0605 now, and missing see through option
nguyenducanh said:
Ok, using 0605 now, and missing see through option
Click to expand...
Click to collapse
That's because of the new theme engine... I saw something on google+ about that. I think it's planned to be re-implemented but may take a while due to complexity..
Hopper8 said:
That's because of the new theme engine... I saw something on google+ about that. I think it's planned to be re-implemented but may take a while due to complexity..
Click to expand...
Click to collapse
I hope "see through" will come back in the next update
Related
Hi I want to install latest CM9 nightly, As Im installing first time, I just want to make sure that my phone is running firmware lower than XXLPH though it looks lower but cant judge, I went through official CM9 Thread I can follow all the steps except this one. And also I have already rooted my device using
GT-I9100_THR_I9100JPKJ2_I9100OJPKJ1_I9100XXKI4 (firmware) and
CF-Root-SGS2_XW_XEF_KJ2-v4.4-CWM4.tar (root kernel)
I still havent installed any custom rom yet.
Here is my current phone details:
GT-19100
Android 2.3.5 (STOCK)
Baseband 19100XXKI4
Kernel 2.6.35.7-I9100XWKJ2-CL676699root
____________________________________________
I thought my firmware is higher than XXLPH so I found this guide to ugrade to ice cream firmware first:
http://androidbeast.com/937/tutoria...oid-ice-cream-firmware-on-galaxy-s2-gt-i9100/
then root it with this kernel :
http://androidbeast.com/948/root-samsung-galaxy-s2-cf-root-kernel-odin/
Now I need your advice that weather should I continue following above guide or should I start flashing CM9 firmware staright away ??
now that you are rooted and on ics, you can then follow the instructions in CM9 thread.
Flash odin version first and then update to latest build from cwm recovery
codeworkx said:
If you're a bloody noob and getting confused by following simple instructions, go down and read about using the noob-proof ODIN method.
First time installing CyanogenMod 9 to your Galaxy S II, or coming from another ROM:
- READ FAQs: http://teamhacksung.org/wiki/index.php/Experimental:GT-I9100:Frequently_Asked_Questions
- Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
- make sure you're running a proper working CWM like the one from CM7
- Copy GApps and CM9 ZIPs to your internal SDCard
- Boot into Recovery
- Flash CM9 zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET (otherwise your calendar sync will not work)
- Reboot
- Don't restore Apps using Titanium Backup!
Upgrading from earlier version of CyanogenMod 9:
- Copy CM9 ZIP to your internal SDCard
- Boot into Recovery
- Flash CM9 zip
- Wipe cache partition and dalvik-cache
- Reboot
Using the noob-proof ODIN method:
- Download CM9 Resurrection Edition
- Download GApps and put it onto your internal sdcard
- Open Odin
- Choose cm-9-XXXXXXXX-ODIN-galaxys2.tar.md5 as PDA
- Boot your phone into download mode
- Connect your device via usb to your computer
- Wait till Odin has fully recognized your phone
- Hit the start button and wait till the flash process is finished
- Device boots automatically into recovery
- Flash GApps, wipe cache and dalvik-cache
- Reboot into CM9
- Follow above steps to update CM9 to lastest available version (Upgrading from earlier version of CyanogenMod 9)
Click to expand...
Click to collapse
sahibunlimited said:
Flash odin version first and then update to latest build from cwm recovery
Click to expand...
Click to collapse
You mean i should install ics rom first with odin then i should go for CM9?
Sent from my GT-I9100 using XDA
loverdude said:
You mean i should install ics rom first with odin then i should go for CM9?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Dude. He even posted the instructions from the CM9 thread. If you can't follow them, you should probably stick to stock. No offense.
sahibunlimited said:
Flash odin version first and then update to latest build from cwm recovery
Click to expand...
Click to collapse
Oh i get it! First i should use noob proof method then i should use "Upgrading from earlier version of cm 9" regardless of what firmware i currently have am i right?
Sent from my GT-I9100 using XDA
ctomgee said:
Dude. He even posted the instructions from the CM9 thread. If you can't follow them, you should probably stick to stock. No offense.
Click to expand...
Click to collapse
Am i right on what i said in my above comment? I was getting confused because i read that CM 9 requires ics firmware already installed first.
Sent from my GT-I9100 using XDA
loverdude said:
Am i right on what i said in my above comment? I was getting confused because i read that CM 9 requires ics firmware already installed first.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yes, follow the "noob proof" method. (which doesn't seem too noob proof at the moment... :/)
And seriously, why did you start two threads (this current one, and this other one) about flashing an ICS ROM? CM9 is considered an ICS ROM, so really the topic is the same.
Hi.... i recommend this site galaxys2root.com
it helped me figure out a lot of stuff in the beginning. Video walkthrough of installing roms is really a big help.
For the latest Ressurection Remix 1.2 looki the Android developer forum.
I am about to install now
Hope you get it all sorted
BobPowers said:
Hi.... i recommend this site galaxys2root.com
it helped me figure out a lot of stuff in the beginning. Video walkthrough of installing roms is really a big help.
For the latest Ressurection Remix 1.2 looki the Android developer forum.
I am about to install now
Hope you get it all sorted
Click to expand...
Click to collapse
Hey i succeeded!!!! Im soooo happy! first I followed your website which u gave me to install Resurrection Rom then I upgraded to cm9 through zip file CWM recovery. thanks a bunch man
ctomgee said:
Yes, follow the "noob proof" method. (which doesn't seem too noob proof at the moment... :/)
And seriously, why did you start two threads (this current one, and this other one) about flashing an ICS ROM? CM9 is considered an ICS ROM, so really the topic is the same.
Click to expand...
Click to collapse
Actually on that post I wasn't sure which ROM was based on what firmware but i came to know from users like you and I got clear idea from you all before that in the mean time, i was gathering info through various guides, videos from weeks and merged those ideas in to one then I decided to install CM9 as it looks similar to new galaxy nexus phone and this is exactly what I wanted my phone to look and behave like. Now I am happy and satisfied.
I have done oden with bootloader but in the middle of that the bootloader progress in oden is turn to red and cell get off. now its hard bricked, dead, what i can do
kami2k said:
I have done oden with bootloader but in the middle of that the bootloader progress in oden is turn to red and cell get off. now its hard bricked, dead, what i can do
Click to expand...
Click to collapse
Man... why did you the touch the bootloader first? never play with it unless you know whats gonna happen! and about noob installation guide for CM9 is not clearly noobproof, I completely did all installation with clockworkmod recovery, I used ODIN only once for rooting my phone after that i never used it as I was very very cautious and careful about each and everything bit i was doing.
But never loose hope, you never know what kind of brick you have you have two ways to unbrick your phone,
1.Using USB jig, search it on XDA, Google, Youtube
2.JTAG Service, This is the ultimate solution if your phone is completely Hard bricked but for this you have to send your device to them.
here is their demonstration:
http://www.youtube.com/watch?v=kQdTi2vgMmY
its written in the cm9 installation to do the boot-loader with ODIN, that is what i do
oh bhai....... make sure you had i9100 not the i9100G,
remove battery and see if you can get download mode.
im running cm9 on new bootloader unless intratech still removes them from his stock ROm as he used too..... i came from stock LPS to cm9
that much sense i have dear its s2, and ya its dead, i send the cell to lahore, khi, rwp, but no one have jtag proper equipment
kami2k said:
that much sense i have dear its s2, and ya its dead, i send the cell to lahore, khi, rwp, but no one have jtag proper equipment
Click to expand...
Click to collapse
you dont get it i9100G is also S2 and virtually same. you have to see under the batter if its written i9100 or i9100G.
because thats what would happened if you flash i9100 bootloader onto i9100G.
plus faulty usb, dead battery can do the trick aswell.
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes
I recently picked up a GP 4.2. I immediately got it rooted so now I'm running a 2.3.6 stock rom with root. What's the next step in terms of getting a recovery installed and maybe moving up to an ICS or JB rom? I've kind of poked around a bit but it's some what confusing with all the other types of GPs in the same area. Does anybody have a recovery and rom they'd recommend? Is using rom manager to push CWM feasible?
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
NapalmDawn said:
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
Click to expand...
Click to collapse
you should flash CWM via odin first and then flash the ROM via CWM
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
NapalmDawn said:
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
Click to expand...
Click to collapse
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
Xenphor said:
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
Click to expand...
Click to collapse
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
MetaMav said:
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
Click to expand...
Click to collapse
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Xenphor said:
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Click to expand...
Click to collapse
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
NapalmDawn said:
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
Click to expand...
Click to collapse
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Where could I find a stock kernel?
Xenphor said:
Where could I find a stock kernel?
Click to expand...
Click to collapse
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Ok thank you. However, will this work with YP-GS1?
But about kernels, on the webpage where I downloaded the stock rooted rom http://tau.shadowchild.nl/attn1/?p=166 it says specifically that the Wifi module in system and kernel must MATCH. This is what I'm talking about in regards to kernel compatibility with roms. How do I know if a kernel I'm downloading will have changes applied to it that will work with another rom like with this stock rom/kernel?
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Well I had to flash this kernel http://forum.xda-developers.com/showthread.php?t=2198234 to get CWM on mine. I haven't actually flashed anything with CWM because there doesn't seem to be any good roms for the 3.6 unless CM7 comes out sometime. I used Odin to flash a stock rom from here http://tau.shadowchild.nl/attn1/?p=166
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
NapalmDawn said:
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
Click to expand...
Click to collapse
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
MetaMav said:
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
Click to expand...
Click to collapse
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Xenphor said:
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Click to expand...
Click to collapse
Xen-it seems GPlayer development is still fairly newish. the work you see from devs now are all ground work. For the 4.2 and 3.6, they seem a little less dev populated than the 4 and 5. People will build upon the work of early devs and eventually get kernels that can OC and maybe ICS and JB roms. At this stage, we likely won't see anything like ZOMG earth shattering until people spend time with the devices. Seems Serk is on his way to doing the best he can for 4.2 but I am not sure who is tackling 3.6
It's weird how roms for devices go. I learned this when I had a tbolt and shockingly saw a FUNCTIONAL JB rom for my old Eris while the tbolt was still hanging back in ginger land with not even a really good ICS rom let alone JB. I asked the Tbolt community-why? How is it the dinosaur Eris has JB and not us? It all depends on what the devs can do with the sources provided. Sometimes certain hardware points are sticky. you can have beautiful JB rom for a device that can't talk to the camera if the hardware source isn't made available (reference the HP TP for many years)
For now, flash what you're comfortable with and and learn what you do and don't like. Also learn if you want to play things safe and not experiment or take on potentially beta builds. For the tbolt, tackling an ICS rom was too dicey so I never did. On my new Rezound, I eat up JB roms as they are in much better shape
Hey there,
I've been using Cyanogen mod 10 for about a year now (actually probably 10 for 6 months and then moved to 10.1 as soon as it came out). But just today I decided to update to the latest version of the OS through cyanogens update feature on the phone. I was updating to 10.2 FROM 10.1, but I didn't realise the latest version was 10.2 until I checked after. Now my phone restarts by itself every 20 mins and my 3G is doing weird things :/
But the main problem is that I CAN'T boot to recovery mode anymore! I don't know why?! If I could, then I could fix everything :/
Any help would be much appreciated thanks. I can provide any further details if needed. I hope to get this fixed soon as I use it quite a lot! xD
Obviously broke recovery. You could try flashing an Odin version of a custom kernel, but this may not work (might as well try it tho). If it were me I'd go back to stock via Odin, re-root & restore nandroid backup or reflash rom/kernel & start again from scratch (tho I wouldn't need to do this because I make regular nandroids).
Personally speaking, I wouldn't use that update from the phone feature in future. Flash updates/nightlies from recovery. Takes a few extra minutes, but saves you a lot of grief.
MistahBungle said:
Obviously broke recovery. You could try flashing an Odin version of a custom kernel, but this may not work (might as well try it tho). If it were me I'd go back to stock via Odin, re-root & restore nandroid backup or reflash rom/kernel & start again from scratch (tho I wouldn't need to do this because I make regular nandroids).
Personally speaking, I wouldn't use that update from the phone feature in future. Flash updates/nightlies from recovery. Takes a few extra minutes, but saves you a lot of grief.
Click to expand...
Click to collapse
Thanks for the quick reply and tip! For now on I will definitely install from recovery only.
I tried reflashing the Clockwork recovery thing but it didn't seem to fix it.
So I was thinking about flashing the Siyah kernel? Is this a good idea? I flash just the PDA file only right?
Sorry for not knowing much about this flashing stuff xD
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
MistahBungle said:
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
Click to expand...
Click to collapse
Ok I tried flashing Siyah and didn't work :/ Ok I will give flashing a stock rom a try. I presume that puts it back to the way it is? Then I have to re root etc?
Thanks!
Yep.
MistahBungle said:
Yep.
Click to expand...
Click to collapse
Reflashed to a pre-release version of JB from Samsung Thanks heaps for your help! Appreciate it. Will probably go back to Cyanogen tomorrow.
One question though. Is Cyanogen 10.1 supposed to be quite stuttery? I know it's a nightly build and all. But using this official pre-release from Samsung, it's JUST SOOOOO MUCH MORE SMOOTHER! But I expect Cyanogen to be a lot faster :/ Maybe my kernel was just having problems the whole time?
Thanks!
Good man Can't comment on CM10 as I've never used it, used CM9 for ages & got fed up with various things not working as they should/being flaky & have never bothered with CM10 as a result, I'm sure someone else will be able to answer those queries.
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........
10.2.....IMO...NOT stable enough for daily use....
10.1.....fast and smooth, and no bugs that make me want to stop using it.......
10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....
JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......
Back to 10.1 for now.....
keithross39 said:
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........
10.2.....IMO...NOT stable enough for daily use....
10.1.....fast and smooth, and no bugs that make me want to stop using it.......
10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....
JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......
Back to 10.1 for now.....
Click to expand...
Click to collapse
Sorry about the late reply.
Yes that was the exact build! xD
Oh well I am actually quite happy with the official JB firmware from Samsung atm. It's A LOT SMOOTHER than 10.1 for some reason :/ I don't know why. Just is. I had lots of problems with 10.1. At times the RAM seemed to leak so much I would have to restart it otherwise it would just be so stuttery. ESPECIALLY with Swift Keyboard and Facebook heads xD It's ashame because I really liked Cyanogen. Missed some of the features.
Haven't signed in to XDA since 2012 LOL. But anyway I have been seeing a few post from some users with a little problem after flashing a custom ROM. Mostly with an AOSP ROM (CM11, AOKP) Etc. This problem only seems to occur after taking the sprint KitKat OTA and then flashing TWRP with Auto Rec, Followed by flashing a custom rom. I've had this same problem when flashing CM11 to unlock my sprint variant for T-Mobile. The sound was completely gone.!!! Zip Ziltch!! No where to be found. Couldn't place calls because the call screen would go black and then come back with a call ended error. I've been searching for a solution for this for the longest and it seems like on every forum when everyone has this issue and needs help there is no response from any member. So I'm here to help in any way that I can. I found this solution after unlocking 3 G2's yesterday.
*I AM NOT RESPONSIBLE IF YOU SOMEHOW BRICK OR FRY YOUR DEVICE. BY FOLLOWING THIS GUIDE YOU AGREE THAT EVERYTHING STEP YOU TAKE IS ON YOU. YOU.!! THIS HAS BEEN TESTED ON 3 G2'S AND WAS CONFIRMED WORKING. I SUGGEST THAT NOOBS WAIT FOR A CONFIRMATION FROM A DEV BEFORE PROCEEDING. THANK YOU.
I AM GOING TO ASSUME YOU ARE BACK TO YOUR STOCK ROM BEFORE DOING THIS, IF NOT JUST GO INTO RECOVERY, DO A FULL WIPE AND FLASH THE ZIP.
Before you begin download the KitKat modem from this link h t t p : / / forums (dot) xda - developers (dot) com / showthread (dot) php?t=2705509 ( can't post links) and place the zip on the root of you internal storage.
STEP 1 - FLASH THE CUSTOM ROM OF YOUR CHOICE.
STEP 2 - AFTER FLAHSING DO NOT FLASH GAPPS JUST YET. BOOT INTO THE ROM AND COMFIRM THAT THE SOUND IS INDEED DEAD.
STEP 3 - TURN OFF THE DEVICE AND BOOT INTO RECOVERY.
STEP 4 - DO A FULL WIPE AND FLASH THE KITKAT MODEM YOU DOWNLOADED. I DIDNT FLASH GAPPS YET TIL AFTER I BOOTED UP AND CONFIRMED WORKING SOUND, BUT YOU CAN FLASH THEM IF YOU WANT *BE CAUTIOUS, IM NOT SURE IF IT WILL DAMAGE ANYTHING*
But after you boot back up do some sound checks. Place a call and you should now have working sound. Congrats!! You did it! I have done this method on 3 sprint G2's so far. Have not tried other variants but they all should work the same.
Androtopia12 said:
Haven't signed in to XDA since 2012 LOL. But anyway I have been seeing a few post from some users with a little problem after flashing a custom ROM. Mostly with an AOSP ROM (CM11, AOKP) Etc. This problem only seems to occur after taking the sprint KitKat OTA and then flashing TWRP with Auto Rec, Followed by flashing a custom rom. I've had this same problem when flashing CM11 to unlock my sprint variant for T-Mobile. The sound was completely gone.!!! Zip Ziltch!! No where to be found. Couldn't place calls because the call screen would go black and then come back with a call ended error. I've been searching for a solution for this for the longest and it seems like on every forum when everyone has this issue and needs help there is no response from any member. So I'm here to help in any way that I can. I found this solution after unlocking 3 G2's yesterday.
*I AM NOT RESPONSIBLE IF YOU SOMEHOW BRICK OR FRY YOUR DEVICE. BY FOLLOWING THIS GUIDE YOU AGREE THAT EVERYTHING STEP YOU TAKE IS ON YOU. YOU.!! THIS HAS BEEN TESTED ON 3 G2'S AND WAS CONFIRMED WORKING. I SUGGEST THAT NOOBS WAIT FOR A CONFIRMATION FROM A DEV BEFORE PROCEEDING. THANK YOU.
I AM GOING TO ASSUME YOU ARE BACK TO YOUR STOCK ROM BEFORE DOING THIS, IF NOT JUST GO INTO RECOVERY, DO A FULL WIPE AND FLASH THE ZIP.
Before you begin download the KitKat modem from this link h t t p : / / forums (dot) xda - developers (dot) com / showthread (dot) php?t=2705509 ( can't post links) and place the zip on the root of you internal storage.
STEP 1 - FLASH THE CUSTOM ROM OF YOUR CHOICE.
STEP 2 - AFTER FLAHSING DO NOT FLASH GAPPS JUST YET. BOOT INTO THE ROM AND COMFIRM THAT THE SOUND IS INDEED DEAD.
STEP 3 - TURN OFF THE DEVICE AND BOOT INTO RECOVERY.
STEP 4 - DO A FULL WIPE AND FLASH THE KITKAT MODEM YOU DOWNLOADED. I DIDNT FLASH GAPPS YET TIL AFTER I BOOTED UP AND CONFIRMED WORKING SOUND, BUT YOU CAN FLASH THEM IF YOU WANT *BE CAUTIOUS, IM NOT SURE IF IT WILL DAMAGE ANYTHING*
But after you boot back up do some sound checks. Place a call and you should now have working sound. Congrats!! You did it! I have done this method on 3 sprint G2's so far. Have not tried other variants but they all should work the same.
Click to expand...
Click to collapse
Hello, I have this problem on a Samsung Galaxy Epress GT 18730. Which modems would I have to use?
Are you running a custom ROM.? I can't really speak for the express. First you have to make sure the sound drivers are there. If they are then try and locate the latest modem. It might be hard to find since the express doesn't really get a lot of attention.
Sent from my XT1056 using XDA Free mobile app
toxious651 said:
Hello, I have this problem on a Samsung Galaxy Epress GT 18730. Which modems would I have to use?
Click to expand...
Click to collapse
Non of the above link cause they're meant for the g2 so not the express. Try to find modems in the galaxy express thread if there are any but just dont flash this modem, dont even try it. It would definetly not work.
Androtopia12 said:
Are you running a custom ROM.? I can't really speak for the express. First you have to make sure the sound drivers are there. If they are then try and locate the latest modem. It might be hard to find since the express doesn't really get a lot of attention.
Sent from my XT1056 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i'm running cm11. But no one on the cm11 thread knows how to fix this rare problem. I brought my android back to the original firmware 100% and this problem is still there
. I think only a modem can help me, but I don't know where to get one.. One that will bring my sound back.
wulsic said:
Non of the above link cause they're meant for the g2 so not the express. Try to find modems in the galaxy express thread if there are any but just dont flash this modem, dont even try it. It would definetly not work.
Click to expand...
Click to collapse
What galaxy express thread? I'm new to xda and I find it hard to navigate around. >_<
Sent from my GT-I8730 using XDA Free mobile app
toxious651 said:
Yes i'm running cm11. But no one on the cm11 thread knows how to fix this rare problem. I brought my android back to the original firmware 100% and this problem is still there
. I think only a modem can help me, but I don't know where to get one.. One that will bring my sound back.
What galaxy express thread? I'm new to xda and I find it hard to navigate around. >_<
Sent from my GT-I8730 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe there is no thread for express yet idk for sure since i am on tapatalk now :/,
Toxious if you already flashed your phone back to stock with odin then it could be an hardware problem maybe cause odin flashed also modem and the other stuff as far as i know so...:crying:
wulsic said:
Maybe there is no thread for express yet idk for sure since i am on tapatalk now :/,
Toxious if you already flashed your phone back to stock with odin then it could be an hardware problem maybe cause odin flashed also modem and the other stuff as far as i know so...:crying:
Click to expand...
Click to collapse
Hmm.. well if Odin should bring back everything, is there a problem I did something wrong during flashing back to stock firmware? What are the exact steps I should take to get back to stock firmware?
toxious651 said:
Hmm.. well if Odin should bring back everything, is there a problem I did something wrong during flashing back to stock firmware? What are the exact steps I should take to get back to stock firmware?
Click to expand...
Click to collapse
Did you flashed the whole system.tar or whut idk how it goes by samsung anymore :9. Can you like extract from the tar.md5 and flash the modem.bin in the Phone section if I am right. You can just extract the things from the tar.md5 by renaming tar.md5 to tar.
But i believed that if you flash the whole Tar.md5 thing from Samsung that it flashes all files inside
Just try to extract the modem.bin from the tar.md5 and flash it in phone
wulsic said:
Did you flashed the whole system.tar or whut idk how it goes by samsung anymore :9. Can you like extract from the tar.md5 and flash the modem.bin in the Phone section if I am right. You can just extract the things from the tar.md5 by renaming tar.md5 to tar.
But i believed that if you flash the whole Tar.md5 thing from Samsung that it flashes all files inside
Just try to extract the modem.bin from the tar.md5 and flash it in phone
Click to expand...
Click to collapse
I got it fixed!! Running CM11 perfectly too!!
Installed a random firmware and the sound worked lol.
toxious651 said:
I got it fixed!! Running CM11 perfectly too!!
Installed a random firmware and the sound worked lol.
Click to expand...
Click to collapse
Odd random firmare?!?! But okay good to hear you fixed it
wulsic said:
Odd random firmare?!?! But okay good to hear you fixed it
Click to expand...
Click to collapse
Lol yeah, a Netherlands one. Thanks for taking the time out to check on my replies to this thread sir!
I got this problem on my LS980 today.
Let me just quote my post from the rom thread:
"I got no sound after flashing this rom on my LS980. Came from Cloudy's rom, full wipe, flashed rom, gapps and the bloat removal script from the gapps thread. No sound, anywhere-not in youtube, not in music player, not in settings, can't be a hardware issue since I had no problems on previous rom and it doesn't work with headphones, too."
I wanted to flash the modem, but the link is dead ;( any ideas what to do? I'm still on custom rom.
EDIT: back-up from ZVE stock kit-kat solved the problem. Now, what should I do to flash custom rom and have working sound..?