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.
Related
As we move forward with cm10, Is it better to use TWRP or CWM ? Any advantages to either ? Can one go back and forth ?
sailerph said:
As we move forward with cm10, Is it better to use TWRP or CWM ? Any advantages to either ? Can one go back and forth ?
Click to expand...
Click to collapse
I've been bouncing back and forth (CWM 6.x, TWRP 2.1.4 and 2.2.2). Not sure if that's recommended or not, but its been working for me. YMMV though.
sailerph said:
As we move forward with cm10, Is it better to use TWRP or CWM ? Any advantages to either ? Can one go back and forth ?
Click to expand...
Click to collapse
TWRP has been bullet-proof for me since I installed it. No problems flashing CM7, CM9, or CM10 ROMs, nor other ROMs based on those.
I'm am currently using TWRP to flash Linaro CM10 SGT7 Port For Nook Tablet, but when it reboots i get kicked back to TWRP even tho it was successful
Any ideas? I have had no issues with CWM
CWM it not good for flashing CM10...Surely
The cm9 5.1 cwm can flash all roms those you listen can't flash cm7 roms
Sent from my LG Spectrum 4G LTE using xda premium
shawner47 said:
I've been bouncing back and forth (CWM 6.x, TWRP 2.1.4 and 2.2.2). Not sure if that's recommended or not, but its been working for me. YMMV though.
Click to expand...
Click to collapse
Where did you get CWM 6.x? I thought 5.5.x was the latest. Please link if you have it available.
As far as the OP, I have been flashing everything across the board for my NT with CWM 5.5, it has worked fine for all three CM builds.
DavDoc said:
Where did you get CWM 6.x? I thought 5.5.x was the latest. Please link if you have it available.
As far as the OP, I have been flashing everything across the board for my NT with CWM 5.5, it has worked fine for all three CM builds.
Click to expand...
Click to collapse
have a look here mate
http://forum.xda-developers.com/showthread.php?t=1640958
Ya, I haven't checked in on that thread for a couple months.
Sent using a DINC4G
megaghostgamer said:
The cm9 5.1 cwm can flash all roms those you listen can't flash cm7 roms
Sent from my LG Spectrum 4G LTE using xda premium
Click to expand...
Click to collapse
TWRP 2.1.4 can flash CM7 ROMs without any problems. I haven't updated to TWRP 2.2, yet...
I have been trying to flash Imonseyon leankernel v5.1 for awhile now and I'm having issues... I don't know if the link doesn't work or what the deal is. I want the 184v undervolt bc I have been having crazy battery drain.. Everytime I flash it I get a status 2 in TWRP. Any suggestions..
lacoursiere18 said:
I have been trying to flash Imonseyon leankernel v5.1 for awhile now and I'm having issues... I don't know if the link doesn't work or what the deal is. I want the 184v undervolt bc I have been having crazy battery drain.. Everytime I flash it I get a status 2 in TWRP. Any suggestions..
Click to expand...
Click to collapse
What rom are you using?
If it's a Sense based GB rom, did you grab the Sense kernel?
If it's an AOSP GB rom, did you grab the Aosp kernel?
If it's an ICS rom, it won't work.
***EDIT
Via TWRP website:
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary.
This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated.
If needed, you can try using this update-binary that was compiled with current sources.
It goes in your zip file in the META-INF/com/google/android folder. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
santod040 said:
What rom are you using?
If it's a Sense based GB rom, did you grab the Sense kernel?
If it's an AOSP GB rom, did you grab the Aosp kernel?
If it's an ICS rom, it won't work.
***EDIT
Via TWRP website:
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary.
This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated.
If needed, you can try using this update-binary that was compiled with current sources.
It goes in your zip file in the META-INF/com/google/android folder. If you're getting a status error 2 during zip install, then an outdated update binary is almost certainly to blame.
Click to expand...
Click to collapse
Ok thank you so much! FAST response lol. Would there be another recovery that is better to use or it doesn't matter?? Currently I am using your, I believe, ICS rooted debloated ROM stock/rooted. I was on liquidsmooth aosp and cm7 thundershed switching between them to get a feel for them... But for some reason I tried to do a full wipe and then reinstall from my restore of those two roms and try the leankernal, it's saying failed after I updated to TWRP 2.4.3
**EDIT:
Where is that zip you are talking about located.. In /system or somewhere else bc I can't seem to find it?
There is a backup bug in the latest release of Twrp. Switch to 4ext and your backups may work again. Someone posted on the n7 he could restore backups in Twrp from the previous version with the version he made them with but restoring backups on the latest version couldn't restore those
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
There is a backup bug in the latest release of Twrp. Switch to 4ext and your backups may work again. Someone posted on the n7 he could restore backups in Twrp from the previous version with the version he made them with but restoring backups on the latest version couldn't restore those
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Thank you!
4ext is definitely the way to go on the Thunderbolt. Best recovery ever, wish the Gnex had it.
Sent from my Galaxy Nexus using xda app-developers app
The zip I was referring to, was the kernel zip you were trying to flash.
And if you have run my rom, you should know I suggest using 4ext recovery.
It's mentioned in all my rom OP's.
santod040 said:
The zip I was referring to, was the kernel zip you were trying to flash.
And if you have run my rom, you should know I suggest using 4ext recovery.
It's mentioned in all my rom OP's.
Click to expand...
Click to collapse
Ok thank you! I have switched to 4ext thank you for the refferal
Do you backups work now?
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Do you backups work now?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
No actually.. It's ok though. I don't mind starting over.. Thank you for your help! I am running leankernal now at 184mhz unlocked to see what kind of battery improvements it brings, if any.. With JellyBlur ROM.. Any sugesstion on a ROM?
lacoursiere18 said:
No actually.. It's ok though. I don't mind starting over.. Thank you for your help! I am running leankernal now at 184mhz unlocked to see what kind of battery improvements it brings, if any.. With JellyBlur ROM.. Any sugesstion on a ROM?
Click to expand...
Click to collapse
Good luck with the 184mhz, I can not use that on my phone, always does the deep sleep of death.... thats not a good thing.
As for a ROM, I always suggest one of Santod's ... really any of them lol
Milimbar said:
Good luck with the 184mhz, I can not use that on my phone, always does the deep sleep of death.... thats not a good thing.
As for a ROM, I always suggest one of Santod's ... really any of them lol
Click to expand...
Click to collapse
Dude so far no problems with 184mhz.. Speed is no issue, no lag, no reboots, but I'll have to put it through the 24hr test to fully see how it does. And I charge my battery to 100% when installed it, approx. 4hr 41mins with pretty much none stop usage.. at 72% now. On the old kernal I would have been dead..
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 am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
My CM version
klin1344 said:
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
cm-11-20140407-NIGHTLY-jewel.zip
rohanpatelt7 said:
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Click to expand...
Click to collapse
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Reply
numel007 said:
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
rohanpatelt7 said:
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
Click to expand...
Click to collapse
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Thanks
numel007 said:
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
rohanpatelt7 said:
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
Click to expand...
Click to collapse
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Reply
GoblinZ said:
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Click to expand...
Click to collapse
Thanks! I am going to flash this after my root tonight but just a question, are you going to be following the updates with the nighties? CM's updater won't work will it with your build of it? Thanks!
Hey guys I didn't think it would happen but for those of you that are still running the sm-n900v we now have official support for lineage OS 7.1.2 merged into hltetmo. The only thing that's required is the hlte recovery not the hltevzw recovery. You have to make sure you're on the latest baseband and just wait till today's official build and it will be in there. Also follow the thread link below and you'll see what I'm talking about. I just tested a test build and my data is working great.
https://forum.xda-developers.com/ga...-0-cm14-trader418-unofficial-t3459973/page427
And this is a screenshot of the test build I'm running just to show proof.
alexp1289 said:
Hey guys I didn't think it would happen but for those of you that are still running the sm-n900v we now have official support for lineage OS 7.1.2 merged into hltetmo. The only thing that's required is the hlte recovery not the hltevzw recovery. You have to make sure you're on the latest baseband and just wait till today's official build and it will be in there. Also follow the thread link below and you'll see what I'm talking about. I just tested a test build and my data is working great.
https://forum.xda-developers.com/ga...-0-cm14-trader418-unofficial-t3459973/page427
And this is a screenshot of the test build I'm running just to show proof.
Click to expand...
Click to collapse
Thanks Alexp1289! What is the latest baseband? And have you by chance tested bluetooth on this? Will it connect to a headset or car stereo?
Droidify said:
Thanks Alexp1289! What is the latest baseband? And have you by chance tested bluetooth on this? Will it connect to a headset or car stereo?
Click to expand...
Click to collapse
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery.
Sent from my SM-N900V using Tapatalk
alexp1289 said:
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery. Then flash the hltetmo test build zip or wait for official hltetmo build today. Verizon support is being baked into hltetmo so that's what we have to flash.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-N900V using Tapatalk
alexp1289 said:
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Ok that is what I am on. Will give this a go at some point soon! Thanks
Droidify said:
Ok that is what I am on. Will give this a go at some point soon! Thanks
Click to expand...
Click to collapse
I've only gotten a couple random reboots so far but other than that it's going great.
Sent from my SM-N900V using Tapatalk
great news bobby
I've flashed it and no signal what's so ever tried 7 different ones I'm on of1 as well as unlocked
happydad4130 said:
I've flashed it and no signal what's so ever tried 7 different ones I'm on of1 as well as unlocked
Click to expand...
Click to collapse
Go to that thread I posted and ask for help. You must be doing something wrong because I'm on Verizon and everything works great on this rom.
What room did u download and what did u do when the room does boot it only boots to safemode and still no signal I'm not.a noob but damn
..
happydad4130 said:
What room did u download and what did u do when the room does boot it only boots to safemode and still no signal I'm not.a noob but damn
..
Click to expand...
Click to collapse
Download 20170719:
https://download.lineageos.org/hltetmo
You also need to have TWRP for hlte installed:
https://dl.twrp.me/hlte/twrp-3.1.1-0-hlte.img.html
And flash that recovery image with flashify:
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Don't forget to download a gapps package (arm 7.1):
http://opengapps.org
You need to make sure your Verizon note 3 is on the lastest baseband which is SEPL1 if it's not you needed to flash this using Odin 3.09 here's the baseband file to flash in Odin:
https://www.androidfilehost.com/?w=files&flid=199473
Here's where you get Odin:
http://androidhost.org/PVAIv
Follow the thread link in the OP for support and submitting bugs after flashing lineage.
This ROM is working flawlessly! I am using a different kernel to add fast charge and new CPU governors. Heavy use for the past 4 days and no problems at all!
https://forum.xda-developers.com/ga...lte-synergy-kernel-la14-1-based-roms-t3612028
alexp1289 said:
You need to make sure your Verizon note 3 is on the lastest baseband which is SEPL1 if it's not you needed to flash this using Odin 3.09 here's the baseband file to flash in Odin:
Click to expand...
Click to collapse
Can you clarify the requirement for the SEPL1 baseband? Your screenshot in the OP shows OF1 as your baseband.
Thanks!
nicky666s said:
Can you clarify the requirement for the SEPL1 baseband? Your screenshot in the OP shows OF1 as your baseband.
Thanks!
Click to expand...
Click to collapse
I was wrong earlier I had to update mine. OF1 works but SEPL1 is preferred since it's the lastest.
cssr said:
This ROM is working flawlessly! I am using a different kernel to add fast charge and new CPU governors. Heavy use for the past 4 days and no problems at all!
https://forum.xda-developers.com/ga...lte-synergy-kernel-la14-1-based-roms-t3612028
Click to expand...
Click to collapse
FYI: After flashing Synergy Kernel I lost root and Reflashing SuperSU did not work. I had to flash Magisk-v13.3 after flashing the kernel and it fixed the root problem.
http://www.stechguide.com/download-magisk-v13-3/
Also, note that if you install Magisk, it will have to be uninstalled before you do an update. If you don't, it will update and you will get an error. You can still uninstall Magisk and install the update again and then reinstall Magisk. If you change the kernel again.
@ golfslicer
I had the same problem after updating the kernel and also use the same solution. Was going to post about it but, you beat me to it.
Lineage also has root (SU) solution.
https://download.lineageos.org/extras
CIFS/SMB & NFS network share
Does anyone know how to mount a cifs/smb (or nfs) share with LineageOS?
bash script that I used with Aryamod 6.5 & 6.6 & SManager no longer works with LOS. Manually trying to mount from the LOS builtin terminal or Term. Emulator (installed from Play Store), also doesn't work.
Thanks in advance.
P.S. Also can I make this permanent by editing fstab, so that the network share is mounted on boot?
I personally don't use file sharing. But a quick search for Samba(smb) will probably give you all the help you need.
Still getting a really bad echo on this mod, same as i did on the unofficial port of CM13. Any recommendations? Thanks for any help offered.
Flashed this ROM a few days ago and had no problems with it yet. Installation was a breeze. Wiped system, data, and cache, then flashed the ROM and open gapps with twrp and it booted right up. I'm using it as a daily driver at this point because it is so stable! Love stock android! Was very pleased to hear the note 3 now has official support!