I've been dealing with this on/off for the past couple months and it's gotten worse. My wifi is stuck at "turning on" and won't turn on and I can't turn it off. Factory reset did nothing, wiping the cache and booting into safemode has done nothing, and I've even tried to flash the original firmware with Odin but it kept failing. If I go into the hotspot menu it crashes the OS and it has to start the GUI again (what is X server called for phones..?) but generally at that point the wifi is at least turned off, but trying to turn it on again does nothing. Every so often I'll get the wifi turned on after rebooting the phone and it will stay connected until I actually need to send/receive data.
My warranty expired last week so sending it off isn't an option. I've searched around and have seen others complaining of similar issues, but generally wiping the dalvik cache has fixed it for them; no such luck for me. I'll nuke this thing and start from scratch if it means getting my wifi back. Help.
cowmoo32 said:
I've been dealing with this on/off for the past couple months and it's gotten worse. My wifi is stuck at "turning on" and won't turn on and I can't turn it off. Factory reset did nothing, wiping the cache and booting into safemode has done nothing, and I've even tried to flash the original firmware with Odin but it kept failing. If I go into the hotspot menu it crashes the OS and it has to start the GUI again (what is X server called for phones..?) but generally at that point the wifi is at least turned off, but trying to turn it on again does nothing. Every so often I'll get the wifi turned on after rebooting the phone and it will stay connected until I actually need to send/receive data.
My warranty expired last week so sending it off isn't an option. I've searched around and have seen others complaining of similar issues, but generally wiping the dalvik cache has fixed it for them; no such luck for me. I'll nuke this thing and start from scratch if it means getting my wifi back. Help.
Click to expand...
Click to collapse
I know its basic but... have you tried to simply reset network settings? What fail message are you getting in odin when flashing stock firmware? Once you get stock flashed back if its still not fixed that rules out software problem? Get back to me with your phone model, region and odin error and i can help further
callumbr1 said:
I know its basic but... have you tried to simply reset network settings?
Click to expand...
Click to collapse
Tried that as well, no dice.
What fail message are you getting in odin when flashing stock firmware? Once you get stock flashed back if its still not fixed that rules out software problem? Get back to me with your phone model, region and odin error and i can help further
Click to expand...
Click to collapse
I'll have to try it again tomorrow when I'm in Windows to get you the exact error message, but it was a nand write error right after trying to flash the pit file. And yeah, I was hoping to flash the stock firmware to remove software as a variable. It's a Galaxy S6 Edge Verizon, SM-G925V. I'm in North America.
cowmoo32 said:
Tried that as well, no dice.
I'll have to try it again tomorrow when I'm in Windows to get you the exact error message, but it was a nand write error right after trying to flash the pit file. And yeah, I was hoping to flash the stock firmware to remove software as a variable. It's a Galaxy S6 Edge Verizon, SM-G925V. I'm in North America.
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/96728/G925VVRS4CPI2_G925VVZW4CPI2_VZW/
This is the firmware you need to flash. If its the same one you tried before you shouldn't need a pit file, which is possibly why you got an error message.
Try that dlfirmware and if it fails post the odin log
callumbr1 said:
http://www.sammobile.com/firmwares/download/96728/G925VVRS4CPI2_G925VVZW4CPI2_VZW/
This is the firmware you need to flash. If its the same one you tried before you shouldn't need a pit file, which is possibly why you got an error message.
Try that dlfirmware and if it fails post the odin log
Click to expand...
Click to collapse
That's the firmware I tried before. Should I unpack it and remove the pit file before flashing?
cowmoo32 said:
That's the firmware I tried before. Should I unpack it and remove the pit file before flashing?
Click to expand...
Click to collapse
I just need to know the odin error then i can tell you what you need to do. Shouldnt need to unpack it i thought you manually flashed a pit. Flash it as it is and post odin log
callumbr1 said:
I just need to know the odin error then i can tell you what you need to do. Shouldnt need to unpack it i thought you manually flashed a pit. Flash it as it is and post odin log
Click to expand...
Click to collapse
Using the firmware from Sammobile
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
cowmoo32 said:
Using the firmware from Sammobile
Click to expand...
Click to collapse
sboot.bin fail is incorrect or locked bootloader. The firmware your flashing has an incompatible bootloader.
Try to flash this
http://www.sammobile.com/firmwares/download/72557/G925VVRU4CPD2_G925VVZW4CPD2_VZW/
Or try restore again via smart switch.
If that doesn't work we need to find the right bootloader. Verizon bootloaders are locked... but smartswitch should flash the stock back. Then once phone back on go to developer options and enable oem unlock.
Restored with Smart Switch, still nothing. I'm downloading the firmware you posted but I'm thinking this might be a hardware issue. Would it be possible to root it and check the status of the wifi card via terminal?
cowmoo32 said:
Restored with Smart Switch, still nothing. I'm downloading the firmware you posted but I'm thinking this might be a hardware issue. Would it be possible to root it and check the status of the wifi card via terminal?
Click to expand...
Click to collapse
If you restored via smart switch and it hasnt fixed it its more than likely hardware issue, because it will be officail stock firmware from samsung. You can try to root and use the secret codes to check hardware
What secret codes? I haven't rooted a phone in a couple years; I need to do some reading.
cowmoo32 said:
What secret codes? I haven't rooted a phone in a couple years; I need to do some reading.
Click to expand...
Click to collapse
Theres an app called samsung phone info, which has secret codes on. To access the service modes etc you can check and reser network services from there
Ohh I've tried those and Verizon disabled them.
I figured I would bump this for posterity in case someone finds it in a search:
I've found a workaround that has worked for me so far. I'm not sure if the wifi and bluetooth card are one in the same but they're both malfunctioning in a similar manner. I found out, by accident, that if the wifi isn't working I can try to turn the bluetooth on and wait. Eventually it will turn on, usually after 5-10 minutes. Once bluetooth is on, try to turn wifi on and it won't. But reboot the phone and bluetooth will be off with wifi working.
Related
So, I tried to root my phone, following Chainfire's guide. I did everything EXACTLY as I was supposed to, but after flashing the kernel in Odin, with XWKDD_insecure.tar, the device no longer worked. It rebooted into a screen with a grey battery and the loading loop, but nothing happened. I didn't even get a chance to use SuperOneClick, because the program just stalled when it said "Waiting for device...". After about 5 minutes, I held down the power button, and then the GS2 logo appeared with a yellow exclamation sign underneath it. And SuperOneClick still didn't register the phone.
I pulled the battery out, booted into download mode again, then tried to install the factory firmware I downloaded from samfirmware.com. But then this happened:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XWKDF_CL170898_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKDJ_REV_02_CL996627.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXXKDD.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.img
<ID:0/004> data.img
<ID:0/004> cache.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
When I saw it, I actually felt physically ill.
So what do I do now? I have a choice of booting into download mode, or turning the phone on normally, and getting a screen that says the update fail to load. Is there something else I can do to reset factory settings, or is that the end of my brand new phone
U could still try to reflash the rom again, check if the file u downloaded is not corupted.
You have to bear in mind that Odin can be temperamental, redownload a firmware and flash it again.
Going off memory here as im not at my pc but it looks like you have too many things in to your odin program.
first thing i notice is that you have the "Re-Partition" box selected, it was my understanding you only need Auto Reboot and F.Reset Time checked.
You could also try getting the most upto date version of Odin too which is v1.85.
Also you have entered something in to the PIT section, when i flashed my device with the firmwear from samfirmware (I9100XWKDF) i didnt put anything in the PIT section.
Maybe try changing them and i hope it works.
Crucio
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Looks like you get first to brick an SGS 2 prize any way .
jje
Not a prize i would like to win heh..
Lets just hope it can be flashed again.
moparman said:
Make sure that in ODIN NOTHING is checked, except the "Auto reboot" and "F. Reset Time" checkboxes. Press the "PDA" button, and select the "XWKDD_insecure.tar" file.
- Press "Start". ODIN you should now be flashing the kernel, and the device should reboot.
Why do you have Re-Partition,phone,css selected ?
Prey that you dont bricked it
Click to expand...
Click to collapse
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
im a rookie to
I just read the instructions to root...
Maybe it works if repartition is not checked and reflash?
I hope someone with better skills then me can help.
If i had done this i wouöd die of a broken hearth
I remember how afraid i was to flash my TyTn2 the first time..And i didnt have any problem
yeah im a rookie also, lets hope someone with a bit for knowledge can help this guy out if we havent ^^
my heart would sick too, it did a bit when i flashed the firmware and it was german that was fixed easy tho lol.
The repartition basicly changest the size of some system partitions based od the PIT file, its not recomended to use the repartition, but that shouldnt be the problem why the ODIN failed.
As he said he is able to go to download mode so he should be safe, just reflash the rom or try other rom versions and flash them.
Crucio_ said:
They have Phone and CSS selected as they were flashing the firmware with the version from samfirmware.com (the one that removes branding and updates the battery usage part) not just the kernel to root the device.
Surely if this device is in a limbo it would make sense to flash this (stock firmware) before flashing a rooted kernel?
id guess the first attempt of the root failed due to the re-partition box being checked but im not 100% on that.
Click to expand...
Click to collapse
The screenshot I posted was from after the damage was done. I had already given up on trying to root my phone, and was trying to install the firmware from SamFirmware, in the hope that it would get my device back to factory settings.
Initially, when I flashed the kernel with Odin, nothing was selected except for "Auto reboot" and "F. Reset Time", and the only file loaded was the XWKDD_insecure.tar on the PDA line. I was also using Odin3 v1.85 at the time. The firmware I downloaded from SamFirware came with v1.83 and I didn't even notice that it wasn't the latest version.
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
rheedan said:
Can someone give me a step by step of what I can do to completely wipe the device, and restore it to factory settings, as that's what I was trying to do, and it clearly didn't work?
Click to expand...
Click to collapse
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
bilboa1 said:
that's exactly what you're doing when you're flashing a complete new firmware with repartition ;-)
(which is what you did/ or tried to)
that is on your screen you're flashing modem/csc/full pda etc aka complete wipe and factory setting reset
repartition formats the memory by wiping the partition table and creating a new one (its like "quick format" on a pc)
Click to expand...
Click to collapse
I don't know if I should be comforted by the fact that I tried to do the right thing, or disheartened by the fact that doing the right thing didn't solve my problem.
Is there perhaps another way to go about the whole process? Should I try another ROM? The one I used was a European XWKDF Gingerbread 2.3.3, but I also have the Russian XEKDB firmware from http://forum.xda-developers.com/showthread.php?t=1057535 - I think it's 2.1.1.
there is not much experience with the SGS2 yet and I don't have one yet personally. Never saw that one error but form the SGS1 experience i'd say try reflashing, and try flashing other SGS2 firmwares ;-)
i havnt flashed mine yet but will wait till i get insurance for the phone because (and i mention this so that people can do the same thing if they wish).. if it does brick then the option of it "accidentally falling onto a busy motorway" is open to me lol
OK, looking at your screenshot, you flashed too many files, and reformated.
Follow this guide.
http://androidadvices.com/how-to-up...ii-i9100-to-gingerbread-xwkdd-2-3-3-firmware/
Make sure you download the files from there as well. I have flashed mine with them after I broke a few things playing, and it worked fine after.
This will get you up and running again.
Then for Root, go to this thread
http://forum.xda-developers.com/showthread.php?t=1056334
Download the XWKDD_insecure.tar file
Odin, Without repartion checked.
Only files to link are the pit file, in pit and XWKDD_insecure.tar in PDA
Then you can use SuperOneClick to add root.
Don't panic, I doubt its a brick.
Good luck
Broomfundel said:
Don't panic, I doubt its a brick.
Click to expand...
Click to collapse
It is fairly hard to brick a Samsung properly, without actually trying... Hope that's some reassurance.
The fact you can get into download mode is a reassurance, as that should be the key. I've not owned a Samsung device, so I won't try and advise how to fix it, but I'd agree about trying that above link to install the "beta" firmware.
ODIN is pretty good, but there isn't much experience in flashing these yet, as I don't know of any devs with them. I might go out at the weekend and get one, but I'll not be starting properly on it until June realistically...
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
dhruvmalik said:
Let us know if the fine folks here have resolved the problem. Looking and learning from peoples experience before I make the leap and root.
(Still waiting for launch in India)
Click to expand...
Click to collapse
now i will never root my s2 when i will get it, faced the same sitution with my n8 once
Ok so last night my phone froze up while I was browsing the web (it froze just after rotating, if that's of any significance) so I held the power button down until it turned off. Trying to turn it on again, it just sat at the galaxy s 2 logo before any bootanimations etc start playing.
I thought I'd try to just re-flash the ROM (CM10 nightly 26/9/2012) and it seemed to just freeze up near the end of the flash, so I left it to do it's thing.
When I returned to the phone, it was showing me a kernel panic screen, so I held the power button to turn it off again and since then it won't boot into the ROM, it won't boot into recovery, and until just now it wouldn't be recognised by odin in download mode.
I had tried installing the USB drivers for the phone etc and it wouldn't work, however while writing this topic I just got a notification on my PC saying USB drivers had been installed and Odin seemed to recognise my phone, so I tried flashing cm9 resurrection, however it seems to be stuck. These are the messages in Odin, for reference:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
and it's just been stuck there since I pressed start. There is no progress bar or anything on the phone either. Oh, and Odin's progress bar thing at the top just says "KERNEL" with a blank bar under it and "0:[com3]" with a yellow background below that.
Is it safe to unplug the phone and try again with a different USB cable?
EDIT: After trying different methods to recover it (with the same result from Odin):
Orkane1989 said:
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Click to expand...
Click to collapse
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
So it's safe to unplug the phone?
D3_ said:
So it's safe to unplug the phone?
Click to expand...
Click to collapse
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Orkane1989 said:
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Just tried this, getting the same thing, Odin gets the first "bar" in the progress bar completed and seems to get stuck. Same output as above.
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
You will have to consult someone with some more knowledge about this than me. You could have a corrupt data partition... but its honestly out of my league now lol. Sorry I couldn't help.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
Click to expand...
Click to collapse
According to the output it gives me (in the OP) it does successfully check the MD5 though.
I'll admit, I haven't actually used Odin since I first rooted this phone (back in december last year) so I'm back to knowing basically nothing about how it works.
Yes it does confirm the md5
But after that it sends the commands to start running the new kernel (basically installing it on the device firstly)
Which is where it gets stuck.
Sent from Jelly Fuelled SGS2
Just tried this: http://forum.xda-developers.com/showthread.php?t=1457458
Same issue with flashing those files.
I don't want to try the .pit because if it doesn't flash then I'll be pretty f*cked, right?
I would try what ever else you could find because if you get that guide wrong you could end up turning your phone into a paperweight. But if you so have to use the guide take note that you ahould try flashing the files WITHOUT .pit or repartition first. If that doesn't succeed than your last option is to use the .pit file and repartition.
Sent from Jelly Fuelled SGS2
I did try it, without the .pit/repartition as the guide says to try it without it first, but again, it won't flash anything (which is why I don't think I'll try the .pit/repartition)
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Sent from Jelly Fuelled SGS2
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
Hi,
I've got this problem with a friends(girl) phone.
Her phone was stuck at the firmware upgrade screen(the one with firmware upgrade encountered an issue). So she searched the internet for a solution and did some things with kies and odin. But nothing worked so i offered to help her.
So i searched and found this article. i followed all the instructions and downloaded 3 different versions of odin V3.07, V1.3 and V1.85.
Specifications of the phone:
samsung Galaxy S II GT-I9100 16GB
what i've tried so far:
i followed the instructions from te link above and tried it with the following roms
-I9100GXXLB1_I9100GATOKL1_ATO
-I9100XWLP9_I9100KPNLP1_KPN
-I9100XXLSJ_I9100OXXLS1_OXX
i also tried the gingerbread and the ICS version
i also tried the pit file. but nothing works, the progress get stuck like in this example
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help me with this problem? I also have a JTAG programmer but don't know how or what to do with it.
Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Look for hopper8's thread.
And stop flashing pit files.
Sent from the little guy
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Basseytje said:
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Click to expand...
Click to collapse
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
when u go to download mode, does it show your model number??
Hopper8 said:
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
Click to expand...
Click to collapse
I've already tried that one but odin is stuck at data.img.
tornado92 said:
when u go to download mode, does it show your model number??
Click to expand...
Click to collapse
Yes it shows the product name.
Basseytje said:
I've already tried that one but odin is stuck at data.img.
Yes it shows the product name.
Click to expand...
Click to collapse
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
tornado92 said:
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
Click to expand...
Click to collapse
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Basseytje said:
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Click to expand...
Click to collapse
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
tornado92 said:
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
Click to expand...
Click to collapse
kies won't recognize the phone. the only 3 screens i can access are showed in the pics below. i've got 2 stock roms which don't work. after i tried kies, i immediately uninstalled it and left the drivers on the pc.
i40.tinypic.com/29gkdi1.jpg
i40.tinypic.com/qsnluc.jpg
i41.tinypic.com/2aep3yx.jpg
can't post any files yet.
I hope there is still someone who can help me...
odin is still stuck on data.img
If you say you've 'tried everything' (which everyone always says), then it's a service centre job. What else do you want anyone here to say ? No miracle fixes. If it were me I'd keep trying, it's almost always something really simple/small/obvious that's causing the flash not to work, and as we're not there looking over your shoulder at what you're doing, it's going to be almost impossible for anyone to say what that is (you have 'tried everything' after all).
is there a way to fix this with jtag?
Basseytje said:
is there a way to fix this with jtag?
Click to expand...
Click to collapse
Maybe. No one can say for sure mate. If you motherboard is really borked, it would have to be replaced nevertheless.
Remember that Jtagging leaves marks on your device, so you can kiss goodbye any warranty u might have.
"To err is human, to forgive is divine."
Sent from my SGS II
hey.. i had this problem too.. the only solution that i had is to use the galaxy note pit file and a stock rom for i9100 ... then the phone went back to normal ..but the memory went from 16 tb to 11.5 gb .. it was the only thing that made my phone work again..
i installed pit from galaxy note ..with and original stock firmware 4.1,2 then after install I did a factory reset via stock cwm and a clear cache ..and it worked.. a few bootloops and it went on:|
alexandru.j91 said:
hey.. i had this problem too..
Click to expand...
Click to collapse
You got so ridiculously lucky that I can't comprehend that it worked. Please don't advise others to do the same, I'd say what you did is normally a recipe for a hard brick. Don't flash files for other phones, let alone a pit file for another phone. Yes I know the note has the same hardware as i9100 but you know what? It's not an i9100.
Edit: Look at what you posted in your other thread:
alexandru.j91 said:
I hardbricked my phone about 3 months ago with the original firmware from orange 4.0.4 and I resolved the problem by putting samsung note PIT file ..but I don't have acces to all the memory on my phone ..I have almosst 12 gb from 16.. and my phone is getting wired ..and it is shutting off randomly since then .and to get it on again i have to remove the battery ..
Does anybody know how to get all my memory back for my phone? tx
Click to expand...
Click to collapse
I'd say that's a reason not to flash files from another phone.
i was just telling him that i had the same problem..not to do the same thing..because of the problem that I have got! i have told in my other post whathappened to my phone! and i know that my problem can be solved by rewriting the memorybut i don't know how!..
---------- Post added at 06:04 AM ---------- Previous post was at 05:05 AM ----------
what I did.. i did because of some threads on xda ..so I am not crazy ..I just told him what I have did.. I haven't advised him to do that ..because of the problem that i had .. and when I wrote what I have did to make my phone worked .. i hace told the fact that it shrinked my memory from my phone..
maybe i'm getting a little progress. when i try to flash a new bootloader. i see a progress bar on the phone. but odin is halfway stuck at sbl.bin
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
everywhere i read, people are saying use different cables. i already tried the samsung s2 cable, a htc desire cable, 3 deal extreme cables and an other htc(dont remember the model) cable. but i'm getting the same problems. stuck at zimage or something else...
anyone?
Hello all,
I want to preface everything that while I know a bit about rooting and messing with the stock status of android phones, I'm still generally a newbie at this.
Last night I started experiencing problems with my phone. I was using it normally until it ran out of battery while in a call, but I figured this happened in the past so it shouldn't be a problem. I plugged it in, however it wouldn't boot up. The CM11.2 loading screen just wouldn't stop spinning. Booting into recovery and download mode was working fine, but I couldn't get into the OS. Since I wanted for a long time to upgrade my Jellybean to Lollipop (and found this thread http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-1-nightly-builds-t3147661 just last night), I decided it's time.
I boot into recovery and try and backup my data, but as soon as I click, the device freezes. Fast forward 5 attempts later with 3 different SD cards, it would still do the same thing. Already annoyed, I decide just to factory reset/wipe data, in order to flash the new Nightly and Gapps. As soon as I click, same thing happens, the CWM freezes and I have to manually reboot.
I figured the CWM is corrupt and I started searching on forums what to do. Tried flashing a new CWM with Odin (specifically this) but now I can't boot into recovery anymore, only download mode. I'm scared of doing more on my own. The current state of the phone is that it stays frozen at the "Samsung Galaxy S2" screen, the one with the yellow triangle w/ "!". Could you please help?
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
noppy22 said:
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
Click to expand...
Click to collapse
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
I tried getting a stock firmware from Sammobile, specifically firmwares/confirm/14909/I9100XWLSU_I9100OROLS5_ORO/. I tried flashing it, and this happened:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS2_I9100BULS3_I9100VDFLSF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ricksis said:
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
Click to expand...
Click to collapse
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Anyway get a stock rom for your region from
sammobile.com
or http://androidfirmwares.net/Home/sgs2
or http://www.tsar3000.com/Joomla/inde...alaxy-sii-firmware&catid=55:samsung&Itemid=82
noppy22 said:
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Click to expand...
Click to collapse
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Ricksis said:
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Click to expand...
Click to collapse
I'm not sure you can expect anything. It's just a common problem. See if you can get it fully charged and try the stock rom with odin again. Also check out this guide
As I said it seems like there is a hardware problem, the battery is just where I would start. Once you can rule that out you can look elsewhere
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
Click to expand...
Click to collapse
I tried with multiple stock roms, but they all fail in the same stage. I bought the phone carrier free, and its code is GT-I9100 (no extra letters afterwards like a lot of S2s have). I also found another solution, but it stopped after NAND WRITE start.
Hopper8 said:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: or here. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
I also found this http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
I've had a quick look at the thread you linked to, and from what I understand, the OP is providing a way to flash the firmware partition by partition......
In theory, this is a good solution, but unfortunately, I don't know enough about the firmware structure or about the odin flashing process to be able to meaningfully pass comment on that method.......My uninformed instinct tells me 'why not'......but my practical, logical side tells me 'caution'....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
Click to expand...
Click to collapse
In Odin 3.07, everything but PDA is greyed out for me. I donwloaded v1.85 and tried the 3 part thing: Odin freezes at NAND Write Start!!, and as for my phone, there is no blue progress bar appearing on the screen in the first place while i'm in download mode.
Just tried the pit file solution as well:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
Things to check for odin flashing.......
1) firewall disabled
2) antivirus disabled
2) all Kies processes killed (use task manager)
4) run Odin as administrator
5) only use main board USB sockets (pc/laptop side)
6) make sure Samsung drivers correctly installed.
7) windows 8 & 10 may not allow odin to operate correctly.
8) Use official Samsung usb lead.....no cheap s**te off eBay
9) try all usb ports on pc/laptop
10) try different cables
11) try different PC's/Laptops.......
12) do the whole procedure multiple times.....Odin flashing is a bit like playing the lottery......it may not work the first 9 or 19 times, but for some reason, on the 10 or 20th attempt, it does.......
The only thing that will 'win the day' is perseverance......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
There is (possibly) a plan B.......
Are you able to get into recovery?
If you are, you *could* try flashing PhilZ recovery which will root your phone.....then you can give flashing a custom rom a try.......
You possibly still could go that route even without recovery......by (maybe) Odin flashing a custom kernel .tar and then flashing a custom rom......
(I'm not talking about the latest CM12. ....but an older KK or JB based rom.....they're far more stable and complete than the LP based roms.....)
http://i.imgur.com/rVnFwJM.jpg
I had a busy week and only could try some solutions today. Unfortunately, I think they ended up with the hardbrick of my phone, as I am not able to turn it on anymore, not even in download mode.
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
Click to expand...
Click to collapse
I'm not sure, but I kinda fiddled enough with ODIN for just the battery to be the cause. Of course I am no expert, but I see no connection between the battery failing and all the other problems: cwm11.2 not wiping cache/dalvik or performing factory resets, the option to only boot in download mode later, etc. When I plug the phone to the USB port, nothing happens anymore.
Sooooo... RIP phone? ...
Ricksis said:
Sooooo... RIP phone? ...
Click to expand...
Click to collapse
If you are sure there's nothing else you can try........
But, even though it's an old device, it's still going to cost money to replace it....
You mentioned that odin failed to recognise it......
Another *possibly* would be the USB socket......
It would account for the lack of odin recognition *AND* a dead (uncharged) battery which could lead you to assume the whole phone is dead.
The port may have been ok at the start of your recovery attempts, but they do wear out (especially on older devices simply due to wear and tear) and by the last attempt it could have failed......
The part costs pocket change on ebay and is relatively easy to replace....I've done it myself......
Here's a guide I wrote on replacing the board......
http://forum.xda-developers.com/showthread.php?t=2335961
http://i.imgur.com/rVnFwJM.jpg