Related
I couldn't find an answer on the threads. I rooted my at&t last night w entropy512s one click kernel and root. Well I'm new to the phone tech so it took me a while. I now cannot use any of the market Hotspot apps to run my tablet off my s2 wifi. I could before the root and from what I was told it should be easier to do this after rooting. Am I missing something? Is there a special way I have to do it now? I'm so confused.
Sent from a still, small voice with help from my Galaxy s2.
I'm not familiar with those applications. I don't know any reason they would not work. And it's not clear from your post what exactly the problem is. You mean you can't install them, or that they do not produce a wifi signal even though installed?
Anyway, almost all custom roms include portable wi-fi hotspot, as well as usb tethering and sometimes bluetooth tethering. Since you have rooted, why don't you go ahead and pick a custom rom and put that on. Problem solved.
There is a good guide linked in my signature.
Yeah, once you have a custom rom, just use the built-in tethering. Works great for tablets.
Yea I can install them, I've tried a few of them and none put out a wifi signal. I don't know what rom I should flash yet. Since I did the entropy512s one click root+ kernel I understand that the kernel is gingerbread, does that mean I need a gingerbread rom? I was hoping for the latest, greatest build. Any guidance is GREATLY appreciated as it took me hour just to root. Lol
Sent from a still, small voice with help from my Galaxy s2.
nednerbish said:
Yea I can install them, I've tried a few of them and none put out a wifi signal. I don't know what rom I should flash yet. Since I did the entropy512s one click root+ kernel I understand that the kernel is gingerbread, does that mean I need a gingerbread rom? I was hoping for the latest, greatest build. Any guidance is GREATLY appreciated as it took me hour just to root. Lol
Sent from a still, small voice with help from my Galaxy s2.
Click to expand...
Click to collapse
Since you used Entropy512's package to root, you have a stock kernel. In order to install custom firmware, you need to first install a custom kernel that contains ClockworkMod Recovery onto your phone. That kernel must be Gingerbread. However, once you have the kernel and CWM installed, you can then flash any firmware you choose, Gingerbread, ICS or JB.
The guide which is the first link in my signature contains all the info you need.
Fantastic. Thank you so much for your time. I will try first chance I can.
Sent from a still, small voice with help from my Galaxy s2.
I will give you two pieces of advice:
1: Follow the instructions given to you by Creepy (and any instructions in the OP of ROMS) to the T.
2: Read then read some more. When you're done with that, read it all over again. Afterwards, follow step 2 again. This goes for searching about any issue you may come across.
Have fun, this device is really amazing once you figure out more about it
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
I thank you. I will. I'm so confused about this stuff but it seems the more I read I am really UNDERSTANDING what it means. But it takes about 10 read throughs.
Sent from a still, small voice with help from my Galaxy s2.
Ok I was told to get entropys dd kernel since it had cwm with it. I guess thats the next step correct?
Sent from a still, small voice with help from my Galaxy s2.
Use creepy's guide Ned! You need to figure out what your next step is.
Im on the mobile tapatalk (on vacation), So i cant use my computer to reaserch the xda site easily. Im trying to learn as much as possibe before i get home and actually do it.
Sent from a still, small voice with help from my Galaxy s2.
Good plan. When you get the cwm kernel, do a nandroid backup then pick any rom you like... (cm10 nightly just came out, if you like jellybean)
AOKP by Task650 is another JB alternative.
Which is better you ask? Gonna have to try them both! They both offer stability and great user experience for most who try them. Maybe you're a GB or an ICS kinda guy though!
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
It really doesn't matter much which kernel you choose for the next step, because it's only on your phone for a short time. Assuming you rooted with the Gingerbread stock plus root package, then you need a custom Gingerbread kernel which has ClockworkMod Recovery. I believe the links in my guide for the kernels are still working links.
The root I did said it was root + kernel. I take it the one with the entropy512 one click root+ kernel doesnt include the cwm. Im sorry im jist trying to understand the whole process not just do it. Alot of what i read doesnt click. Loke when I rooted it took me 6+ hours because I didnt know you want to save the file not open it when downldng it. also I read the deleting the tethermanager2.apk will open wifi/tether. True?
Sent from a still, small voice with help from my Galaxy s2.
Forget i asked. I re read your comment. Ok its a stock kernel. So it wouldnt. I understand. A stock kernel probably would make it easier to return to stock. right?
Sent from a still, small voice with help from my Galaxy s2.
nednerbish said:
Forget i asked. I re read your comment. Ok its a stock kernel. So it wouldnt. I understand. A stock kernel probably would make it easier to return to stock. right?
Sent from a still, small voice with help from my Galaxy s2.
Click to expand...
Click to collapse
Essentially, yes, but if you're going for custom ROMs, that's not what you want. There are easy ways of getting back to stock if all else fails.
You gotta know what you want first, before you move forward. I know you want tethering to work, and people here have recommended moving to a custom ROM because tethering does not seem to work for you on rooted, stock ROM and stock kernel. So do you want a custom ROM instead (you'll lose some of your current data via that route)? Or do you not care about ROMs and you just want wifi tethering to work now that you're rooted?
Assuming you want just the latter of the two options, I would recommend that you first try a custom kernel (this is different from a custom ROM, but note most custom ROMs include a custom kernel upon install). You mentioned Entropy's Daily Driver Gingerbread kernel, which is a great one. I'd recommend installing it and seeing if that fixes your wifi tethering problem. To install, use Mobile Odin lite version; you can find that apk in Creepy's guide. Download and save the zip from Entropy's DD thread, then extract the zImage file from it (make sure to use the name "zImage", no file extension, important) and move that to your phone via USB mounting. After that, in Mobile Odin lite navigate to the zImage file and flash it; viola, you now have Entropy's custom Gingerbread kernel and stock GB ROM. All custom kernels include ClockworkMod (no other way to get it), so you have that too.
If the custom kernel alone does not fix your wifi tethering problem, then maybe it's time to move to a custom ROM. With CWM, you can flash anything (ROMs, kernels, what have you) much more easily, but we'll get to that after you get the kernel, which is part of the process anyway.
These instructions are all repeated in paragraph 3a of Creepy's guide, and more information is written there, so I would recommend reading it thoroughly so you do understand. I know it's frustrating at first, but you'll get it, and you seem like the type to eventually get it right and understand what you're doing.
THANK YOU!!! I will try that tonight. That was very helpful info. So I CAN do this right from phone the? I saw there were some Apps that can do stuff like that but wasn't sure if they worked. I think I saw one linked to the superuser app. Ill keep you updated
Sent from a still, small voice with help from my Galaxy s2.
I also want a new rom also. I'm just trying to get there. LOL
Sent from a still, small voice with help from my Galaxy s2.
[Chinese accent] Have patience, Grasshopper.
Hi, I successfully flashed my T-mobile Vibrant about twelve months ago to a custom 2.2 Froyo rom (Trigger 3.2 Final). It's a great rom and EVERYTHING works. However lately I've read rave things said about newer roms such as ICS passion. It's been a while and I'm still a noobie at this so my question is:
What is the easiest way to get to ICS passion from my current custom Froyo rom ? Thanks ~ Chris
hi,
Its very easy to get ICS running on your vibe. There may be various ways to proceed. I ll give you what I did (AFTER failing for 5-6 times )
Odin back to stock (It may be not necessary. But I started from the beginning which is better AFAIK )
Then stored ICS ROM (ICZen which in my case) and update.zip (CWM) on internal SD
then flashed GB Bootloaders (It also may/ may not necessary. But I did it b/c I already had many failed attempts)
Then flashed CM7 first
After that flashed ICS on top of it
Worked at last for me
NOTE: Please read relevant instructions provided by ROMs b/c flashing one may differ from flashing another.
You can find more information if you run into problems in my thread [SOLVED]Cannot install ICS ROM--please HELP
link: http://forum.xda-developers.com/showthread.php?t=1752937
tc
Happy Flashing
You may just want to read this before flashing ICS. http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my SGH-T959 using Tapatalk 2
^^^ Truth
And I would suggest staying away from Passion. It is based on 4.0.3 and there was a pretty significant code upgread when ICS went to 4.0.4.
IIRC, Passion is the last ROM that still uses 4.0.3 and is probably why it is dead now (but for some reason lives in infamy on YouTube and Google Search).
Haarsh's way works just fine but here is another method as another option too.
Thanks
Thanks for the replies. This is why I subscribed to the forum.
mmm... I see a few pitfalls ahead.
Background info from me is that I can't use Odin on my Linux computer. Never really got into Heimdall. I flashed my first rom by downloading the rom zip file and put it on my phone's internal sd card then let clockwork do the rest, ie nandroid backup and flash the rom from the update zip. I'd like to do the same again.
Ok, it's my understanding that anything above 2.2 needs the GB bootloader so the first step is to install that over my Trigger rom. I think Trigger would still run with the GB bootloader at that stage. Next download an update zip of a rom of my choice, put it on my phone's sd, then flash it with Clockwork.
Seems to me that should work or am I missing something I wonder ?
You can flash the GB bootloader. Its backward compatible so it will work with any ROM currently available.
Download the .zip of the ROM you want, and any Gapps if applicable. Then just follow the instructions on page 1 of the ROM (OP).
The usual would be Wipe Data/Factory Reset, Clear Cache, Clear Dalvik. Flash ROM, flash Gapps, restart. The instructions will tell you all you need to know.
If something goes wrong, give us a shout. That's what we're here for.
help me plz
hi mate i know this is quite outdated maybe but im searching for Samsung T959 stock rom Froyo 2.2 that i search everywhere but didnt find. Can you help me for any link ?
or please suggest me someone.
Thanks in advance.
castan said:
Hi, I successfully flashed my T-mobile Vibrant about twelve months ago to a custom 2.2 Froyo rom (Trigger 3.2 Final). It's a great rom and EVERYTHING works. However lately I've read rave things said about newer roms such as ICS passion. It's been a while and I'm still a noobie at this so my question is:
What is the easiest way to get to ICS passion from my current custom Froyo rom ? Thanks ~ Chris
Click to expand...
Click to collapse
I've been keeping half an eye on developments with CM9/10 for the Galaxy Tab 10.1 over the last few months and I'd now like to take the plunge and start using the CM10 nightlies on my P7510.
My wifi only Tab is currently running stock ICS 4.0.4 and has NOT been rooted. Looking through the threads in this forum, it looks like I need to first flash a custom recovery (pershoot's CWM?) and then I can use the custom recovery to flash CM10.
Last night, I tried following the instructions on CyanogenMod's wiki page for the P7510 but hit a problem very early on with the Heimdall utility reporting a protocol error during the recovery flashing. It seems a few people are having this problem and it may be a bug in the Heimdall utility.
Other methods I have read about include this super-easy method (but unfortunately that does not work for stock ICS devices) and also using ODIN, which I believe to be Windows only. I'm running Ubuntu on my laptop but do have access to a Windows machine if need be.
Could anyone offer some advice on the simplest way to go about doing this, specifically for taking a stock ICS 4.0.4 P7510 to running CM10 nightlies?
Thanks!
Hi. Recently tried to do exactly the same thing i.e. install CWM and then CM10 (which by default is rooted) and had the same problem.
I used ODIN instead. My guide through the process was s0ckm0nkys '[How-To] Root/Unroot The SGT 10.1 GT-P7510 USA Retail WiFi HoneyComb Only' pinned thread at the top of the android development sub-forum for the galaxy tab, which has some good links to youtube videos which help - just be careful of any files linked to as they are out of date (don't let the title put you off as all you are interested in is installing CWM).
The rest of the process as per the cyanogenmod wiki worked for me.
be aware that although you will have access to OTA updates after this which make this whole process much easier on an ongoing basis, I don't believe this will work for the upcoming CM10.1 which seems to require a reinstall.
I hadn't thought to look in the development sub-forum but that looks like a great thread, thanks!
After my initial post, I actually went ahead and borrowed a Windows PC to use ODIN to flash pershoot's ClockworkMod 5.5.0.5 to my Tab. I'm happy to report all went well! I've just done a nandroid backup so before I go ahead and install CM10, I'm going to check out those videos, just in case there's anything I should make note of.
Cheers mate, and thanks for the heads-up on the CM10.1 reinstall thing. I'll hopefully be posting back here shortly when I'm running CM10.
Now running the latest CM10 nightly (20121217) and all good so far.
For anyone in same boat as I was a couple of hours ago, check out the videos in the thread tomorrowmanuk mentions above and you'll be up and running in no time. The only changes I made were to use a more recent ClockworkMod recovery than shown in the videos. I used 5.5.0.4 which at this time is the latest one provided by pershoot (I think).
monkeyhybrid said:
Now running the latest CM10 nightly (20121217) and all good so far.
For anyone in same boat as I was a couple of hours ago, check out the videos in the thread tomorrowmanuk mentions above and you'll be up and running in no time. The only changes I made were to use a more recent ClockworkMod recovery than shown in the videos. I used 5.5.0.4 which at this time is the latest one provided by pershoot (I think).
Click to expand...
Click to collapse
Congrats I found the CM10 update definitely gives the tab a new lease of life.
tomorrowmanuk said:
Congrats I found the CM10 update definitely gives the tab a new lease of life.
Click to expand...
Click to collapse
Yep, it does that alright. I'm looking forward to CM10.1 too, for Android 4.2's multiple user support so me and my misses can both use it without messing around with each other's settings all the time.
By the way, do you find CM10's default font looks a little less smooth at small sizes than the older stock one?
Does everything on the Tab work with the latest CM10 nightlies (cameras, mic, etc)?
kielby said:
Does everything on the Tab work with the latest CM10 nightlies (cameras, mic, etc)?
Click to expand...
Click to collapse
As far as I can tell, everything is working well so far. Front and rear cameras work although possibly a bit of lag on the front camera's live preview (which I have seen reported elsewhere). I had also read that 720p recording with the rear camera wasn't working on earlier builds but seems to work fine on mine with the latest nightly (20121217). The camera preview for the rear video camera does not fill the screen for some reason but doesn't stop anything working. A quick test just now of the microphone shows that as working too.
I'm only half a day in to testing, reinstalling some apps, etc, but it's been very smooth and pain free. The interface is definately smoother now, both on the homescreen and within apps. I'm happy to say goodbye to TouchWiz too.
I'll post back here if I hit any problems or bugs.
monkeyhybrid said:
Yep, it does that alright. I'm looking forward to CM10.1 too, for Android 4.2's multiple user support so me and my misses can both use it without messing around with each other's settings all the time.
By the way, do you find CM10's default font looks a little less smooth at small sizes than the older stock one?
Click to expand...
Click to collapse
Can't say I'd noticed any major font differences.
With regards 10.1, the earybird version has popped up on pershoot's droidbasement.com/db-log (man deserves a medal for his work on this tab). Will keep an eye on CM10 preview development thread to determine when to jump to 10.1
tomorrowmanuk said:
With regards 10.1, the earybird version has popped up on pershoot's droidbasement.com/db-log (man deserves a medal for his work on this tab). Will keep an eye on CM10 preview development thread to determine when to jump to 10.1
Click to expand...
Click to collapse
Ah, coool! It's great to hear pershoot is on the case. Top man! I'll keep an eye on his blog for developments...
Went ahead and updated my wife's Galaxy Tab last night, everything went smoothly and Tab is working great.
I think I followed pretty much the same instructions as instructions as you:
1) Installed Samsung USB drivers and downloaded Odin 3.0.7
2) Flashed CWM 5.5.0.4 from pershoot using Odin
3) Downloaded latest CM 10.0 nightly from get.cm for Galaxy Tab, and 10.0 gapps to sdcard
3) Booted into recovery, created nandroid backup
4) Factory wiped, wiped cache, wiped dalvik cache
5) Flashed CM, then gapps
6) Reboot
Thanks for the heads up that prompted me to look into this again!
I'd recommended you to use ODIN instead the other things
1. Copy the .zip to /sdcard root
2. Flash ClockWordmod 6.x.x with ODIN 1.85 (You can find this in Development Area/Google it)
3. Apply .zip through ClockWordmod. Don't forget to Wipe Cache&Dalvik Cache
4. You're done, i've been using pershot's build for more than two month. His build are really stable with a minor bugs.
And the CyanogemMod 10.1 Android 4.2.1 is seriously fast. I would recommended this to you
hope this helps!
I have read through the forums and am hesitant to post, but I am stuck. I have rooted my Note II using Causal and following the tutorial after Verizon's first update.It worked great. I am not using a custom rom, but have the TRWP recovery, super user, busy box installed; I am certain that was part of the Casual Root (thank you Adam). I have also updated Casual to NoYouVerizon, but realized that my phone is already rooted. I want to update to 4.1.2 and have read to not do so OTA. Would someone please either provide a link or directions on how to update I did download the stock Root Odex - I605VRAMC3 on both my PC and my Note II, but have no idea what to do with it.
Thank you
I was in exact same scenario as you. I was rooted and was just using themes but the only way to get updated was to use a custom rom. I may be wrong but that was my way of updating. Since then I have flashed just about every rom out there that is touchwiz. Been happy with the Beans build 17.
Hope this helps!
Sent from my SCH-I605 using Tapatalk 2
SAVJR said:
I have read through the forums and am hesitant to post, but I am stuck. I have rooted my Note II using Causal and following the tutorial after Verizon's first update.It worked great. I am not using a custom rom, but have the TRWP recovery, super user, busy box installed; I am certain that was part of the Casual Root (thank you Adam). I have also updated Casual to NoYouVerizon, but realized that my phone is already rooted. I want to update to 4.1.2 and have read to not do so OTA. Would someone please either provide a link or directions on how to update I did download the stock Root Odex - I605VRAMC3 on both my PC and my Note II, but have no idea what to do with it.
Thank you
Click to expand...
Click to collapse
The best way to do it would be to flash a rom through recovery, and only a rom made for flashing in recovery (ie a .zip, NOT a tar.md5).
You need to figure out which rom you want, download it, make sure the md5 checksum matches, and the flash the zip in your recovery.
There are quite a few choices for stock TW roms, and everyone had a favorite, but you have to decide which you would want and if you want any of the added features. Here are a few of the more popular stock roms that are the latest update from Big Red:
Stock Odex/Deodex:
http://forum.xda-developers.com/showthread.php?t=2108510
This is just the latest straight Verizon stock rom and you can choose the original odex or get the deodexed version if you want to theme your phone because having a deodexed room makes themeing easier and less glitchy.
Beans 17:
http://forum.xda-developers.com/showthread.php?t=2032447
This is the latest Verizon stock rom with a few added tweak and it is themed to look like an AOSP rom.
CleanRom VZW SE 3.1
http://forum.xda-developers.com/showthread.php?t=2073390
This is the latest Verizon stock rom but it had been completely debloated and had an Aroma installer so you can choose what all you want to be present in the rom. It is different from CleanRom ACE. CleanRom ACE is the latest international Note 2 rom that had been modified to work on our phones, it usually has more updates and features than CleanRom VZW SE because CR VZW SE is the Verizon stock rom with very little added. All CleanRom roms have bloatware removed.
You also need to flash the latest radio along with your new rom if you want the newest radio that came with the VRAMC3 update, the radio will be the VRAMC3 one.
Radios:
http://forum.xda-developers.com/showthread.php?t=2108510
Sent from my SCH-I605 using XDA Premium HD app
Thank you - Can the ROM be flashed from a SD Card or does it have to be on the internal card. ?
shangrila500 said:
The best way to do it would be to flash a rom through recovery, and only a rom made for flashing in recovery (ie a .zip, NOT a tar.md5).
You need to figure out which rom you want, download it, make sure the md5 checksum matches, and the flash the zip in your recovery.
There are quite a few choices for stock TW roms, and everyone had a favorite, but you have to decide which you would want and if you want any of the added features. Here are a few of the more popular stock roms that are the latest update from Big Red:
Stock Odex/Deodex:
http://forum.xda-developers.com/showthread.php?t=2108510
This is just the latest straight Verizon stock rom and you can choose the original odex or get the deodexed version if you want to theme your phone because having a deodexed room makes themeing easier and less glitchy.
Beans 17:
http://forum.xda-developers.com/showthread.php?t=2032447
This is the latest Verizon stock rom with a few added tweak and it is themed to look like an AOSP rom.
CleanRom VZW SE 3.1
http://forum.xda-developers.com/showthread.php?t=2073390
This is the latest Verizon stock rom but it had been completely debloated and had an Aroma installer so you can choose what all you want to be present in the rom. It is different from CleanRom ACE. CleanRom ACE is the latest international Note 2 rom that had been modified to work on our phones, it usually has more updates and features than CleanRom VZW SE because CR VZW SE is the Verizon stock rom with very little added. All CleanRom roms have bloatware removed.
You also need to flash the latest radio along with your new rom if you want the newest radio that came with the VRAMC3 update, the radio will be the VRAMC3 one.
Radios:
http://forum.xda-developers.com/showthread.php?t=2108510
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
SAVJR said:
Thank you - Can the ROM be flashed from a SD Card or does it have to be on the internal card. ?
Click to expand...
Click to collapse
Either or. Just navigate to the folder that it's in.
Sent from my SCH-I605 using xda app-developers app
SAVJR said:
Thank you - Can the ROM be flashed from a SD Card or does it have to be on the internal card. ?
Click to expand...
Click to collapse
I generally move mine to my external SD because I like to wipe the entire internal memory when flashing to a competent different rom to get rid of all the filets and miscellaneous crap that I let accumulate so it'll be like a freshI new phone.
Then again I have a 64 GB micro SD card and keep several different releases of each rom I use along with all the recovery flashable kernels, radios, GAPPs, current version of TWRP and CWM, a couple previous releases of TWRP and CWM, miscellaneous mods, and various other flashable stuff.
Really its all up to you though. I like to keeo everything perfectly arranged in its own folder in my external and leave the internal for apps, if you want evening on your internal you can do that too!
Just remember if you choose to wipe your internal memory before flagging like I do then itll delete EVERYTHING on your internal SD card so you'll need to back up your media (pictures, videos, and music) because itll be deleted. You don't have to wipe your internal memory and it won't hurt anything if you choose to wipe it or if your choose not to hurt anything, it's completely up to you!
Sent from my SCH-I605 using XDA Premium HD app
Thank you
Thank you, you have been a great help. I was able to flash Scotts Rom CleanRomAce last night and worked without a hitch. I assume, from what I have read, that I can flash any Rom or updated Rom over this, when the time comes. Just curious, which one do you favor.
Thank you Again for taking the time to help me.
shangrila500 said:
I generally move mine to my external SD because I like to wipe the entire internal memory when flashing to a competent different rom to get rid of all the filets and miscellaneous crap that I let accumulate so it'll be like a freshI new phone.
Then again I have a 64 GB micro SD card and keep several different releases of each rom I use along with all the recovery flashable kernels, radios, GAPPs, current version of TWRP and CWM, a couple previous releases of TWRP and CWM, miscellaneous mods, and various other flashable stuff.
Really its all up to you though. I like to keeo everything perfectly arranged in its own folder in my external and leave the internal for apps, if you want evening on your internal you can do that too!
Just remember if you choose to wipe your internal memory before flagging like I do then itll delete EVERYTHING on your internal SD card so you'll need to back up your media (pictures, videos, and music) because itll be deleted. You don't have to wipe your internal memory and it won't hurt anything if you choose to wipe it or if your choose not to hurt anything, it's completely up to you!
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
SAVJR said:
Thank you, you have been a great help. I was able to flash Scotts Rom CleanRomAce last night and worked without a hitch. I assume, from what I have read, that I can flash any Rom or updated Rom over this, when the time comes. Just curious, which one do you favor.
Thank you Again for taking the time to help me.
Click to expand...
Click to collapse
When an updated version of Cleanrom comes out you can dirty flash over the current version you are running, however I ALWAYS clean flash Cleanrom because usually the only reason Scott updates it is to fix an issue, rarely because there aren't many, and when a new version comes out. When a new version comes out I like to clean flash, and its recommended to clean flash BTW, because dirty flashing can lead to all kinds of bugs. As for AOSP it is generally recommended to clean flash because it is more lrone to bugs because its constantly updated. Whenever you flash a different rom though, like from Cleanrom to Beans or CR to anything else, you ALWAYS clean flash it.
Just in case you dont know what a clean flash and a dirty flash are:
Clean is when you do the wipes explained in the OP of every rom thread.
Dirty is when you flash a rom over your current one without wiping anything.
if I am going to use TW I am going to use Cleanrom, its just a personal preference. Some people love Beans because it is modded to look like AOSP, personally I would rather run AOSP. As for AOSP I prefer ParanoidAndroid (aka PA or AOSPA) and Vanilla RootBox (aka VRB or RB). I prefer VRB more than PA lately though because for me it seems more stable at the current time, when HALO is finally released for PA I will most definitely test it out and may switch back until VRB kangs it. Really you should run any that tickle your fancy out and see what you think of them before deciding on just one.
Sent from my SCH-I605 using XDA Premium HD app
Okay - Maybe you can help me one more time...So I dirty flashed over CleanRom ACE to try Beans17. I didn't like it and flashed back to ACE. Everything was working fine until I realized ACE doesn't support Verizon Visual VM. No real big deal, but I use it regularly. So II was going to flash to CLeanRom SE and when I went to do so, I soft bricked my phone (Triangle of Death). I read through the threads and read Adams post to flash back to stock using Odin (downloaded the correct pit file and tar, but Odin will not recognize the device. I tried new cables, ports and installed the latest Samsung USB drivers. Am I stuck taking it to Verizon?
shangrila500 said:
When an updated version of Cleanrom comes out you can dirty flash over the current version you are running, however I ALWAYS clean flash Cleanrom because usually the only reason Scott updates it is to fix an issue, rarely because there aren't many, and when a new version comes out. When a new version comes out I like to clean flash, and its recommended to clean flash BTW, because dirty flashing can lead to all kinds of bugs. As for AOSP it is generally recommended to clean flash because it is more lrone to bugs because its constantly updated. Whenever you flash a different rom though, like from Cleanrom to Beans or CR to anything else, you ALWAYS clean flash it.
Just in case you dont know what a clean flash and a dirty flash are:
Clean is when you do the wipes explained in the OP of every rom thread.
Dirty is when you flash a rom over your current one without wiping anything.
if I am going to use TW I am going to use Cleanrom, its just a personal preference. Some people love Beans because it is modded to look like AOSP, personally I would rather run AOSP. As for AOSP I prefer ParanoidAndroid (aka PA or AOSPA) and Vanilla RootBox (aka VRB or RB). I prefer VRB more than PA lately though because for me it seems more stable at the current time, when HALO is finally released for PA I will most definitely test it out and may switch back until VRB kangs it. Really you should run any that tickle your fancy out and see what you think of them before deciding on just one.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
SAVJR said:
Okay - Maybe you can help me one more time...So I dirty flashed over CleanRom ACE to try Beans17. I didn't like it and flashed back to ACE. Everything was working fine until I realized ACE doesn't support Verizon Visual VM. No real big deal, but I use it regularly. So II was going to flash to CLeanRom SE and when I went to do so, I soft bricked my phone (Triangle of Death). I read through the threads and read Adams post to flash back to stock using Odin (downloaded the correct pit file and tar, but Odin will not recognize the device. I tried new cables, ports and installed the latest Samsung USB drivers. Am I stuck taking it to Verizon?
Click to expand...
Click to collapse
Not yet you aren't, you don't take it to them until its a last resort. this is just a driver issue.
Thats also why I said you needed to clean flash different roms, if you were updating from Cleanrom ACE 4.9 for 5.0 a dirty flash would be acceptable but if you experienced bugs you would have had to go back and clean flash before you could report those bugs and get help from the guys in the CR thread. When flashing completely different roms you ALWAYS clean flash.
Did you put the phone in download mode before connecting to Odin? What OS is your computer on? Do you have both the drivers from droidstyles guide and Kies installed?
I will help you with the driver issue as much as i can but you should really really really create a new thread in the Q&A section about this so it will get more views and maybe Hopesrequiem, droidstyle, and some of the other members who trouble shoot the driver issues can help. You should title it something like Odin driver issue with a soft brick, they'll need to know what OS youre using, what version of Odin you're using, and a lot of other stuff. Before you do that though I have a thread I am going to link in my next post here and I want you to read it and do what it says.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 09:30 AM ---------- Previous post was at 09:26 AM ----------
Here is the link I said I would post, read the OP and do what he did and see if that fixes your issue with Odin not seeing your phone.
http://forum.xda-developers.com/showthread.php?t=2304481
Also remember when youre using Odin to put your phone into Download Mode and to launch Odin before you plug your phone in.
Sent from my SCH-I605 using XDA Premium HD app
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