Database Info

How to restore to factory settings?

I screwed up my phone, I rooted it and was uninstalling some bloatware that came with it (sound hound, check-in app etc) but I deleted something important and for some reason I my internet browser was uninstalled and I cannot install CWM (will clarify below). Before my brower was uninstalled I was unable to install any more apps (things from the Market would download, but never install), so I tried a factory reset (being stupid since I uninstalled so much from the stock ROM) and then my browser was gone.
Being a total moron I did not back anything up, so I thought I could install CWM to just reflash the stock ROM. I rooted my phone successfully (following htc dev) but could not install CWM, after flashing the .img file and rebooting it just reboots as normal and shows no evidence of CWM being installed.
My phone is a Rogers HTC One X and I've been making sure to find the guides for Rogers/AT&T HTC's, but I'm still failing .

Use ADB to push the missing apps to the phone?
But it sounds like you want to restore the phone to the state it was before you removed apps?
If so, first step is to get a working recovery. Can you get Rom Manager on your phone? If so, you could flash CM from there.
If not, find a thread on flashing recovery. I have not yet rooted mine so can't be more specific.
And you do know how to get into recovery by holding volume down and power etc? Sorry if I underestimate your experience but sometimes people miss basic stuff.
Sent from my EPAD using Tapatalk 2

Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Edit: I see from comments below it appears that some people think I was being sarcastic in making this post: however, see this thread:
http://forum.xda-developers.com/showthread.php?p=22897771
I have seen a number of other warnings over the years of inexperienced users who try to get out of trouble by simply applying manufacturers' updates or factory images to an unlocked phone with a custom recovery and make things much worse.
Sent from my EPAD using Tapatalk 2

How do I use ABD to push missing apps back? Don't worry about underestimating my knowledge at all, this is my first android phone.
I googled how to install custom ROMs and CWM and TWRP came up, I tried both and neither installed. I unrooted my phone successfully and started phone in fastboot, flashed the .img files and then restarted but nothing new was installed.

tangiers said:
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Why are you saying that? Nobody is hard bricking a phone by flashing the correct RUU.

Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting. <br />
<br />
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Funny guy.
Sent from my HTC One X using xda premium

The FUD is strong in this one...

So what do you guys suggest I do? Should I just bring it back to the store? I got it like four days ago. How do I unroot it? I can't access the market (no brower or market app) so I can't get SU to unroot.

to get back to factory you can do the following
relock the bootloader.
reboot to bootloader and use the command fastboot oem lock
after that install the 1.85 RUU from here http://forum.xda-developers.com/showthread.php?t=1670238
it will take longer than the 10 minutes it says it will take so don't worry.
after that you can unlock again with that same token you used to unlock in the first place.

I'm at work right now so I can't do that yet
If I bring it in without doing that stuff will they know or even care? I have some BS story made up D). Also mine is a Rogers, but the AT&T stuff works with it right?
I appreciate your quick responses

Rogers phone would need rogers ruu loaded

ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?

bman3k said:
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
Click to expand...
Click to collapse
why do you want to return it? For this problem or is there something else?

Yes it is for this problem (and all the ones in the first post) I tried for several hours last night to fix it, but couldn't.
I followed the guides for how to install CWM and TWRP to the word and they would not install. If I cannot install them, I cannot reflash stock RUU right?
I still want the HTC One X... just one I didn't screw up XD.

This will put you back to stock and you won't need to return anything
http://forum.xda-developers.com/showthread.php?t=1658929

Ok, I'll try that when I get home, thanks for your help.
PJ83IMG​_Evita​_UL_Rogers​_WWE​_1.73​.631​.1_Radio​_0.16a​.32.0​... from http://forum.xda-developers.com/showthread.php?t=1543593 is what I'll need right?

Correct.

Thanks for your help, that last guide you linked solved it. The first time I looked at it I misread "lock" for "unlock", but I got it to work now . Thanks for your patience and help gunny.

No problem. I'm glad you got it sorted.

I just got my rogers one x and, I'm fairly disappointed in the storage capacity. What advantages would I gain from routing a phone that is already as fast and responsive as it is?
Sent from my HTC One X using xda premium

[Q] Jelly Bean OTA Update Failed?

My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)

Flameninja00 said:
My OTA Jelly Bean update does nothing but fail. It gets as far in the update as having the little 'Droid with the progress bar underneath, but gets 1/3 of the way and fails every time. I AM rooted.
Tried the following:
Wifi
4G
3G
Factory Reset
Removing SD
Putting SD back in
Updating while rooted (didn't mean to)
Updating without root
Updating while on Temp Unroot with Voodoo Rootkeeper
I'm starting to get aggravated, and I really don't want to have to go through Verizon customer service. Any ideas?
(PS: First post!)
Click to expand...
Click to collapse
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you

flying_dutchman said:
Hi, did you remove bloatware? Possibly the OTA refuses because of this (was in my case....)
Furthermore, attention to how you proceed with the root - in the process of updating I've lost mine - so do check out the psosts regarding root/update, it might work for you
Click to expand...
Click to collapse
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X

Flameninja00 said:
Yes, I did remove bloatware, but when I factory reset, they came back, and worked fine.
Did what 90%+ of posts say. Use Voodoo to "hide" your root while you update, then restore.
Update still failed. Will be calling Verizon when I get home from class today because it's just making me mad at this point.
UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail. He also said that if I can pull it back all the way to factory everything, no root, and they can't tell the bootloader has been modified, then they'll replace it. If they see the bootloader's been touched, they're gonna charge me $299.
I have rooted via MotoFail2Go, would a step in that process be to modify the bootloader? Pardon my ignorance, I haven't done any tinkering into real modifications. Although, now I'm gonna go back and play around with my Droid X
Click to expand...
Click to collapse
I'm having the same exact software. I uninstalled and froze a few bloatwear. Used MotoFail2Go to get my root. So what do we do now??? are you tell me we're stranded unless we beef up another 300.00 for a new device?????? Nahhh all these nerds on XDA someone's gotta have an answer....................right?

I'm glad I'm not the only one having issues, but I agree. Someone's gotta have an idea on what to do, or try next.
Sent from my DROID RAZR HD using xda app-developers app

Well I gave up. Luckily I got Verizon to send me another device
Sent from my DROID RAZR HD using xda app-developers app

same thing happened to me..and yes they gave me another device too...

Ncruze said:
Well I gave up. Luckily I got Verizon to send me another device
Click to expand...
Click to collapse
johnxpotter said:
same thing happened to me..and yes they gave me another device too...
Click to expand...
Click to collapse
I'm assuming you both were rooted via MotoFail2Go? What did you do before you sent it in to hide your root? Just unrooted and restore to factory?
Thanks everybody for your help!!!
Sent from my DROID RAZR HD using xda app-developers app

Cool did your new device come pre installed with job? If not did you have any problems upgrading to job on ur replacement device?
Sent from my DROID RAZR HD using xda app-developers app

Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.

djousma said:
Not that it matters much anymore, but with root, if you actually deleted bloatware apps with titanium, or froze them, but didnt defrost them, the update will fail. Also, if you had safestrap installed, the OTA will fail.
Most you want to do with the bloatware is just freeze it. and then remember to defrost it before the OTA.
Gotta be careful.
Click to expand...
Click to collapse
The bloatware came back and works fine after a factory reset though.
Are you telling me I'm screwed then?
Sent from my DROID RAZR HD using xda app-developers app

No, you are not screwed. You may have to reload original ICS from FBR process. It is documented on this site. I had to do that not because the OTA failed, but because I lost root.

"UPDATE:
Talked to Verizon, and the tech (who is a fellow phone nerd) says that the first step in the update is to check the bootloader. If it's been tampered, it will fail."
I have the Dev Edition with an unlocked Bootloader.. is this why my update is failing?
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean.
When I try to load the update my self through recovery, same thing happens, but the error shows....
assert failed:motorola.update_bl_backup()
Any one...Any one...Bueller.

rebretz000 said:
My Jelly Bean OTA gets all the way to the last tiny bit, then right before the end Andy Android ends up on his back with the red triangle over his open stomach, my phone reboots, goes through the update process and shows update failed but I'm running Jelly Bean
Click to expand...
Click to collapse
Mine fails 1/3 of the way up the bar, but the animation is the same.
Sent from my DROID RAZR HD using xda app-developers app

Hi I am using galaxy S2 i1900g. yesterday i downloaded the jellybean update for my device OTA. when installing it said device will reboot .
After the droid loading symbol it rebooted and now its stuck where the device name "Samsung GALAXY SII" comes and its stuck here for the past 2 and a half hours .
what should i do..... should i reset the device in the middle of installation but that will curru[pt the device right?? Has the installation failed.???? please help

Ota rootkeeper ???

Has any one perhaps used this app
Essentially ist an app that allows you to back up and restore your root access therefore allowing you to take updates over the air and then afterwards allowing to restore your root. I saw a couple videos on you tube but they were all dated months ago I was wondering if any one had any comments or feedback based on there own experience using this tool cause in theory it sounds pretty awesome
Sent from my SCH-I535 using xda app-developers app
Sent from my SCH-I535 using xda app-developers app

I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium

ota rootkeeper
Firealoha said:
I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
is there any chance you could list the steps you did involving ota rootkeeper....i still have ics 4.0.4, stock rooted unlocked. didnt take the jb update cause i didnt want to lose everything....thanks

Both times I used it I was running CM10 stable and CWM touch 6.0.2.3. I then did a full wipe, restored my stock back up, downloaded voodoo and hit "protect root", and then accepted the OTA. It was that easy.
The first phone I carelessly forgot to re-unlock my bootloader using ez-unlock and when I rebooted I got the dreaded triangle. Learned my lesson with the second one. I remember something about having to answer some ?'s during the reboot process about keeping my custom recovery, but I don't remember exactly what they were. The answers were pretty obvious.
Also, I just tried ez unlock now and it says device status unknown. After the update I remember getting that msg too for some reason. I just locked the bootloader and then unlocked it for good measure, making sure to get the "your bootloader has been successfully unlocked“ msg.
Good luck and lmk how it turns out
Sent from my SCH-I535 using xda premium

So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app

MIKEYSAKZ said:
So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry was to busy watching the Super bowl and didnt have acces to a computer on my last post. Hopefully this is a little easier to follow.
1) Return to stock rooted/unlocked ics (in my case it was the backup I made of my phone straight out of the box)
2) Download the app and when you run it, it should have all but one of the boxes checked (you'll see what I mean when you open the app). Click on "protect root" and the final box should now be checked (indicating that a protected su copy is available)
3) I did not select temp unroot as an option, so I cannot attest to what selecting this will do. Once I selected "protect root", I went and initiated the OTA download. I did this with two gsIII's following the above sequence and had zero problems (well, except for forgetting to re-unclock my bootloader).
4) After the phone has downloaded the update it will ask you if you want to allow CWM (or whatever your recovery is) to install the unsigned.zip - select YES and answer YES to keeping root.
5) Once the phone is done booting up go into ezunlock and re-unlock your bootloader before booting into recovery or rebooting the device.
I think most people will agree that this is kind of a waste of time as their are a number of debloated Stock JB ROMS on this forum that you can flash without having to go through all the hassle of doing all this. I chose to do it as more of a learning tool. This is my first Samsung device having owned and rooted/S-Off''ed two previous HTC devices. I am by no means an expert, but this community has been so helpful to me over the last few years,that I figured it's about time I started spreading the Aloha. Good Luck!

[Q] Unauthorized software message ONLY when booting into recovery

This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?

Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.

Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?

Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.

Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?

Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.

[Q] Bad Recovery flash? (SOLVED)

I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich

Anyone?
Sent from my SCH-I535 using xda premium

Never mind...

Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.

david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium

Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app

stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!

I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app

stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium