Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
ANSWERED - Firmware Install - factory reset in recovery
I made a mess of a rom install rushing through rom Manager and now my phone can't get past the Samsung screen when booting, and I can't find out the version of my kernel to install the correct one without getting my phone on. I can get the phone into download mode and I have tried a number of different kernels but have had no luck. It's a UK phone so I know it's a XW or XX to start, I was wondering is their a kernel that works on any SGS2.
I have been having trouble with getting windows to recognize the phone and have found a number of fixes on this site which have worked and not worked (atm not connecting)
it's a sgs2 GT-i9100
Any advice greatly appreciated
Did you make a Nandroid backup? If so boot into recovery (vol up, power, home buttons) and restore the backup.
Can you get into recovery mode. Vol up plus home plus power. Then do a factory reset. this should get past the Samsung boot screen. Then flash another rom.
Sent from my ThinkPad Tablet using XDA App
Thanks for getting back, no unfortunately not, couldn't see recovery mode since the original failed rom install. That combination gets me to download mode now.
So as far as I can tell I need to get a firmware working properly or do a reset but I don't know which is the right firmware to use
Main thing is you can get to download mode. If you can do that, you can fix your phone 95% of the time.
You can find carrier/country specific firmware here or country-only/non-specific firmware here
owen5y said:
Thanks for getting back, no unfortunately not, couldn't see recovery mode since the original failed rom install. That combination gets me to download mode now.
So as far as I can tell I need to get a firmware working properly or do a reset but I don't know which is the right firmware to use
Click to expand...
Click to collapse
Just flash any CF-root kernel and then you have recovery back. Start flashing from there on.
Lennyz1988 said:
Just flash any CF-root kernel and then you have recovery back. Start flashing from there on.
Click to expand...
Click to collapse
I have tried a number of CF-root kernels and no joy. I tried a few more kernels this morning before work, including cf-root and siyahv2.6.4 and had no luck.
MistahBungle said:
Main thing is you can get to download mode. If you can do that, you can fix your phone 95% of the time.
You can find carrier/country specific firmware here or country-only/non-specific firmware here
Click to expand...
Click to collapse
I actually flashed some of those kernels XWKE1 for example and a few others with no joy.
The problem started when I tried to update the Galent Miui ICS which I see you are running. I (stupidly) didn't read through the statement as I had my NYE hungover and just put the update on my sd and used recovery to update which froze the phone at the boot screen. (I didn't do re-flash and I didn't wipe the data and everything else.) I know it sometimes takes time to boot but I had left it for a half hour to see if it would and no joy. I was no longer able to get to recovery mode so I tried a half dozen kernels with the same problems before putting up a post. I'm not sure would people find it inappropriate to talk about an this problem here, I thought as it's a kernel problem now it would be a better place to find the solution although my own lazy Miui install was the cause.
Flashing just the kernels obviously didn't fix the problem. Have you flashed any of the entire stock firmwares ? Choose the most recent firmware for your carrier/country from the first link I gave you (if there's more than two listed).
owen5y said:
I actually flashed some of those kernels XWKE1 for and a few others with no joy.
The problem started when I tried to update the Galent Miui ICS which I see you are running. I (studidly) didn't read through the statement as I was hungover and just pu the update on my sd and used recovery to update which froze the phone at the boot screen. I know it sometimes takes time to boot but I had left it for a half hour to see if it would and no joy. I was no longer able to get to recovery so I tried a half dozen kernels with the same problems before putting up a post.
Click to expand...
Click to collapse
MistahBungle said:
Flashing just the kernels obviously didn't fix the problem. Have you flashed any of the entire stock firmwares ? Choose the most recent firmware for your carrier/country from the first link I gave you (if there's more than two listed).
Click to expand...
Click to collapse
Yes I will try that. At work currently and so can't play with the phone. I will post the result this evening.
Thanks
NP. Let us know how you get on.
MistahBungle said:
NP. Let us know how you get on.
Click to expand...
Click to collapse
All good, I installed the firmware and was able to get into recovery mode from there. Did a factory reset because I was stuck in a boot loop. Going to give it a go again to upgrade to the new ics build. Any advice on the best process of getting there?
I installed the following firmware prior to the reset
UK
XWKE1:http://www.multiupload.com/15RY5CHHW9
Firmware info: PDA: XWKE1 Phone: NEKD5 CSC:H3GKD4
Yep. Given the problems you've been having, stay away from the currently alpha ICS builds that are floating around.
Frankly, that's a disaster waiting to happen.
Wait until CM (or someone else) releases something that's stable and has most things working in 4-6 weeks or so.
There's a ton of roms/kernels out there, do your research/reading & ask questions if necessary in the respective threads for those & then pick something out & try it.
And no, I don't do recommendations. Because nobody's phone come's out of the factory the same, nobody has the same phone setup & nobody uses the phone the same way.
owen5y said:
All good, I installed the firmware and was able to get into recovery mode from there. Did a factory reset because I was stuck in a boot loop. Going to give it a go again to upgrade to the new ics build. Any advice on the best process of getting there?
I installed the following firmware prior to the reset
UK
XWKE1:http://www.multiupload.com/15RY5CHHW9
Firmware info: PDA: XWKE1 Phone: NEKD5 CSC:H3GKD4
Click to expand...
Click to collapse
OK, I did like the Galnet Miui ICS rom I was running although there was a few bugs with it when it died it was difficult to charge again. That's fair if you don't want to give out recommendations it's shooting in the dark over the interenet I suppose. I will have a good look through the forum and se if I find something that I would think is suiting.
Thanks for your help, and the advice is appreciated
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
Not my first time to root and install a custom rom on other phone, but this phone isn't treating me well.
So I followed the root guides to root the phone.
Downloaded an insecure kernel for i9100. Although, oddly enough, I bought this phone 2nd hand, and when I went to the "about" part for the kernel look up before tried to root it, the kernel info just contained ICS3.?? (forgot) and the date. There was no four or five letter kernel code like I've been seeing. But according to cnet (one of many rooting tutorials), the kernel version doesn't matter as you can change the kernel anytime, or after rooting in this case.
So I installed Kies to get the Samsung drivers installed. Done.
Restarted phone to download mode (volume down, home, power)
Started Odin 3 v1.83
Phone was recognized. Click the 2 boxes (Auto reboot and F. Rest Time).
Clicked PDA, loaded up an insecure kernel.
Status went through OK, ended up with "Pass!"
Phone automatically restarted.
Now the problem. It restarts, shows the Samsung Galaxy S2 logo with the big triangle underneath it, and thats it. Never leaves this screen. I thought maybe it's a kernel problem, so I tried several different insecure kernels, all with no change. I have no idea how to find what kernel was the original one that came with this phone. Would using Odin with the original secure kernel (or even insecure) solve this problem? Otherwise, what else can I do? My note 2 was stolen so I bought this s2 second hand until I can scrape up enough money for a note 2 again, but the damn thing won't even boot up now. :crying:
How can I get this working again, even to have it stock again I'd be fine (though obviously putting on a custom room with root would be best).
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
TheATHEiST said:
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
Click to expand...
Click to collapse
There wasn't much to try, at least as far as my noob self knows about. I tried flashing 6 other kernels I found, merely taking guesses at which might possibly be the Chinese s2 one, I remember from flashing other phones that i had to look for Z or D in the kernel ID. But all of them just led to the same problem of not booting past the logo screen.
Besides just trying to start it up as normal (which doesn't work) and starting it up in download (by holding down vol+home+power), what others ways can I start it up? I don't know how to boot into recovery, and I didn't know I can flash a rom without first rooting it, which I haven't done yet because it's still stuck in start-up.
Searching enough xda threads and just googling seems show a pretty large consensus supporting the existance of a China i9100, plus I see them everywhere (as well as s3, s4, and notes), so I'm 99% sure they are an official and semi-large market for them here (after iPhones unfortunately). But even still, that doesn't help me locate the original kernel.
Under the battery, is says this:
Samsung WCDMA
Model #: GT-I9100
CMIIT ID: 2011CP2751
Do these help? So is any of the steps I did wrong, or can you otherwise point me in the right direction? Appreciate the help.
Don't post your IMEI (or your SN for that matter).
MistahBungle said:
Don't post your IMEI (or your SN for that matter).
Click to expand...
Click to collapse
Thanks for the tip MistahBungle. Edited out.
Hate to say it, but found more help on youtube... Found a guide that walked me through replacing all the files (not just kernel) in Odin that got it back up and running. I'll follow the xda guides again and hopefully it'll work this time... Thanks anyways...
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
siva aggzz said:
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
Click to expand...
Click to collapse
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
steven2k7 said:
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
Click to expand...
Click to collapse
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
siva aggzz said:
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
Click to expand...
Click to collapse
Will I be able to flash the stock firmware after doing the OTA update? My baseband version is I337UCUAMF3 and the only ROM versions I can find are I337UCUAMDL and I337UCUAMDB.
steven2k7 said:
will i be able to flash the stock firmware after doing the ota update? My baseband version is i337ucuamf3 and the only rom versions i can find are i337ucuamdl and i337ucuamdb.
Click to expand...
Click to collapse
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
siva aggzz said:
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
Click to expand...
Click to collapse
Is there a version or a download you recommend I use? I have I337UCUAMDB that is a .tar.md5 file, but when I use Odin to flash it, it gives an Aboot warning then fail about 2 seconds after I start it. How can I fix that? Do I need to be rooted or not before I flash an update, or does it matter?
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
No u dnt need to b rooted bro for flashing stock rom...
siva aggzz said:
No u dnt need to b rooted bro for flashing stock rom...
Click to expand...
Click to collapse
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
steven2k7 said:
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
Click to expand...
Click to collapse
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Fantassy123 said:
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
Yeah, its not listed there, just two older ones that I can't get to work on my device.
Edit: Just realized my device isn't showing that its custom now. When I boot, I have the normal 'Samsung Galaxy S4' splash screen and in about device, the secure boot status is Samsung. I think I got that somehow with GooManager. Still rooted though as far as I can tell. Tested the phone calling again and seems it only works when my S4 is on speaker phone. I may try and just call samsung tomorrow and see if they will ship me a new one.
Well, I solved the problem. Kinda. I called AT&T warranty support (1-800-801-1101), talked to a guy and ran him through everything I've done. He tried a few things on his end, asked around to see if anyone else had heard of a similar problem (no one had), and they are sending me a replacement and I send the old one back.