Verizon Samsung S3 I747 ROM issues - Android Q&A, Help & Troubleshooting

Ok first off Good Morning Everyone.
So I'm a noob when it comes to android anything- (gamer music plays in background).
My issues arise when I went through several threads on the forum. Let me first tell you specifically the equipment I have:
Verizon Samsung Galaxy S3 I747
OS version was 4.0.4
Ok, so I have T-Mobile as my service provider.Since this was originally a Verizon phone that was unlocked from the store I bought it at. (Not a Verizon store). Verizon now will not help me update the software. As I said it was OS 4.0.4. I want 4.4.3 (at least).
So since Verizon won't help and T-Mobile said they can't help. I decided I will try this myself. So last night after I got my son in bed. I got on and started reading. I very quickly figured out you better get the stuff that is specific for your device or you will be SOL. Anywho:
I got the phone rooted after about 2 hours of trying to figure out how. And then I found a rom that I thought would work. I then came across this: http://forum.xda-developers.com/showthread.php?t=2580924 which I thought would work.
However after it started Installing System I get the error- set_metadata_recursive: some changes failed
E: Error in /sdcard/kitkat.zip
(Status 7)
Installation aborted.
So being the tech savvy person I am, I decided oh this should be easy to fix. I youtube it and find several videos. One video said you just have to enable signature verification. So I do that. STILL GET ERROR
I watched another video and it says I need to reset the custom binary download so it says YES (0 counts), they tell you to do this through the app store. But I can not get into the android software. It will only turn on to Recovery Mode or the Boot Menu.
So I am at a loss on where to go from here. Could someone help me through this?

Related

[Q] Samsung Galaxy Rugby: various issues

Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- Samsung KIES (PC software suite) doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
I have a Bell as well
Yogi.B said:
Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- Samsung KIES (PC software suite) doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
Click to expand...
Click to collapse
I have the same model and when I try to root it it fails. Also, after installing the drivers on my PC, it shows up as an external drive and when I try to open it, it tells me to put in a disc...??? Any help?
chilli1327 said:
I have the same model and when I try to root it it fails. Also, after installing the drivers on my PC, it shows up as an external drive and when I try to open it, it tells me to put in a disc...??? Any help?
Click to expand...
Click to collapse
The external drive will only work if you select "Enable USB Connection" in the Android menu.
I've revived my phone for a hobby project. Can't remember how I solved the above issues at the time, but it doesn't want to accept the stock firmware image. I can only find one old version on my external HDD with old backup data. Tried several Odin versions to no avail. 3.07 stays stuck at "SetupConnection". 3.04 fails with "Complete(Write) operation failed."
Galaxy Grand Duos
Please padone me for posting in the wrong LOC. It just that my Phone brake down,N I forgot my old XDA account password I had to Create a new 1
Now here is my Q: my galaxy grand dous GT-I9082 just is now on Boot Loop I can't write down any detail about the phone cose it can't boot sorry bout that. Now I boot into CMW then I mistaken navigate to Mount & Storage then On FORMAT SYSTEM after it successfully formated the phone can't boot it stock on the GALAXY GRAND GT-I9082 logo please I need urgent help please it really annoying I had to crearte a new XDA account cose of my phone

Stock S4 receiving "Unauthorized System Software" notice

Hi all,
A friend of mine has a bone stock S4 that he purchased a couple of months ago, and when he looked at his phone yesterday it had a message about "Unauthorized System Software" found on the device, and it has basically bricked the device. He's tried doing a factory reset on the device to no avail. He is not a techie at all, and has not attempted to root or ROM the device (he didn't even know what the terms meant when I asked if he had attempted to do anything). When he contacted Verizon they basically told him, "Sucks to be you, and oh, btw, your warranty is now void."
Needless to say this is ridiculous, so I was curious if anybody else had run into something similar or had any other ideas on how to try and get his phone back up and running without Verizon's BS.
Thanks!
manthas said:
Hi all,
A friend of mine has a bone stock S4 that he purchased a couple of months ago, and when he looked at his phone yesterday it had a message about "Unauthorized System Software" found on the device, and it has basically bricked the device. He's tried doing a factory reset on the device to no avail. He is not a techie at all, and has not attempted to root or ROM the device (he didn't even know what the terms meant when I asked if he had attempted to do anything). When he contacted Verizon they basically told him, "Sucks to be you, and oh, btw, your warranty is now void."
Needless to say this is ridiculous, so I was curious if anybody else had run into something similar or had any other ideas on how to try and get his phone back up and running without Verizon's BS.
Thanks!
Click to expand...
Click to collapse
well if you still have the phone, try odin it to me7. maybe itll fix it
http://forum.xda-developers.com/showthread.php?t=2357235
manthas said:
Hi all,
A friend of mine has a bone stock S4 that he purchased a couple of months ago, and when he looked at his phone yesterday it had a message about "Unauthorized System Software" found on the device, and it has basically bricked the device. He's tried doing a factory reset on the device to no avail. He is not a techie at all, and has not attempted to root or ROM the device (he didn't even know what the terms meant when I asked if he had attempted to do anything). When he contacted Verizon they basically told him, "Sucks to be you, and oh, btw, your warranty is now void."
Needless to say this is ridiculous, so I was curious if anybody else had run into something similar or had any other ideas on how to try and get his phone back up and running without Verizon's BS.
Thanks!
Click to expand...
Click to collapse
You could try kies or use the software update utility/repair utility that comes on the phone. Plug the phone into a computer and install the vzw utility. When it comes up select repair utility. It will put into download mode and flash the latest firmware. Used it several times it works great.
Yoshi and Eris,
Thank you both; I will pass these suggestions along! I appreciate the suggestions.
An interesting addition to this story, it appears the S4 in question has its bootloader unlocked. On the phone's bootup screen, it shows the familiar unlocked padlock icon, and a message that says "Custom". It almost sounds to me like a botched system update somehow got pushed to his device, but we're still in the dark about what caused it. He apparently did another factory reset and he's able to use the phone without the unauthorized system software message, but the whole situation is extremely bizarre.

[Q] Dark Bootloader with S-On. Options?

I have an AT&T HTC One I bought off swappa. It was fully converted to the Google Play Edition. About a week ago I clicked install update when it popped up (dumb probably). It rebooted and showed a "no command" screen with a keeled over android guy with his stomach open and a caution sign there.
I took it to Seattle Android Guy who tried to get it all stock by locking the bootloader and turning s-on, but it wouldn't take it because the bootloader was still the dark bootloader. I took it back home and managed to get TWRP Recovery on it, but it won't take any of the roms I try to flash over to it or install via TWRP. I am pretty new to everything so if you have a solution, the more detailed the better. I've read that it's possible it is bricked, but I really want to keep looking for a solution. I paid almost $400 for this device and only got a couple weeks use out of it. Any suggestions, ideas, or help would be greatly appreciated.
Thanks.

SII key/in-call audio problem after JB update

Hi friends, i am asking for help regarding my gt-i9100 unit.
This phone was given to me as a gift, and so i happily accepted it. i noticed that it ran
on gingerbread (not sure what version though). after a while i checked for update via wi-fi
and i got a message that a new update is available. so i happily downloaded it.
this is where the problems started.
after downloading the update i got stuck on the loading screen for the update (the white screen with the loading bar in the middle)
but it never progressed after a day (yes i waited that long). after googling about it i found a workaround via the recovery mode. i wiped the cache and did a factory reset.
after that the phone worked fine again.
then i got the message to update again, same thing happened. i tried googleing again and found out about odin and flashing roms.
i'm not an expert so please do comment on what i did.
-turned on the USB debuggin thing.
-downloaded odin.
-downloaded firmware (philippine version as i am fron the philippines) from sammobile.
-powered down the phone, entered recovery mode
-flashed the rom with odin-it said PASS and failed=0 so i think i did nothing wrong.
-after that voila i now have jellybean 4.2.1.
i thought it was fine, until i noticed one thing, the keys (the 3 buttons-home, back, menu) all lit up fine, but didn.t work.
well actually the home button worked, but it now appears to be a back button.
and when my girlfriend called me, i can't hear a thing, although music plays fine.
my girlfriend also told me that she cannot hear me, so i think there' s something wrong there.
i believe this is a software issue, but i'm not an expert.
i want to take it to the samsung center but it is still closed until the end of the holiday center.
also i'm trying my best to keep me from spending cash on this phone (taking it to the service center is my last option).
i have followed similar steps on different threads but to no avail. maybe i'm just doing something wrong.
i need your expert opinions.
any help will be appreciated. thanks guys in advance!

Installed Kies Air update now phone won't boot

Hello everyone,
I have a weird problem I'm trying to solve for my cousin, he clicked on his "Updates available for…" notification and he said one of them was Kies Air, he let it update and then his phone said it was going to restart, once it restarted he got a Security Error screen with red text at the top "SECURE FAIL: Modem". Now his phone won't boot up at all. He took it to his local T-Mobile store and they didn't know what to do, they also treated him like he was some noob who failed to root his phone (my cousin doesn't even know what rooting is). So they told him this is a time to learn and to check out "android forums".
Now he's brought it to me and I've only found one thread with anything pertaining to this error:
http://forum.xda-developers.com/showthread.php?t=2791494
I'm going to try some of the tips in there but I'm just wondering if any of you have encountered this same problem with your T-Mobile S5's?
Tiny update as I'm writing this: he said his phone didn't come with Kies Air, but somehow he installed it when he got dropbox.
Got it working now.
Since the error was mentioning the modem I figured I'd try and flash a stock modem through Odin, and that worked. Pretty basic fix.
I wasn't sure what firmware he was running so I installed the NCH modem from here:
http://forum.xda-developers.com/showthread.php?t=2761412
Hope this is helpful for anyone in the future.

Categories

Resources