i've just flash rom 4.3 for I9300 via odin but my phone is SHW-M440S. Odin showed red "fail" and the progress in s3 was about 10% and i unplugged the usb cable. When i turn on my s3 again, it said that upgrade... and i can only go to download mode. I'm downloading SHW-M440S rom and gotta install it again. May it work? I'm too scared now :crying:
Flash the firmware via odin and it will work for sure. Be sure to perform a factory reset after flashing. This happens for various reasons. No need to panic.
i've flash it again, odin fail and s3 even didnt show the progress
sriram231092 said:
Flash the firmware via odin and it will work for sure. Be sure to perform a factory reset after flashing. This happens for various reasons. No need to panic.
Click to expand...
Click to collapse
I just dont know i could thank you. It worked. Thank for encouraged me :crying: I'm really really crying
But i still want to ask you: why i install new rom but my phone isnt different from its before? My apps and data still there
Fails occur due to various reasons some of them are loose usb connections, drivers problem, Samsung kies running in the background etc., So the stock firmware would definitely recover the phone. And the main point of your mistake is, you flashed the wrong firmware. Glad that your phone isn't hard bricked! The shops won't get deleted most of the times but it's better to backup your data and factory reset the phone from recovery mode for a fresh installation.
Related
i was using:crying: neat rom until today , this morning i was using it simply looking through apps my phone got stuck and now its in a boot loop ....it does not load after the samsung i9100 appears. and i have flashed other stock roms but it is not working and when i do a wipe factory data it again stucks and i have to put the battery out.
adeeljalali said:
i was using:crying: neat rom until today , this morning i was using it simply looking through apps my phone got stuck and now its in a boot loop ....it does not load after the samsung i9100 appears. and i have flashed other stock roms but it is not working and when i do a wipe factory data it again stucks and i have to put the battery out.
Click to expand...
Click to collapse
seems like you are new on xda, so welcome buddy,
download a firmware from sammobile, you have to register yourself, before you can download anything, dont worry, its free. flash this one file via odin3 v3.04, drop the file to PDA, connect your phone with USB and go to download mode, start just everything from begin.
i have tried all the things but i cannot solve the problems
Have you tried flashing a different Kernet?
True, did you try a other kernel ? Dorimanx v8.34, its good, by my side, its perfect, not bugged etc. flash via odin
adeeljalali said:
i have tried all the things but i cannot solve the problems
Click to expand...
Click to collapse
Do a full wipe. It will get you out of the boot loop (hopefully)
Why does it 'not work'? There's gotta be a reason. Does odin fail when it flashes? If so, click the link in my signature and follow those steps.
And you do have an i9100 right? If you do, flash JB leak using odin. Download it from samfirmware. Its a 3 part firmware, and will wipe your device as it flashes. Give it a go.
i have tried all the things done flashing , stock and custom kernels and also the pit files but the behaviour is still the same ......
There"s no quick fix for this (other than buying a new phone) afraid you're here for the 'long haul'........
Look at @Hopper8 s guide for troubleshooting a failed Odin flash and follow it exactly (all steps) and repeat (all steps) as often as is necessary.........
......Unless you've done irreparable harm by flashing a pit file......
Sent from either my S2 or my W via XDA developers app
and now my device is bricked
Damn.
adeeljalali said:
and now my device is bricked
Click to expand...
Click to collapse
hard or softbricked ?
i think its hard .......because whin i press power button it does not shows any thing the cellphone becomes warm ,from the under side the sim area , but not too warm a mild one........ and i made the jig but accidently put 300 ohms instead of 300k ohm ......i have ruined it further more
I should just delete the pictures in the camera folder from the internal store from my computer, when the phone froze and I had to disconnect it and restart it. It would then only go in bootloop, and I could just access download mode, not recovery. Odin just stucks on "nand write start" and then fails, no matter what rom/cable/odin version I try. The phone has always been stock, and it was on 4.1.2 when this happened. I was about to ship the phone back to Samsung as there is still warranty left on it, when I noticed that I now has 2 counts of custom firmware in download mode, probably after trying to flash Siyah kernel, even tho Odin would'nt flash that either.
Made a jig, and the phone goes into download mode, but it wont reset because of the newer firmware I guess.
Any other way to reset counter? If not; should I try to flash pit files as a chance to get it working again?
Mach III said:
I should just delete the pictures in the camera folder from the internal store from my computer, when the phone froze and I had to disconnect it and restart it. It would then only go in bootloop, and I could just access download mode, not recovery. Odin just stucks on "nand write start" and then fails, no matter what rom/cable/odin version I try. The phone has always been stock, and it was on 4.1.2 when this happened. I was about to ship the phone back to Samsung as there is still warranty left on it, when I noticed that I now has 2 counts of custom firmware in download mode, probably after trying to flash Siyah kernel, even tho Odin would'nt flash that either.
Made a jig, and the phone goes into download mode, but it wont reset because of the newer firmware I guess.
Any other way to reset counter? If not; should I try to flash pit files as a chance to get it working again?
Click to expand...
Click to collapse
Ive had the problem of odin not getting passed nand write. After about the 5th/6th time it worked. Think I also tried different filmware ie bloated carrier then stock unbloated link below. Use odin 3.0.7. Not sure about the counts though.
http://forum.xda-developers.com/showthread.php?t=1544487
stonedpsycho said:
Ive had the problem of odin not getting passed nand write. After about the 5th/6th time it worked. Think I also tried different filmware ie bloated carrier then stock unbloated link below. Use odin 3.0.7. Not sure about the counts though.
http://forum.xda-developers.com/showthread.php?t=1544487
Click to expand...
Click to collapse
That is actually the firmware I've tried the most, flashed another S2 with it, so I know the image is valid, and the computer/cable/drivers is correct. Also tried odin 3.07 now, among with many other older versions, but always stuck on "nand write start".
Nothing to lose to flash pit now?
Im sure you know your situation.If samsung see youve flashed stuff,they can refuse warranty.If you brick your phone,how can they tell what youve done.
And a jig only resets counter on gb/old bootloader.If youve no recovery,and odin doesnt flash anything,then I cant see how you can change anything.
I'm having real issues trying to get a stock ROM on my Virgin Mobile S3 (GT-I9300) and I'm hoping you guys can help me. I've looked absolutely everywhere for a solution but so far nothing has worked.
OK so a little history about the problem:
Using phone as normal, and then randomly turns off. Turn it back on and I get the two Samsung splash screens loop booting constantly. I boot into recovery mode and do a factory reset - same problem. Clear the cache - same problem. Send phone back to Virgin and they tell me I've rooted and installed a custom ROM which I absolutely have not but they have a screenshot with the custom counter showing '1'.
I've no idea how this is possible, but I would have remembered if I'd installed a custom ROM. Anyway, they send it back because I'm not going to fork out £100 for them to flash it.
So...lots of research later, I download the latest Odin (3.09), find the most likely stock ROM that will work with my phone (Carrier is Virgin Mobile UK). I find this ROM on SamMobile: I9300XXUGMK6_I9300OXAGMK6_BTU. Cannot for the life of me find an actual Virgin rom so this apparently should be fine as it's a generic EU build.
Fine, so I apply it using the AP selection in Odin, connect phone, it goes through and applies fine "PASS" etc.. and phone reboots automatically.
Now, it just sits at the Samsung splash screen (the static white text) and doesn't go any further. I've left it upwards of 10 minutes but no dice. So look online and find threads that suggest booting to recovery and doing a factory reset will do the trick. So try that (Power+volume up+home) and same problem - static splash screen. Balls.
So now I don't know what to do. I either need to try an actual Virgin ROM which doesn't seem to exist(?!) or my phone is truely bricked and I'll finally have a good reason to destroy the thing.
Can anyone let me know what the next steps should be? I would be eternally grateful.
Thanks in advance.
I found the s3 to be a pain when doing a reset. Basically do it twice. Wipe, flash, wipe then boot. As far as I know btu is correct but virmin mobile used to rent their airspace from tmobile who are now half ee. Such a minefield..
Sent from my GT-I9300 using Tapatalk
shivadow said:
I found the s3 to be a pain when doing a reset. Basically do it twice. Wipe, flash, wipe then boot. As far as I know btu is correct but virmin mobile used to rent their airspace from tmobile who are now half ee. Such a minefield..
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
When you say 'wipe' do you mean factory reset via recovery mode? Because I'm not able to access that. All I can get to is Download Manager to use with Odin...
I thought you said you could access recovery and you had cleared cache. In that case you are buggered. If it goes through the flashing phase and reboots but you still cannot get into recovery then you have 3 options..
1. Flash another rom but no lower than 4.3. Carrier shouldn't matter.
2. Full on flash with pit file (dangerous and can perma brick).
3. Return the phone under warranty and state that the flash counter also clocks official flashes too, samsung should know this as they make the phone.. staff need training if they say otherwise.
Sent from my GT-I9300 using Tapatalk
Try the rescue firmware from general forum, follow the instructions exactly as it includes a pit.
It sounds like nand failure, so it's possible that you won't be able to fix it.
Sent from my GT-I9300 using Tapatalk
I thought you said you could access recovery and you had cleared cache.
Click to expand...
Click to collapse
Apologies for not being clearer, before sending it back to Virgin for the warranty repair I could access the recovery mode fine, when I got it back I couldn't - whether that was caused by the flashing of the firmware or something Virgin did I don't know unfortunately.
Try the rescue firmware from general forum, follow the instructions exactly as it includes a pit.
Click to expand...
Click to collapse
Thanks for the tip - I've flashed the stock recovery and I can now get into recovery mode! Looks slightly different but I can now access the factory reset/wipe cache options so that's some improvement.
I'm just downloading the stock international ROM as per this thread http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847 but it's going to take a few hours. Thanks so much for your advice so far i'll report back once the download completes.
No joy
I can however get into download mode and recovery mode now. Is there anything else I can try? Is it possible I can get a custom recovery image on there and flash it with something other than the stock rom?
I've got a feeling you're correct and it could be a hardware fault. Virgin say I can pay £100 to get it fixed, if they have to replace the entire phone that would prove it wasn't 'tampering' that caused it so I could potentially get my money back I guess, if I complained. I think that might be my only option now.
Ok I just booted into recovery mode and I was greeted with this error:
Any ideas what this could mean?
crispin85 said:
Ok I just booted into recovery mode and I was greeted with this error:
Any ideas what this could mean?
Click to expand...
Click to collapse
I say this to people who have this sort of problem but I mention the dreaded word and they tend to ignore it but will tell you what to try anyway.
Install Kies 3 for android 4.3 (there I said it Kies) on the top menu bar click Tools then Firmware Upgrade and Installation
Follow the on screen instructions, this process will wipe the phone and install the most up to date original carrier / phone firmware, after this the phone should work and you can then root, flash roms etc , it may work for you so try it, don't just dismiss it because it refers to the use of Kies
ag4751 said:
I say this to people who have this sort of problem but I mention the dreaded word and they tend to ignore it but will tell you what to try anyway.
Install Kies 3 for android 4.3 (there I said it Kies) on the top menu bar click Tools then Firmware Upgrade and Installation
Follow the on screen instructions, this process will wipe the phone and install the most up to date original carrier / phone firmware, after this the phone should work and you can then root, flash roms etc , it may work for you so try it, don't just dismiss it because it refers to the use of Kies
Click to expand...
Click to collapse
Unfortunately I've already tried Kies, and it doesn't recognise the device when in recovery mode.
crispin85 said:
Unfortunately I've already tried Kies, and it doesn't recognise the device when in recovery mode.
Click to expand...
Click to collapse
Make sure you are using the USB cable supplied with the phone and it is connected direct to your PC USB port, ideally the ones on the back but don't connect through any multi USB port connectors.
The USB cables and how you connect can make a difference
Hi
I'm currently on CM11 (nightly and TWRP) and want to revert to stock. Kies has the "Firmware upgrade and initialization" option ..
My question is:
Is it necessary to reset the flash counter in order to use this? What will happen if I try to use it without resetting the counter?
I tried to find an answer for the last few days, but couldn't (or couldn't understand what I found).
The backstory is my serial number was reset and I can't connect to network after flashing ArchiDroid with a new modem. I afterwards flashed a different (JB) modem. I was already on Samsung stock 4.3 so I guess my efs is v2 (so no Ariza's patch..), and I have some backups of it.
I'd rather not use Odin or ADB. I figured the easiest and safest way is to reset and restore everything to stock, send to a lab if necessary, then reinstall cm11. I'm also not sure how restoring the efs works ..
I'll be very thankful for any feedback, as I've been wasting a lot of time on trying to solve it recently ..
Ron
Kies sucks. Flash with Odin and no it don't matter about flash counter. Flash counter only matters when sending back to samsung service.
andrewwright said:
Kies sucks. Flash with Odin and no it don't matter about flash counter. Flash counter only matters when sending back to samsung service.
Click to expand...
Click to collapse
Thanks. Flashed with Odin - something went wrong at first, then went fine and now the phone won't boot But I'm on the right track and lost my fear of Odin, so thanks
Factory reset it stock recovery and reboot.
andrewwright said:
Kies sucks. Flash with Odin and no it don't matter about flash counter. Flash counter only matters when sending back to samsung service.
Click to expand...
Click to collapse
+1 to Odin.
Kies creates more problems than it solves.
~ RazorMC
andrewwright said:
Factory reset it stock recovery and reboot.
Click to expand...
Click to collapse
That solved it. Unfortunately my phone would not connect to the cellular network stating "service is not available". Good thing I have a backup phone (in which the same SIM works ...)
Personally I don't think Kies is that back, but Samsung's mobile-related software (Android, apps, etc.) is truly bad. Kies was mainly useless when it was relevant ..
Once you come to XDA you should learn the best ways of doing things. Odin is a very good tool. Kies should be deleted once you come here and understand what odin can do. I didn't like odin at the start but have grown to have respect for its uses. Saved my s3 a few times :thumbup:
So, I'm sending my Verizon Samsung S4 Sch-1545 back to Verizon for a warranty return.
So while help with bricking is needed, I really still need to be able to flash the stock ROM.
I previously had rooted my phone, and decided to flash the stock ROM via Odin v 3.09. I used the 1545VRUFNC5 ROM which is the correct one for my model.
However only partially through the flashing I get the FAIL message in Odin and now my phone is bricked and I get the message upon boot "Firmware Upgrade encountered and issue. Please select a recovery mode in KIES and try again".
I even re-tried using a different USB cable and port on my computer, that didn't change anything.
I don't know what to do now, and how to get my phone un-bricked and flashed back to the stock ROM with Odin failing. Per the Odin dialog box, it keeps failing at system.img.ext4.
Please help! I have to send my phone back to Verizon ASAP and I'm at a loss here.
Thanks!!
Try Odin 3.07
DX.Deception said:
Try Odin 3.07
Click to expand...
Click to collapse
Thanks, that worked and it passed. So at least my phone is working again, but I'm having other problems now.
My phone rebooted automatically to the normal home screen, however I keep getting the dialog box that won't close out that says "Unfortunately, the process android.process.acore has stopped" as well as "android.process.media has stopped".
So I'm not sure at this point what to do . Should I try flashing it again, or doing a factory data reset? All II'm really trying to do is take this completely back to to stock for the warranty return.
Did you use the no wipe tar or full wipe?
DX.Deception said:
Did you use the no wipe tar or full wipe?
Click to expand...
Click to collapse
I didn't know there was a difference? I used the 1545VRUFNC5 ROM .
Was this a setting that I should have chosen in Odin? The TAR file didn't specify wipe or no wipe in it's filename.
z71Kevin said:
I didn't know there was a difference? I used the 1545VRUFNC5 ROM .
Was this a setting that I should have chosen in Odin? The TAR file didn't specify wipe or no wipe in it's filename.
Click to expand...
Click to collapse
OK so I did a hard factory data reset, that seemed to fix the problem.
I installed ES File Manager and Root Checker and there's no evidence of root access or the SU binary.
Sounds like I may be good to go with sending this back to Verizon. What do you think?
http://forum.xda-developers.com/showthread.php?t=2735172 that should help, remember full wipe completely wipes all data on your phone pictures and everything.
DX.Deception said:
http://forum.xda-developers.com/showthread.php?t=2735172 that should help, remember full wipe completely wipes all data on your phone pictures and everything.
Click to expand...
Click to collapse
Cool. Thanks for all your help! Looks like I'm all set now.
No problem man.