[HELP]Bootloop will pay by paypal for solution! - Galaxy S III Q&A, Help & Troubleshooting

So I bought a blue s3 gt-i9300 from ebay.co.uk and I received it with a boot loop problem.
It only gets into download mode (odin mode) and says CUSTOM BINARY DOWNLOAD: NO, CURRENT BINARY: Samsung Official, SYSTEM STATUS STATUS: Official
It tried to flash a CW recovery but it keeps failing with NAND Write(start)... Fail.
Tried to flash a stock firmaware same NAND error.
Tried to do a repartition and nand erase with a pit file. It gets stuck at Erase...
I have adb installed but my device is not showing, although in odin it connects to my phone and windows shows my phone in the device manager.
I have tried with windows 8 on one computer and windows 7 on another. I have also changed the usb cable 2 times.
Is there anything else I should try or the only fix is a new mobo?
I am ready to pay for solving this problem through paypal. I can give you teamviewer access etc.
Please help me I am desperate...

new motherboard or read the forum this is a repetitive topic you have posted .

JJEgan said:
new motherboard or read the forum this is a repetitive topic you have posted .
Click to expand...
Click to collapse
Is this the only option? How much should they charge me for a mobo replacement?

milupas2 said:
Is this the only option? How much should they charge me for a mobo replacement?
Click to expand...
Click to collapse
I gave you two options .

JJEgan said:
I gave you two options .
Click to expand...
Click to collapse
Yes, but I do not know what else to try, I've read at least 100 topics with no results. I have posted everything I tried.
Could you please at least give me an estimative cost for emmc replacement if that is the only solution?

milupas2 said:
Yes, but I do not know what else to try, I've read at least 100 topics with no results. I have posted everything I tried.
Could you please at least give me an estimative cost for emmc replacement if that is the only solution?
Click to expand...
Click to collapse
you can try a rescue firmware here http://forum.xda-developers.com/showthread.php?t=1825272 make sure if you flash pit that it is correct. based on your internal storage.

ashraf sharif said:
you can try a rescue firmware here http://forum.xda-developers.com/showthread.php?t=1825272 make sure if you flash pit that it is correct. based on your internal storage.
Click to expand...
Click to collapse
with pit file: no pit partition found.
without pit file: Nand write start. . fail
with a pit named u1_02_20110310_emmc_EXT4 i get a different pit error, something like pit failed. (not the no pit partition found this time)

9634482 140
milupas2 said:
with pit file: no pit partition found.
without pit file: Nand write start. . fail
with a pit named u1_02_20110310_emmc_EXT4 i get a different pit error, something like pit failed. (not the no pit partition found this time)
Click to expand...
Click to collapse
can jtag fix this?

No, you have nand memory failure and require a new motherboard.

Related

brick the phone after flash with a wrong pit file

hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
m_adnan said:
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
Click to expand...
Click to collapse
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
sak500 said:
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
Click to expand...
Click to collapse
100% agree stay away from PIT unless you really know what you are doing .
jje
sak500 said:
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
Click to expand...
Click to collapse
JJEgan said:
100% agree stay away from PIT unless you really know what you are doing .
jje
Click to expand...
Click to collapse
its only as a information, maybe somebody runs into the same problem..
It's true that's it's not advised to play with pit files, but I think it would be better if you explained to people why.
Pit files are to be used only when you need to restore partition layout on the phone. That means after you mess up partitions and not before. Bu some guys just ignore warnings like this.
PjotrFias said:
It's true that's it's not advised to play with pit files, but I think it would be better if you explained to people why.
Pit files are to be used only when you need to restore partition layout on the phone. That means after you mess up partitions and not before. Bu some guys just ignore warnings like this.
Click to expand...
Click to collapse
The why is generally that they use the wrong PIT files .
One of the stupid reasons why is going to forum xxxx downloading firmware from them then coming here to ask why has it broke my phone .
PIT mistakes for SG range are in the thousands not just the odd few .
jje
flashed a pit file and now my galaxy s2 is hard bricked
Hi
im new to xda. but having been trying to root my galaxy s2 I9100 through xda tutorials.
my problem started when i flashed a pit file with odin.and now i think its hard bricked. doesn't respond to anything, doesn't show on odin either. ive taken the battery out and have kept it like it for more than 6 hours, with no luck at all. but once i put in the battery to check it becomes hot. even bought a USB Jig and tried, nothing happened. please help as in my country we dont get warranty or we dont samsung service centers. I've tried so many ways to get my phone to life but have failed.. please help:crying:
Does the phone boot to download mode does Odin see the phone .
jje
JJEgan said:
Does the phone boot to download mode does Odin see the phone .
jje
Click to expand...
Click to collapse
nope nothing happens only gets hot..
boboschiyax said:
nope nothing happens only gets hot..
Click to expand...
Click to collapse
One source a USB Recovery Jig and try to enter download mode .Flash stock firmware .
That fails its a paid for service centre job .
jje
JJEgan said:
One source a USB Recovery Jig and try to enter download mode .Flash stock firmware .
That fails its a paid for service centre job .
jje
Click to expand...
Click to collapse
thanks but already did that. didn't work
boboschiyax said:
i think its hard bricked. doesn't respond to anything, doesn't show on odin either.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32367917
pleaaaaaaaaaase help me !!
m_adnan said:
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
Click to expand...
Click to collapse
i tried 4 pit files to repartition my samsung s3 i9300 but all the result is fault
my s3 now dead
please help me
i search google for all pit files of i9300 but no success
pleaaaaaaaaaaaaaaaaaaaaaaaaaaaaase can anybody help me!!
please help me i did the same thing i have note 3 of n9005 UAE version of 32gb and i flashed a wrong pit file (i.e i flashed N900A pit file in N9005 ) and i tried many pit files using Nand erase all in odin but its not working for me as it just erased the partion in my phone but its not repartioning i mean not replacing any pit file
and odin just showing me error all the time and flashing FAIL
Nothing you can do. If you flash a wrong pit file then your phone is broken. Hard bricked.
The only possibility for you is finding someone with a JTAG box. Try one of those phone repair shops. AFAIK, that's your only hope.
Flashing a wrong pit file is pretty much the worst possible thing you can do to your phone. How the hell did you manage to flash the wrong pit file? Didn't you double, triple, quadruple check that it was the correct file before flashing?
Please don't tell me that you knew that the file was meant for another phone? I've actually seen people do that... :facepalm:
Sent from my GT-I9300 using Tapatalk
NeilH1978 said:
Nothing you can do. If you flash a wrong pit file then your phone is broken. Hard bricked.
The only possibility for you is finding someone with a JTAG box. Try one of those phone repair shops. AFAIK, that's your only hope.
Flashing a wrong pit file is pretty much the worst possible thing you can do to your phone. How the hell did you manage to flash the wrong pit file? Didn't you double, triple, quadruple check that it was the correct file before flashing?
Please don't tell me that you knew that the file was meant for another phone? I've actually seen people do that... :facepalm:
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
It is possible because people usually think in terms of branding. Not aware different models may exist in different regions. Example the note gen1 has Korean and Chinese and US versions, each has a different model number.
XyRo7ec said:
please help me i did the same thing i have note 3 of n9005 UAE version of 32gb and i flashed a wrong pit file (i.e i flashed N900A pit file in N9005 ) and i tried many pit files using Nand erase all in odin but its not working for me as it just erased the partion in my phone but its not repartioning i mean not replacing any pit file
and odin just showing me error all the time and flashing FAIL
Click to expand...
Click to collapse
Here is the pit file for Note 3 SM-N9005 32gb varient.
HELP i think flashed the wrong .tar root file for my Galaxy J7 Pro
Hey man,
XDA doesn't trust me enough to let me make my own post and as I'm writing this I'm supposed to be studying for the 3 exams I will be having.
So,
I rooted my phone susing ODIN and the same root file a few months ago on Android 7.1 and it worked. I used it with TWRP recovery and everthing was fine.
Then the Android Oreo update was released for my phone, finally, and I hooked my phone up to my laptop and downloaded the firmware using Samsung's new Software called SmartThings.
Now I had stock ROM, but my device was recognized as rooted and modified, so couldn't use a few apps like Samsung Health and Pay. Then, without thinking, I put my phone in Download Mode and flashed the SAME .tar root file with ODIN, and now my phone won't boot to the pulsating Samsung logo and is stuck in the bootloader
wanted to say that Odin said PASS when .tar file was downloaded in the AP slot
In download mode,
Download Mode says:
Current Binary: Custom
System status: Official
FAP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x0303)
I have access to STOCK recovery and download mode, and I've already tried factory resetting phone and wiping cache. I don't want to take more rash steps without someone knowledgeable guiding me. and I cant find any other forum to post on because I'm not a high enough member.
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .

Calling all Developers!! (Posted here for a Reason)

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 :/

Stuck on getting Pit mapping

Hey guys i'm trying to fix a friend's i9300. He bought it from someone already in the current state.
It boots to the samsung logo but does nothing after that
Model: GT-I9300
FCC ID: A3LGTI9300A
SSN: I9300GSMH
I have tried to ODIN I9300ZNUBML1_I9300CHUBML1_CHU.zip onto it, but it says its missing pit partition, so i tried to load a pit onto it, I've tried GT-I9300_mx_20120329.pit but it gets stuck of getting pit mapping.
What am I doing wrong? I have no clue which country this phone is from either.
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Flash the firmware and pit at the same time, or try the rescue firmware in general thread.
If it still fails then emmc chip is blown, new motherboard required.
Sent from my GT-I9300 using Tapatalk
thanks guys i'll give that a shot and report back.
eric303 said:
thanks guys i'll give that a shot and report back.
Click to expand...
Click to collapse
if you enter on recovery mode and you get this:
http://forum.xda-developers.com/galaxy-s3/help/emmc-problem-t2722684
its the same of my phone, report back if you solved, mine dont flash pit files
k-semler said:
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Click to expand...
Click to collapse
I have a lot of PIT files, but with yours i can flash in heidmall, but return an error on 7%... i dont understand
sergio_f said:
I have a lot of PIT files, but with yours i can flash in heidmall, but return an error on 7%... i dont understand
Click to expand...
Click to collapse
Have you tried a different USB cable, and/or using a different USB port on your computer?
k-semler said:
Have you tried a different USB cable, and/or using a different USB port on your computer?
Click to expand...
Click to collapse
Yes, tried different computers also, i think it's the memory, it's corrupted, but it's funny because only with PIT file from this post i get something when try flash the stock Rom even with errors..

Tmobile firmware test build?

I was told the only way to get my phone to be restored via Odin is to flash a "test build" of a firmware because it is the only kind that will truly fully delete everything when flashing, anyone know if this is available anywhere?
Thanks
Not that I have ever seen.
Who told you that?
I would think you should be able to use the reset option in ODIN when flashing.
What problems are you having that flashing the stock file in Odin isn't fixing?
TheArtiszan said:
Not that I have ever seen.
Who told you that?
I would think you should be able to use the reset option in ODIN when flashing.
What problems are you having that flashing the stock file in Odin isn't fixing?
Click to expand...
Click to collapse
keithross39 told me that.
I tried all the conventional ways of odin flashing to no avail, I posted detailed info here.
link
I would do a little research into if repartition or erase nand might help.
I think pit file is in those files so you might be able to try repartition.
TheArtiszan said:
I would do a little research into if repartition or erase nand might help.
I think pit file is in those files so you might be able to try repartition.
Click to expand...
Click to collapse
I flashed pit several and checked erase nand in odin several times with no success
The not seandroid enforcing is cause of the custom recovery. I ran into something similar awhile back and it was the kernel.

Possible dead NAND SCH-I605?

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:

Categories

Resources