CWM Backup and Restore: It backs up fine. But it won't restore. I can't remember the error message...something about rfs and can't mount. I know that's not much help. I was wondering if anyone besides me has had problems restoring with this version of CWM, and has a fix for this problem. I have presently done several backups of my stock rooted GB 2.3.6. And I can't restore any of them. As a noob to the Samsung Charge, I have very little knowledge to work with on this. But it seems to me that I read something somewhere that said I needed to use ADB to do something. Darned if I can remember where I saw it. Any help here would be appreciated. Thanks in advance.
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
trparky said:
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
Click to expand...
Click to collapse
if you don't mind my asking why is it banned from being posted now? that's the orange 4.0.1.4 version that was up publicly for months and had few issues besides the voodoo menu being removed/disabled... I guess if imnuts ok's it I'll post or pm a link to anyone who needs it
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
trparky said:
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
Click to expand...
Click to collapse
ah yes I remember, something about imnuts himself wanted to host it to keep track of support and downloads.. nevermind then I won't post publicly but if anyone wants it just pm me
blazing through on my Acer A500 via XDA app
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Lexus One said:
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Click to expand...
Click to collapse
backups may or may not work with the new 5.x CWM, some people say they can do it and doesn't work for others so I'd just stick with the 4.x CWM... voodoo options were removed from CWM due to them not working right or not working at all sometimes when trying to disable lagfix which caused bootloops and softbricks
Same problem on Samsung Epic 4G. Backed up rooted stock FC09 & flashed to CM9 Beta 3. Attempted to restore the stock FC09 & error message popped up. I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
---------- Post added at 07:52 PM ---------- Previous post was at 07:14 PM ----------
Just Reposting To Give Further Detailed Info
I'm sure you already know of this issue but, I'll re-post here as from my understanding, this is updated most often & I'm really amped about this project.
Major stock Samsung Epic 4G Gingerbread FC09 restore issue.
I did this exactly:
1) Started stock FC09
2) Odin to cwm-5.0.2.7-epic4g.tar.md5
3) Flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip using CWM 5.0.2.7 recovery mode (volume down, camera button & power button combo)
4) Backed up rooted stock
5) Attempted to restore the stock FC09 to make sure it works before I got too into the new release
6) Error message popped up
7) I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
Again, my deepest apologies but, right now, I'm like the kid who missed the ice-cream truck. I'm not new to flashing but, am new to trying to run a restore. I only wanted the stock FC09 back because Swype wasn't included in the CM9 Beta 3 release & the text messaging background is white (kinda thwarts the sleek, stealthy black color scheme). Will there be a black text messaging background soon? Let me know if I can install Swype using Titanium Backup or any app backup app. If I can at least have Skype, I'll be good as my Beta 2 Bluetooth issue has been corrected.
---------- Post added at 08:03 PM ---------- Previous post was at 07:52 PM ----------
Sorry. I meant to say I flashed Deodexed-FC09-BML.zip before I flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip
---------- Post added at 08:23 PM ---------- Previous post was at 08:03 PM ----------
Brain farts today >.< I also ran a CM9 Beta 3 backup before I attempted the stock FC09 restore. After the FC09 restore failed, I tried the CM9 Beta 3 restore & that worked perfectly so, again, my suspicions lye in the wrong date stamp factor. At some point tonight, I'll test this theory and post the results. If anyone beats me to the punch, awesomeness.
So you bumped a 5 month old thread in the Charge forum to say you had a similar issue with an Epic 4G?
Well
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Casey Stellar said:
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Click to expand...
Click to collapse
You can clearly see at the top of the screen what forum your in. CWM is individually built for each phone, and not every phone is going to support the same features in the same way. Chances are, no one here is going to know anything about the Epic unless someone here just happens to own one.
Wow
Man that thing's tiny. But, as I stated, I didn't notice that & I only posted because the rules say try not to start a new thread concerning a topic that's already been posted. I'm aware each CWM is custom to every phone. I posted the exact details in case someone does notice this thread & has a solution or a definite no it can't be done. I have read on other posts that CWM will restore other custom non-stock ROMs just fine. One source claims people have been able to restore stock back-ups just fine while others have not. But, there were no definite solutions or enough details to go on. Still waiting for a return on that.
XDA (and others) are built around the idea of device specific forums as there are many differences between devices, even in the same family, that prevent anything for one device from working on another. The Droid Charge, as an example, is in the Galaxy S family, but none of the Galaxy S stuff will work directly on it. Even further, the Galaxy S Aviator and the Droid Charge are the same hardware for different carriers, and nothing for the Charge will work on the Aviator. Don't hesitate to make a thread in one device forum just because a thread exists in a different device forum. There's a "Search this forum" button at the top of every subforum. Use it for your device, and post in that forum if you can't find anything.
O.O
Well now I know I've been up to long. I didn't even realize the fact he said "Samsung Charge" nor was I aware there is a Samsung phone called Charge. But, in my defense, I attempted to start a new thread but, as I was typing out a title for the post, the site showed suggestions of other posts that may have my issue already resolved or at least discussed and this one seemed to be the closest. Had I known the Charge was a phone, it may have stuck out more & I would've known I was in the wrong place -_- Silly me. I am glad to announce however that after a little tinkering, I think I have found the solution to my issue. I'll post any results and details in the proper forum. Sorry for any inconveniences.
Related
Im really new to rooting phones && this ODIN stuff. I want to get the Glorious Overdose rom but I need KJ2. I downloaded the [ROM][ODIN] T839UVKJ2 (Sidekick 4G) Firmware [13.10.11] but it got my phone stuck in the logo screen loop. I really want the rom , can anyone help ?!
bump..
This is my first post - but have spent the past few weeks searching through the depths of xda. I know the rules, and am rather turned off that questions get immediately shot down.
I'm not new to this but am no expert either. My phone is soft bricked, though not the first time and been able to get myself out of it a few times. However I am not stuck, trying in ODIN, but either am not receiving the proper files to download on this on other forums, or something is not working.
I've had a ton of questions but tried to trouble shoot, since it appears most on here either get ignored (hence above) or receive a weeks worth of "WHY are you asking questions dumbass?!" responses without help.
Though there are alot of you that have been tremendous help, through reading your responses to those have similar questions.
Anyway - bump this subject - Ive downloaded multiple zips and files relating to what my sk4g needs to odin properly, however none have worked. some have made it through odin, but reek havoc on the phone and still will not boot.
does anyone have the modern rar and mc5 files i need to odin flash my sk4g. ultimately im looking to flash glorious overdose and soo close, only to end up sooooo far behind with bricks.
any help or file links would be great
Hey guys. I know how you feel on the no answering of the posts. I got a lot of that when I first started out. Don't get discouraged though. I think both of you guys are soft bricked. Go to this site http://www.youtube.com/watch?v=X6H-5SSE0E0, he will give you a full description w/ video on how to odin back to normal. Make sure your phone is in downloading mode (there is a vid link for that too.) I myself am tryin to find a way to get to get the update, so i can try another rom. Hope this helps, don't get discouraged!
the link is not working i am trying to do this too! damn government.... does anybody have a good working link?
this is only to get back from a soft brick. as far as trying to switch over to kj1 im not too sure. been tryin to find a link or post about it. the link works fine for me.
---------- Post added at 08:00 PM ---------- Previous post was at 07:44 PM ----------
ok guys. odin your phones using the link earlier. when that is done, you will be back to stock. after that go to http://support.t-mobile.com/docs/DOC-2452. this is tmobiles site which will give you the samsung klies app, which will then update(when directions are followed) and you will have kj2 operating system. from there you root your phone, and can put on your new rom. search the internet guys. i bounced around 3 different sites and found the answer in about 10 minutes. seek and you shall find...
Just to update. I did try and it did not work. trying to find a fix guys.
---------- Post added at 11:25 PM ---------- Previous post was at 10:30 PM ----------
Just to let you guys know i tried the Heimdall file and it worked fine. Had to try about 5 times but it worked. Phone wiped to original state and now doing the klies upgrade for the phone. will be flashing glorious overdose in a second.
This thread seems to be developing pretty nicely..
I need help with my bric.. I mean Sidekick.
Soft-bricked it trying to flash Smooth Maximus I believe..
I can get it into download mode but I need mirrors.
does anyone have the KD1 or KG2 stock .tars? If so, a mirror would be VERY helpful to quite a few people now.. =\
EDIT: I found a firmware claiming to be newer than the 2 mentioned above. It is labeled "KH1" instead of either KD1 or KG2.
http://hotfile.com/dl/145788939/08a9a06/SGH-T839_T839UVKH1_TMB.zip.htm
That is the address to it, I just downloaded it so I can confirm it is a working link.
You will need the password to open the file, and to get it, sign up on samfirmware.com (free), and look for the password for files containing the symbol "##".
It should be in place of the KD1OdinSTOCK.tar, or the KG2OdinSTOCK.tar, along with the .pit being sk4g.pit.
Any questions or comments, (I'm not an expert by any chance at all) Ask me and I'll try my hardest to answer.
Is KH1 a beta because my sidekick doesn't detect it as an update?
Hi guys. I get new ICS firmware pack directly from the OEM, but when i first try to upload it into the device using Odin 1.85, the device got corrputed.
It can only boot up in flash mode (which means is not completly wroken), and the model displayed there is P7560 and the flasher counter changed to 1.
Of course the rest of the flashing process has failed several times.
After contacting the OEM for support, they had created a custom PDA section for my problem, and the flashing went fine, but now the device is not recognizing the touch of my fingers.
They told me that, somehow, the first firmware package has corrupted the boot.bin (where the kernel information is), and they have to recover it with some secret process they are not allowed to share.
Does any one have a clue what they are talking about????
thanks
yes and no.
first can you can you kindly share more info about getting the ICS firmware leak? We dont want to get anyone in trouble, etc. just curious. Are you sure it wasnt someone playing a cruel joke?? GT-P7560 is a Tab Plus w/3G 32GB if not mistaken the GT-P6200L is 16GB.
What did you mean by "he created a custom PDA section for you"?
As for the "secret process", could be a number of things. Could be reinstalling touchscreen firmware or a new boot.bin, which arent incredibly secret. Most likely he probably just wants to reset your custom flash counter binary(and perhaps a second hidden secret counter as well, that supposedly counts how many times your 1st counter has been reset..if such a thing exists). There is an app by @ChainfireXDA which will reset your custom binary count(dispayed in Download Mode) on ICS.
Please keep us up to date on any new findings.
Well I think this *unofficially* officially confirms someone from Samsung is /actually working/ on this update.
Hi there. I am 100% sure it was not a joke. I get this firmware from someone inside the company. Don't want to give more details about that for not burn anyone
That person didn't know much about what he was giving to me, so he putted me in touch with someone more in engeneering enviroment, for his language.
They asked me for some details, and after that they sent me the file i mentioned before. I flashed the tablet and it came back to life, with its limitations on the touch, and i can not do anything with it
I suggested this idea of reseting the counter, the same way we did for the I9000 for example, but they told me that because of that mismatch of models, that won't be possible.
Do you know how to run that program from download mode? or recovery mode?
thanks
so after giving them your details they gave you this mismatch firmware. yikes.
would it be possible to share the leaked package they gave you? I dont want anyone to flash it, just the devs to have a look.
worst case scenario : they look at it and says its total rubbish.
best case scenario.. they fix camera and wifi, etc...
It may be possible to reset flash counter from recovery mode using a script.
If we knew about their secret process, it wouldnt be a secret. Obviously more than just Odin though.
They didnt happen to whisper any release dates did they?
thank you.
---------- Post added at 09:20 PM ---------- Previous post was at 09:14 PM ----------
edit: this post proves its possible... http://forum.xda-developers.com/showthread.php?t=1578184
however he is doing a raw write which is very dangerous, using an untouched secondary bootloader.
It may be even easier using a script, Chainfire's method knows the location of this variable, and just changes the number. I would try it that way if I had to.
hi!
can you give me the converted software for p7560, because i didn t find anywhere. I want to try that,because my tab dont want to start.
Thank you!
Hi guys, I need some help here. I'm not new to this at all and have rooted TONS of phones for people and myself. Something strange just happened though. I was attempting to flash a ROM (specifically Energy HD 2.0) through CWM. The flash was unsuccessful, which happens at times, so I thought "no big deal, I'll just do a quick restore and try again or try a different one". I chose the backup I wanted to restore to, it did the restore, it said it completed successfully, so I chose reboot. When I looked at it again I realized I never saw the boot animation or anything so I checked it.....dead. The phone wouldn't boot, wouldn't go into recovery, nothing. I've pulled the battery several times, tried both the stock recovery and CWM and I get nothing but a black screened brick. I don't even get the Samsung logo. I have no idea what I could have done here. I attempted the method in this thread - http://forum.xda-developers.com/showthread.php?t=1840030. The only problem there is that I can't even get my device to go to downloading mode. I literally does nothing at all. When I connect to the PC, I get the sound of a USB device being connected, but no access to it and as far as I can tell the PC doesn't even see it. ODIN does nothing either because the device doesn't show up (it was showing up before). I'd really appreciate any help anyone can give on this as this is a brand new phone and I'd hate to think I bricked it beyond recovery somehow. Thanks in advance!
Your bricked because you flashed a rom on your verizon S3 for an international s3 variant. It's amazing you even got far enough to attempt a restore, but the damage was already done, as your nandroid was trying to run on an already corrupted system. You're up the Creek there my friend, sorry. There are links to a company that fixes them for $60, I can't remember the name, so I can't post the link, but will if I do.
---------- Post added at 04:09 AM ---------- Previous post was at 04:06 AM ----------
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Here's the link, thanks prdog for posting in thread below this one.
Stunned at the fact you made the mistake of flashing a rom from a different carrier that is a HUGE NO NO.
Sent from my Galaxy SIII
annoyingduck said:
Your bricked because you flashed a rom on your verizon S3 for an international s3 variant. It's amazing you even got far enough to attempt a restore, but the damage was already done, as your nandroid was trying to run on an already corrupted system. You're up the Creek there my friend, sorry. There are links to a company that fixes them for $60, I can't remember the name, so I can't post the link, but will if I do.
---------- Post added at 04:09 AM ---------- Previous post was at 04:06 AM ----------
Here's the link, thanks prdog for posting in thread below this one.
Click to expand...
Click to collapse
Wow. I seriously can't believe I did that. No more flashing when I'm wasted... :cyclops: Glad I'm still in the 14 days and I can swap it out as DOA. If I can't turn it on to check it, they can't either.
Wow, glad I haven't made that mistake yet. I can see how easy it would be though.
Friends don't let friends flash fried. Good lesson in there somewhere 8 guess.
Alcohol + cell phone + boredom = brick.
The only reason it happened is because instead of going straight to the XDA Android dev thread for the phone like I normally would to find a ROM, I googled "best ROM's for GS3" and the list I got apparently was written by someone overseas (I now realize looking back at the article). I just clicked a link to one of the ROMs that looked cool and the link was actually to XDA anyway so I felt fine about the whole thing. Until my phone bricked that is...
wisdroid said:
Wow. I seriously can't believe I did that. No more flashing when I'm wasted... :cyclops: Glad I'm still in the 14 days and I can swap it out as DOA. If I can't turn it on to check it, they can't either.
Click to expand...
Click to collapse
Yes, committing fraud when you made a mistake yourself it the right thing to do.
Man up and pay to get it Jtagged imo. If you can't afford to get it Jtagged, you shouldn't be flashing ROMS.
Things like this are probably the reason the bootloader was locked in the first place.
Alright, so I need a little help here deciding what to do next.
My girlfriend has the SGH-T959v with android 2.2.1 on it.
It had been randomly shutting down when the screen turned off. It was much the same as the Samsung Captivate had its issues.
It also wouldn't charge sometimes and would also not turn on unless the battery was removed.
Well, I replaced the battery with an OEM one from a mobile store.
Now there are no more random shutdowns but there's a whole slew of different issues.
If the phone is turned off you have to remove the battery, put it back in, plug it in quickly, and then turn it on.
If the phone charges too long all the signal stops working until a reboot.
The phone always thinks it's charging even when the battery is draining.
It's a pretty irritating problem especially with the reboot issue because if we're out and away from electricity and it gets turned off accidentally then there's nothing we can do till we get back to the charger.
Has anyone had these issues and solved them with a new ROM?
I had the random shutdowns on my Captivate and solved it with CyanogenMod. I'm thinking about flashing but I don't want to wipe it all and then have it not work or brick the thing (it is unlocked on Straight Talk so I also don't want to relock it to T-Mobile)
Some foresight would be appreciated before I move forward with it.
Thanks
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Yes, flashing a better ROM will help in certain cases
pisherthefisher said:
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Click to expand...
Click to collapse
Actually my question was whether or not anyone has had this issue.
I'm trying to see if it's a known firmware problem or a known hardware problem so I don't waste my time.
I don't have all day everyday to backup the phone and flash and test and then reinstall all the apps.
Thanks for the contribution though.
That being said would anyone suggest a TW ROM for this? I don't want to change the functionality because she's used to TouchWiz and not tech savvy
Now I must throw in, you should search around for a TW styled ROM. I don't know if we have one or not, but I can tell you that looking yourself will be a lot quicker then waiting for somebody to feel sorry for you, search for it, and give you a link to it.
Ignore those guys. Dont flash a custom rom YET.
http://forum.xda-developers.com/showthread.php?t=1822626
Read that post follow the directions. I suggest reading the thread it links to while backing up the phone. Then while actually doing the flashing with heimdal follow it.
Now be sure to follow eollies directions of flashing the kernel after the initial boot or wifi will be broken.
This will wipe her phone out and reflash everything plus give you root access to remove bloat and add things like titanium backup.
---------- Post added at 07:49 PM ---------- Previous post was at 07:37 PM ----------
Whoops looks like eollies pulled the file from dropbox.
Just follow the directions in the thread by lumin30 that eollie links too.
I forgot to say why I suggest using a one click. This device sometimes just needs to be reset to factory. And Using a one click will remove all stuff not suppose to be hanging around.
Here's another one that I find much more simple.
Heimdall One Click back to Stock for the T959V
I have the grimlin remover one click on my computer I can upload it later
Cooptx said:
I have the grimlin remover one click on my computer I can upload it later
Click to expand...
Click to collapse
I have it also, but cant get it to upload for whatever reason. So.....
Here's the link: http://forum.xda-developers.com/showthread.php?t=1500427 Post #41 has a working DL. get it, unzip, run it. Maybe it helps him.
Use the heimdall one clicks they are 2.3.3 stock touchwiz. Like I said follow lumin30's guide to the letter. He is a recognized contributor for a damn good reason. That guide has also been featured on the portal. I would flash the antonx kernel after for root and then flash bhundvens latest kernel. This will allow just a bit more control and troubleshooting if something happens.
Alright, I was just throwing it out there xD
Really guys? You're not even answering his question and linking him to old guides that are complicated. If someone needs to go to a stock KJ6 rom just link them to lumin's guide!
Anyway, I doubt you will find anyone on these forums who are still running the 2.2.1 stock rom, I personally haven't run it in over 2 years when I first bought my phone.
Samsung has released an official update from Froyo (what her phone is running) to Gingerbread (the last officially released version for this phone).
I recommend you try that, but know that there is a long-sms bug. If you go over 140 characters the message will get cut off and you will get a "message sending failed" notice when you try to send it. You can instead try to use a 3rd party app like handcent or gosms that will split the message for you if it goes beyond 140 characters.
If you would like an easy to follow, reliable guide WITH PICTURES, then go ahead and follow lumins' guide:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Just remember that everything on her phone will get wiped, but you can use google to back up contacts. It sounds like it'll be worth it.
Again, lumin's guide will allow you to upgrade her phone to the last official rom Samsung released for our phone.
Good luck!
I wonder if Samsung kies is still upgrading.
I have been a long time lurker of XDA. Usually with some diligent searching and several hours of reading threads to understand, I can figure out what I need to do. I spent five hours yesterday and feel I'm no closer to a solution than I was when I started. So I think I need some help dissecting my problem so I can focus my searches better.
My wife and I both have a Samsung S3. It is my standard practice to throw on my own Recovery, snag the earliest possible nandroid backup, and then root. I like to run CM but my wife prefers the stock ROM. With my wife's S3 when a new OTA update is available and nagging her I would roll back to the backup that would take the OTA update. I haven't figure out why some do and some don't. Once fully updated I snap another backup and on she rolls.
Now my problem and you've probably already figured it out. I am getting a Status 7 on just about anything I do. I tried tons of stuff and all of it resulted in a Status 7. This is the first time that I have to ask for Android help because I don't understand the moving parts of the problem I'm having. Any pointers would really help.
I would like to list everything I tried, but I'm not sure I would paint an accurate picture since I was furiously searching and trying things in any fleeting direction yesterday for over 5 hours. I can list some bullet points, but don't assume any of them are fully explored, or done in proper order.
I read about knox'd firmware and ROMs. I'm not certain if that's related to my problem space.
I read something about RUU, but I seemed to have lost the bead on that one.
I could comment out the assert that is failing, but that is a huge risk that I'm not sure I want to take unless I can get out of it.
I upgraded to latest CWM and the status 7 still happens.
I have done factory resets and the status 7 happens.
I'm not exactly clear on what I did, but I recall wondering what had changed to cause the status 7 because I couldn't do updates from old backups that I used to be able to do updates from. It's like something changed on the phone.
If someone has any ideas, could you point me in the right direction?
Hi there!!
There seems to be many threads about status 7 errors, for the s3 as well as other devices. Its a common error.
If you search on status 7 and s3 you will find a lot.
But I found a couple very detailed guides.
This one is non device specific....
http://forum.xda-developers.com/showthread.php?t=2302599
This is about the S3's boot loader....causing status 7 errors. Perhaps you are not on the right boot loader for what you're trying to do?
http://forum.xda-developers.com/showthread.php?t=2302599
And this is how to return to stock, which is an option if nothing else works. Then you can start fresh....
http://forum.xda-developers.com/showthread.php?t=1725839
I'm not sure which S3 version you have, so be sure you use files made for your version if its not one of the models mentioned in the above guide.
Good luck! ?
KJ said:
Hi there!!
There seems to be many threads about status 7 errors, for the s3 as well as other devices. Its a common error.
If you search on status 7 and s3 you will find a lot.
But I found a couple very detailed guides.
This one is non device specific....
http://forum.xda-developers.com/showthread.php?t=2302599
This is about the S3's boot loader....causing status 7 errors. Perhaps you are not on the right boot loader for what you're trying to do?
http://forum.xda-developers.com/showthread.php?t=2302599
And this is how to return to stock, which is an option if nothing else works. Then you can start fresh....
http://forum.xda-developers.com/showthread.php?t=1725839
I'm not sure which S3 version you have, so be sure you use files made for your version if its not one of the models mentioned in the above guide.
Good luck! ?
Click to expand...
Click to collapse
I have the Samsung Galaxy S III L710.
I did try the recovery version issue. That didn't help. I think my best option is to return to stock. I will see if there is a return to stock thread for my phone.
Thanks!
You could try twrp.... Just be sure whatever recovery you use, that it is definitely for your model. Or that can give you status 7 errors too.
---------- Post added at 12:00 PM ---------- Previous post was at 11:57 AM ----------
Here's a return to stock for your model... http://forum.xda-developers.com/showthread.php?t=2591818
Though I'm not a big one click fan, or toolkits. Lol
And here's another.... http://forum.xda-developers.com/showthread.php?t=2605812
KJ said:
You could try twrp.... Just be sure whatever recovery you use, that it is definitely for your model. Or that can give you status 7 errors too.
Click to expand...
Click to collapse
I will give TWRP a shot since that's easy to do. I will post back what works, and what doesn't.
If twrp doesn't work...return to stock might be simplest answer. ?