My AT&T Samsung Captivate i897 has gone bad so I just purchased a used Note i717 (i tis on the way). I like the larger format, dual cameras +flash, LTE speed.
The phone is already in stock ICS 4.04 (build UCLF6). I would like to 1) root, 2) add CWM, 3) flash to final CM9 stable (like I have on my Captivate). I have read and read threads and posts to the point that I am a little dizzy. My questions are:
1) what is the best way for ICS 4.04 stock to be rooted and injected with CWM (the posts all seem to be targeted at the original GB)?
2) if I get in trouble and brick it (always seems to happen on my root attempts), is there a SuperOneclick or Heimdall or Odin approach that will push stock software (or any) so that I can retry 1 - in the past Heimdall was the savior)?
Thank you and I look forward to participating in this forum :good:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
gregsarg said:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
Click to expand...
Click to collapse
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
tonyo123 said:
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
Click to expand...
Click to collapse
Go to the last page in that thread. I posted an easy, fool-proof root method. It was simple enough that even I could do it.:laugh:
root for the ICS 4.0.4 is easy....
It consists of Odin pushing a CWM image, and flashing SU from your new found recovery.
But there are a few tips that will help you out...
follow teyshablue...and you'll be rooted in 10 minutes....g
THANKS
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
tonyo123 said:
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
Click to expand...
Click to collapse
Yeah, the video tutorial saved my bacon!:good:
Okay I'm planning on doing similar tonight with my newly arrived refurbed i717. It shipped with ICS.
I'm confused however...if I simply want to flash a custom ROM (versus running rooted stock ICS), I've seen threads stating that I don't need Root, but instead install TWRP2 via Odin from here:
http://forum.xda-developers.com/showthread.php?t=1584576
...then flash custom ROM via TWRP2 recovery.
Am I missing something? Searching on Q&A seems to indicate some worrying issues about attempting this method of root on these refurbed Note's running ICS:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
TIA
Root is your first step.....as you need the custom recovery to flash the roms...
ultimately.....pushing a recovery via Odin, is giving you root....g
You don't need to root to flash a ROM. You can flash cwm through Odin then flash the twrp zip if that's the recovery you desire. I'm not sure if all the bugs are worked out on the twrp Odin tar. Once you flash a recovery, you can make a backup of your stocker and then flash your ROM of choice. Again, you do not need to root. Flashing a custom recovery through Odin does not root your phone, and is the first step. If you wish to root , then you would flash the su binaries zip in a custom recovery. I just don't want there to be any confusion.
Gubment Cheeze
Oh boy...want to be sure here...
Froid, I think what you type is consistent with Teyshablue's process.
1) This process first adds CWM (the custom recovery) using ODIN with the file “odin_ni717_cwm_recovery_b4.tar" in PDS slot. I assumed it needed root first but here CWM is the first step.
See here:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
1A) Then, I think I should nandroid back up the Stock ICS ROM here with CWM? I think so but it's not in the guide.
2) The next step using CWM is to load "Superuser-3.0.7-efghi-signed.zip ". So this roots correct Froid?
3) After that, then I can nandroid back-up rooted ICS ROM again with CWM.
4) Then can clean cache, Dalvik, and flash CM9 with CWM (Do I need to do some factory reset full wipe before adding CM9 ROM)?
Am I missing anything?
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
---------- Post added at 08:36 PM ---------- Previous post was at 08:25 PM ----------
On a side note, make sure you do your homework on the available recovery options before diving in head first. I personally use TWRP and would highly recommend.
Gubment Cheeze
Froid said:
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
Click to expand...
Click to collapse
Froid, mind checking me one more time? I edited my prior post (with numbered steps) as you were typing the reply. I am not sure about skipping the rooting step but I know you are probably right. I think I will run through the process as stated adding the stock backup then the rooted backup. Sound okay?
MUCH THANKS !!!! :good:
On the recovery program, I have only used CWM while I had my Captivate. TWRP is new to me. More options better program?
That will absolutely work. Not a bad idea to have both stock and rooted backed up. Always full wipe when flashing a new ROM. follow the OP of the ROM you're flashing. I don't use cwm so do some research on whether or not you need the latest version to flash a cm9 ROM. There was an issue in the past with using an older version of cwm. Not sure if that still exists. Good luck
Gubment Cheeze
Rooting Upgrading Anxiety
thanks all for the help, knowing that I just purchsed a close to $500 (shipping and accesories) used phone and knowing how many times I messed up my Captivate did not allow me to sleep well last night. I really want to do this right and not be panicked with a messed up Note to start with. I will sleep better knowing that I have a thought out and tested approach for when it arrives tomorrow.
And yes, TWRP has a few more options. I was always a fan of cwm, and its a great recovery. I just prefer TWRP for its UI, backup speeds, and being able to name the backup beforehand.
Gubment Cheeze
Let me know of progress
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
tonyo123 said:
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
Click to expand...
Click to collapse
Yes, naming backups is good as I have had to go back and just had many dated files which became almost hunt and peck in finding the exact one I needed. As for CWM, I also used the Devil Kernel, not sure if it is available for the Note, that beyond speed, also gave a few added optionsto CWM including a file manager which came in handy in swapping out system files (like CM9's Trebuchet launcher being replaced by a lighter version). But, a step at a time. I only used the added kernel because the Captivate with single core was a bit speed challenged (but CM9 made it like new).
Success!!
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Madtowndave said:
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Click to expand...
Click to collapse
Awesome for you. I am awaiting dilivery from USPS. I hope they don't let me down after payong $40 for the overnight.
Two questions:
1) What did(do) your Win7 drivers in 'device manager' indicate? Was it something like “Samsung Mobile USB CDC Composite Device" or did it identify the phone by name. I have seen both types in my Win7 setup with my Captivate so want to make sure I get this right.
2) So, you did not specifically root (no need for the "Superuser-3.0.7-efghi-signed.zip" or something like it). So assuming adter I add CWMm I flash the CM9 (Cyanogenmod 9 stable) ROM will that root my phone? I guess the more general question is do these ROMS automatically come rooted?
Related
My apologies if this has been asked before, but I've spent hours searching and think I've done a better job of confusing myself, than answering my question.
I've rooted my wife's Samsung Fascinate, using Super One Click and removed all annoyances such as the Verizon bloat ware and got add blocker installed, etc. The point on doing so, was also to improve battery life, backup the ROM and some of the other associated advantages with rooting. One of my main goals was to also install a custom ROM on her phone, as the factory ROM is very flaky. It receives emails, then doesn't. It sends a text, then can't minutes later. It's been a great phone HW wise, but just junk as far as the OS.
Thus far, all attempts to backup the factory (modified) ROM has failed, which evidently is part of the limitation with the stock ROM. At this point, she's so frustrated (me too) with her phone, that it's time to get serious.
So, my confusion stems from varying reports regarding what the proper steps are to install a new ROM. On my Thunderbolt, I simply used CWM to install and backup/restore my ROMs as needed. This doesn't seem to be the case with the Fascinate and there's varying reports of whether this can even be done if Super One Click was used.
Has anyone had experience with flashing new ROMs after the phone was rooted and if so, by what method?
Her current ROM details are:
Firmware
2.2.2
Baseband
S:i500.04 V.ED05
Kernel
2.6.32.9
Build
SCH-I500.ED05
Thanks in advance.
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cm7 zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
droidstyle said:
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cwm zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
Click to expand...
Click to collapse
Okay, that makes a lot more sense now. Thanks for the quick reply.
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
ibsk8 said:
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
Click to expand...
Click to collapse
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
droidstyle said:
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
Click to expand...
Click to collapse
I never could get to the ROM flashing part. Every time I tried I got the same set of errors as when trying to backup the original ROM. I did manage to get the CWM 4 fix applied through ODIN and it said successful, but nothing really changed and my attempts to flash the new ROM still failed.
I searched around this forum and others and found another file to flash and things went very badly. The flash was moving super slow and I left the phone, so I wouldn't be tempted to do anything stupid and after an hour, it was at the same point. When I rebooted the phone, I got a sad face icon only. No Samsung logo or anything.
Luckily, I was able to re flash the stock rom, but after messing with it for 4 hours and getting nowhere, I decided the stock ROM was good enough for now. I have no idea why this phone is so pesky and read how some folks had to ref lash the stock ROM, before being able to flash a new ROM. I made one final attempt to do so and got the same error as the first time, so that was enough for that day. I don't recall exactly what the error said at this point, but I had blue text, followed by orange, which I think said something to the fact that is was unable to verify the package, followed by red text showing the failures.
Sorry there's no more detail than that for now. I may try this again in the future, but as mentioned this is the wife's phone, so I can't take nearly the liberties with it as I could my own.
If anyone has any ideas on what I may be able to try next, that would be great. If not, I may keep digging on this forum (a very helpful place indeed) and see what the options may be.
Thanks everyone for your help.
refer to section 3 of my guide and follow those steps. for some reason certain fascinates have trouble flashing mtd roms when starting from ed05. I have to start with dl09 eclair then flash cm7. look in page 2 of this section for my guide. all files needed can be found there aswell. good luck!
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
samsung s3 gt i9300 16gb 4.1.2 xxemb2
i am going to follow this guide to root (the basic one u can find in stickies things )
Step 1. Download Odin3.07 from HERE
Step 2. Power off your Galaxy S3. Then hold down Volume Down, Center Home, and Power buttons together until you see the warning screen.
Step 3. Hit Volume Up button to enter Download mode and connect a microUSB cable from your Galaxy S3 to your computer.
Step 4. Next, download GalaxyS3RootNew.zip, unzip the files and run odin3.07.exe by double-clicking on the file.
Step 5. When ODIN program opens, you should find a highlighted yellow box with a random COM number. If you don’t see this, download and install Samsung USB drivers below:
SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Step 6. DO NOT TOUCH ANYTHING ELSE, hit “PDA” button and select the file CF-Root-SGS3-v6.4.tar.
Step 7. Hit “Start” button. This will install ClockworkMod Recovery on your Galaxy S3 i9300. If you get stuck on this step, just try a different USB port.
Step 8. Once ODIN is done flashing, you will see “PASS!” in green highlighted box.
Step 9. Your Galaxy S3 will reboot once into CWM Recovery and automatically install root and Superuser app.
Step 10. Once your phone reboots, you will find an app called “SuperSU”, this is your superuser app.
Step 11. Download and install Titanium Backup app from Play Store to verify you have root, a Superuser request window should pop up.
my questions are : do i need an external memoory card to root ( i have 3GB free space left)
whats the difference bitween CF-root and CF-autoroot ??
THANKS IN ADVANCE
Hey.
No, you don't need any external card to use root. About 10 MB on your internal card should be fine .
CF-AutoRoot isn't same as CF-Root. If you're not going to change your rom/kernel/recovery/etc and you just want to have your stock rom rooted then CF-AutoRoot suits you best. However, if you want to change your rom/kernel/recovery/etc in future then it's highly advised to use CF-Root which basicly roots your phone and installs custom recovery CWM 5.5 afaik.
If you want to choose second option then I'd recommend flashing modern recovery, for example PhilZ Touch, TWRP or even CWM 6.0.3.0. In fact it won't root your phone but most of the "cooked" roms are already rooted so you just need to reflash rom later or use AutoRoot described above. You can also flash CF-Root and then custom recovery, basicly you don't even need any other recovery than CF-Root but it's highly recommended to do so.
can u please give me the advantages of custom roms in breef , why would i need them for ? all what im thinking about right now is Adblocker and such things ..
and can i use CF root without installing a ROM for the moment ?? thx a lot
and i didnt understand a word in this paragraph
"If you want to choose second option then I'd recommend flashing modern recovery, for example PhilZ Touch, TWRP or even CWM 6.0.3.0. In fact it won't root your phone but most of the "cooked" roms are already rooted so you just need to reflash rom later or use AutoRoot described above. You can also flash CF-Root and then custom recovery, basicly you don't even need any other recovery than CF-Root but it's highly recommended to do so."
what is PhilzTouch ???
By the sound of things I would just root for now for the adblocking and then start reading like mad and getting familiar with all the terminology and methodology before going any further.....this is the bit so many people miss and hence end up with a very expensive paper weight and a lot of disappointment and heartache
Basicly "cooked" roms have newest firmware versions, many tweaks, optimization and many things which full stock roms are missing. I'm not going to list all these things, check yourself if you wish.
@2
There are two ways to "flash" software to your device. Using USB cable and computer (via Odin) or directly from recovery. To do so directly from recovery you need custom (non-stock) recovery which gives you an option to do so. CF-AutoRoot gives you root while CF-Root gives you root + old CWM 5.5 recovery (because CF isn't supporting this method anymore). So basicly if you want to have a great time with your device, flash different roms etc. then you can directly flash modern recovery through odin f.e. PhilZ Touch Recovery without needing to use CF-Root.
All i want now is to have a rooted device on stock .. then i will take my time and read if i wanna add ROM/kernel
what do u think i should do
CF-AutoRoot. Best, easiest and nice solution for rooting full stock rom. You don't need anything else if you're not going to change roms/kernels or whatever.
Just a note that you may want to use the thanks button....it's kind of traditional courtesy when asking for help and receiving it
R: just two little small questions about root
JustArchi said:
CF-AutoRoot. Best, easiest and nice solution for rooting full stock rom. You don't need anything else if you're not going to change roms/kernels or whatever.
Click to expand...
Click to collapse
Actually i would suggest the op also get a cuatom recovery into his phone.
Cuz if he f*** up his phone real bad and doesnt have a pc with him (cuz otherwise you would have to use odin to flash, or odin mobile from phone but if ure phone doesnt work, u cant) he can still fix things thru recovery.
Other things recoveries are for is making NANDROID BACKUPS. basically an almost total backup of your phone data: it backups rom, kernel , apps and their data, modem, system cache a bunch of technical stuff.
It doesnt backup other files of course (such as music on ur phone or videos or documents) just what is necessary to make the phone run with ur apps.
The reason this backup is important is because if you f*** up your phone real bad (again, phone can be tricky to hande) you can just flash it clean (you internal phone storage, such as music or any folder which doesnt concern rom, or microsd stuff, wont be touched when you choose "factory reset" in custom recovery)
And restore from a backup when your phone was working. Then u reboot and voila, a trip back into the past!
Might i suggest you also backup the efs folder which is found in the root directory. Nandroids DO NOT cover that. And basically for an s3, if you've got root and internal components are not damaged, if youve got the efs you can fix anything....if ya dont - not so much.
Might suggest once more that IF YOU DONT CARE about all this 'faster roms' kernels and mumbo jumbo root stuff, you still flash a recovery: the most stable one is CWM (clockworkmod recovery). To get it just boot into ur rooted phone, install free app from store "rom manager" and install latest version of recovery. you can boot into phone recovery at ANY GIVEN TIME, just follow instructions u can find on google, pressing buttons at same time and ****.
If ure curious, other recoveries exist:
Clockworkmod touch(premium):it's basically cwm just that it's touch. If you want my point of view...having touch on recovery is stupid and useless...recoveries are for fixin or doing important stuff, you dont wanna mess everything up cuz u touched the screen for mistake. Much better to use buttons and be sure.
Twrp...whatever cant remember da name: same thing as cwm touch, only .......i dunno but cwm is better.
Philz Touch(now this is the real ****!):not stable as cwm. It's a mod of cwm with MANY added cool features such as aroma file browser within the rom and look changing and of course touch( all toucb/double tap touch/touch only for scrolling) but the BEST option is BACKUP COMPRESSION. This little guy made me earn 1gb of free-er space out of my nandroid backups i perform onto my microsd. I went fron 3.5gigs to 2.5gigs. Awesome! Plus you can skip md5 checksum...which is a safety thing of course...but it slows down the backup/restore process, for the most daring disabling it spares them some waiting (nandroids are faster than kies from the pc anyways, no more than 20mins guaranteed!).
If ure interested about kernels i suggest:
Siyah kernel (or syiah...never know which)
Perseus kernel.
They both are good and fast, syiah is more performance, but you can get just the same performance on perseus if you handle the tweaking well and yiu get more battery time.
If youre interested about roms:
Foxhound (most complete one for the s3 i believe, it's packing all you need, and of course it's faster than stock samsung rom)
Rootbox(light rom. Its got less features but still fully packed for speed)
Omega (never tried it. Still have to...but it looks like in this rom look-costumization of look is the easiest thing to do. But i believe foxhound to be fully customizable as well...)
others are also
Jellybam
ResurrectionRemix
Hope i helped you get some root **** together
Sent from my GT-I9300 using xda app-developers app
I totally agree with your point of view but I've been using PhilZ Touch for about a few months now, flashing stuff, making backups and having fun about 1 time per day. Don't call this masterpiece "unstable" because it's based on latest CWM and without any "unstable" thing . I haven't got any problem with that recovery since 4.01 or so.
JustArchi said:
I totally agree with your point of view but I've been using PhilZ Touch for about a few months now, flashing stuff, making backups and having fun about 1 time per day. Don't call this masterpiece "unstable" because it's based on latest CWM and without any "unstable" thing . I haven't got any problem with that recovery since 4.01 or so.
Click to expand...
Click to collapse
Totally agree, never had a problem with it
R: just two little small questions about root
JustArchi said:
I totally agree with your point of view but I've been using PhilZ Touch for about a few months now, flashing stuff, making backups and having fun about 1 time per day. Don't call this masterpiece "unstable" because it's based on latest CWM and without any "unstable" thing . I haven't got any problem with that recovery since 4.01 or so.
Click to expand...
Click to collapse
Impossible, much less than a month ago there was a versione of the recovery (4.8.8.1 i think) in which it did not save any of the recovery settings i had changed, cuz when i rebooted into recovery for backup/restore stuff i had to keep reenabling some features (like max compression, save to excard ecc ecc). Then there was an update (and they changed selection menu to [x] kinda like thing, if u boot into it now u see md5 checksum if enabled has an x) and the recovery rememberes all settings now (all interface tweaks amd stuff).
that's what i meant for unstable, also cuz rom manager doesnt recognize updated version of clockwork...but thats another story.
Thou i do think philz is a masterpiece, but its missing some stuff...for example aroma file manager needs to be included into the recovery already, also it needs its own updating app, also aroma file manager is a bit too low on features for me. like...if im gonna move some pixtures from a folder i wanna see them first...and if my rom isnt working i cant do that with aroma..
Sent from my GT-I9300 using xda app-developers app
Thanks a lottr guyysss especially u killbubble u really helped me im gona ask u for one more favor
U said install rom manager on ur rooted phone and install CWM (so i guess i should root with CF root rightt???)
And if i chose Philz how can i really get it on my phone ?? Will i find it in Rom manager also??
Thanks in advancee!
killbubble said:
Impossible, much less than a month ago there was a versione of the recovery (4.8.8.1 i think) in which it did not save any of the recovery settings i had changed, cuz when i rebooted into recovery for backup/restore stuff i had to keep reenabling some features (like max compression, save to excard ecc ecc). Then there was an update (and they changed selection menu to [x] kinda like thing, if u boot into it now u see md5 checksum if enabled has an x) and the recovery rememberes all settings now (all interface tweaks amd stuff).
that's what i meant for unstable, also cuz rom manager doesnt recognize updated version of clockwork...but thats another story.
Thou i do think philz is a masterpiece, but its missing some stuff...for example aroma file manager needs to be included into the recovery already, also it needs its own updating app, also aroma file manager is a bit too low on features for me. like...if im gonna move some pixtures from a folder i wanna see them first...and if my rom isnt working i cant do that with aroma..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
4.89.4 (14.03.2013)
- New Custom Install Zip mode: set a default folder to start with + browse backward up to the root
4.88.5
- toggle menus are now formatted to device screen width (right align menu option)
- add 30mn timezone offset
- merge CM 10.1 commit: Fix segfault with dead symlinks in char** gather_files()
- add extra check for carriage return for get_rom_name function: ensures windobe noobs do not get stuck
4.88.2
- fix: ors backup could overwrite an existing folder and end up with mixed old/new backup images
Click to expand...
Click to collapse
Impossible, Phil would include it in his changelog . Also I know what you're talking about, it happens when there isn't a folder clockworkmod on /sdcard , sometimes you need to create it manualy but how often do you format /sdcard anyway? Recovery restores it after reboot anyway.
Also autoupdate from one point of view is a nice feature, I totally agree with that but on the other hand it would require many more things included in the recovery because itself it doesn't support many options, that's why it's called recovery, not a software . Personally I prefer having an option to choose, newer version isn't always better, usually yes, but not always . Also recovery just need to "work", flash roms, make backups and eventually some simple other tasks. I don't need anything else .
Just archi can u help me with My question please?? thank u so much
georgeskhater said:
Just archi can u help me with My question please?? thank u so much
Click to expand...
Click to collapse
Root using auto root, then use mobile Odin to flash recovery.img
Or
Root with cf root then just flash Phil's with the cwm recovery that comes with cf root
georgeskhater said:
Thanks a lottr guyysss especially u killbubble u really helped me im gona ask u for one more favor
U said install rom manager on ur rooted phone and install CWM (so i guess i should root with CF root rightt???)
And if i chose Philz how can i really get it on my phone ?? Will i find it in Rom manager also??
Thanks in advancee!
Click to expand...
Click to collapse
Doesnt really matter how u root as pong as u do. Once u do run rom manager and update clockworkmod (cuz if u rooted the otherway cwm is probab uoutdated).
If u chose philz just google philz and find the thread (gonna be first on google, if not google philz recovery)
Read the thread well and find i9300 version (best if u choose .zip version flashable with cwm, if not u gotta use tar.gz flashable thru odin) then put it on phone and in recovery flash dat pakage. Then reboot recovery and make sure u configure philz to your liking.
no philz is not included in rom manager.
Rom manager is a weird name, since it's only of use to update to the latest version of cwm, or install it if you still have stock. Thou it does have a list where u can download roms...i dont recommend it cuz it suks..much better for this is goo manager.
But i prefer googling the rom or recovery (if cwm, i would use the app of course) or whatever and downloaing it from source, much safer and has full instructions (needed for some stuff, for example if a rom needs latest gapps cuz not included, apps like rom manager would not tell ya).
Glad to help, if u wanna thank just hit the :thumbup: button...
Sent from my GT-I9300 using xda app-developers app
Yeah, I don't recommend tools like Rom Manager as well. It's not bad of course but some kind of useless, in my honest opinion at least.
P.S. Like I said if you're going to change rom then you don't need ANY CF-Root, just flash PhilZ (or clean CWM) through odin then flash any pre-rooted rom. CF-Root isn't required here, only if you're not going to change rom, then use cf-autoroot.
I have a new stock Gingerbread Fascinate, and want to install the Geewiz Media 4.4/JB 4.2.2 ROM/Kernel on it (making it an ipod-like device). I really really hate having to ask, especially after spending the past week reading a couple of hundred pages of posts, including the dev's, droidstyle's guide, and others, learning as much as I can. I have rooted a Motorola Droid 2 before, but this is all new, and I am still unsure.
So Geewiz comes as Edify .zip files or Odin-compatible .tar files. Based on the dev's provided information, I choose to start with the Odin-compatible .tar file named "GeeWiz Media 4.4 ROM/Kernel/Modem/Recovery/Data Wipe Full Update". As I understand it this is includes everything I need to start: a rooted JB OS with modified EH03 kernel, plus CWM, data folders reformatted to ext4, and an EH03 recovery. I need to start on stock EH03, which I already am.
I have plenty of threads saved (& many printed), so I don't need help with the button-pushing. My confusion stems from the different file types (tar vs. zip) and software (Odin and Clockwork), and what I am supposed to do in what order.
So my questions:
1. Does the .tar file to be installed by Odin go on my SD card or stay on my computer?
2. Since the .tar contains everything at once, what process do I follow after installing it? (Reboot into recovery, download mode, etc.)
3. Should I expect a CWM .zip file on my SD card after installing the tar?
I seems like I should have been able to figure this out on my own, but the dev thread doesn't get into the basics, and I haven't found explicit instructions for the all-in-one Geewiz ROM, or other instructions that I am comfortably sure are completely relevant.
Thank you.
I'm by no means an expert, but I've flashed a lot of roms including Geewiz before so I'll try to help you out.
1) Odin pushes files to your device from the computer, so there's no need to have anything saved on your phone
2) Once everything completes simply reboot the phone and you should be good to go
3) I'm not sure, but I don't think so. I'm pretty sure Geewiz has it's own recovery included with the rom and there will be no need to separately install CWM recovery
If anything goes wrong, simply follow droidstyle's guide to go back to stock and start over again. The Fascinate is extremely hard to break (luckily).
Thank you, Crawshayi! :fingers-crossed:
Wow, after all that worry, it was a piece of cake. If its any use to someone, I installed with Odin, following this procedure:
1. Remove battery
2. Fire up Odin (I used 1.85)
3. Plug in the factory USB cable and hold the volume down button
4. Wait for download mode and yellow box in Odin
5. Put my Geewiz full-wipe / kernel / recovery .tar file in Odin's PDA box
6. Hit start.
7. Wait till Odin box turns green and says pass
8. Reboot phone. (I wasn't sure about clicking the "Auto-Reboot" box. Some say yes and some say no, in my readings. I clicked it, but it didn't auto reboot anyway. I also had "F. Reset Time" checked as instructed.
9. First there was a brief message about wiping phone & ext4. Then, a pretty long wait time, watching a big colored "X". Just when I was starting to worry a little bit, a message from Google popped up and I was "in".
This is the first time I've ever looked at Jelly Bean. It's beautiful and really different from Gingerbread (which is my only exposure to Android since moving from Blackberry)
Yeah Jelly Bean is really great, Google hit a home run with that one and we're lucky enough to have a lot of good Jelly Bean roms to choose from on the Fascinate
I am at my wits end and hopefully one of you can help.
The phone in question is is the AT&T Galaxy S2 SGH i777. It was running a jellybean ROM and there were problems with the GPS and google maps not working at all about four months ago. Not sure what happened. I went through the usual process of putting a ROM on the SD card, wiping cache/davlik and installing, then installing the gapp.apk for that rom. Everything was fine. Except wireless. Wireless would not connect. Just wouldn't do it. Googled forever, found no real solution. Thinking it was the rom I reinstalled. Wash rinse repeat. Same issue. Thinking it was a bad rom I proceeded to go through about six more roms. Same issue. Four hours later I resolved to unroot, take it back to stock. Took it back to stop with no issues. Wireless worked just fine. Everything was great. Rooted it again with the stock gingerbread. Wireless worked fine. Made a backup of the rom and was feeling lucky so I installed the Carbon ROM from the Sept 29th post on galaxys2root.com (I don't know if you guys allow linking here) and the gapps from that post. I boot. Everything is looking fine....yet the wireless doesn't work. This has been consistent across every rom I installed. I am quitting for the night.
It is currently running android 4.3, kernel version 3.064-CM-gbc8f4c9 (if that helps). The phone service is fine and makes/receives calls/texts just fine. No other blaring issues. Worth pointing out: all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect.
I had this phone for years (girlfriend has it now) and Rom'd it many times with next to no issues, especially not with wireless. I don't understand why it was working fine on a JB rom and trying to change rom suddenly screwed the wireless.
I am literally at my wits end and it's probably the result of me being an idiot somehow and missing something. Can anyone suggest a fix?
God bless in advance.
fifthmanstanding said:
[...]all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect. [...]Can anyone suggest a fix?
God bless in advance.
Click to expand...
Click to collapse
My advice is to avoid downloading ROMS from galaxys2root.com
If you want the insider scoop, keep up at xda or at each group's G+ community.
if you want:
-Carbon; get it from: http://download.carbon-rom.com/?dir=./i777/nightly
-Cyanogenmod; get it from http://download.cyanogenmod.org/?device=i777
-Omni; get it from http://dl.omnirom.org/i777/
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
cyril279 said:
My advice is to avoid downloading ROMS from galaxys2root
If you want the insider scoop, keep up at xda or at each group's G+ community.
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
Click to expand...
Click to collapse
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
fifthmanstanding said:
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
Click to expand...
Click to collapse
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
creepyncrawly said:
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
Click to expand...
Click to collapse
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
fifthmanstanding said:
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
Click to expand...
Click to collapse
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
creepyncrawly said:
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
Click to expand...
Click to collapse
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
fifthmanstanding said:
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
Click to expand...
Click to collapse
hint: http://forum.xda-developers.com/member.php?u=2916435
cyril279 said:
hint: http://forum.xda-developers.com/member.php?u=2916435
Click to expand...
Click to collapse
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
fifthmanstanding said:
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
cyril279 said:
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
Click to expand...
Click to collapse
I agree.
Which links?
I read through the notes on the repository:
There is always some risk involved when flashing bootloaders and Param.lfs. Please don't flash this unless you absolutely need to.
"This is the complete stock UCMD8 Binaries downloaded from samfirmware at sammobile.com. Please note, this package contains boot.bin, sbl.bin and param.lfs, plus cache.img, factoryfs.img, hidden.img, modem.bin and zImage.I777UCMD8 Full Odin Flashable tar: I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z 427.02 MB (Contains I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5)
(MD5: 307cc8fcbb8f220d3ae75d387569da40)"
And I'm downloading the file now. I've used odin before so I assume that goes by the standard process ( download mode, open, pda, select file, hit start, wait, finish) and then I went here http://forum.xda-developers.com/showthread.php?t=2130276 and he says "Version 1.3: Add Aragorn and Legolas exploits" so I assume based on Creepy's previous statement that's the one I need. I would download the apk and run it.
What am I missing?
Yeah I just installed the tar file using odin and before I even get to rooting process, wireless isn't working. This time it sees the network, password goes in as usual, it attempts to obtain IP address and says that forever. Never connects. Then goes back to scanning. Then attempts to connect again. No dice. No other device in the home has this issue. I'm out of ideas.
Edit:
Yeah I just tried again, using odin, took it back to stock, wireless works, using odin took it to stock with root, wireless works, using the tar file located here http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 took it to I777UCMD8 Stock Binary. Wireless is not working.
Does anyone have any insight? I've got a pissed off girlfriend an a perment dent in my desk from my head.
update: took it back to i777 UCMD8 with odin, just for kicks I tethered it to my nexus 4. Works fine. Turned off data, disconnected the wireless just to be sure. Turned it back on. Working fine. Still will not connect to my router. This would imply there is a router issue and I have less knowledge of how/why that would work. Thoughts?
fifthmanstanding said:
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Edit: Failed to click on the latest page of the thread before I posted this. Yes, it sounds like an issue with your router, perhaps. So find other routers and test the wifi. If that's the issue, then the other roms will probably also work on a different router.
creepyncrawly said:
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Click to expand...
Click to collapse
Yeah I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
EDITosted before I saw your edit
fifthmanstanding said:
Yeah as stated, I'm familiar with odin. I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
Click to expand...
Click to collapse
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
creepyncrawly said:
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
Click to expand...
Click to collapse
Fair enough.
I've downloaded the AJK no swap from here http://forum.xda-developers.com/showthread.php?t=2110542
I've downloaded Mobile Odin lite and am going to work on that.
Assuming it all works out and I get to make a backup. Where to next? This rom is terrible. What do you recommend for a jellybean experience as stock nexus 4 as possible.
Yeah the ajk no swap 4.9 is giving me a consistent java error that kills the download. I attempted to move it to the sd card and open in odin lite but am not seeing it on the card. Am I doing something wrong?
Edit. I tried connecting the phone to the computer and opening in explorer, following directions from here http://forum.xda-developers.com/showthread.php?t=2197157 , created a folder and attempted to drop the zip in there and it's not letting me drop files to the phone. nor to the sd card.
Edit 2: suddenly file xfer is working again. I dropped the .zip to the new folder on the internal and also created a new folder with the boot, METAINF folder and system folder that shows when you unzip. It's not detecting the zip file so I assume you're supposed to select the Boot file. I select it. Nothing happens.
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
fifthmanstanding said:
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
Click to expand...
Click to collapse
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
creepyncrawly said:
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
Click to expand...
Click to collapse
Ok by the looks of it that worked. Thanks for that.
In terms of roms I'm looking for something stable, jelly bean and non-touchwiz. As close to possible as nexus 4's jelly bean. Nothing comes to mind?
Edit: apparently the home key now no longer works properly, hitt it brings up a selection box and selects whatever is the left most side whether it's 'apps' tab or an icon on the home screen. Also the search magnifying glass soft key doesn't work, same function as the home key it seems.
Edit 2: And the wireless is no longer working. Was working fine before flashing the kernel. Put the phone directly on top of the router. It shows the network, allows for password input, says 'connecting' and never ever connects. Then it drops and goes to 'out of range'...sitting directly on the router. Just for kicks, like last time, I enabled the hotspot on my N4 and it connected fine. I attempted to connect to the router again and it does the same...connecting and drops to out of range. Sigh.