Related
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
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?
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
I am looking for some help bc of all the roms out there I am really confused. Ihad a droid X before this and flashed several roms without a problem. Here is when I get lost:
Right now I am back on stock I605VRAMC3.
I use adam outliers root method to get rooted with super user acess.
This gives me TWRP not CWM.
If I use TWRP to flash a rom I end up with a bricked phone.
I would like to use a CM11 4.4 rom or something similar. When I watch the video on galaxynote2root.com the user uses CWM and if I use that on my phone it turns into a brick even after rooting. What step am I missing? I see some roms are touchwiz based. I'm not familiar with what touchwiz is or how to install ot before flashing roms or if I even need it for CM11. Anyone on the same build as me that has flashed several roms I would greatly appreciate any info so I can start to enjoy some of these roms and decide which one I like. Thanks.
Sorry, I haven't done this stuff to know exactly where the issue is, but I will assume you're more likely to get the answer in the development section since it's all about themes, roms, rom flashing, rooting etc. If not there, then the trouble shooting section. Hope that helps. (assuming you're still looking)
You can flash Philz recovery in twrp & switch to it. Then you can flash CM11.
http://forum.xda-developers.com/showthread.php?t=2552655
You can use casual to root and unlock bootloader.... And then install cwm via rom manager apk... Hope this solves your concern
Sent from my SCH-I605 using XDA Premium 4 mobile app
How is TWRP bricking your phone? I rooted with Outler's method and have had no problems with TWRP. You've mentioned that CWM has bricked your phone too. If that's the case, how were able to flash anything at all? As for TouchWiz, it's not anything you install. There are two basic types of ROMS for the N2. TouchWiz based, which have more of the Samsung apps along with the ROM customizations, and AOSP (Android Open Source Project). AOSP is more like stock Android, but with custom features. CM11 is an AOSP ROM. Here are the steps I took when I initially rooted:
Installed Samsung drivers to my laptop
Made sure Java was up to date
D/L Outler's Casual
Put phone in USB Debugging Mode
Attached phone
Ran Casual
Rooted phone (at this point I believe I had to select between CWM or TWRP)
There you have it. If you missed any of these steps, that could be the problem. Another issue might be that you're trying to use TWRP and CWM simultaneously
I'm assuming you are not wiping(factory reset. I do it three times) prior to your install. If you're not then your trying to install a rom on top of a rom and bam...boot loop.
nikhil.kdhand said:
You can use casual to root and unlock bootloader.... And then install cwm via rom manager apk... Hope this solves your concern
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1 for this... when i tried to flash CM11 using TWRP I ended up in a bootloop.. restored my backup, downloaded rom manager apk from google play and used that to install CWM... then in CWM did a backup, wipe everything, and flashed CM11 + gapps and everything works without a hitch
one more note... my CWM backup was hanging on generating the MD5 sum, so i changed the encryption method away from the default... takes up more space on the ext-sd, but it works.
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.