Just got given an i9100 today with a faulty USB port. A new one is coming in the mail, but ebay is slow.
It charges fine so it can be used, just no data connection over USB (connects and disconnects, cleaning the port did not help)
Currently on 4.1.2, i9100XXLS9
I can get files to it via SD card, is there any methods to root it or get TWRP on it that can be done before i fix the USB port?
Mussels84 said:
Just got given an i9100 today with a faulty USB port. A new one is coming in the mail, but ebay is slow.
It charges fine so it can be used, just no data connection over USB (connects and disconnects, cleaning the port did not help)
Currently on 4.1.2, i9100XXLS9
I can get files to it via SD card, is there any methods to root it or get TWRP on it that can be done before i fix the USB port?
Click to expand...
Click to collapse
Mobile Odin
noppy22 said:
Mobile Odin
Click to expand...
Click to collapse
looks like its working, its loaded a stock rom and has its many options. How do i add a custom recovery with it? I'm fuzzy on the S2, since it combined kernel + recovery.
Mussels84 said:
looks like its working, its loaded a stock rom and has its many options. How do i add a custom recovery with it? I'm fuzzy on the S2, since it combined kernel + recovery.
Click to expand...
Click to collapse
You could use any kernel in .tar format to load a custom recovery. Philz or siyah kernel are normally used to root the s2, but I think any will work.
Alternatively you could download philz kernel in .zip format. You just need to find the correct kernel for your firmware HERE.
This guide is one of many for basic info on rooting etc
i figured it out, got philz on there for now.
Thanks for the idea of mobile ODIN, i tried flashify. TWRP manager, Rash, and terminal commands and none of them worked... mobile ODIN did however.
Now i get to read up on the custom roms available for the S2
Any recommendations?
Mussels84 said:
Any recommendations?
Click to expand...
Click to collapse
Marshmallow is quite stable now on the S2, so is Lollipop. Any of the recent MM roms are pretty good. I've been running AICP, Oct M, and AOKP recently(MM) and no real major bugs. On lollipop, Oct OS is good and Mokee is still releasing new builds. There are others that are good as well; too many to list...
On kitkat I love Slimsaber by fusionjack(and GreekDragon has released newer builds). Kitkat is a bit more battery friendly than LP or MM.
Many many options
noppy22 said:
Marshmallow is quite stable now on the S2, so is Lollipop. Any of the recent MM roms are pretty good. I've been running AICP, Oct M, and AOKP recently(MM) and no real major bugs. On lollipop, Oct OS is good and Mokee is still releasing new builds. There are others that are good as well; too many to list...
On kitkat I love Slimsaber by fusionjack(and GreekDragon has released newer builds). Kitkat is a bit more battery friendly than LP or MM.
Many many options
Click to expand...
Click to collapse
due to messing around with recoveries and getting into a no-boot situation, i've used the recovery i had to flash dirty unicorns android 6.0.1
hopefully that works, and all is well. So frustrating when recovery + kernel are paired.
edit: DU included the latest TWRP. Bliss.
Mussels84 said:
due to messing around with recoveries and getting into a no-boot situation, i've used the recovery i had to flash dirty unicorns android 6.0.1
hopefully that works, and all is well. So frustrating when recovery + kernel are paired.
Click to expand...
Click to collapse
Well good news on that front. @Lanchon has done some very nice work for the S2 community and come up with a solution to the bundled recovery/kernel. Read up on "isorec" HERE. Basically on the newer MM roms and some later LP roms, the kernel supports this isolated recovery. Just flash the isorec recovery and you have a seperated recovery and kernel
noppy22 said:
Well good news on that front. @Lanchon has done some very nice work for the S2 community and come up with a solution to the bundled recovery/kernel. Read up on "isorec" HERE. Basically on the newer MM roms and some later LP roms, the kernel supports this isolated recovery. Just flash the isorec recovery and you have a seperated recovery and kernel
Click to expand...
Click to collapse
only thing left - repartitioning without ODIN.
found some very vague guides on that...
Mussels84 said:
only thing left - repartitioning without ODIN.
found some very vague guides on that...
Click to expand...
Click to collapse
My first recommendation is if you need a 6.0.1 rom, then wait until your usb port is fixed.
If you don't want to wait for that, then take your time and read the link I gave you over on the DU thread for Lanchons re-pit tool. There is a link near the start of that thread to github where you will find downloads for the tool and a more detailed guide. In the xda thread(the one I linked), there are posts from users that will make clear how to use the tool. Basically you need to rename the file to re-partition how you want your layout
If you are not too worried about android version, then maybe try LP or KK. You don't need to re-partition for these roms as long as you use a pico/minimal gapps package and you will get better battery performance.
noppy22 said:
My first recommendation is if you need a 6.0.1 rom, then wait until your usb port is fixed.
If you don't want to wait for that, then take your time and read the link I gave you over on the DU thread for Lanchons re-pit tool. There is a link near the start of that thread to github where you will find downloads for the tool and a more detailed guide. In the xda thread(the one I linked), there are posts from users that will make clear how to use the tool. Basically you need to rename the file to re-partition how you want your layout
If you are not too worried about android version, then maybe try LP or KK. You don't need to re-partition for these roms as long as you use a pico/minimal gapps package and you will get better battery performance.
Click to expand...
Click to collapse
What i've ran into as a hurdle, is the following:
The latest TWRP doesnt work with that tool, there are no older links on the TWRP website.
The Isolated recovery is now merged with TWRP, so there are no older links there either.
If i can find the recommended 2.8.7.0 i guess it would work.
https://www.androidfilehost.com/?fid=24369303960684130
Edit: That link i posted above was correct and worked to repartition.
Related
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.
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
hi there I've been installing a custom rom in a recovery mode before so i was surprised now with the new method i think of CM 11 nightlies because every time i try to download the zip file on their site it redirects me to download their installer which is new to me and i dont know how to use it? how can i install the Gapps with that installer?
heyjhay said:
hi there I've been installing a custom rom in a recovery mode before so i was surprised now with the new method i think of CM 11 nightlies because every time i try to download the zip file on their site it redirects me to download their installer which is new to me and i dont know how to use it? how can i install the Gapps with that installer?
Click to expand...
Click to collapse
Installer automatically installs the correct gapps file. Nightlies can only be flashed via recovery, not via the installer. Make sure you are downloading the zips from downloads.cyanogenmod.org (or something like that).
gsstudios said:
Installer automatically installs the correct gapps file. Nightlies can only be flashed via recovery, not via the installer. Make sure you are downloading the zips from downloads.cyanogenmod.org (or something like that).
Click to expand...
Click to collapse
Thank you very much for your time already have CM 11 now and it's working fine to me now except the battery because i think it drains fast than my stock rom also the keyboard is a little bit boldy to me
heyjhay said:
Thank you very much for your time already have CM 11 now and it's working fine to me now except the battery because i think it drains fast than my stock rom also the keyboard is a little bit boldy to me
Click to expand...
Click to collapse
Yes. Battery drain is quite common in the s2 with kitkat roms. This is due to the lack of drivers for our device. Reverting back to stock will make battey last as long as the original. You could experiment different roms too. Right now, i'm using slimsaber rom by fusionjack, so far battery is good. (Using it with combination of custom kernel).
gsstudios said:
Yes. Battery drain is quite common in the s2 with kitkat roms. This is due to the lack of drivers for our device. Reverting back to stock will make battey last as long as the original. You could experiment different roms too. Right now, i'm using slimsaber rom by fusionjack, so far battery is good. (Using it with combination of custom kernel).
Click to expand...
Click to collapse
I think you're right that s2 is not compatible for cyanogen rom because I've been using this rom before but I'll remove it because of battery issues ill just try it again maybe the updates fix that issues but i think it's not but i like the feature and the look of their update but still the battery make sense to me anyway maybe I'll try other roms or back to stock
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