Related
YES, I KNOW THAT ALL QUESTIONS GO IN THE Q&A FORUMS BUT ITS HERE TO GET THE DEVELOPERS. SINCE I HAVEN'T FOUND ANY PERSON THAT CAN HANDLE SUCH SITUATION. (Please read ahead to take note of the problem clearly)
Please think of this as to help me (and other people who made these dead like this one). Don't comment "Questions go in the Q&A forum you friggin' NOOB". I know all of this stuff!!!!!
How it happened??:-
Rooted the phone using CF Root 6.4. Working "Perfectly"!
Did an OTA update (0.17MB) accidently. Encountered Random Reboots after then.
Then it won't boot at all
Stuck at the "GT-i9300" logo.
I HAVE THE NANDROID BACKUP BUT WON'T GO INTO THE RECOVERY SO ITS USELESS (is there any way to do it without the Recovery??)
Current situation:-
No Recovery. Tried Re-flashing the Official ROM and Re-rooting it. Either doesn't shows up or when shows up stays for 2 seconds and then goes to the GT-i9300 Logo.
Download mode is PRESENT.
Charges with NO PROBLEMS. Shows the Battery Logo going up and the Blue LED comes on too.
It once gave an error saying : "E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
It also gave a similar one in the above but with some other error. I didn't noticed it.
Odin Flashes WITHOUT any errors(no errors within the Odin). Writes the Firmware completely but unable to proceed due to some unknown reason.
I have tried these:-
Changed the NAND Memory Chip. Still the exact same problem. (Partition problem or something?)
J-Tagged it. No use!
Flashed all the Official ROMs via Odin.
Re-Rooted it. No use. Recovery isn't stable. Keeps rebooting after 2 seconds to the GT-i9300 Logo.
Please take this Question very seriously. Since its not just me with the same problem. There are many many other people with the same problem and with no solutions. Isn't this the main reason of XDA-Developer? Or is it just ROMs, Themes or Kernels? A person would be more happy if he gets his/her phone repaired instead of lying there on the desk and keeping those papers in there place and stop them being blown away from the fan!
For the moderators:- I know this isn't in the rules of the XDA to post a Question in the Android Development Section but this is here to summon all the ROM Developers and the Kernel Tweakers. Thank You for your valuable time!
Flash FULL ICS rom with .pit file
AusafSal said:
YES, I KNOW THAT ALL QUESTIONS GO IN THE Q&A FORUMS BUT ITS HERE TO GET THE DEVELOPERS. SINCE I HAVEN'T FOUND ANY PERSON THAT CAN HANDLE SUCH SITUATION. (Please read ahead to take note of the problem clearly)
Please think of this as to help me (and other people who made these dead like this one). Don't comment "Questions go in the Q&A forum you friggin' NOOB". I know all of this stuff!!!!!
How it happened??:-
Rooted the phone using CF Root 6.4. Working "Perfectly"!
Did an OTA update (0.17MB) accidently. Encountered Random Reboots after then.
Then it won't boot at all
Stuck at the "GT-i9300" logo.
I HAVE THE NANDROID BACKUP BUT WON'T GO INTO THE RECOVERY SO ITS USELESS (is there any way to do it without the Recovery??)
Current situation:-
No Recovery. Tried Re-flashing the Official ROM and Re-rooting it. Either doesn't shows up or when shows up stays for 2 seconds and then goes to the GT-i9300 Logo.
Download mode is PRESENT.
Charges with NO PROBLEMS. Shows the Battery Logo going up and the Blue LED comes on too.
It once gave an error saying : "E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
It also gave a similar one in the above but with some other error. I didn't noticed it.
Odin Flashes WITHOUT any errors(no errors within the Odin). Writes the Firmware completely but unable to proceed due to some unknown reason.
I have tried these:-
Changed the NAND Memory Chip. Still the exact same problem. (Partition problem or something?)
J-Tagged it. No use!
Flashed all the Official ROMs via Odin.
Re-Rooted it. No use. Recovery isn't stable. Keeps rebooting after 2 seconds to the GT-i9300 Logo.
Please take this Question very seriously. Since its not just me with the same problem. There are many many other people with the same problem and with no solutions. Isn't this the main reason of XDA-Developer? Or is it just ROMs, Themes or Kernels? A person would be more happy if he gets his/her phone repaired instead of lying there on the desk and keeping those papers in there place and stop them being blown away from the fan!
For the moderators:- I know this isn't in the rules of the XDA to post a Question in the Android Development Section but this is here to summon all the ROM Developers and the Kernel Tweakers. Thank You for your valuable time!
Click to expand...
Click to collapse
Download *.tar file from sammobile. As you have download option live, you can flash the same with help of Odin (for ICS)
Flash A Stock ICS ROM with Odin.
Get them from Sammobile or from a thread with stock rom collections.
Even get an Galaxy S3 .pit file for odin.
That will fix it.
Just to keep you happy, Most Samsung Devices are unbrickable. As long as it boots, even if its in bootloop it can get fixed with odin.
Keep us updated.
Sorry, even questions like this go into the Q&A, that's where the devs are, aswell..
Anyway, go to this website and create an account.
Download latest JB/ICS ROM and get a .pit file. Open Odin and flash away..
Done, your phone is working again..
Moved to Q/A, there is no reason to post this in the development section.
That is the problem!! No one in the Q&A section answered like u guys have :/
All I get told was "give it to the Service Center".
Anyway! Which PIT file should I flash. A Procedure would be nice. My Last firmware was 4.0.4 don't know the number.
Ohk so I found it from the Nandroid Backup. It was I9300XXBLG8 I also found something written as IMM76D
But this was before the OTA update. Can someone tell me about the .pit file for it?
Which .pit file should I use?
bump?
AusafSal said:
bump?
Click to expand...
Click to collapse
Changed the NAND Memory Chip how have you changed on board components .
Isn't this the main reason of XDA-Developer?
Nope its not a fix my phone forum .
JJEgan said:
Changed the NAND Memory Chip how have you changed on board components .
Isn't this the main reason of XDA-Developer?
Nope its not a fix my phone forum .
Click to expand...
Click to collapse
I gave it to a person here in the phone market. He also J-tags it. He had a spare broken motherboard. he changed the NAND Flash Memory Unit by himself. He said it is in the same condition as it was before. So no problem to the NAND Flash Memory Unit is done.
Suggest that you join sammobile as posted and use stock firmware .
Sammobile has a forum and you may get more information regarding a PIT file there .
jje
JJEgan said:
Suggest that you join sammobile as posted and use stock firmware .
Sammobile has a forum and you may get more information regarding a PIT file there .
jje
Click to expand...
Click to collapse
Hey! I didn't noticed its JJE!
I remembered u helped me alot in the previous Threads I made!
I downloaded the U.K version. Which is the one I had according to the Nandroid Backup I made.
I opened the "system.ext4.tar" by WinZip.
Saw a CSCVersion.txt file.
It had written "I9300OXABLG8" on it.
Also in the "build.prop" file (Opened by Notepad) I saw I9300XXBLG8 written aswell.
So I downloaded that one.
So I have only one Question:
Which PIT File should I put? :/
I see 5 of them :-
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
M0_20120220.pit
mx.pit
Which one?
should be the last one...
Why don't you just spare yourself numerous headaches by sending the phone in for repair? Just say it died on you or something.
Theshawty said:
Why don't you just spare yourself numerous headaches by sending the phone in for repair? Just say it died on you or something.
Click to expand...
Click to collapse
No warranty bro! And I'll try tomorrow
btw If I do a wrong pit file. what are the consequences? :/
Mine is the 16GB one of United Kingdom. Non-Branded GT-i9300
AusafSal said:
No warranty bro! And I'll try tomorrow
btw If I do a wrong pit file. what are the consequences? :/
Mine is the 16GB one of United Kingdom. Non-Branded GT-i9300
Click to expand...
Click to collapse
Anyone??
AusafSal said:
Anyone??
Click to expand...
Click to collapse
Wrong Pit possible brick .
jje
AusafSal said:
No warranty bro! And I'll try tomorrow
btw If I do a wrong pit file. what are the consequences? :/
Mine is the 16GB one of United Kingdom. Non-Branded GT-i9300
Click to expand...
Click to collapse
If you flash the wrong pit file or if the pit file fails to flash, you might destroy your nand memory. The pit file is the partition table, hence you should be very careful.
Theshawty said:
If you flash the wrong pit file or if the pit file fails to flash, you might destroy your nand memory. The pit file is the partition table, hence you should be very careful.
Click to expand...
Click to collapse
Ok so Im gonna give it to the Samsung Service Center first thing. I don't wanna completely Eff up my device :/
Gonna take the phone from the person I gave to and hope to God that the NAND change has made that flash counter to Zero :/
OK so many of u might know this thing
I rooted the phone... did an OTA Update. BAM phone not booting up
Still in the same condition tried all kinds of software/hardware techniques. Before trying the PIT file i thought that I might give it to Samsung and ask what they say (My frnd's frnd works there)
So he said this
"Ur phone has a Processor problem, There is no problem with the Partition on ur SD Card. I can change the Processor for u but its a 20% chance that it might work. A Motherboard replacement for Rs. 27,000 will only do it [bought the phone for Rs. 55,000]"
So here is my status:
I'm waiting for the phone to come back and I'll take it and try the PIT file thing
My device is a U.K Unbranded Pebble Blue and rooted. Sometimes goes into the Recovery. Almost about 1 in 10 attempts it goes there and 1 in 5 attempts it is actually stable in it. Other wise it just gets back to the GT-i9300 logo.
So!
2 people say that my device should be flashed with the "mx.pit" file. These guys were experts. I mean 1000+ on the Thanks bar.
1 person says that it shud be "...029.pit" format. He did it on his own. Same device as mine but just that his was White in colour. ONLY DIFFERENCE
I need Answers on the following:
1. Is my phone really having the processor problem? Cuz if it was then it shudnt hav booted up in the first place (I thnk?)
2. WHICH PIT SHOULD I GO FOR. ALSO I'M HAVING A BAD TIME FINDING THE 3-PART FIRMWARE FILE.
3. Flashes OK in the Odin. Like it should on ANY S3. Doesn't gives me errors or anything. But it seems like it doesn't really affect it at all. Its still the same. WHATS THE CULPRIT IN THIS PROBLEM?
4. When I go to the Recovery mode (when stable) I can't mount the SD Card? :/
On going to the "Install Zip from SD Card" it says "cannot mount Sd Card". So i think it is the PIT Problem.
He does says "We are trying everything on our par. Even we're doing what we aren't supposed to be doing to a normal person's S3. (frnd u know)."
So what should I do?
I KNOW ITS A LONG THREAD. BUT DO READ IT CAREFULLY :/ :/
THANKS I REALLY NEED SOME HELP...
How did you manage to do an ota update with a rooted phone....usually a message comes up with something like (phone is modified, update cancelled) so how you managed to do that i dont know!....firmware files for the S3 only come as 1 .tar file because thats all thats needed, in terms of the .pit i suggest you search the stickies....theirs bound to be something in their. But im still baffled as to how you managed to do an ota update on a rooted phone :s
Sent from my GT-I9300 using xda premium
AusafSal said:
. did an OTA Update. BAM phone not booting up
>>>> Not with root . You need to flash stock via Odin .
I can change the Processor for u but its a 20% chance that it might work.
>>>>That sounds nonsense if the CPU is changeable and is the problem its only a 20% chance of working ????
2 people say that my device should be flashed with the "mx.pit" file. These guys were experts. I mean 1000+ on the Thanks bar.
>>>> 1000 thanks does not make an expert in PIT files .
>>> PIT is deadly do not flash a wrong PIT .
I need Answers on the following:
1. Is my phone really having the processor problem? Cuz if it was then it shudnt hav booted up in the first place (I thnk?)
>>>>Samsung Service would need to answer that question .
He does says "We are trying everything on our par. Even we're doing what we aren't supposed to be doing to a normal person's S3. (frnd u know)."
So what should I do?
>>. Take the phone back under warranty to a Samsung service centre with trained staff .
jje
Click to expand...
Click to collapse
JJEgan said:
AusafSal said:
. did an OTA Update. BAM phone not booting up
>>>> Not with root . You need to flash stock via Odin .
I can change the Processor for u but its a 20% chance that it might work.
>>>>That sounds nonsense if the CPU is changeable and is the problem its only a 20% chance of working ????
2 people say that my device should be flashed with the "mx.pit" file. These guys were experts. I mean 1000+ on the Thanks bar.
>>>> 1000 thanks does not make an expert in PIT files .
>>> PIT is deadly do not flash a wrong PIT .
I need Answers on the following:
1. Is my phone really having the processor problem? Cuz if it was then it shudnt hav booted up in the first place (I thnk?)
>>>>Samsung Service would need to answer that question .
He does says "We are trying everything on our par. Even we're doing what we aren't supposed to be doing to a normal person's S3. (frnd u know)."
So what should I do?
>>. Take the phone back under warranty to a Samsung service centre with trained staff .
jje
Click to expand...
Click to collapse
Saying that....if hes rooted his phone, theyll pick up on that and void his warranty....
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I can change the Processor for u but its a 20% chance that it might work. A Motherboard replacement for Rs. 27,000 will only do i
Click to expand...
Click to collapse
Either someone mistranslated it from another language or they are trying to rip you off.
It's VERY,VERY hard to replace the soldered CPU on the logic-board and I'm sure your CPU and logic board are fine.
Usually motherboard replacements are executed whenever they have no clue what's wrong and don't want to search the issue.
There is no problem with the Partition on ur SD Card.
Click to expand...
Click to collapse
Your SDcard has nothing to do with the issue at all. The only problem is your internal storage (which is an SSD, not an SDcard)
Your partitions might be corrupted.
Please define "phone not booting up". It if's stuck in a bootloop, try removing the SDcard and booting the phone to CWM recovery,
and formatting all usual partitions, then running ext2fs on the internal partition.
(Tip: if you have data on it, you can usually skip the formatting and only run ext2fs, that way you usually won't lose any files but the chance of the phone booting again is lower)
d4fseeker said:
Either someone mistranslated it from another language or they are trying to rip you off.
It's VERY,VERY hard to replace the soldered CPU on the logic-board and I'm sure your CPU and logic board are fine.
Usually motherboard replacements are executed whenever they have no clue what's wrong and don't want to search the issue.
Your SDcard has nothing to do with the issue at all. The only problem is your internal storage (which is an SSD, not an SDcard)
Your partitions might be corrupted.
Please define "phone not booting up". It if's stuck in a bootloop, try removing the SDcard and booting the phone to CWM recovery,
and formatting all usual partitions, then running ext2fs on the internal partition.
(Tip: if you have data on it, you can usually skip the formatting and only run ext2fs, that way you usually won't lose any files but the chance of the phone booting again is lower)
Click to expand...
Click to collapse
The Internal memory is generally called an internal 'SD Card', so no need to be picky
Just use the recommended PIT and pray to god, if anything goes wrong just get it to the service center and behave like a blonde, seriously.. be dumb.
Skander1998 said:
The Internal memory is generally called an internal 'SD Card', so no need to be picky
Just use the recommended PIT and pray to god, if anything goes wrong just get it to the service center and behave like a blonde, seriously.. be dumb.
Click to expand...
Click to collapse
What a useless reply .
jje
Try flashing FULL ROM (PDA, PHONE, MODEM, PIT)
GR0S said:
Try flashing FULL ROM (PDA, PHONE, MODEM, PIT)
Click to expand...
Click to collapse
Did you not read the post above....flashing a .pit is not good and he could end up doing more damage than good....fool!
Sent from my GT-I9300 using xda premium
If phone cant boot, maybe filesystem is damaged. TS should completly reflash everything (that will recreate partition table)
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
OTA can't break hardware (I believe), so this is software problem. In the worst case JTAG station will be needen
GR0S said:
Try flashing FULL ROM (PDA, PHONE, MODEM, PIT)
Click to expand...
Click to collapse
I would not send it for warranty repair if your able to boot into recovery - samsung will void warranty for good.
If you can go into downloader mode then I would do the above with a stock rom and PC odin. - preferbably the one that was shipped with ROM or last official update (for UK XXBLG8)
the PIT file determines the partitioning tables so will be needed. I don't know the standard size and type for SGS3 as not done on sgs3 (but have on other devices) - you'll have to research it; look in some of the stickies in general and development section. (this is better and make you more confident then being told and just relying on that. the stickies have somewhat silent agreement behind them. )
I am no expert but have been flashing long time with some breaks which have always been fixed by odin and repartition with PIT. AT the least it may fix it at the most it will completely kill it but less chance of samsung figuring out that you rooted it.
It is unlikely to be processor problem - even 20% processing power is ~ 300mhz quad i.e.1100mhz which should boot the system just take a while.
THANKS alot guys who replied. really helps me out
I've been going into the market for like 2 months now. Searching for something. I even changed the Internal SD but that didnt do the thing. I know its a Software problem and the only thing I haven't tried is the PIT file.
About the Processor thing. he says that "there is 20% chance of it being OK after that". Sorry if I mistyped that. and yeah i wont do that thing as the processor is very hard to replace. i have no idea how he will do it. but he really has fixed S3's in the past with doing this.
and the phone was with Samsung Service Center. My friend's close friend works there. He also tried everything. He is the one stating the Processor Problem
As for the condition.
The phone just boots up to the GT-i9300 and then reboots to there again... and again... and again.
goes to download mode NO PROBLEM!
Flashes the ODIN files either root or Home.tar with NO PROBLEM too. but it doesn't gives ANY errors. and still it doesn't do anything to it. Still gets stuck in the Bootloop.
If u guys need any more details regarding this. Do tell. please!
Plus:- I've too checked in the Stickies. NO ONE has this problem in which ODIN flashes fine but the software fails to do anythng good. it does WRITE on the Internal SD but doesn't do anything good. I can say that because when I root it. It sometimes goes into the Recovery.
AusafSal said:
I even changed the Internal SD
Click to expand...
Click to collapse
What exactly does that mean?
speedyjay said:
How did you manage to do an ota update with a rooted phone....usually a message comes up with something like (phone is modified, update cancelled) so how you managed to do that i dont know!....firmware files for the S3 only come as 1 .tar file because thats all thats needed, in terms of the .pit i suggest you search the stickies....theirs bound to be something in their. But im still baffled as to how you managed to do an ota update on a rooted phone :s
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Mine is also rooted with Samsung stock Rom and managed to ota update but had to reinstall cf-root again to install super user and cwm.
Sent from my GT-I9300T using xda premium
GUYS! My only way out is to flash a PIT File with 3 part file. I can't find the FULL ROM of it. Mine is U.K - BTU
16GB Pebble Blue unbranded GT-i9300
Just tell link me the file please! Then if it doesn't work I will give it off for Mother Board replacement since its the ONLY way out. And it doesn't really matter if I do the wrong one (but still I would really wish the PIT file would fix it) they will JUST REPLACE THE MOTHERBOARD!!
AusafSal said:
GUYS! My only way out is to flash a PIT File with 3 part file. I can't find the FULL ROM of it. Mine is U.K - BTU
16GB Pebble Blue unbranded GT-i9300
Just tell link me the file please! Then if it doesn't work I will give it off for Mother Board replacement since its the ONLY way out. And it doesn't really matter if I do the wrong one (but still I would really wish the PIT file would fix it) they will JUST REPLACE THE MOTHERBOARD!!
Click to expand...
Click to collapse
We don't have the file search sammobile.com or ask on their forum .
jje
I think BTU is general CSC code for all of uk.
Last official UK was BLG8
See here http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1
Faryabs stock ROM thread hotfile links are down
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
http://widefide.com/mobile/galaxy-s3-boot-problem-solution
try the pit from this link also has the procedure
AbuYahya said:
I think BTU is general CSC code for all of uk.
Last official UK was BLG8
No thats wrong .
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
jje
Click to expand...
Click to collapse
JJEgan said:
AbuYahya said:
I think BTU is general CSC code for all of uk.
Last official UK was BLG8
Click to expand...
Click to collapse
No thats wrong .
---------- Post added at 02:46 PM ---------- Previous post was at 02:27 PM ----------
jje
Click to expand...
Click to collapse
so what was it ?
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> cache.img
<ID:0/010> NAND Write Start!!
<ID:0/010> factoryfs.img
<ID:0/010> hidden.img
<ID:0/010> MLO
<ID:0/010> modem.bin
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
What exactly do you mean by that ?
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
NejaaHal said:
I didn't tried with a x86 computer yet but I will this afternoon.
Click to expand...
Click to collapse
MistahBungle said:
What exactly do you mean by that ?
Click to expand...
Click to collapse
I mean that my computer is running a 64bit OS (windows 7). I will get a computer running a 32bit OS this afternoon (maybe Odin don't like being run on a 64 bit environement <.<
MistahBungle said:
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
Click to expand...
Click to collapse
Bad downloads : maybe, but that would mean that the 3 or 4 differents downloads I did (because I thought of that possibility and I've tried to re-download the roms) all were corrupted at some point ^^'
Connection problem : maybe too, but (yeah again a but) I don't touch my computer at all during the process expeciallt to avoid the connexion to be broke.
PS : all my .tar.md5 archives gives me the "error" "There is no correct records at the end of archive" when I check them with 7-zip
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
MistahBungle said:
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
Click to expand...
Click to collapse
Yeah, I ment to use another computer ^^ I'm trying right now. Can you confirm me that a flashing can take one hour or more? (I'm not used to that amount of time)
And yeah, I don't want to give up and pay someone to do something I could do. I'm not a newbie in IT stuff, (even if I don't really know the architecture of an android phone and I don't know the use of the differents files in a rom).
7zip tell me that everything is ok about the downloaded .zip.
Thanks for the tip, I'm going to read that thread
No, a stock rom flash on the S2 should only take a couple of minutes tops. Normally in these situations, as long as you have download mode you can recover it, unless the NAND is messed up, then it's a JTAG (not always possible though) or in many cases a motherboard replacement. But forget that for now & only worry about that when you reach the end of the line so far as stuff you can try goes.
OK. So we can rule out bad download plus pretty much all the other stuff you've tried so far. Try on another machine & read his thread to make doubly sure there's not something really small/obvious we're both missing here.
ok, The ROM I've took come from sammobile so I guess it shouldn't take that amound of time.
That's factoryfs.img that take the most of the time ^^
I just realized that I forgot to launch Odin as administrator with windows 7 (my current try is on a x86 windows XP). But my previous (successfull ) flashes were like that too ^^'
I will continue to try on that other computer, but that will take some time to try all ports (since there is roughly 1h-1h30 to try to flash + the time for a full recharge of the battery <.<)
After having read a couple of threads here I realized that I took a .pit file from somewhere but haven't followed the step there :
[Fix] [Guide] [For Noobs] Recover from Corrupted Memory[USE EXTREME CAUTION]
But since I still not know how is organized an android phone I don't know if I've just used a generic thing that have just done nothing or if I could have messed up something. The file have this name : omap4_all_20110627_emmc.pit
I'm sorry for the double post : this is an update
The first try failed during factoryfs.img. I'm currently charging the phone for a next try.
So far I've tried
- I9100GXXLB1_I9100GATOKL1_ATO
- I9100GXXLSR_I9100GXEFLSR_XEF
- I9100GXXKL5_I9100GXEFKL3_XEF
Would anyone have any idea of which other rom I could try?
Shouldn't make any difference which rom you use, as long as it's an I9100G rom. Try every stock rom you're physically able to download; Sometimes with these situations you could try 10 flashes and they all fail, yet for whatever reason the 11th works. If I had a dollar for every occasion I've seen that happen on here over the past ~2 yrs, I'd have a fair bit of money - it's not super common, but it's not unheard of either.
So keep at it, perseverance might just recover it when trying every single thing you/everyone else on here can think of won't.
Okay, I'll keep going then ^^ may a custom rom work better?
I still don't understand why it take so much time ^^'
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
No, as I said in my first post I can't access the recovery mode. or I don't do it correctly or it don't work anymore.
Hummm ok I will wait about the test firmware ^^' what could happend if it is not compatible?
I'm a little lost into the amount of rom available. Should I only try official roms? could I try other ones, if yes, which ones?
The worst part is that I don't remember which version was running on my phone. I was rooted, up to date I think, but that's all I remember, and I always see "only use this rom with a x.x.x rom" so <.<
also, after having tried so much time to reinstall it, does the indication "only use this rom with a x.x.x rom" still apply?
It doesn't matter which stock firmware you flash/whether it's specifically for your carrier or not. The aim is to get the phone working normally, so any stock I9100G firmware will do.
The suggestion to try a 3 part firmware is a good one, but I honestly don't know if there is such a thing for the I9100G as there is for the I9100.
You really need to start trying with a different PC and more than one if you can, because the alternative involves paying a Samsung service centre a not insignificant sum of money to fix your phone.
Done some google searching and it seems that there is no test firmware for your phone.....I WOULDN'T recommend using the one linked to in hopper8s thread.....the hardware in the phones (specifically the chipsets) are different......you'd probably kill your phone if you used it.
Below is a link to the latest firmware for your phone...
http://hotfile.com/dl/193267715/c98...GT-I9100G-XEF-I9100GXXLSR-1359122020.zip.html
Sent from my GT-I9100 using xda app-developers app
Thanks for all your answers.
I will then continue to try severals computers and severals roms.
I still wonder one thing :
would it be possible to install all the different parts separately? it always fail at the same step, is it possible to install the different parte one after the other? that would avoid me to have to wait 2h between two tries ^^
Also I wonder : what is the use of the .dll file I always find in the .zip ?
Edit : I just noticed something; in the latest version of Odin there is a option called "NAND erase all". would it be a good alternative to the 3-part test firmware?
I hate to do that but : little up about my last questions ^^'
NejaaHal said:
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
Click to expand...
Click to collapse
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Jimsilver73 said:
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Click to expand...
Click to collapse
Thanks ^^ but I am completly absolutely sure I have a i9100G ^^ because I already had problems before to find a way to root my phone ^^ and it say I9100G on the phone ;p I even tried to change it for a normal i9100 at the store I bought it but they told me they only had that version^^
Edit / news: I've tried to flash some part separately (from here :
[COLLECTIONS][MIRROR] Official Firmwares, Kernels, Modems, Bootloaders ). the bootloader don't fail, the kernel don't fail but the modem always fail while writing (now writing [...] -> blank line -> Received response from LOKE -> fail)
I don't know what to do now <.<
New question : have anyone any solution to allow me to have at least access to the recovery? is there any way to flash only the recovery? I made a lot of searches but couldn't find anything :/
If you can flash a custom kernel, you'll get (usually) CWM recovery.......then at that point you can do the full range of wipes and in theory flash custom roms.....
Sent from my GT-I9100 using xda app-developers app
Here we go:
I was trying to install a custom rom today (done it about 20 times before on different devices including this one).
Had rooted stock & CWM custom bootloader (unlocked using Casual months ago I think).
Flashed custom rom and (unfortunately) downloaded and flashed a file for the international version (GT-N7100).
Basically, I accidentally flashed the MJ5 custom bootloader by accident (again, it's for international version, which I have SCH-i605).
It's from here under the SPECIAL INSTRUCTIONS FOR 3.6 AND ABOVE heading
(don't ask why, I'm an idiot. Was trying to install this rom and just totally blew past the fact it was for international version)
I've tried using odin to flash "KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5" (stock rom) and "sch-i605-16gb.pit" as outlined in the countless 'Restore to stock rom/bootloader from bricked state' articles out there on the webs but it keeps failing. (Part 1b from here)
Current symptoms:
Boot loop almost instant at samsung logo with new N7100 line. Will not boot into bootloader but I can get it into odin download mode.
Using Odin3 v 3.07 (on multiple computers with the right drivers I'm pretty sure) I go into download mode and this is listed:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
WARRANTY BIT: 0
Odin hangs at 'Get PIT for mapping' if re-partition is checked, outputs the following if re-partition is unchecked (only auto-reboot and F. Reset Time checked)
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
After this point, it's like the phone stops responding to odin, because if I try to flash again or flash something else, odin just outputs:
<OSM> All threads completed. (succeed 0 / failed 0)
I've been at it for about 8 hours now and I know I'm getting desperate, so I'm hoping you all can help me out before I resort to new phone/sending in for factory reset
Thanks!
- John
Which stock rom are you trying to put back
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Is the Samsung logo Blickling or is stable
thanks,
chat/email : [email protected]
Sorry to say John but that's not a soft brick. Flashing a bootloader for another device causes a hard brick which willl require a JTAG.
nikhil.kdhand said:
Which stock rom are you trying to put back
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Is the Samsung logo Blickling or is stable
thanks,
chat/email : [email protected]
Click to expand...
Click to collapse
Everything you ask is in the op.
Samsung logo not stable.
Stock rom he's trying to flash is vramc3 4.1.2
Sent from my SCH-I605 using Tapatalk
Re: JTAG
Hälftebyte said:
Sorry to say John but that's not a soft brick. Flashing a bootloader for another device causes a hard brick which willl require a JTAG.
Everything you ask is in the op.
Samsung logo not stable.
Stock rom he's trying to flash is vramc3 4.1.2
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Ah, thanks for clearing that up. Guess it's JTAG repair time. I went ahead and purchased a JTAG repair from mobiletechvideos[dot]mybigcommerce[dot]com (Sorry, I haven't posted enough on my account to put outside links in)
For $50, I think it'll be worth having my baby back.
Thanks for your help!
- John Miller
he1calledbubba said:
Ah, thanks for clearing that up. Guess it's JTAG repair time. I went ahead and purchased a JTAG repair from mobiletechvideos[dot]mybigcommerce[dot]com (Sorry, I haven't posted enough on my account to put outside links in)
For $50, I think it'll be worth having my baby back.
Thanks for your help!
- John Miller
Click to expand...
Click to collapse
Yeah many people use him. He's also here on XDA.
Let us know how it turns out. :good:
I actually did the exact thing you did. I can flash other roms, but can't get the radio back or flash AOSP roms. Can you let me know how the JTAG goes? I need to do it, too. It's either that or upgrade to a note 3.
Could you guys give me a recommendation on the one I should choose?
Also. I don't mean to sound like a "noob" or anything, but would it be possible to just flash the i605 bootloader back?
Numzi said:
I actually did the exact thing you did. I can flash other roms, but can't get the radio back or flash AOSP roms. Can you let me know how the JTAG goes? I need to do it, too. It's either that or upgrade to a note 3.
Could you guys give me a recommendation on the one I should choose?
Also. I don't mean to sound like a "noob" or anything, but would it be possible to just flash the i605 bootloader back?
Click to expand...
Click to collapse
Sounds like you have a different issue. Have you tried reverting to stock? If you can flash roms fine then you should be able to go back to stock which would return you to i605 radio and bootloader. If you go back to stock and still have no radio then you probably borked your efs
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Sounds like you have a different issue. Have you tried reverting to stock? If you can flash roms fine then you should be able to go back to stock which would return you to i605 radio and bootloader. If you go back to stock and still have no radio then you probably borked your efs
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I have tried doing that, but Odin gets stuck on different things. I cant even repartition with the i605 pit file. But it lets me repartition with the N7100 one. Also, I cant flash the stock rom as it gets stuck on sboot, but if I use 66root one, it goes through, but doesn't run properly. (Odin also allows me to flash the N7100 stock file.)
The bootloader baseline file also gets stuck on tz.img. (Unless I'm using the wrong one, but I'm sure I'm not)
I kind of lost hope in restoring my phone to normal. if I flash a 4.3 TW Rom, it works fine, but the radio doesnt read. If I flash a 4.1.2 Rom, it works fine and I might or might not get signal, but data doesnt work and my internal memory reads 0/0. Any ideas?
Sent from my SCH-I605 using xda app-developers app
Numzi said:
I have tried doing that, but Odin gets stuck on different things. I cant even repartition with the i605 pit file. But it lets me repartition with the N7100 one. Also, I cant flash the stock rom as it gets stuck on sboot, but if I use 66root one, it goes through, but doesn't run properly. (Odin also allows me to flash the N7100 stock file.)
The bootloader baseline file also gets stuck on tz.img. (Unless I'm using the wrong one, but I'm sure I'm not)
I kind of lost hope in restoring my phone to normal. if I flash a 4.3 TW Rom, it works fine, but the radio doesnt read. If I flash a 4.1.2 Rom, it works fine and I might or might not get signal, but data doesnt work and my internal memory reads 0/0. Any ideas?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Most likely you're going to need JTAG if you really want to be back to original. If not there are a few things I would try.
Anyway, from what I'm reading you're on an N7100 bootloader so that's why you're able to repartition with the N7100 pit file. You're pretty lucky you're even able to repartition to be honest.
What happens when you flash the N7100 stock rom? Are you able to boot?
Are you using your phone on the Verizon network?
Btw, the reason root66 works is because it only contains the system partition. There's no sboot, boot, modem etc in there to conflict with the N7100 bootloader you currently have. But of course it will have issues since the i605 system image won't jell well with N7100 boot, etc.
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Most likely you're going to need JTAG if you really want to be back to original. If not there are a few things I would try.
Anyway, from what I'm reading you're on an N7100 bootloader so that's why you're able to repartition with the N7100 pit file. You're pretty lucky you're even able to repartition to be honest.
What happens when you flash the N7100 stock rom? Are you able to boot?
Are you using your phone on the Verizon network?
Btw, the reason root66 works is because it only contains the system partition. There's no sboot, boot, modem etc in there to conflict with the N7100 bootloader you currently have. But of course it will have issues since the i605 system image won't jell well with N7100 boot, etc.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
If I could avoid JTagging it would be preferred haha. I don't care about going back to complete original (stock) if that's what you mean. I just want to get my Radio to read while being able to access my storage and data because I'm pretty happy with the 4.3 Touchwiz Rom (at least for now).
When I flash the N7100 stock rom, I can boot. It boot loops until I go into recovery and format data/cache and after that it works fine, with no radio service. Also, I have always been using my phone on the H2O Wireless network with APN settings. But now, the radio doesn't read at all and shows no imei and what not. However if I go back to Jedi X 19 (was my daily 4.1.2 TW driver), the radio reads and I have my imei, but I can't get data and it says my memory is full (can't open gallery and my internal SD says 0/0 bytes).
I know about root66, but what I don't understand is why I was able to flash to the N7100 bootloader and now can't flash back to the i605 one. Is there a specific reason for that?
Btw, Thanks for trying to help me right now. Really appreciated.
Numzi said:
If I could avoid JTagging it would be preferred haha. I don't care about going back to complete original (stock) if that's what you mean. I just want to get my Radio to read while being able to access my storage and data because I'm pretty happy with the 4.3 Touchwiz Rom (at least for now).
When I flash the N7100 stock rom, I can boot. It boot loops until I go into recovery and format data/cache and after that it works fine, with no radio service. Also, I have always been using my phone on the H2O Wireless network with APN settings. But now, the radio doesn't read at all and shows no imei and what not. However if I go back to Jedi X 19 (was my daily 4.1.2 TW driver), the radio reads and I have my imei, but I can't get data and it says my memory is full (can't open gallery and my internal SD says 0/0 bytes).
I know about root66, but what I don't understand is why I was able to flash to the N7100 bootloader and now can't flash back to the i605 one. Is there a specific reason for that?
Btw, Thanks for trying to help me right now. Really appreciated.
Click to expand...
Click to collapse
Okay, I doubt what I was thinking of is going to work then. I was thinking you should flash the N7105 modem while you're on the N7100 rom. Maybe you can try that or maybe try flashing the i605 modem there's always the risk of fully bricking it though.
If that doesn't work I would try using Heimdall to flash the I605 pit file and sboot.bin.
Heimdall sometimes works in cases where Odin fails (according to a JTAG guy a spoke to once)
I have no problem helping. I have three motherboards myself, two of which i experiment with. One is bricked, one is water damaged and semi bricked (no efs, imei, internal memory only works on 4.3 TW) and one is fully functional :laugh:
Hälftebyte said:
Okay, I doubt what I was thinking of is going to work then. I was thinking you should flash the N7105 modem while you're on the N7100 rom. Maybe you can try that or maybe try flashing the i605 modem there's always the risk of fully bricking it though.
If that doesn't work I would try using Heimdall to flash the I605 pit file and sboot.bin.
Heimdall sometimes works in cases where Odin fails (according to a JTAG guy a spoke to once)
I have no problem helping. I have three motherboards myself, two of which i experiment with. One is bricked, one is water damaged and semi bricked (no efs, imei, internal memory only works on 4.3 TW) and one is fully functional :laugh:
Click to expand...
Click to collapse
Well at this point, I was already ready to send it for JTag repair so I'll try anything. Would you mind letting me know which N7105 modem I should flash? I've already tried i605 modems (not through Odin though) and they haven't worked.
I'm a bit confused with how to use Heimdall and where to find sboot for i605. I have it and wanted to try it, but was lost haha.
Oh that's great lolol. Mine is like yours for internal memory right now. I have a back up of my efs folder, but when I restore it, it doesn't read it.
Numzi said:
Well at this point, I was already ready to send it for JTag repair so I'll try anything. Would you mind letting me know which N7105 modem I should flash? I've already tried i605 modems (not through Odin though) and they haven't worked.
I'm a bit confused with how to use Heimdall and where to find sboot for i605. I have it and wanted to try it, but was lost haha.
Oh that's great lolol. Mine is like yours for internal memory right now. I have a back up of my efs folder, but when I restore it, it doesn't read it.
Click to expand...
Click to collapse
If you have CWM or TWRP you could try one of these flashable modems from here http://forum.xda-developers.com/showthread.php?t=2031575
As I said this might brick you fully
Heimdall is pretty easy after you get the hang of it. After download you will need to setup the drivers with the zadig.exe installer. I would use a different usb port from the one you currently use for Odin so you don't have to reinstall samsung drivers whenever you want to use Odin. You should find a tutorial easily to get started. If you need more help I can go into a bit more detail.
To access the files that Heimdall will need (sboot.bin, boot, tz, system, param, modem.bin etc ), make a copy of the tar.md5 rom file you have. Remove the .md5 at the end and use 7z to extract the contents. You will see all the separate files needed for each partition.
The fact that you can actually repartition sounds good though. I feel like if you can get the I605 sboot.bin (bootloader) flashed, you can then partition with the I605 PIT. This is all speculation though :fingers-crossed:
Hälftebyte said:
If you have CWM or TWRP you could try one of these flashable modems from here http://forum.xda-developers.com/showthread.php?t=2031575
As I said this might brick you fully
Heimdall is pretty easy after you get the hang of it. After download you will need to setup the drivers with the zadig.exe installer. I would use a different usb port from the one you currently use for Odin so you don't have to reinstall samsung drivers whenever you want to use Odin. You should find a tutorial easily to get started. If you need more help I can go into a bit more detail.
To access the files that Heimdall will need (sboot.bin, boot, tz, system, param, modem.bin etc ), make a copy of the tar.md5 rom file you have. Remove the .md5 at the end and use 7z to extract the contents. You will see all the separate files needed for each partition.
The fact that you can actually repartition sounds good though. I feel like if you can get the I605 sboot.bin (bootloader) flashed, you can then partition with the I605 PIT. This is all speculation though :fingers-crossed:
Click to expand...
Click to collapse
I got it. Alright then I will try this tomorrow when I finish classes (It's 3am right now and I have to wake up in 4 hours). I'll post here with the result! This is a new suggestion for this, so I'm kind of nervous/excited about the result. haha.
Just think of it as another experiment for you. Fingers crossed. I'll let you know and thanks so much.
Numzi said:
I got it. Alright then I will try this tomorrow when I finish classes (It's 3am right now and I have to wake up in 4 hours). I'll post here with the result! This is a new suggestion for this, so I'm kind of nervous/excited about the result. haha.
Just think of it as another experiment for you. Fingers crossed. I'll let you know and thanks so much.
Click to expand...
Click to collapse
Also in case you didn't realize, since everything except internal storage works in JediX19, when installing Jedi you can install the swap script, FAT32 script (no need to format external sd card). Then you will have 'internal storage' and a signal. Not the best solution but a workaround. Not many roms have the swap script option so I guess you'd be stuck on Jedi if you choose this route.
Hälftebyte said:
Also in case you didn't realize, since everything except internal storage works in JediX19, when installing Jedi you can install the swap script, FAT32 script (no need to format external sd card). Then you will have 'internal storage' and a signal. Not the best solution but a workaround. Not many roms have the swap script option so I guess you'd be stuck on Jedi if you choose this route.
Click to expand...
Click to collapse
So Heimdall didn't work - it failed repartitioning and when I tried unchecking that, failed at bootloader, then at cache, etc. Do you think it's wiser for me to first try flashing the modem then do the SD Swap? or to just do the SD Swap thing on Jedi?
EDIT: I just did the FAT32 script and the internal storage (which is actually my ext SD card), still says 0/0 bytes...
Numzi said:
...
EDIT: I just did the FAT32 script and the internal storage (which is actually my ext SD card), still says 0/0 bytes...
Click to expand...
Click to collapse
Strange it works for me. Otherwise I only have internal memory when I'm on TW 4.3
I guess there's not much more experimenting to do
Hälftebyte said:
Strange it works for me. Otherwise I only have internal memory when I'm on TW 4.3
I guess there's not much more experimenting to do
Click to expand...
Click to collapse
I'll keep trying to see if the Swap could work eventually. I'll just stick with Jedi or the 4.3 rom until I JTag repair in 2 weeks. Thanks for your help. I really appreciate it.
Numzi said:
I'll keep trying to see if the Swap could work eventually. I'll just stick with Jedi or the 4.3 rom until I JTag repair in 2 weeks. Thanks for your help. I really appreciate it.
Click to expand...
Click to collapse
No prob. Good luck. It looked so hopeful with you being able to partition. :good:
Hälftebyte said:
No prob. Good luck. It looked so hopeful with you being able to partition. :good:
Click to expand...
Click to collapse
I decided to just get the JTag service now and just paid for it. I'll let you know if it really goes back to perfect.
Hey guys, I have a Galaxy Note II SCH-I605 that won't boot. It's stuck on the Galaxy Note II splash screen, and Odin is failing at NAND write start, Recovery menu has a bunch of stuff about not being able to mount /cache and /sdcard. I tried a lot of things, booting without external sdcard/simcard and trying to load my stock ROM with the external SD card and ADB which both don't work. I'm wondering if my NAND is fried and dead.
Any thoughts?
EDIT: This is my only phone, same phone I've had for 3 years plus. I reeeeally want to get this working again. I don't have the money to buy a new phone, and I have all my contacts and data on this one. I hope someone can lend a hand!
Hellstorm32 said:
Hey guys, I have a Galaxy Note II SCH-I605 that won't boot. It's stuck on the Galaxy Note II splash screen, and Odin is failing at NAND write start, Recovery menu has a bunch of stuff about not being able to mount /cache and /sdcard. I tried a lot of things, booting without external sdcard/simcard and trying to load my stock ROM with the external SD card and ADB which both don't work. I'm wondering if my NAND is fried and dead.
Any thoughts?
EDIT: This is my only phone, same phone I've had for 3 years plus. I reeeeally want to get this working again. I don't have the money to buy a new phone, and I have all my contacts and data on this one. I hope someone can lend a hand!
Click to expand...
Click to collapse
Try booting to recovery and factory reset and wipe cache and then try Odin again. Verify that you are using the correct stock firmware for your model number and your region.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try booting to recovery and factory reset and wipe cache and then try Odin again. Verify that you are using the correct stock firmware for your model number and your region.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thanks for your suggestions, I appreciate all help I can get. I have already tried Recovery Mode. I haven't had any success. Every time I attempt to launch recovery mode it won't launch the traditional way I am familiar with. It always takes a while to start, then goes into a picture of the Android with the spinning geometric shape, then it turns into a red triangle with an exclamation point. Then it has a bunch of red text show up on the screen about "E: failed to mount /efs (No such file or directory), E: Can't mount /cache/recovery/log, E: Can't open cache/recovery/log, E: failed to mount /system (No such file or directory), E: failed to mount /cache (No such file or directory), E: failed to mount /sdcard (No such file or directory)". I then get a blue menu with all the red text still in the background. I have 6 selections on this menu: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update from cache. I've tried apply update from ADB, to which I can't get ADB to recognize my phone. I've tried loading my ROM on the external SD card, but the menu won't navigate to the external SD card and i get more additional red text stating E: failed to mount /sdcard (No such file or directory).
I've tried the laymans ways to flash the phone (I've rooted with GhettoRoot before, but recently reverted to a stock ROM about 2 months ago due to not having the time to stay on top of things so I'm familiar with all the standard troubleshooting. I'm out of the general options that I can think of.
I have tried flashing the stock ROM with Odin, but it always fails at NAND write start. I've tried different USB cables, and I'm using Odin 3.07. The stock ROM I have is good, I've used it before to recover a soft brick I had a year and a half ago (tried installing TWRP from the play store, didn't know about bootloaders back then).
If you have any other ideas on how to fix it, I would be happy to listen and try. I'm heading to Best Buy tomorrow (they're going to try to flash me with a stock ROM.)
Thanks
Hellstorm32 said:
Thanks for your suggestions, I appreciate all help I can get. I have already tried Recovery Mode. I haven't had any success. Every time I attempt to launch recovery mode it won't launch the traditional way I am familiar with. It always takes a while to start, then goes into a picture of the Android with the spinning geometric shape, then it turns into a red triangle with an exclamation point. Then it has a bunch of red text show up on the screen about "E: failed to mount /efs (No such file or directory), E: Can't mount /cache/recovery/log, E: Can't open cache/recovery/log, E: failed to mount /system (No such file or directory), E: failed to mount /cache (No such file or directory), E: failed to mount /sdcard (No such file or directory)". I then get a blue menu with all the red text still in the background. I have 6 selections on this menu: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update from cache. I've tried apply update from ADB, to which I can't get ADB to recognize my phone. I've tried loading my ROM on the external SD card, but the menu won't navigate to the external SD card and i get more additional red text stating E: failed to mount /sdcard (No such file or directory).
I've tried the laymans ways to flash the phone (I've rooted with GhettoRoot before, but recently reverted to a stock ROM about 2 months ago due to not having the time to stay on top of things so I'm familiar with all the standard troubleshooting. I'm out of the general options that I can think of.
I have tried flashing the stock ROM with Odin, but it always fails at NAND write start. I've tried different USB cables, and I'm using Odin 3.07. The stock ROM I have is good, I've used it before to recover a soft brick I had a year and a half ago (tried installing TWRP from the play store, didn't know about bootloaders back then).
If you have any other ideas on how to fix it, I would be happy to listen and try. I'm heading to Best Buy tomorrow (they're going to try to flash me with a stock ROM.)
Thanks
Click to expand...
Click to collapse
When you get the blue menu, have you tried the factory reset and the wipe cache and then flashing with Odin?
Have you tried finding the PIT file for your model number then flashing it along with the stock firmware in Odin. Those mount errors tell me that your partitions are corrupted somewhere, the PIT will make sure its flashing everything to the correct partition.
If you can find your firmware in a 4 part file you can flash them in Odin but you have to put each part of the firmware in the slot they go in when using Odin. This is different than having an all in one firmware, these you flash in the AP slot but the 4 part is not flashed in the AP slot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
When you get the blue menu, have you tried the factory reset and the wipe cache and then flashing with Odin?
Have you tried finding the PIT file for your model number then flashing it along with the stock firmware in Odin. Those mount errors tell me that your partitions are corrupted somewhere, the PIT will make sure its flashing everything to the correct partition.
If you can find your firmware in a 4 part file you can flash them in Odin but you have to put each part of the firmware in the slot they go in when using Odin. This is different than having an all in one firmware, these you flash in the AP slot but the 4 part is not flashed in the AP slot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Yes, I have tried clearing the cache. I only get errors on not being able to mount /cache. I have just located a .pit file that says it's for SCH-I605. I will try to flash that with Odin. I'm using an old version of Odin because I didn't understand the newer ones. Last time I had to use it was about a year and a half ago, so I wasn't familiar with all the new fields in Odin 3.12.
I wasn't able to find many different links with the .pit file for the SCH-I605. I found one link that was still good, and I'm going to try it. I believe the file is 3k, which makes sense to me because it's just partition data.
I'll let you know how this works out.
Hellstorm32 said:
Yes, I have tried clearing the cache. I only get errors on not being able to mount /cache. I have just located a .pit file that says it's for SCH-I605. I will try to flash that with Odin. I'm using an old version of Odin because I didn't understand the newer ones. Last time I had to use it was about a year and a half ago, so I wasn't familiar with all the new fields in Odin 3.12.
I wasn't able to find many different links with the .pit file for the SCH-I605. I found one link that was still good, and I'm going to try it. I believe the file is 3k, which makes sense to me because it's just partition data.
I'll let you know how this works out.
Click to expand...
Click to collapse
Use the newer Odin and put the PIT in its own slot and the stock firmware in the AP slot. Do a search if you don't know where to put the PIT in Odin, also, make sure you have the correct options checked in Odin, if you select the wrong options it'll mess the device up.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Well, I hope I didn't jump the gun. I did use the .pit file in Odin 3.07, I just saw your message about Odin 3.12. I loaded the PIT in the PIT slot, loaded my ROM in the PDAslot, and it seems to be taking a while on the <ID:0/003> Get PITfor mapping..
Droidriven said:
Use the newer Odin and put the PIT in its own slot and the stock firmware in the AP slot. Do a search if you don't know where to put the PIT in Odin, also, make sure you have the correct options checked in Odin, if you select the wrong options it'll mess the device up.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
How long should it take for the "Get PIT for mapping.." part? I've been waiting about 8 minutes, and it's still on that step. I have a newer computer, i3 processor 16gb ram and I don't remember it taking this long before. Would I be safe to unplug if it takes much longer, or is it a bad idea since I'm using the PIT file?
Hellstorm32 said:
How long should it take for the "Get PIT for mapping.." part? I've been waiting about 8 minutes, and it's still on that step. I have a newer computer, i3 processor 16gb ram and I don't remember it taking this long before. Would I be safe to unplug if it takes much longer, or is it a bad idea since I'm using the PIT file?
Click to expand...
Click to collapse
Don't ever unplug it while flashing, that's a brick scenario for sure. You can cancel if it doesn't start the flash process, I'm not sure what results will be though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Don't ever unplug it while flashing, that's a brick scenario for sure. You can cancel if it doesn't start the flash process, I'm not sure what results will be though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok. It's still on this step, "Getting PIT for mapping.."
All the buttons are greyed out (can't click on them) so that tells me that the flash process is undertaking, but I can't understand why it's taking so long. I don't see my HDD light flashing, and Odin is using zero CPU in my resource monitor.
I'm wondering if my flash process is stuck and not progressing.
Text in Odin so far..
<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> Get PIT for mapping..
Hellstorm32 said:
Ok. It's still on this step, "Getting PIT for mapping.."
All the buttons are greyed out (can't click on them) so that tells me that the flash process is undertaking, but I can't understand why it's taking so long. I don't see my HDD light flashing, and Odin is using zero CPU in my resource monitor.
I'm wondering if my flash process is stuck and not progressing.
Click to expand...
Click to collapse
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Hellstorm32 said:
Text in Odin so far..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Click to expand...
Click to collapse
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok, I've closed Odin. I've disconnected my device. I've checked and yes, I can still enter download mode (phew, I don't have much hardmod skills to get it running if it's hard bricked).
I'm going to bring it in to Best Buy today and see if the Samsung staff can flash it there. I was running stock when this happened. It's crazy, I was driving my car and I had my phone in my mount on the dash. I just happened to look over and it was stuck on the boot screen. No warning. It just restarted and froze on it's own.
Thanks for the help, I'm going to keep working on it today and see if I can get things moving.
Droidriven said:
Yep, its stuck, close Odin and then disconnect the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
---------- Post added at 10:39 PM ---------- Previous post was at 10:31 PM ----------
Check this thread out and see if it helps
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Ignore that its from the S2 forum, its about Odin issues so it might help.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Ok, so here's an update. I was able to send my stock ROM to my device using the ADB sideload option from the recovery menu, but was unable to load the ROM due to the partition being corrupted.
I attempted a flash in Odin 3.12.3 with the PIT file and my stock ROM in the AP slot. I haven't been able to obtain a ROM in 4 seperate parts like you had suggested, I'm only still using the ROM that I have had for a year or so. This flash fails at partitioning. Odin message: Re-Partition operation failed.
I scoped out the guide you linked to me for the S2, and from what I'm seeing they say that if Odin fails a partition operation there is no hope. Only thing I can do is get a new motherboard.
Looks like the phone is completely dead. I'll look on Ebay for a new MB, but I may just end up getting a new phone.
Thanks for the help man. Too bad we couldn't get it up and running. I'm probably going to still mess with it. Please let me know if you have any other suggestions.
Hellstorm32 said:
Ok, so here's an update. I was able to send my stock ROM to my device using the ADB sideload option from the recovery menu, but was unable to load the ROM due to the partition being corrupted.
I attempted a flash in Odin 3.12.3 with the PIT file and my stock ROM in the AP slot. I haven't been able to obtain a ROM in 4 seperate parts like you had suggested, I'm only still using the ROM that I have had for a year or so. This flash fails at partitioning. Odin message: Re-Partition operation failed.
I scoped out the guide you linked to me for the S2, and from what I'm seeing they say that if Odin fails a partition operation there is no hope. Only thing I can do is get a new motherboard.
Looks like the phone is completely dead. I'll look on Ebay for a new MB, but I may just end up getting a new phone.
Thanks for the help man. Too bad we couldn't get it up and running. I'm probably going to still mess with it. Please let me know if you have any other suggestions.
Click to expand...
Click to collapse
Don't give up yet, I'm not done with my bag of tricks.[emoji6]
There is a method that involves using a debrick.IMG to boot from extsdcard like using a bootable USB drive on PC.
forum.xda-developers.com/showthread.php?t=2660566
You'll have to find the debrick.IMG that was created from the same stock firmware that you have. If you can find someone with your same model number device that is rooted, you can get them to pull a debrick.img from their device using Terminal Emulator, you'll have to do a google search to find the terminal command for your model number to pull the debrick.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Don't give up yet, I'm not done with my bag of tricks.[emoji6]
There is a method that involves using a debrick.IMG to boot from extsdcard like using a bootable USB drive on PC.
forum.xda-developers.com/showthread.php?t=2660566
You'll have to find the debrick.IMG that was created from the same stock firmware that you have. If you can find someone with your same model number device that is rooted, you can get them to pull a debrick.img from their device using Terminal Emulator, you'll have to do a google search to find the terminal command for your model number to pull the debrick.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Wow man, that sounds good! Never heard of that before...I gotta admit though, I'm wondering what my chances are of finding someone with a Note 2 SCH-I605 that's rooted nowadays...I gotta admit my phone feels kind of ancient. I think it's going to be tough to find, but I will do some searches and look around. Thanks for the suggestion! I'll report back what I find.
Also, how do I do this method? If I find the file, do I load up recovery and try to load from SDcard?
UPDATE: Also, I tried enabling the Nand Erase All checkbox in Odin, and no dice. The error was that it failed to write to the NAND during the erase process. The more I mess with this the more I think my flash memory in the NAND is dead. I'm still completely open to your advice though and appreciate it very much.
Hellstorm32 said:
Wow man, that sounds good! Never heard of that before...I gotta admit though, I'm wondering what my chances are of finding someone with a Note 2 SCH-I605 that's rooted nowadays...I gotta admit my phone feels kind of ancient. I think it's going to be tough to find, but I will do some searches and look around. Thanks for the suggestion! I'll report back what I find.
Also, how do I do this method? If I find the file, do I load up recovery and try to load from SDcard?
UPDATE: Also, I tried enabling the Nand Erase All checkbox in Odin, and no dice. The error was that it failed to write to the NAND during the erase process. The more I mess with this the more I think my flash memory in the NAND is dead. I'm still completely open to your advice though and appreciate it very much.
Click to expand...
Click to collapse
If you did NAND erase all its dead. I started to warn you when you first mentioned NAND to leave it alone and don't mess with NAND in Odin. You can send it in for JTAG service, its usually $50 and they send it back to you fixed. Cheaper than replacing the motherboard. JTAG is the last ditch effort.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
If you did NAND erase all its dead. You can send it in for JTAG service, its usually $50 and they send it back to you fixed.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I can still load to the Download screen. Does that mean that there's still hope? Or is the fact that the erase operation fails to write indicate that the flash hardware is bad like I've thought?
I also have thought about just getting a new mobo for it. Is there soldering involved in installing one? Also, is there some sort of hardware signing that will prevent me from installing a different mobo than was shipped with the phone?
Hellstorm32 said:
I can still load to the Download screen. Does that mean that there's still hope? Or is the fact that the erase operation fails to write indicate that the flash hardware is bad like I've thought?
I also have thought about just getting a new mobo for it. Is there soldering involved in installing one? Also, is there some sort of hardware signing that will prevent me from installing a different mobo than was shipped with the phone?
Click to expand...
Click to collapse
The mobo you have is shot. You can replace it yourself, no soldering involved unless the battery wires are soldered, if so, you'd have to solder that back on the new mobo. You have to get the same motherboard from the same model number you have, a different mobo will require altering your firmware. If you do it yourself just be careful disassembling the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
The mobo you have is shot. You can replace it yourself, no soldering involved unless the battery wires are soldered, if so, you'd have to solder that back on the new mobo. You have to get the same motherboard from the same model number you have, a different mobo will require altering your firmware. If you do it yourself just be careful disassembling the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Great help. Thanks man. I think I'm going to look at new models and see about upgrading. I believe with all the battery problems on the Note 7 that Verizon is offering 0$ down as incentive to purchase one. I'll have to do my research, but it's listed as 36$ a month and I may be able to afford that. After I get a new phone, I'll do my best to get the old one working again (new mobo) and probably look to unload it on Ebay after it's up and running no problems. Either that or let my wife take tthe Note 2 over (She has an S3).
I'm bummed. Especially because this happened out of the blue. I was running stock ROM and phone rebooted out of the blue to the splash screen and BAM...dead. I've been able to recover devices before (I bricked a Stealth Trio 7 before and had to write .sh files to get the touch screen to work again), this is the first time I've been unable to fix an android device. Had to happen sometime.
Thanks again for your efforts.:highfive: