[Q] Unroot + Uninstall CWM Instructions? - T-Mobile Samsung Galaxy Note

Hey there I was searching/googleing the instructions for unrooting the T-Mobile Galaxy Note (t879) but could only find the international versions.
Does anyone know the process or can point me to a video/tutorial to go back to a fully unrooted Note?
Also, how do I go about going back to the tmo recovery, removing the CWM recovery? Where can I find that? Do I do that before I unroot it or after?
Once I flash the unrooted stock rom (if there is any for Tmo) do i need to reset the flash counter and how would I do that if it is unrooted?
Sorry for all the questions, I hope someone can help me...
Thanks in advance!
Background: my mic started to produce garbled noise, it works fine on handsfree mode but not on the regular mode. if I can fix it I don't need to go back to stock or unroot it.
I tried a different ROM but that didn't work (CM10), i cleared the tmo talkvoice app cache and data but still the same result.
So i assume that the mic is broken and that I will have to send it in/RMA it...

Try this post here,
http://forum.xda-developers.com/showthread.php?p=32691120
Sent from my SGH-T879 using xda premium

joemm said:
Try this post here,
http://forum.xda-developers.com/showthread.php?p=32691120
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Thank you joemm, that did it.
If the mic problem ever happens to anyone else then flashing to another ROM, such as ICS/JB wont fix it. You need to return to stock, preferably to a nandroid back up (from when it worked)
Then I rooted the stock phone again, put CWM recovery on it and went straight from there to JB (AoCP) and have not had any problems with the mic so far. its been running great so far!

Related

A custom ROM! A custom ROM! My phone for a custom ROM!.!

Okay, I have no idea why, but my phone doesn't seem to like any ROM except for the stock. Every ROM, every update I've tried, has just gone and bricked my phone. I'm a newbie as far as development goes, but I do know my way around flashing, applying updates from SD and stuff. And I'm careful not to mess with files designed for the other ace. I also follow instructions to the letter. I'm as scared of bricks as anyone else.
So I was wondering whether any of you could help me out here. Do tell me if it's better to stick with the stock ROM though. Awaiting a reply.
Cheers
EDIT:
Okay, I downloaded this iDroid ROM from here
My phone's kernel version says 2.6.35.7([email protected] #201209221033), but there's absolutely no change. Any ideas on what to do now? Still waiting for a reply. :-\
Still struggling to find a proper non-stock ROM that works on my phone X-(
kittuboy said:
Okay, I have no idea why, but my phone doesn't seem to like any ROM except for the stock. Every ROM, every update I've tried, has just gone and bricked my phone. I'm a newbie as far as development goes, but I do know my way around flashing, applying updates from SD and stuff. And I'm careful not to mess with files designed for the other ace. I also follow instructions to the letter. I'm as scared of bricks as anyone else.
So I was wondering whether any of you could help me out here. Do tell me if it's better to stick with the stock ROM though. Awaiting a reply.
Cheers
EDIT:
Okay, I downloaded this iDroid ROM from here
My phone's kernel version says 2.6.35.7([email protected] #201209221033), but there's absolutely no change. Any ideas on what to do now? Still waiting for a reply. :-\
Still struggling to find a proper non-stock ROM that works on my phone X-(
Click to expand...
Click to collapse
Well firstly ask why yourself why you want to flash a particular custom ROM? Does it have features you need etc? If not then stock is fine and there are many ways alter the appearance of your phone without flashing a new custom ROM via apps in the play store.
As always prior to flashing a custom ROM make sure you have all the tools and knowledge to flash back to stock if anything goes wrong. OK so by the sounds of it you have installed RB,s kernel but have not installed IDroid ROM, tell us how you tried to flash and that will give us more of an idea where you are going wrong.
Sent from my Nexus 7 using xda app-developers app
Viprdxd said:
Well firstly ask why yourself why you want to flash a particular custom ROM? Does it have features you need etc? If not then stock is fine and there are many ways alter the appearance of your phone without flashing a new custom ROM via apps in the play store.
As always prior to flashing a custom ROM make sure you have all the tools and knowledge to flash back to stock if anything goes wrong. OK so by the sounds of it you have installed RB,s kernel but have not installed IDroid ROM, tell us how you tried to flash and that will give us more of an idea where you are going wrong.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Why the custom ROM: I was told by a friend (who uses a Galaxy Y) to use one, so as to make the phone less laggy. And I like to have my devices looking a little different from what everyone uses. Pardon me
EDIT: And yes, I do have the firmware required to flash back, as well as Odin. I've flashed before, so you could say I'm not a total waste there And I seem to have trouble understanding the difference between ROM and kernel.... could you please explain it to me? At least I'll know where I'm going wrong.
http://forum.xda-developers.com/showthread.php?t=1976674
[PORTED][ROM]Jelly Blast V3.0.4 [29/11/2012]try flashing this from.
It is good method I hope u know then to
1.download the from from the link.
2.install it using cwm recovery.
3.then press wipe data/reset.
4.then go to the advanced menu and clean the dalvik cache.
5.reboot and enjoy
Sent from my GT-S5830i
vkv.5991 said:
http://forum.xda-developers.com/showthread.php?t=1976674
[PORTED][ROM]Jelly Blast V3.0.4 [29/11/2012]try flashing this from.
It is good method I hope u know then to
1.download the from from the link.
2.install it using cwm recovery.
3.then press wipe data/reset.
4.then go to the advanced menu and clean the dalvik cache.
5.reboot and enjoy
Sent from my GT-S5830i
Click to expand...
Click to collapse
Booted. First off the bat, crashed MMS app. Within seconds, crashed phone app. :crying: And where did my status bar go off to?? :crying::crying: Disappointed, am going to try RazoDroid! :crying:
kittuboy said:
Booted. First off the bat, crashed MMS app. Within seconds, crashed phone app. :crying: And where did my status bar go off to?? :crying::crying:
Click to expand...
Click to collapse
On which firmware you are?
Sent from my GT-S5830i using xda premium
Try fixing permissions in cwm
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
Did you ROM wipe. Before you install custom ROMs?
Sent from my SGH-T679 using xda app-developers app
kittuboy said:
Booted. First off the bat, crashed MMS app. Within seconds, crashed phone app. :crying: And where did my status bar go off to?? :crying::crying: Disappointed, am going to try RazoDroid! :crying:
Click to expand...
Click to collapse
Kitt explain to us how you are doing your flashes and let us know what firmware your running. To advise we need as much info as you can give.
Sent from my Nexus 7 using xda app-developers app
The standard procedure I follow:
1. Download the flashable zip to my phone SD card.
2. Reboot into stock recovery, enter clockworkmod through its zip file
3. Backup just in case, install the zip through cwm or stock recovery, whichever the dev advises
4. Reboot
Update: managed to get RazoDroid working. Firmware XXLD2, Rafael Baugis kernel (obviously, duh ) and no problems so far!
Just because you're probably not following the instructions correctly doesn't mean it's the developer's fault, and that you should be 'disappointed'.
True. I do my best to follow instructions, but I may have overlooked something somewhere. And no, I'm not blaming any devs, not intentionally anyway, because I don't have any rights to.... At the end of the day, I did manage to make something work, and now I'm happy with it, so all I can say is peace out
Running RazoDroid ROM on Rafael Baugis kernel, somehow managed through without bricking phone for the nth time

[Q] I957 ATT , touch screen not working after ICS upgrade

Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
wamaOnline said:
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
Click to expand...
Click to collapse
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
jd1639 said:
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
First was this one sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=XXX&os=1&type=3#firmware[/url]
Then when it didn't work, tried this one
sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=ATT&os=1&type=3#firmware
Sorry for the strange URL format, but seems as anew member I don't get to add URLs yet
orlandoxpolice said:
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sorry, I meant the cwm recovery was flashed correctly and functioning
Btwi tried the fix permissions suggestion from the similar thread but no luck
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
jd1639 said:
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
It is the Odin version I have used,
One more note now, am not sure if that is normal if not.but after the latest flash ( preceded by a data wipe and format ) I can now see zip file I have placed on sdcard but can't access them for flashing and/or ad new zip files from pc
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried,booted, "SAMASUNG"screen only ( as expected sicne i formatted the system ), then re-flushed the ATT ICS and same output
Am trying to get a new ROM flashed, but when the device powers up [ without me going through the wizard ], i can't write anything to SD from my PC.
Any info around here about flashing CM or AOKP using ODIN for this I957 ?
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
I'm at a loss, you've tried everything that has gotten me beyond the boot screen.
Anyone else have any ideas?
Sent from my SGH-I727
wamaOnline said:
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
Click to expand...
Click to collapse
I should mention something that has gotten me worried, i flashed a TWRP recovery to check if the touch would work there, but it didn't.
Not sure if i should be worried about HW now, or try another TWRP for instance? Or perhaps TWRP shares another flawed tab wide configuration with the Android image ?
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Then why is it still borked when reverting to hc?
Sent from my SAMSUNG-SGH-I727 using xda premium
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
jd1639 said:
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
Click to expand...
Click to collapse
yea i dont get how a rom flash could cause a hardware issue
orlandoxpolice said:
yea i dont get how a rom flash could cause a hardware issue
Click to expand...
Click to collapse
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
wamaOnline said:
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
Click to expand...
Click to collapse
Got it Reassembled and cleaned it and it worked
same prob, touchscreen not responding
wamaOnline said:
Got it Reassembled and cleaned it and it worked
Click to expand...
Click to collapse
I'm having this issue of the touchscreen not responding on my s2 now
You say you got it reassembled? What did you have to do to repair it
any help greatly appreciated
I have JB 4.1.2 and cwm 9.1 flashed
after reboot screen comes on but won't respond to touch, I can only access download and recobvery screens
I also have the phone not showing on computer when usb attached but am loading rom etc to ext sd card first and installing them from cwm
Got the maintenance center to disassemble it, clean the pins and reconnect the screen and then it worked
Sent from my LT26ii using xda app-developers app

[Q] Rooted/s-on. Can I update anything.

Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?
you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app
From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device
Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app
I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?
jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk
Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk
Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048

Att NC2 need help going back to factory ASAP

Hello I searched and couldn't find an answer basically I rooted my note 3 with root towel and safe strap unfortunately i didn't back up or back anything up was kinda drunk lol so at this point I can't seem to flash anything I see the galaxy note 3 on the booting then the safe strap shows up and it is giving me two options recovery or continue ... If I hit continue nothing happens ...black screen now if I hit recovery I'll be in safe strap recovery but can't see to flash any NC2 rom anyway at ths point I rather like to go back to stock ncu and start over any help will be greatly appreciated!!
Hello no one here can help? Please!!!
I am having the almost same problem a you, with the exception that I can still use my phone right now. But I can't install any other rom or even use my backup that I made in recovery. They just keep failing. I can give you a copy of my backup that I made maybe that will help you. Just pm me if you want it OK.
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
I ran into a similar issue. I messed up and learned the hard way to make sure and run a backup before messing with my phone. In my case, I make sure to run Nandriod backup and make a full backup to my external sdcard.
As a suggestion, you can always restore to MLG using the n900aucumlg one click (by designgears) 4.4.2: http://forum.xda-developers.com/showthread.php?t=2619941
You can then simply update the modem using this thread: http://forum.xda-developers.com/showthread.php?t=2698464
Did you install busybox. The order to do all that was 1. Towelroot. 2. Install busybox. 3. Install safestrap. If nothing is happening I would suggest to boot into stock recovery via power, home, volume up (or down I forget which one it is) and just factory reset like that. It should erase everything and start you fresh
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
FYI, I would also check out the source from where you are loading your ROMs. Since I swapped over to a different SD card, my installation problems have been cleared up.

[Q] Stuck on Boot S-5 Screen

Hi I have an A&TT S900A. I just installed Unity Rom and upon reboot all is the S-5 Boot screen without ever getting to safestrap. How can I fix this?
I can tell you the same thing hapenned to me and going back to stock was my only option. The only thing to remember here though is that the file to odin back to stock will wipe everything off your internal memory, so you should probably make a back up of your internal memory first if you can. Good luck man.
Sent from my SM-G900A using XDA Premium 4 mobile app
Thanks a lot. I don't see an Odin return to stock thread specific to this model, so I assume it's pretty standard and will look for just a general walk through online.
ok odin worked fine, now to try if I can get this rom to install again... Thanks for the help!

Categories

Resources