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..?
Related
I've spent the last 2 days trying to fix my mistake. I have the GS2 ATT version, and I didn't realise there was a difference between that and the GTI9100 S2.
I wanted to give some tips I learned on how to recover your phone if you make this mistake.
First, here are some posts you'll want to look at:
http://forum.xda-developers.com/showthread.php?t=1286432 - Stock firwmware
http://forum.xda-developers.com/showthread.php?t=1285823 - Clockworkmod for the ATT
http://forum.xda-developers.com/showthread.php?t=1286192 - Cyanogenmod for our phones.
Using Odin and the stock firmware, you can recover your phone to a 95% working state. Once I got my stock firmware on there, I found that while making calls my phone made no sound, and the mic didn't work. The mic did work when I wasn't making calls though.
I reflashed the modem.bin file found on the stock firmware, not sure if its required but that is what I did first. Then, I unpacked the rooted stock firmware, and flashed JUST THE zImage file. After doing this, I rebooted, and my calls were working again.
After that, I installed the correct version of Clockworkmod, and then CM7 nightly. Now everything seems to be running great on my phone.
Hope this helps someone out there,
-Orbital
Good job thanx man.
Sent from my SAMSUNG-SGH-I777 using XDA App
Been awhile since I messed w/ android. I forgot about the different models myself until I realized I was spending half my day in the wrong section
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Alucardis666 said:
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Click to expand...
Click to collapse
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Alucardis666 said:
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Click to expand...
Click to collapse
Those are NOT for our version of the GS2, International only. Our version is here in the development forum.
Sent from my SGH-I777 using xda premium
Yes, it will return a status error 7 which means it's unmatched. Ask me how I know. I flashed international roms last night and used this fix to get me good again.
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
connexion2005 said:
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
Click to expand...
Click to collapse
The simple thing would be to change out the sec_touchkey.kl with rootexplorer and take the sec_touchkey from system/usr/keylayout should fix the i9100 rom to work with the i777. Seeing as how this worked for the Captivate *i897* for jvr, jvs, and jvt darkyrom releases and I would assume that it would work.
daraj said:
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
Click to expand...
Click to collapse
Personally I would think that you had a bad flash? Did you flash through Odin or CWM? From what I have been reading the gb bootloaders between the i777 and i9100 are different and I can see if you used a custom i9100 rom flashing via cwm could cause that. Since I am not too sure on the sgs2 if the differences between the euro models versus the carrier locked, the Kernel will not fix the button mapping, I learned this with the captivate when I switched over to using DarkyRom jvr and jvs builds since they were the most stable of GB for the i897 captivate. Plus if you are going to run a i9100 rom, I am sure the modem will not work with the att kernel. Especially if the situation with the cappy is any indication that att kernel needs att modem and i9000 kernel needs i9000 modem. I will be able to know more as soon as I get my i777 tomorrow.
HTH,
Charlie
Does anyone know how to remove the i9100 splash screen?
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
spbluffmaster said:
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
Click to expand...
Click to collapse
wipe data/factory reset
tried that three times... didnt help..
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
DiscipleDOC said:
Does anyone know how to remove the i9100 splash screen?
Click to expand...
Click to collapse
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1311975
re: get rid of i9100 boot logo
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
Use a download mode jig or flash entropy 512's stock TAR kernel with Odin from the link below.
http://forum.xda-developers.com/show....php?t=1286432
Good luck!
highaltitude said:
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
Click to expand...
Click to collapse
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Entropy512 said:
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Click to expand...
Click to collapse
i messed up and flashed an i9100 rom and am having the call prob u described. can i just flash the modem or stock rooted kernel and be back to 100%? if so do i use odin and do i need to check the box for repartition or anything like that? thx in advance!!!
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
Guys I know this is long but PLEASE don't freak out! I really need some advice from you experts on this! I hope you could spend your time reading everything here and give me some advices! Thanks!
Phone details:
Model number: GT-I9300
Android version: 4.3
Baseband version: I9300DXUGNB1
Build number: JSS15J.I9300XXUGNA5
Hello guys, since I'm not really a rooting expert (previously I rooted a motorola device), I would like to ask for some advices regarding rooting our S3 because I have only one phone and I can't afford to brick it.
1. So basically I'm referring to the guide here. However, that rooting guide is for Samsung Galaxy S3 on I9300XXUGNA7 Android 4.3 Jelly Bean, which is different from my build number (I've checked software update on my device over OTA and Kies3 but it says I have the latest firmware), will it works for my phone? Also in the guide it says to use odin3 v3.09, however in CF_auto_root page here it says to use odin3 v1.85, so which one is working for my device or which one is better?
2. Next I would like to ask is it necessary to install CWM recovery to replace the stock one? After searching around, I found that there are some people who installed CWM recovery even before rooting, is that even possible? So basically to install CMW recovery I think I will follow the steps here, is this working for my device?
3. Okay I know this is the dumbest question... but is there anything else I need to do after the above 2 steps (flashing kernel, modem etc.)?
Thank you very much for spending your time reading my post. I hope you can clear those doubts for me!
You are posting in the wrong section my friend you need to post your question here >> http://forum.xda-developers.com/galaxy-s3/help << you will find you will get alot more replies...Ask a mod to move your post....
tallman43 said:
You are posting in the wrong section my friend you need to post your question here >> http://forum.xda-developers.com/galaxy-s3/help << you will find you will get alot more replies...Ask a mod to move your post....
Click to expand...
Click to collapse
Oops I see... thanks for telling!
nikctsh said:
Oops I see... thanks for telling!
Click to expand...
Click to collapse
Glad to see you in the right place now
Have a look at this thread >> http://forum.xda-developers.com/galaxy-s3/general/howto-rooting-wiping-flashing-ultimate-t1911726 << it may help you answer a few questions...
Also if you are planning to flash custom roms you do not need to root if you are doing it to mod your phone only then you will need to root..
nikctsh said:
Guys I know this is long but PLEASE don't freak out! I really need some advice from you experts on this! I hope you could spend your time reading everything here and give me some advices! Thanks!
Phone details:
Model number: GT-I9300
Android version: 4.3
Baseband version: I9300DXUGNB1
Build number: JSS15J.I9300XXUGNA5
Thank you very much for spending your time reading my post. I hope you can clear those doubts for me!
Click to expand...
Click to collapse
Flashing your phone in any way doesn't guarantee not bricking it, see this thread
Scroll down to the quoted section headed Quick Root from there
Download Odin
Download CF-AutoRoot for your phone
Read the link on rooting
It is really straight forward just read up on it but don't read too much into it a frighten yourself
tallman43 said:
Glad to see you in the right place now
Have a look at this thread >> http://forum.xda-developers.com/galaxy-s3/general/howto-rooting-wiping-flashing-ultimate-t1911726 << it may help you answer a few questions...
Also if you are planning to flash custom roms you do not need to root if you are doing it to mod your phone only then you will need to root..
Click to expand...
Click to collapse
Great that thread helps a lot! I cleared most of my doubts now, but one more question please, after rooting, I wished to install ported apps like S5 launcher and accuweather, and in order to install these I need to flash from recovery. Is it possible to flash this using stock recovery? Or I need to install custom recovery like CMW?
You can't install anything with stock recovery, you'll need a custom recovery.
Make sure you have a full nandroid and efs backup before you flash anything -ported apps can break the framework and produce bootloops.
Seriously though, all this information is available in the sticky or by searching -why do need people to write it all out for you?
Sent from my GT-I9300 using Tapatalk
boomboomer said:
You can't install anything with stock recovery, you'll need a custom recovery.
Make sure you have a full nandroid and efs backup before you flash anything -ported apps can break the framework and produce bootloops.
Seriously though, all this information is available in the sticky or by searching -why do need people to write it all out for you?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks for your information. I did search around and try to understand the things myself, but still there are some doubts remain, that's why I opened this thread hoping that someone can clear the doubts for me. This is my only phone and I really can't afford another (I'm from a low-income family), I just want to make sure everything is alright so that I don't mess up my device. Thanks for your understanding
If this is relevant for Samsung galaxy s3, I got this done the other day using Odin to unlock and root, ran the root app to confirm root. The ROM manager to found CWM recovery flash. So far all good, should take 5 mins in all but an hour in prep and homework.
Sent from my Nexus 4 using XDA Free mobile app
Don't use rom manager, it can soft brick your phone.
Sent from my GT-I9300 using Tapatalk
Hello! I agree that it would be better NOT to use Rom Manager. Many users had problems because of it. The safest way, in my opinion, is to flash a custom kernel using Odin. For example, I had stock rom and used Odin to flash boeffla kernel (not advertising it, just saying what I did) because that kernel had both a .tar version and a .zip one. I downloaded the .tar version and flashed it with Odin by putting the .tar file in the PDA column. That's for root.
For recovery I'm using PhilZTouch and I love it. It supports both JB and KK roms and that is preety cool. Also it's full touch so I don't need to stress my hardware buttons. It's also available as .tar file so you can flash it with Odin just like the kernel.
That's how I'd recommend anyone to root and install a custom recovery on a Sammy phone because I believe it's the safest way. PS: before launching Odin make sure the phone is NOT connected to the PC and that Kies isn't running in the background (use Task Manager to check) Goodluck! !! :thumbup::thumbup:
Sent from my GT-I9300
fatcarrotcake said:
If this is relevant for Samsung galaxy s3, I got this done the other day using Odin to unlock and root, ran the root app to confirm root. The ROM manager to found CWM recovery flash. So far all good, should take 5 mins in all but an hour in prep and homework.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Wow, that's great. By saying unlock, do you mean unlock the bootloader? Wait, is the bootloader locked in our S3?
AlexVat said:
Hello! I agree that it would be better NOT to use Rom Manager. Many users had problems because of it. The safest way, in my opinion, is to flash a custom kernel using Odin. For example, I had stock rom and used Odin to flash boeffla kernel (not advertising it, just saying what I did) because that kernel had both a .tar version and a .zip one. I downloaded the .tar version and flashed it with Odin by putting the .tar file in the PDA column. That's for root.
For recovery I'm using PhilZTouch and I love it. It supports both JB and KK roms and that is preety cool. Also it's full touch so I don't need to stress my hardware buttons. It's also available as .tar file so you can flash it with Odin just like the kernel.
That's how I'd recommend anyone to root and install a custom recovery on a Sammy phone because I believe it's the safest way. PS: before launching Odin make sure the phone is NOT connected to the PC and that Kies isn't running in the background (use Task Manager to check) Goodluck! !! :thumbup::thumbup:
Sent from my GT-I9300
Click to expand...
Click to collapse
Thanks! Will check out PhilZTouch recovery :fingers-crossed:
Currently struggling with deodexing/odexing the stock rom, after reading around I can differentiate between the odex and deodex rom, still digging on how to deodex a rom though (since I want to install some S5 mods). After searching around, it seems like titanium backup can do the deodexing/odexing just nice Gonna do some more preparation, hopefully I can have my device rooted by this week
You could flash PhilZ Recovery and make a nand backup of your rom. This way you'd have an emergency copy if something goes wrong or if you break something in the system. Just my thought
Sent from my GT-I9300
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
so I got this galaxy s5 (free) to replace the S4 I had.. I'm on AT&T and the S5 is a T-Mobile device.. I unlocked and am currently using on AT&T without any issues.. I tried Cyanogenmod 12 on it.. had way too many Bluetooth music issues.. so I switched back to a rooted t-mobile stock.. which is terrible.. bluetooth music works great but everything is is painfully slow.. so I want to find a good fast custom rom (that also has proper bluetooth music support).. With so many device versions and so many custom roms I'm just a bit perplexed.. I found some that are debloated stock roms which seem like that would be good. but I'm just a bit confused on what parts I need to have as "t-mobile g900t" and which parts I don't have to have that way? so yeah this is a bit of a newbie question (even though I have run 4 or 5 custom roms in the past (original galaxy s and my s4 both had custom roms). .but those were always at&t devices on at&t network.. so was an easier choice..
at any rate.. looking for some tips on how to best find the right rom.. Would love to do this today/tomorrow.. avoid messing with the phone during the work week..
Thanks in advance!!
Gary
Try the latest stock ROM for the phone. Many of us were having issues with lag with prior 5.1.1 ROMS. The latest ROM has fixed all these issues. Very snappy.
i feel like i remember seeing bluetooth/audio fixes & updates in the CM13 nightly changelogs, you also didnt specify which CM 12 you installed... the last 12.1 snapshot from october or the last nightly from december?
You can run whatever rom you want. If it works with KLTE it works on your phone. Check the S5 unified development. Cyanogen has always been crap on this phone, probably always will be. Try an AOSP based one like Tesla or TipsyOS (probably won't find them on this site, they post all of their roms on their Google+ page)
Unfortunately the only Marshmallow available for this phone so far is CM-13 based so it's also crap and full of bugs...
To be honest, no ROM you find will be perfect. The most stable thing I've found is to just use a rooted stock ROM and debloat the hell out of it then run Google Now launcher or Nova and forget that you have a Samsung device for a while, until the next OTA comes out and you have to do the process over again.
Sean89us said:
You can run whatever rom you want. If it works with KLTE it works on your phone. Check the S5 unified development. Cyanogen has always been crap on this phone, probably always will be. Try an AOSP based one like Tesla or TipsyOS (probably won't find them on this site, they post all of their roms on their Google+ page)
Unfortunately the only Marshmallow available for this phone so far is CM-13 based so it's also crap and full of bugs...
To be honest, no ROM you find will be perfect. The most stable thing I've found is to just use a rooted stock ROM and debloat the hell out of it then run Google Now launcher or Nova and forget that you have a Samsung device for a while, until the next OTA comes out and you have to do the process over again.
Click to expand...
Click to collapse
much improved deep sleep battery means crap & full of bugs? i'm over a week behind on nightlies & there arent that many bugs... http://www.cmxlog.com/13/klte/ things are improving all the time, only CM 12.1 is stuck... but the last december nightly isnt buggy either
Sort of forgot about this thread. first Thanks for the replies.. So I have been using CM13 since I posted this.. and this has great for speed.. but BlueTooth continues to suck.. no matter what bluetooth device I use with this Rom it skips and stutters. I've finally had enough.. it's been quite a long time with this issue so time for me to switch.. I will try one of the rooted stock roms and debloat it with one of those tools.. thanks again everyone!
gpinkham said:
Sort of forgot about this thread. first Thanks for the replies.. So I have been using CM13 since I posted this.. and this has great for speed.. but BlueTooth continues to suck.. no matter what bluetooth device I use with this Rom it skips and stutters. I've finally had enough.. it's been quite a long time with this issue so time for me to switch.. I will try one of the rooted stock roms and debloat it with one of those tools.. thanks again everyone!
Click to expand...
Click to collapse
Go to the international s5 site look at Tamirda's phoenix rom . It's 6.0.1 mm very snappy very few bugs. Very moddable. Just load a stock mm rom from here first than so you have the proper bootloader and modem. After installing you feel like you got a mini s7. Good good.
Sean89us said:
You can run whatever rom you want. If it works with KLTE it works on your phone. Check the S5 unified development. Cyanogen has always been crap on this phone, probably always will be. Try an AOSP based one like Tesla or TipsyOS (probably won't find them on this site, they post all of their roms on their Google+ page)
Unfortunately the only Marshmallow available for this phone so far is CM-13 based so it's also crap and full of bugs...
To be honest, no ROM you find will be perfect. The most stable thing I've found is to just use a rooted stock ROM and debloat the hell out of it then run Google Now launcher or Nova and forget that you have a Samsung device for a while, until the next OTA comes out and you have to do the process over again.
Click to expand...
Click to collapse
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
Go to the international s5 site look at Tamirda's phoenix rom . It's 6.0.1 mm very snappy very few bugs. Very moddable. Just load a stock mm rom from here first than so you have the proper bootloader and modem. After installing you feel like you got a mini s7. Good good.
Click to expand...
Click to collapse
Question.. I currently have CM13 loaded in this phone.. so do I still need to do the "Just load a stock mm rom" first? I assumed I already had the proper bootloader and modem..
thanks!
gpinkham said:
Question.. I currently have CM13 loaded in this phone.. so do I still need to do the "Just load a stock mm rom" first? I assumed I already had the proper bootloader and modem..
thanks!
Click to expand...
Click to collapse
If you have the mm bootloader and modem installed just wipe and flash. But I believe cm 13 could be ran on the lp bootloader. I odined the stock tar first that way you know all the partitions are proper. Than Odin Twrp 3 0.0 . Make sure you back up your data from internal storage because when you Odin factory package it wipes phone storage. I learned this the hard way lost a bunch of pictures lol anyway I found this to be the best way. Hoping this helps....
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
If you have the mm bootloader and modem installed just wipe and flash. But I believe cm 13 could be ran on the lp bootloader. I odined the stock tar first that way you know all the partitions are proper. Than Odin Twrp 3 0.0 . Make sure you back up your data from internal storage because when you Odin factory package it wipes phone storage. I learned this the hard way lost a bunch of pictures lol anyway I found this to be the best way. Hoping this helps....]
Click to expand...
Click to collapse
1. is there a way to tell which bootloader I have?
2. I'm running teamwin.. I assume that's fine for flashing Phoenix but does one really need Odin?
3. I had a rooted stock image before I installed CM13.. (the stock image was so dang slow.. forget which.)
thanks again!
Gary
gpinkham said:
1. is there a way to tell which bootloader I have?
2. I'm running teamwin.. I assume that's fine for flashing Phoenix but does one really need Odin?
3. I had a rooted stock image before I installed CM13.. (the stock image was so dang slow.. forget which.)
thanks again!
Gary
Click to expand...
Click to collapse
Get any phone info app and check and see if your bootloader ends in pe1 if it don't you don't have mm bootloader. Teamwin is twrp just make sure it's version 3.0.0 that version seems to do best with the phoenix rom.
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
Get any phone info app and check and see if your bootloader ends in pe3 if it don't you don't have mm bootloader. Teamwin is twrp just make sure it's version 3.0.0 that version seems to do best with the phoenix rom.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry for eavesdropping but I dont think that PE3 came yet, either via OTA or on sammobile.
Correct me if I am wrong
Sent from my SM-G900T using XDA-Developers mobile app
S.N [user=2501176 said:
@.k.[/user]3;67525688]Sorry for eavesdropping but I dont think that PE3 came yet, either via OTA or on sammobile.
Correct me if I am wrong
Sent from my SM-G900T using
I'm sorry you are correct I meant pe1 pe3 is for the Note 4. I've been working with a friends note 4 past few days. Thanks for catching my error . Hate giving wrong advice... original post edited...
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
inspired55 said:
Get any phone info app and check and see if your bootloader ends in pe3 if it don't you don't have mm bootloader. Teamwin is twrp just make sure it's version 3.0.0 that version seems to do best with the phoenix rom.[/URL]
Click to expand...
Click to collapse
thanks for sticking with me on the all the newbie questions.. bootloader version reported as G900TUV1FOG6.. later in the list it shows Latest Firmware: G900TUVUGPE1/G900TTMBGPE1/G900TUVU1GPE1.. so at first I was thinking I was ok.. but that second entry had me wondering.. (dang.. just noticed this was never submitted (from 6/28).. oh well)..
ok.. So I assumed I'm good to go.. installed the latest TWRP (3.0.2).. wiped the data area and tried to flash Phoenix.. It starts installing Aroma.. and within a couple of seconds the phone reboots back into TWRP.. did this a few times.. rebooting into the OS gets me a new Cyanagenomod not Phoenix.. figure I must be missing a step somewhere (or have something that is preventing Phoenix from installing).. thoughts?
thanks again!!
gpinkham said:
ok.. So I assumed I'm good to go.. installed the latest TWRP (3.0.2).. wiped the data area and tried to flash Phoenix.. It starts installing Aroma.. and within a couple of seconds the phone reboots back into TWRP.. did this a few times.. rebooting into the OS gets me a new Cyanagenomod not Phoenix.. figure I must be missing a step somewhere (or have something that is preventing Phoenix from installing).. thoughts?
thanks again!!
Click to expand...
Click to collapse
I think you still don't have the correct bootloader . The firmware is mm because your using CM13. The easiest way to get it done for sure is to odin the official MM firmware. Than install Twrp 3.0.0 flash superuser to have root . Reboot in recovery and flash phoenix rom v12.0 than the 12.6 update. This may take extra time this way but all the partitions will be correct. Or odin bootloader in BL slot and modem in cp slot . Don't set for auto reboot pull battery back into download mode Odin Twrp pull battery. Reboot into recovery than flash superuser. Than flash phoenix. Good luck
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
I think you still don't have the correct bootloader . The firmware is mm because your using CM13. The easiest way to get it done for sure is to odin the official MM firmware. Than install Twrp 3.0.0 flash superuser to have root . Reboot in recovery and flash phoenix rom v12.0 than the 12.6 update. This may take extra time this way but all the partitions will be correct. Or odin bootloader in BL slot and modem in cp slot . Don't set for auto reboot pull battery back into download mode Odin Twrp pull battery. Reboot into recovery than flash superuser. Than flash phoenix. Good luck
Click to expand...
Click to collapse
OK.. you may be right.. I downgraded TWRP to 3.0.0 and the install started working fine.. but now the reboot into Phoenix has been going for about 35 mins.. I know it can take some time but that seems extreme.. will wait a bit longer and if it doesn't work I'll try the steps you listed above..
thanks again
Gary
inspired55 said:
I think you still don't have the correct bootloader . The firmware is mm because your using CM13. The easiest way to get it done for sure is to odin the official MM firmware.
Click to expand...
Click to collapse
Well I used Heimdall.. flashed a bootloader image MM.. now the phone seems to be completely bricked.. get the samsung galaxy s5 screen keys light up.. and just sits there.. time to toss it I guess. .(was a freebie anyway)..
gpinkham said:
Well I used Heimdall.. flashed a bootloader image MM.. now the phone seems to be completely bricked.. get the samsung galaxy s5 screen keys light up.. and just sits there.. time to toss it I guess. .(was a freebie anyway)..
Click to expand...
Click to collapse
Got the phone back to CM13. so back to crappy bluetooth music streaming.. ha.. oh well I will give this try again some other day..
thanks again for the help!
Gary
gpinkham said:
Got the phone back to CM13. so back to crappy bluetooth music streaming.. ha.. oh well I will give this try again some other day..
thanks again for the help!
Gary
Click to expand...
Click to collapse
Gary look in this general section for the post that instructs you how to install factory mm. Follow the guide. Google to see how to install factory tar files using Lunix . I'm guessing my instructional writing skills leave something to be desired lol . Once you have the factory mm up and running install Twrp flash superuser reboot. Than reboot into recovery flash phoenix rom. Good good
Sent from my SM-G935F using XDA-Developers mobile app