Trying to flash a rom - Sprint Samsung Galaxy S III

I have sprint gs3 rooted with cwm 6.0.3.1 installed on it. I was trying to flash SuperNexus-2.0-i9300-BUILD4. Zip onto my phone. I recieved an error when it attempted to do the flash. The error was: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. This also happens when try to restore a backup not done by rom manager

Please I hope you where not successful at all. You are trying to flash an International rom. Can't you see it says it's for the I9300 not the SPH-L710??? You will brick your phone. Please stop and do about two more Weeks of reading and research.
Sent from the future via Xparent Green Tapatalk 2

Do what Ed says unless you want a $700 paperweight. Would you put Diesel fuel into your gasoline powered car?
Now I understand why carriers are locking the bootloader.

As said above, PLEASE put the phone DOWN and step away from the merchandise....now go read, read, read, and read. You should never flash roms that are not made for your specific device AND carrier. Ever. No exceptions.

Here are two links to with a wealth of information for you and anyone new to rooting and flashing roms:
http://forum.xda-developers.com/showthread.php?t=1726558
and just to drive the subject home, because it is very important:
http://forum.xda-developers.com/showthread.php?t=2156714

There is another thread HERE that you should look over.

Thank you didn't even notice that. As far as the recovery.log file, what is going on there?

Okikix said:
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Click to expand...
Click to collapse
Use the links above and read Don't worry about the recovery log for now.

Okikix said:
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Click to expand...
Click to collapse
as noted above don't worry about that but be thankful you got that error it just might of saved your phone.

Your device still works?!?! You should be thanking the GS3 Gods right now cause someone was looking over your shoulder lol. I seriouslyyyy question how some people here even got through the rooting process successfully... SMH

Related

[Q] Help Updating Rooted Epic

I have a rooted Epic on Froyo with CWM. No custom mod or kernel.
I got the OTA Update, and it failed.
I downloaded the Zip and tried CWM to install it. And it fails with this message :
Code:
I:Update location: /sdcard/update.zip
Opening update package...
Installing update...
FSR VERSION: FSR_1.2.1p1_b139_RTM
minor position size units id
1: 0x00000000-0x00040000 0x00040000 1 0
2: 0x00040000-0x00080000 0x00040000 1 1
3: 0x00080000-0x00a80000 0x00a00000 40 20
4: 0x00a80000-0x00bc0000 0x00140000 5 3
5: 0x00bc0000-0x00d00000 0x00140000 5 4
6: 0x00d00000-0x01200000 0x00500000 20 21
7: 0x01200000-0x01980000 0x00780000 30 6
8: 0x01980000-0x02100000 0x00780000 30 7
9: 0x02100000-0x12d80000 0x10c80000 1074 22
10: 0x12d80000-0x32f80000 0x20200000 2056 23
11: 0x32f80000-0x3de80000 0x0af00000 700 24
12: 0x3de80000-0x3eb00000 0x00c80000 50 11
(0)(0) bad mapping information
No BadUnit RsvUnit
0: 775 4090
1: 1023 4089
2: 1053 4088
3: 2879 4087
4: 2894 4086
5: 2944 4085
6: 3446 4084
MountFn : RFS File System, location : system
mount: failed to mount /dev/block/stl9 at /system: Device or resource busy
Verifying current system...
file "/system/bin/recovery" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/bin/recovery", "f729fa2bfefbcd4cc31428ad35078d910bbaa369", "1c924ddea21616379df7c7ac4445eb2e54e5b11d")
assert failed: apply_patch_check("/system/bin/recovery", "f729fa2bfefbcd4cc31428ad35078d910bbaa369", "1c924ddea21616379df7c7ac4445eb2e54e5b11d")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Do I have to do a full flash and wipe my phone to get to GB? Can I unroot & try?
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
marschmellau said:
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
Click to expand...
Click to collapse
Hey, I am sure a billion other people are asking this same question left and right, but do you know if any roots are available yet for the 2.3.5 gingerbread update? I am well aware that it takes a while for one to be developed. I am currently rooted with the 2.2.1 froyo and love it so I don't mind waiting for the new root. I just wasn't sure how the headway is going with it. Also, the revert back to stock link you posted, is that to unroot the phone? I'm sure all will be explained for us in due time, unrooting the 2.2.1... installing the 2.3.5... rooting to gingerbreak... yada yada yada...
But yeah, any advice would be great.
I was told be 2 Epic users & Best Buy sales rep, you can get OTA update if you are rooted. But I've also heard that you can't aswell. Hence the question.
So can you unroot without losing data?
infyrno676767 said:
Hey, I am sure a billion other people are asking this same question left and right, but do you know if any roots are available yet for the 2.3.5 gingerbread update? I am well aware that it takes a while for one to be developed. I am currently rooted with the 2.2.1 froyo and love it so I don't mind waiting for the new root. I just wasn't sure how the headway is going with it. Also, the revert back to stock link you posted, is that to unroot the phone? I'm sure all will be explained for us in due time, unrooting the 2.2.1... installing the 2.3.5... rooting to gingerbreak... yada yada yada...
But yeah, any advice would be great.
Click to expand...
Click to collapse
Yes, there is a root available. I'm currently rooted & running ACS ICS v4.
Take a look at this video: http://www.youtube.com/watch?v=KesCXPpa3cI
DjFarout said:
I was told be 2 Epic users & Best Buy sales rep, you can get OTA update if you are rooted. But I've also heard that you can't aswell. Hence the question.
So can you unroot without losing data?
Click to expand...
Click to collapse
Preeeetty sure you cannot get OTA with Root, you need to manually install or flash back to Stock. There are lots of threads about this, with the same answer. Also, Best Buy doesn't know a thiiiing. A friend of mine works there, and she's pretty damn stupid.
Well, since you're rooted.. you should probably invest in Titanium Backup. It can backup your data (contacts, messages, apps. you name it) and restore this all as well. Once you back up all of your data, revert to Stock, upgrade to the OTA, root it, then install Titanium Backup & you'll have it all back.
https://market.android.com/details?id=com.keramidas.TitaniumBackup&hl=en (free)
https://market.android.com/details?...iY29tLmtlcmFtaWRhcy5UaXRhbml1bUJhY2t1cFBybyJd (paid)
I Odined back to stock, ran the update.zip, Odined a recovery, flashed su and then started flashing roms to test. I save my messages with mms backup & restore, but other than that, most of the things I use save to sd. I like a really clean install so I know where my problems are coming from.
marschmellau said:
You need to use the search function.
But here, let me say this again. YOU CANNOT GET THE OTA UPDATE WHILE ROOTED.
You either need to revert back to STOCK and update or manually install GB yourself.. which you CAN do while Rooted.
You're probably going to ask how to do both, so I'll provide these for you as well.
If you want to update this manually while rooted, follow this link:
http://forum.xda-developers.com/showthread.php?t=1337453
If you want to revert back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=1052813
then follow part 2 (For Stock) in the link that was provided for manual update.
Any other questions?
Click to expand...
Click to collapse
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
You're very welcome!
This isn't very hard to understand. You do your research, you follow directions, and you'll have success. If you decide not to do it correctly and break your phone, that is on YOU. You broke your phone simply because you did not read. That is your own stupidity.
Also, you don't check everything in ODIN. You obviously do not know what you are doing, so I suggest reading some things before attempting this again.
Both guides worked for me, without any issue. The same goes for many others as well.
ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
Seriously? You're *****ing at this person because you failed to take the time and research these forums. I spent an entire day reading threads and watching QBKing77's videos to gather all the necessary information and files before doing anything. Also, spare me with any replies to you not having enough time to do so.
Hope you walk away from this with a new found respect for doing research.
Edit: You even posted in the "Everything EI22" thread in the General forum where I gave a typed out how-to for a clean install, or full ODIN to Froyo then the upgrade to Gingerbread. You could've simply scrolled up on page 10 to this post. (Seeing as your post created page 11 of that thread.)
marschmellau said:
You're very welcome!
This isn't very hard to understand. You do your research, you follow directions, and you'll have success. If you decide not to do it correctly and break your phone, that is on YOU. You broke your phone simply because you did not read. That is your own stupidity.
Also, you don't check everything in ODIN. You obviously do not know what you are doing, so I suggest reading some things before attempting this again.
Both guides worked for me, without any issue. The same goes for many others as well.
Click to expand...
Click to collapse
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
ThunderOKC said:
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
Click to expand...
Click to collapse
They see me trollin'..
You're obviously an idiot. I used the method to return to stock just last week. It's not my fault that you can't comprehend simple instructions. That is not the wrong picture, btw. ODIN looks like that.
Also, Out of oh.. I don't know, all of the people I've linked this to, you're the only one who had any issue. It's damn near obvious that you were the one who screwed up.
Do some damn research before you even post anything else.
Oh! And, if you actually used the search function you would learn how to get your phone into download mode so you can reflash stock rom.
I think this is pretty hilarious, btw.
Incorrect!
In the picture, it shows everything checked. Everyone in the chat room informed me that its wrong.
@ThunderOKC,
I live in the OKC area. I imagine you are from here. If you need hand holding help, PM me. I've been around snooping the forums since January. I am now confident enough to answer questions, troubleshooting, and also start producing my own mods. There is always someone willing to help.
I can do this. It just been a long time since I've messed with this.
I just realized the title of that linked thread "How to Restore a semi-brinked Epic..." and this thread is most likely not proper for those with phones being just fine and all they want is to revert back to stock. I"ve searched for the real thread on reverting back to stock, but I can't find it. Nothing stays stickied on here for long. When I get access to my comp, everything there is bookmarked.
For now, don't check all the options as it says. lol
ThunderOKC said:
Thanks for breaking my phone and costing me HUNDREDS OF DOLLARS to get a new phone, because you linked me (and everyone) to that very old thread. In there, it is telling us to check everything in Odin and now cuz of you, a lot of people have broken phone.
Click to expand...
Click to collapse
The only people with the broken phones are the ones who haven't the slightest clue on what to do. Just because you know how to download odin, doesn't mean you should use it. Btw, your phone is soft bricked and its your own fault. Send it to me, ill have it working in 5 minutes fool.
Sent from my Ei22 Epicaladocious
ThunderOKC said:
Incorrect!
In the picture, it shows everything checked. Everyone in the chat room informed me that its wrong.
Click to expand...
Click to collapse
Well then, the picture itself is wrong. Don't rely on pictures for a guide, half the time they aren't correct. Next time, follow it step by step from the directions, not pictures.
b16flybye said:
The only people with the broken phones are the ones who haven't the slightest clue on what to do. Just because you know how to download odin, doesn't mean you should use it. Btw, your phone is soft bricked and its your own fault. Send it to me, ill have it working in 5 minutes fool.
Sent from my Ei22 Epicaladocious
Click to expand...
Click to collapse
Lol, Pretty much what has been said.
Also, ThunderOKC. You do realize that to fix the "soft brick" on an epic means returning it to STOCK. So yes, you idiot, you can use that thread to return to stock without it having a soft brick.
like I said, do some more research
ThunderOKC said:
I can do this. It just been a long time since I've messed with this.
I just realized the title of that linked thread "How to Restore a semi-brinked Epic..." and this thread is most likely not proper for those with phones being just fine and all they want is to revert back to stock. I"ve searched for the real thread on reverting back to stock, but I can't find it. Nothing stays stickied on here for long. When I get access to my comp, everything there is bookmarked.
For now, don't check all the options as it says. lol
Click to expand...
Click to collapse
Funny thing is that thread works for everyone but you. No one has cried about it semi-bricking the phone or that they can no longer afford to get the breast implants, or whatever the surgery was you claimed you couldn't get to because you had to buy a new phone. That statement alone showed your mentality and level of competence. The Red fail means your stock cable is a piece of crap and you should spend $2 of your surgery money to get a good cable. If you just red through the thread instead of running your mouth everywhere you would have seen that is common for Odin and stock cables.
---------- Post added at 05:57 PM ---------- Previous post was at 05:52 PM ----------
ThunderOKC said:
No, you are in the wrong. You're out to brick as many phones that you can. Everyone in the chat told me that the thread/instruction is very old and all wrong. The picture used was wrong. Everyone told me that I did nothing wrong and that I followed everything right.
Warning to everyone, don't try his link to revert back to stock. It will immediately show a red fail in the first box, then your phone will never, ever...not now, not ever...turn back on. Then expect to shell out hundreds for a new phone.
This isn't funny. Not one bit.
Click to expand...
Click to collapse
Actually it is funny. Your level of incompetence shows you should not be rooting or messing with your phone. You are very rude and have no gratitude for people trying to help you. Stay out of the love connection chat rooms asking for help with your phone.
I followed the instructions exactly. In the picture AND in the instructions, say to check it all. Stupid kids, learn how to read and understand. Not my fault. Hell, even had the whole chat room support laughing at how wrong the thread was.
I fixed it on my own. Grow up, kids.
@ ThunderOKC
It's your choice to hack your phone. With that choice comes the responsibility to do proper research beforehand and make educated decisions based upon that research. Otherwise you will likely end up with a paper weight. That is the inherent risk of hacking the phone.
You've been posting all over this forum complaining, and the tone has been down right rude. Welcome to the ignore list.
ThunderOKC said:
I followed the instructions exactly. In the picture AND in the instructions, say to check it all. Stupid kids, learn how to read and understand. Not my fault. Hell, even had the whole chat room support laughing at how wrong the thread was.
I fixed it on my own. Grow up, kids.
Click to expand...
Click to collapse
This is why your stupid. You rely on a picture, and whatever chat room you have laughing at xda devs, are just as idiotic as you are. Your not welcome here douche. Good luck in the future. I think your dumbass should stick with what sprint gave ya.
Sent from my SPH-D700 using XDA App

Rooting went wrong

After the Rooting procedure failed (for some reason), my phone just went popped up with an error "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
EDITS:
Progress 1: Got into the download mode but I cant seem to find the firmware appropriate for it:
SGH-1747M
Baseband: 1747MVLLH1
Progress 2: After scouring the internet I have found SGH-1747M
The problem is its 1747MVLALH1
Rather than 1747MVLLH1
Not quite sure at the moment if this is the right firmware for my phone
Advice would be appreciated
I'm sorry, can you be more clear? Can you not use the phone at all? Also, what method of root did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If you are able to get into download mode then you are good to go, it just sounds like whatever you were flashing was either incomplete or was interrupted, otherwise referred to as a bad flash. Mosy on over to this thread, http://forum.xda-developers.com/showthread.php?t=1739426 , read it through...maybe even twice and flash the stock rom with root. Once this is working you can proceed to installing a custom recovery. The easiest way ti do this is install Clockwork Rom Manager from the market and install ClockWorkMod Recovery. Once you have a recovery (and before you flash anything from here on for that matter) make a backup, this will give you a fall back in case of future bad flashes. Let us know how it goes.
You guys could say that I "bad flash"-ed it
I did rooting before with my S2 and it had no problem but when I flashed the S3 it said that it failed and thats when this problem arose
Anyway is I747MVLALH1 the same as I747MVLLH1 (my baseband)
I'm not sure what 'rooting procedure' you used as you didn't specify, but if you use the guide i linked in my previous post and follow the directions exactly you should be ok and chalk this up as a lesson learned.
dntesinfrno said:
I'm not sure what 'rooting procedure' you used as you didn't specify, but if you use the guide i linked in my previous post and follow the directions exactly you should be ok and chalk this up as a lesson learned.
Click to expand...
Click to collapse
Its the one made by chainfire and I probably got the wrong guide thats why it went like that
I'll try your guide hopefully it works
cant post links at the moment
Thank you sir, I'll probably try the clockwork mod when its confirmed working for Rogers users
It's entirely possible with all the different variations of the GS3, which is why i emphasized you read everything very carefully first, and follow each direction exactly. If something doesn't go as it is supposed then there is a reason, 'i'll just skip that step' rarely works :cyclops:. Let me know how it goes.
dntesinfrno said:
It's entirely possible with all the different variations of the GS3, which is why i emphasized you read everything very carefully first, and follow each direction exactly. If something doesn't go as it is supposed then there is a reason, 'i'll just skip that step' rarely works :cyclops:. Let me know how it goes.
Click to expand...
Click to collapse
It worked great
you literally saved my bum from spending 600 bucks - I appreciate it
for now Im just gonna leave it at that (stock and rooted) since you did mention in the Third step that your not quite sure if it works for Rogers users as well (clockwork etc..)
gek00 said:
It worked great
you literally saved my bum from spending 600 bucks - I appreciate it
for now Im just gonna leave it at that (stock and rooted) since you did mention in the Third step that your not quite sure if it works for Rogers users as well (clockwork etc..)
Click to expand...
Click to collapse
I believe you may have just misunderstood me, but yes CWM will work with Rogers based phones although not being a Rogers user myself i cannot offer any insight to any do's or don't specific to that carrier, if there are any. In any case, i'm glad you got your phone working, i've been in that position a few times myself.
dntesinfrno said:
I believe you may have just misunderstood me, but yes CWM will work with Rogers based phones although not being a Rogers user myself i cannot offer any insight to any do's or don't specific to that carrier, if there are any. In any case, i'm glad you got your phone working, i've been in that position a few times myself.
Click to expand...
Click to collapse
Oh yes, I apologize for that I might try it later on but one last question (if its not too much of a bother)
Would you mind giving me advice on what ROM is a "go-to" at the moment for the S3
Thanks in advance
The short answer to that question is no, as it is really a personal preference as well as device dependent, meaning the same ROM may or may not run the same way on two seemingly identical phones for any number of reasons. Personally I use the JB AOKP, which is also what i used to run on my GS2 , a lot of people seem to like Cyanogenmod as well. The only way to know is flash them and find out if you like them. Just always make sure to have a recovery backup handy in case you dont like it, or if anything goes wrong during the flash. Like i said before, the important thing is to read everything in the post carefully and follow the directions .

Clockworkmod Recovery?

I did some forum searching & Googling but I'm not able to find a reliable, working method of getting CWM recovery on the Note II. I want to keep the stock ROM, but not the stock recovery. I'm rooted with stock recovery right now.
Any suggestions? Thanks in advance.
look harder. Perhaps find a thread talking about root in the at&t noteII general forum.
garyd9 said:
look harder. Perhaps find a thread talking about root in the at&t noteII general forum.
Click to expand...
Click to collapse
"look harder"? That doesn't help me much. I used that "search in this forum" feature, where I typed in "clockworkmod" and came up with no results. A threat talking about rooting doesn't necessarily mean it will discuss CWM (I also checked the thread here for information on CWM, since that's the root method I used, but no dice). Not really sure which thread you want me to play hide & seek with.
Sorry to say but the person who responded to you is right... look for a thread that contains root for the note II
Really? You want to root your phone, but you are incapable of following simple directions? I did everything but give you a direct link to the thread. I told you which forum, which subforum, and a keyword to look for in the thread title.
If you aren't able to handle it, please DO NOT root your device and please DO NOT install a non-stock recovery.
Edit...im sorry guys...I want to keep this place pleasant and friendly.
I googled it and found it here and on the site I quoted.
Artimus009 said:
Here...I dont want to to see this forum to go to $***. Consider this my last spoon feed for the week.
Click to expand...
Click to collapse
Fine - YOU support him if/when he screws it up.
Lets see if I even get a thanks... from the OP.
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
Nevermind...youre right Gary...I shouldn't do it.
garyd9 said:
Really? You want to root your phone, but you are incapable of following simple directions? I did everything but give you a direct link to the thread. I told you which forum, which subforum, and a keyword to look for in the thread title.
If you aren't able to handle it, please DO NOT root your device and please DO NOT install a non-stock recovery.
Click to expand...
Click to collapse
No one is forcing you to help me, if you are going to be rude just kindly ignore me and move on. Also I don't need you to worry about my device, I can handle it just fine.
Android.Addiction said:
No one is forcing you to help me, if you are going to be rude just kindly ignore me and move on. Also I don't need you to worry about my device, I can handle it just fine.
Click to expand...
Click to collapse
Which part about my post is rude? I think you might be misinterpreting...
I'm very serious that if you are unable to find the post with the information you want based on the instructions I gave, that you have a high risk of screwing up your phone by flashing stuff on it. That's not being rude. That's trying to be helpful. Asking you to PLEASE not flash your phone is so I (and others like myself) don't have to spend the time trying to help you fix your phone afterwards (and so you don't have to spend the time asking for that help.)
Not everything on these forums is spelled out and spoon-fed to users. It's assumed that they have a certain amount of innate ability and prior knowledge. Lack of that ability and knowledge results in broken phones. I'm trying to help someone like that in another thread - they flashed the wrong thing to their phone and now, basically, they are screwed.
Granted, I might not come off as "newbie friendly" or even "user friendly." I'm an engineer. I'm one of the folks that make the things that people like you flash. For some reason people like me don't usually come off as being "nice."
I'm going to try (again) to be nice. Here's a link to a post I think it'd be good for you to read. This post tries to explain in a different way what I'm trying to say here: http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
I suspect that if/when you understand that post, you'll better understand my replies.
take care and good luck
Gary
Thanks, it's sometimes hard to read tone on here, so i apologize for any misunderstandings.
I think i have a really bad time finding information, not because I'm a newbie at flashing, but probably more so due to the fact that development in this phone is so fresh, there isn't much information to centralize yet. But once i find the information i need i can usually handle the work involved.
I ended up finding the post you were talking about (well, i can only assume). Unfortunately i didn't find a walkthrough or step by step instructions. But at least i know a better place to find the information.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Does it have to be cwm? Because for rooting, chainfire has cf root. And for recovery, twrp already supports our device. It's all in the original development sub forum. Won't be hard to find either. Those two things are the only threads existent there for now
Sent from my SGH-I317M using xda premium
AlonB. said:
Does it have to be cwm? Because for rooting, chainfire has cf root. And for recovery, twrp already supports our device. It's all in the original development sub forum. Won't be hard to find either. Those two things are the only threads existent there for now
Click to expand...
Click to collapse
Actually, that's a good idea. I had used the CWM Recovery originally on my i317, but found that when I tried to restore a backup I made with it, that nothing was actually restored. TWRP, on the other hand, seems to work okay backing up and restoring.
garyd9 said:
Actually, that's a good idea. I had used the CWM Recovery originally on my i317, but found that when I tried to restore a backup I made with it, that nothing was actually restored. TWRP, on the other hand, seems to work okay backing up and restoring.
Click to expand...
Click to collapse
Twrp has come a long way. To be fully honest, I kinda hated it at first, I don't even have a clue why, since I didn't try it prior to forming those feelings about it. But then I actually got to flash it, after some self convincing, on my s2 lte and it grew on me very quickly. And now, I prefer it over cwm
Sent from my SGH-I317M using xda premium
If you need exFAT then use CWM which comes with CF_root which you can find the Original Dev forums. Use Odin,click on PDA then select the CF-Root.*.att file. It's that easy.
One thing about TWRP is that it doesn't support exFAT formatted SDCards, so if you have a 64GB like most folks on here & need exFAT for larger than 4GB file size, then CWM is the only way to go.
I think i may just wait a bit until more options become available. I don't need it right away. I'd rather sick with CWM since that is what I'm familiar with.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Android.Addiction said:
I think i may just wait a bit until more options become available. I don't need it right away. I'd rather sick with CWM since that is what I'm familiar with.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
That's entirely up to you. Although I would suggest giving twrp a go, even just to try it out. My favorite features in it are the option to name your backup in recovery prior to creating it, and the fact that it actually does things faster than cwm
Sent from my SGH-I317M using xda premium
Since this thread is going nowhere, but south...
Thread closed.

[Q] Won't boot and /sdcard/ won't mount

I was on stock FI27 (I think) and tried to root using:
http://forum.xda-developers.com/showthread.php?t=2139759
I booted successfully into CWM after the ODIN, but when I tried to reboot the phone, it got stuck on the boot screen (with the lock). So I thought I would just go into recovery and flash a custom ROM, but I get the following errors when I try to access the external SD card:
"E:unable to write to ums lunfile" and "Error mounting sdcard!"
The internal SD Card is available though. I've tried pushing the ROM to the internal via adb, but it wont show up. Nothing shows up when the phone is plugged in to the computer. Any suggestions?
Was able to get it to boot by flashing this in ODIN:
http://forum.xda-developers.com/showthread.php?t=1932032
But my file manager is showing no External SD Card. So that issue has not been resolved..
Also, as I'm on FI27, what is the best way to install CWM Recovery? The Auto-Root tool option D only goes to FF18..
Bump.
Try unmounting your external in settings, storage and then remounting.
Just out of curiosity, why not just use a one click to root? Much easier and less chance of error.
Slithering from the nether regions of a twisted mind and tarnished soul
Stryke_the_Orc said:
Try unmounting your external in settings, storage and then remounting.
Just out of curiosity, why not just use a one click to root? Much easier and less chance of error.
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
I didn't think one click would work for my firmware and decided to follow the most popular post. I'll tell my friend to try that and update here. Thanks!
twolves14 said:
I didn't think one click would work for my firmware and decided to follow the most popular post. I'll tell my friend to try that and update here. Thanks!
Click to expand...
Click to collapse
Usually when it comes to stuff on XDA, the popular method may work for you. But that isn't always the case, just think back to high school for a moment. The "popular" kids were always the trend setters whether it be right or wrong, the sheep followed everything they did or said.
Here on XDA or any other tech site, it's always a good rule of thumb to see what the popular method is, read comments from other users, see what works for your situation and what you are trying to accomplish, and determine what the best and easiest option will be that is known to work.
I would rather see new users asking questions before flashing something or altering their phone than see a new user follow incorrect information and result in a hard brick. Basically just read, read some more, ask yourself if you understand what you are doing, read again, then if you are still unsure feel free to ask a question here in Q&A while making it as short and to the point as possible. There are many of us who have been here for over a year and some almost two years that are willing to give you the best answer for your situation.
Sent from my SPH-D710 using xda premium
Mattix724 said:
Usually when it comes to stuff on XDA, the popular method may work for you. But that isn't always the case, just think back to high school for a moment. The "popular" kids were always the trend setters whether it be right or wrong, the sheep followed everything they did or said.
Here on XDA or any other tech site, it's always a good rule of thumb to see what the popular method is, read comments from other users, see what works for your situation and what you are trying to accomplish, and determine what the best and easiest option will be that is known to work.
I would rather see new users asking questions before flashing something or altering their phone than see a new user follow incorrect information and result in a hard brick. Basically just read, read some more, ask yourself if you understand what you are doing, read again, then if you are still unsure feel free to ask a question here in Q&A while making it as short and to the point as possible. There are many of us who have been here for over a year and some almost two years that are willing to give you the best answer for your situation.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I appreciate the advice. But I read comments and read the instructions carefully for each method. The instructions for the method I chose were the newest set and were applicable to the firmware I was on, and almost everyone was successful. I guess I'll ask in his thread how to fix the problem. I've been flashing for about 2 years now, but have no experience with Epic 4G Touch (doing this for a friend, as I own a SGSIII). Thanks though.

[Q] [HELP] Soft Bricked i9505

I rooted my GS4 yesterday and had no issues at all until i tried to flash a MOD to obtain wireless hotspot, but what i didnt notice was the MOD was for a Sprint version GS4. I know know if thats exactly what made my phone brick but im pretty positive because it was during the reboot that the phone got stuck on the TMO screen and apparently remaining soft-bricked. I spent the rest of the night and all of today reading and researching how to fix it myself before coming here to ask for help, so please bare with me.
I have already attempted to flash the official stock firmware using Odin, but it displays an error everytime saying it failed and something about AUTH. Sorry if im sounding vague, i am on a back up phone to use the internet and forgot to right down the exact message.. Anywho, i tried wiping everything and redoing the process and i even tried to flash the appropiate PIT file that i found but it still displays an error and says failed because of some AUTH or SEC problem.
Ive been at this diligently for almost 12 hours. My brain is filled with all these suggestions and methods that i have tried to use to restore my phone back to factory, but none of them have worked. I can still get into recovery and all that, so im assuming that there is still good chance i could fix the problem?
Also i am starting to get myself more and more confused about whether the firmware i downloaded is the right one i need for my phone, it seemed so at first but now i see theres TONS of region codes that can determine the firmware version?
Sorry if im all over the place, but i just dont know which step to take next..
I appreciate any help that is given, and im even willing to pay (some) bucks or maybe even (btc) for someone to walk me through what i need to do or what im doing wrong.
Thanks in Advance
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Toleraen said:
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Click to expand...
Click to collapse
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
koolbreez12 said:
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
Click to expand...
Click to collapse
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Toleraen said:
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Click to expand...
Click to collapse
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
error post
If you can get into download mode i would suggest flashing stock with that then rerooting that way the program downloads all of the nessacary stuff on its own.
koolbreez12 said:
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
Click to expand...
Click to collapse
Welcome!
Sent from my SGH-M919 using xda premium

Categories

Resources