###THIS IS EXPERIMENTAL###
#I am not responsible for broken phones, missed calls, missed texts,
#cats destroying your house or anything else that happens.
#Flash this at your own risk.
####THIS DOES NOT WORK ONLY DOWNLOAD IF YOU KNOW WHAT YOU ARE DOING AND ARE ABLE TO RESTORE YOUR PHONE!####
Click to expand...
Click to collapse
Here is the last build of the broken CM build that I am uploading if anybody who know what they are doing can get it working. The boot.img file inside it does not work, you will need to flash the CM-BOOT.img file.
Again:
####THIS DOES NOT WORK ONLY DOWNLOAD IF YOU KNOW WHAT YOU ARE DOING AND ARE ABLE TO RESTORE YOUR PHONE! DO NOT LOOK AT ME IF YOU BREAK YOUR PHONE!####
Broken CM Build.
CM-BOOT.img
XDA:DevDB Information
[EXPERIMENTAL] [UNOFFICIAL] CM13 for R1 HD, ROM for the BLU R1 HD
Contributors
bullet25, ColtonDRG, jasonmerc
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Device Tree: https://github.com/Bullet25fxbx/android_device_blu_p6601
Kernel: https://github.com/Bullet25fxbx/android_kernel_mediatek_mt6735
Version Information
Status: Alpha
Created 2016-09-15
Last Updated 2016-09-15
Okay, So I can't get this working. I can't get BLU to build a boot.img file that works to boot the ROM past the CM logo, and on a boot.img that does boot to the CM logo I can not make heads or tails out of the logcats. I cam going to build one more time with ENG variant of CM and post it for anybody else to mess with. I'm officially done.
reserve 3
Nice to see some development for this device. I may give it a try but my wife may not let me till her work week over.
Really excited to see if this boots or not.
This does not boot/flash please do not try yet. I am looking into it.
Okay I got CyanogenMod recovery working. I'm trying again with the rom itself.
any updates/changes/good news?
KazuDante said:
any updates/changes/good news?
Click to expand...
Click to collapse
I am able to build a working CyanogenMod Recovery that will boot and flash the ROM. The issue currently is that the ROM will not then boot. It will sit at the bootloader splash screen. It appears to be an issue with the boot.img that is being build but I am not 100% sure.
bullet25 said:
I am able to build a working CyanogenMod Recovery that will boot and flash the ROM. The issue currently is that the ROM will not then boot. It will sit at the bootloader splash screen. It appears to be an issue with the boot.img that is being build but I am not 100% sure.
Click to expand...
Click to collapse
from what i seen when i tried to install it last time...it seemed like its more of where and how its installing(flashing the cm13) ....also looking at other cm13 zip files i noticed that the blu r1hd one is missing a file named system.transfer.list......idk if thats important or not but in 5 different cm13 i downloaded to compare they all had it.
also something about releasekey....but what i think is that the way its flashing it....either the mounts arent mounted or its flashing it incorrectly.
bullet25 said:
I am able to build a working CyanogenMod Recovery that will boot and flash the ROM. The issue currently is that the ROM will not then boot. It will sit at the bootloader splash screen. It appears to be an issue with the boot.img that is being build but I am not 100% sure.
Click to expand...
Click to collapse
If the problem is in the kernel, you just need to use stock kernel. CM works with stock kernel, as long as the necessary proprietary "blobs" from the same version of Android were correctly added to the rom. Where are you getting your blobs from, BTW?
KazuDante said:
from what i seen when i tried to install it last time...it seemed like its more of where and how its installing(flashing the cm13) ....also looking at other cm13 zip files i noticed that the blu r1hd one is missing a file named system.transfer.list......idk if thats important or not but in 5 different cm13 i downloaded to compare they all had it.
also something about releasekey....but what i think is that the way its flashing it....either the mounts arent mounted or its flashing it incorrectly.
Click to expand...
Click to collapse
Honestly, not too sure what that is for either, I did look at the contents of the system folder on the phone and its all there.
jacoghi said:
If the problem is in the kernel, you just need to use stock kernel. CM works with stock kernel, as long as the necessary proprietary "blobs" from the same version of Android were correctly added to the rom. Where are you getting your blobs from, BTW?
Click to expand...
Click to collapse
Okay here's where I am going to admit I really don't know what I am doing. I don't even know how to figure out which blobs I need. I am under the assumption that without any blobs the phone should have at least booted but a bunch of stuff would have been force crashing. All of the guides I find are no help too because they do not explain how to figure out which blobs are needed where.
I am using the stock kernel.
bullet25 said:
Honestly, not too sure what that is for either, I did look at the contents of the system folder on the phone and its all there.
Okay here's where I am going to admit I really don't know what I am doing. I don't even know how to figure out which blobs I need. I am under the assumption that without any blobs the phone should have at least booted but a bunch of stuff would have been force crashing. All of the guides I find are no help too because they do not explain how to figure out which blobs are needed where.
I am using the stock kernel.
Click to expand...
Click to collapse
Without the blobs the most you can get is a successfully booted kernel afterwards the blobs are needed
Okay Update. Current issue is I need a selinux permissive kernel for the phone right now. CM does not like the stock kernel which seems to be enforcing. I am attempting to make a permissive kernel but not having much luck at the moment. If anybody has a working permissive kernel for this phone that I can use it would be greatly appreciated. In the meantime I am still working on getting CM booted.
bullet25 said:
Okay Update. Current issue is I need a selinux permissive kernel for the phone right now. CM does not like the stock kernel which seems to be enforcing. I am attempting to make a permissive kernel but not having much luck at the moment. If anybody has a working permissive kernel for this phone that I can use it would be greatly appreciated. In the meantime I am still working on getting CM booted.
Click to expand...
Click to collapse
Can you give me the link to your device tree, i could help
DarkBlood. said:
Can you give me the link to your device tree, i could help
Click to expand...
Click to collapse
https://github.com/Bullet25fxbx/android_device_blu_p6601
I know I'm probably missing things.
bullet25 said:
https://github.com/Bullet25fxbx/android_device_blu_p6601
I know I'm probably missing things.
Click to expand...
Click to collapse
It should be permissive already
DarkBlood. said:
It should be permissive already
Click to expand...
Click to collapse
Okay that's what I thought. The phone bootloops before getting to CM splash screen with the kernel compiled from that. Using the stock kernel the phone doesn't bootloop but doesn't get to the CM splash screen.
bullet25 said:
Okay that's what I thought. The phone bootloops before getting to CM splash screen with the kernel compiled from that. Using the stock kernel the phone doesn't bootloop but doesn't get to the CM splash screen.
Click to expand...
Click to collapse
You should do adb. Secure 0 and start adb at the beginning
Just a small update; We now have CM booting to a logo, but that's it, and can't get a log pulled because regardless of what we do we can't get adb to get out of unauthorized mode.
Related
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
BDogg718 said:
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
Click to expand...
Click to collapse
I'd love to see it on the fascinate! I'm rolling with it on my a500 and its freaking awesome
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
Click to expand...
Click to collapse
You don't have to unlock the fascinate its all open just put cwm on it and flash cm10.1 twrp won't work on cm10 and above so you have to use cwm use this guide here http://forum.xda-developers.com/showthread.php?t=1238070
Sent from my SCH-I500 using Tapatalk 2
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Click to expand...
Click to collapse
cm10 includes it's own "cmupdater" app. Checks for new builds on your schedule (or manually), notifies of new builds, displays change logs, and installs the updates. Works well. It's visible on the "about phone" settings menu. Also available in the app drawer...
Sent from my SCH-I500 using xda premium
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
jt1134 said:
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
Click to expand...
Click to collapse
Nice I've never used twrp so I may have to try it
Sent from my SCH-I500 using Tapatalk 2
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
Click to expand...
Click to collapse
Thanx JT! Back-up and restore work just fine! Great work as always!
BDogg718 said:
Thanx JT! Back-up and restore work just fine! Great work as always!
Click to expand...
Click to collapse
Good to know. Thanks for testing it
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Click to expand...
Click to collapse
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
hhp_211 said:
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I'd love to see this incorporated into the devil kernel
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Thanks jt. It`s a step forward. You da man that's all I can say. :thumbup::beer:
Sent from my SCH-I500 using Xparent Green Tapatalk 2
if you are on fassy, notta posted a pa twp recovery flashable test as of now
LasVegasRomeo said:
if you are on fassy, notta posted a pa twp recovery flashable test as of now
Click to expand...
Click to collapse
does that kernel notta posted kill your WiFi?
kill type ?my wifi is workin I havent had any issues as far as i know. ran wifi a lil bit earlier and no issues. My wifi has is always crappy for me though here at home. Seems spotty a lil but like i said thats normal for me.
jt1134 said:
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Click to expand...
Click to collapse
is there a way to modify the source to use the prebuilt bootimage.Also when compiling it fails to create the utilities folder.
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
I updated to the 4.4.2 ROM and forgot I had replaced my digitizer with Chinese crap. I tried all the available flashable zips but nothing worked with this kernel so I made my own. Took most of the day to get done, but it's done!
Code:
nvflash --resume --download 6 ./newboot.img
UPDATE 4/13/2014
Here is a new version for Namidairo's CM11 3/31/2014 update.
UPDATE 1/26/2014
Here is a new version for Namidairo's CM11 1/23/2014 update.
rayden25 said:
I updated to the 4.4.2 ROM and forgot I had replaced my digitizer with Chinese crap. I tried all the available flashable zips but nothing worked with this kernel so I made my own. Took most of the day to get done, but it's done!
Code:
nvflash --resume --download 6 ./newboot.img
Click to expand...
Click to collapse
Nice work!
Right when I was about to break kernel compatibility.
Edit: Well not really, you just won't have access to the sysfs for fsync toggle. Just recompile when I push it.
Just let me know when you push it and I will recompile it and post it again.
Updat in OP.
rayden25 said:
I updated to the 4.4.2 ROM and forgot I had replaced my digitizer with Chinese crap. I tried all the available flashable zips but nothing worked with this kernel so I made my own. Took most of the day to get done, but it's done!
Code:
nvflash --resume --download 6 ./newboot.img
UPDATE 1/26/2014
Here is a new version for Namidairo's CM11 1/23/2014 update.
Click to expand...
Click to collapse
So this must be flashed through nvflash commands? Or do you have a zip flashable? I'm assuming this is obviously only compatible with CM11?
TappEd from my Note II
Check out my website for encouragement....
www.projectintercession.blogspot.com
Yes, needs to be nvflash only. I do not have a flashable zip. This should work with many of the kitkat cm11 builds out now.
Here is a flashable zip. Warning this is untested, but should work fine.
I tried to flash the zip file, but got a "failed" message. I'm using Voyager2k's modified bl /twrp...
I'm needing a CM11 Kernel and this one the only one I could find. I don't have NVFlash though. Any other way of flashing this? Thanks! :good:
Is there a Kernel for CM11 or KitKat then that is flashable through TWRP??? I am trying install the BAM ROM but I need a Kernel apparently to get it flashed and this is the only one I have found that is KitKat maybe?
Can you make one for the newest build?
golokipok said:
Can you make one for the newest build?
Click to expand...
Click to collapse
I may have to. The old one should work with the latest build (3/31/14) I am going to update to that one right now, if it doesn't work I will make a new one. Didn't think anyone was using this.
rayden25 said:
I may have to. The old one should work with the latest build (3/31/14) I am going to update to that one right now, if it doesn't work I will make a new one. Didn't think anyone was using this.
Click to expand...
Click to collapse
Doesn't work. Phone crashes on mine. Will make a new one and post.
alias4ever said:
Is there a Kernel for CM11 or KitKat then that is flashable through TWRP??? I am trying install the BAM ROM but I need a Kernel apparently to get it flashed and this is the only one I have found that is KitKat maybe?
Click to expand...
Click to collapse
Kernel is device and rom specific. This kernel only works with Slimrom.
rayden25 said:
I may have to. The old one should work with the latest build (3/31/14) I am going to update to that one right now, if it doesn't work I will make a new one. Didn't think anyone was using this.
Click to expand...
Click to collapse
I guess many had dump their prime already . Anyway, I tried it on the 3/6/14 build but screen is still inverted though it was working perfectly on the 2/20/14 build. Do you mind modifying the kernel they are using for data2sd?
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.
I want to start developing my own kernel but I need some basic information about Android Kernel. First thing I wonder if I flash corrupted kernel image, what would happen? Will device goes black screen and become hardware bricked or just turns on and you can see splash screen and not boot up or something like that? I'm asking this because I have Samsung device (which has Odin mode (like other Samsung devices)) and I read in several sites that saying unless you don't corrupt Odin mode partition you can do whatever you want. I really wonder if it's true.
veli.tasali said:
I want to start developing my own kernel but I need some basic information about Android Kernel. First thing I wonder if I flash corrupted kernel image, what would happen? Will device goes black screen and become hardware bricked or just turns on and you can see splash screen and not boot up or something like that? I'm asking this because I have Samsung device (which has Odin mode (like other Samsung devices)) and I read in several sites that saying unless you don't corrupt Odin mode partition you can do whatever you want. I really wonder if it's true.
Click to expand...
Click to collapse
Read this..
http://forum.xda-developers.com/showthread.php?t=3429355
This will help I'm sure.
Sent from my SM-G800F using Tapatalk
spookcity138 said:
Read this..
http://forum.xda-developers.com/showthread.php?t=3429355
This will help I'm sure.
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
I compiled a kernel but I still have questions. Do I have to use NDK version used by kernel that I'm compiling? Why we are have to install wireless module separately? And do recovery mode work separate from kernel. These question are essential for me. Thanks you a lot.
veli.tasali said:
I compiled a kernel but I still have questions. Do I have to use NDK version used by kernel that I'm compiling? Why we are have to install wireless module separately? And do recovery mode work separate from kernel. These question are essential for me. Thanks you a lot.
Click to expand...
Click to collapse
Well, I will answer best I can .I'm no expert,but have compiled kernels for a few devices..
1. I guess you mean the NDK toolchain,either way,you do not. I don't use NDK.
2. Really depends on the kernel I think whether or not you need to add the WiFi module separately. I have never needed to,but its not hard to if you need to I don't think.
3. Also not fully sure what you mean. You will need a custom recovery ,TWRP or such to flash the kernel,but you do not need to build the recovery image with the kernel like you would with a full ROM.
Sent from my SM-G800F using Tapatalk