Related
I have (Had)a rooted SGH-174. I flashed cyanogenmod 10 using Rom Manager and got into a boot loop. I wiped the data and it booted up fine. The ONLY ISSUE is that my phone now says it is a SCH-R530M. Computer doesnt regonize it and I can't install any apps.
Oh my god what have I done???I've booted into recovery and reset but it is still showing a different phone model. Please help???:crying:
I rooted the phone after buying from Telus and installed cyanogen because to install jellybean ota release would have meant rerooting
stragf said:
I have (Had)a rooted SGH-174. I flashed cyanogenmod 10 using Rom Manager and got into a boot loop. I wiped the data and it booted up fine. The ONLY ISSUE is that my phone now says it is a SCH-R530M. Computer doesnt regonize it and I can't install any apps.
Oh my god what have I done???I've booted into recovery and reset but it is still showing a different phone model. Please help???:crying:
I rooted the phone after buying from Telus and installed cyanogen because to install jellybean ota release would have meant rerooting
Click to expand...
Click to collapse
Hi,
Have a look at this thread :
http://forum.xda-developers.com/showthread.php?t=1739426
Hope this helps.
It seems you installed CM10 for another model. You will need to hit the Development sections in these forums and look for the correct CM10, and you will need to do a clean install (full wipe). Please read the Guides in around the forum and you'll be good to go. Remember read first before flashing anything and always make a backup, good luck.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Thank you. I have a full back up but of course I can't reinstall because the backup doesn't recognize my phone so I can't download Titanium backup or ANYTHING from Google play. When I went into Rom Manager I hit the S3 button and it was a Metro PCS with the different model number.My factory reset sets it back to that model and not my SGH i747.
I feel like an idiot
\
You will need to flash a correct ROM via recovery or ODIN and by backup I meant nandroid backup, not titanium. Either way you should always backup both before flashing anything. Check this thread out it might share some light on how to do several things: http://forum.xda-developers.com/showthread.php?t=1725839. Always double and triple check that the ROM, kernel, modem, etc., you are flashing works with you model and carrier.
Need More assistance!? Please
jgaf said:
It seems you installed CM10 for another model. You will need to hit the Development sections in these forums and look for the correct CM10, and you will need to do a clean install (full wipe). Please read the Guides in around the forum and you'll be good to go. Remember read first before flashing anything and always make a backup, good luck.
Click to expand...
Click to collapse
:crying:
I have a rooted SGH-i747 S3. The stock release of Jellybean came out today, and instead, I used Rom Manager to flash CMOD 10. Unfortunately, the rom I flashed was for a METRO PCS model SCH R530M.
I downloaded the proper stable Mod for my SGH and installed it onto my phone, but now the install aborts. The model number of my phone shows as the SCH and not the SGH. I have spent six hours and tried virtually every thing I can think of and can't get it back to original version. Can some one please heip????
Thank you.
Use this method
stragf said:
:crying:
I have a rooted SGH-i747 S3. The stock release of Jellybean came out today, and instead, I used Rom Manager to flash CMOD 10. Unfortunately, the rom I flashed was for a METRO PCS model SCH R530M.
I downloaded the proper stable Mod for my SGH and installed it onto my phone, but now the install aborts. The model number of my phone shows as the SCH and not the SGH. I have spent six hours and tried virtually every thing I can think of and can't get it back to original version. Can some one please heip????
Thank you.
Click to expand...
Click to collapse
<<<<I just checked your threads and you said you're phone is a SGH-I747M <--- There's an "M", as in monkey, which isn't an AT&T model Galaxy S3. You need to check your phone by going to your settings, click About device(phone), and read Model number(Samsung-SGH-I747 is mine) Do this before you flash ANYTHING else or you could permanently brick your phone. I noticed you said that your phone isn't showing the original Model number so check here: pull out battery, read the label and it will say the Model number.
Here is a link to various carrier roms: http://forum.xda-developers.com/showthread.php?t=1739426
Okay I'm going to give you a link to the REAL AT&T Galaxy S3 SGH-I747 Jelly Bean ROM, which is rooted, which you need to download and then extract onto the desktop. After extracting the One-Click Odin program open it (((EDIT))) Go to Recovery mode by holding (+) plus volume button + Home + Power and then if you have a custom recovery make sure you wipe data/factory reset, wipe cache, format system, format data, wipe dalvik cache. If you don't have a custom recovery do a factory reset and wipe the cache. (((EDIT))) and then put your phone into "Download"(Odin) mode by holding the (-)minus volume button + Home button + Power button until it says "Warning a custom OS can cause damage etc" and then press (+) plus volume button and then plug in the phone, using the USB cable that came with your phone, to your computer.
It will say 0:[COMx] where x is a random number. Press START and then let it finish until it says "PASS" in green. If it says any errors and aborts the program refer back to here and edit your thread with the new information.
If this works PLEASE hit thanks...my wife is behind me telling me to go to bed with her and instead I'm here typing because I care about your welfare so a thanks isn't too much to ask for.
I hope it works. Here's the link: http://forum.xda-developers.com/showthread.php?t=2031840
something is happening! Stay tuned...Late in Edmonton too
Update while this is running. It definitely is the SGH-i747M. When I flashed the ROM, I checked the GalaxyS3, but after it installed The model came up as the SH R530M. I maintain hope though as in download mode where we are now in the top corner (very tiny print) it is showing as SGH-i747M. when I plug it in though the model is showing the SHR 530 from Metro PCS. I <about phone> it doesn't show Telus or anything.
Oh..Just finished:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
oh oh...Now stuck on samsung boot screen....
stragf said:
Update while this is running. It definitely is the SGH-i747M. When I flashed the ROM, I checked the GalaxyS3, but after it installed The model came up as the SH R530M. I maintain hope though as in download mode where we are now in the top corner (very tiny print) it is showing as SGH-i747M. when I plug it in though the model is showing the SHR 530 from Metro PCS. I <about phone> it doesn't show Telus or anything.
Oh..Just finished:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
oh oh...Now stuck on samsung boot screen....
Click to expand...
Click to collapse
What firmware did you flash? Did you check behind your battery for the Model number? Don't be hasty to flash or you could brick.
Give it time, has to rebuild cache.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It did show pass but stuck on Samsung logo on reboot
Grant
stragf said:
It did show pass but stuck on Samsung logo on reboot
Grant
Click to expand...
Click to collapse
Yeah if it is just sitting on the Samsung Logo more than likely it is rebuilding the dalvik cache and you NEED to leave it alone so it can finish. It looks like your problem is fixed.
The Samsung logo keeps flashing from white to blue, etc. I will just let it go all night. How long can it take? I am quite apprehensive, but you have gotten me way further than anything else. thank you so much...
stragf said:
The Samsung logo keeps flashing from white to blue, etc. I will just let it go all night. How long can it take? I am quite apprehensive, but you have gotten me way further than anything else. thank you so much...
Click to expand...
Click to collapse
The dalvik-cache building process can take up to 10 minutes so be patient and calm.
I have to ask, is the logo swirling over and over? or is it pulsing in place like a neon light? The swirling means that the Samsung boot logo is cycling and is in a "boot loop" and firmware needs to be flashed to resolve the issue. If it is pulsing in place it is building the dalvik-cache and it needs to be left alone. Nevertheless you need to be sure of the Model number or you could brick by flashing the rom from another carrier. Behind the battery is one place to check, and the internet is the second. Whatever carrier you're on type this: (carrier name) + Samsung Galaxy S3 Model number then press search and then get back with me.
Sounds like you need to boot into recovery and factory reset. If it booted up and is stuck there thats most likely the problem. BTW- A good way to tell if it is building the cache or stuck is the keys at the bottom. If they dont light up within 5 mins then its not gonna boot and needs wiped
It is static on the screen with Samsung "pulsing" between whit and a light bluish tinge to it. The Logo is NOT swirling, just the word Samsung pulsing white/blue, white/blue, and on and on and......
stragf said:
It is static on the screen with Samsung "pulsing" between whit and a light bluish tinge to it. The Logo is NOT swirling, just the word Samsung pulsing white/blue, white/blue, and on and on and......
Click to expand...
Click to collapse
Well it seems to be taking a while so go ahead and try to access Recovery Mode by holding: (+) plus volume button + Home button + Power button until the phone reboots and you see blue text in the top left corner that says "Recovery booting..." and then let go.
If it worked tell me if you have a custom recovery like ClockworkMod or TWRP, etc to flash a rom. If you're on stock try to do a factory data/reset and wipe cache then reboot and wait.
Nabbu said:
The dalvik-cache building process can take up to 10 minutes so be patient and calm.
I have to ask, is the logo swirling over and over? or is it pulsing in place like a neon light? The swirling means that the Samsung boot logo is cycling and is in a "boot loop" and firmware needs to be flashed to resolve the issue. If it is pulsing in place it is building the dalvik-cache and it needs to be left alone. Nevertheless you need to be sure of the Model number or you could brick by flashing the rom from another carrier. Behind the battery is one place to check, and the internet is the second. Whatever carrier you're on type this: (carrier name) + Samsung Galaxy S3 Model number then press search and then get back with me.
Click to expand...
Click to collapse
stragf said:
It is static on the screen with Samsung "pulsing" between whit and a light bluish tinge to it. The Logo is NOT swirling, just the word Samsung pulsing white/blue, white/blue, and on and on and......
Click to expand...
Click to collapse
factory reset. unless you know how to use adb then i have a few commands you can enter
Hi every one any help will be greatlly apreciated. First what happened we'll shut down and stuck at Galaxy Note II Screen and restarting itself until it stops frozen at the Galaxy Note II Screen. Was working fine for a couple months after my last flash froze some times but battery pull fixed it before. Now I can not get into CWM Recovery So I tried flashing factory rom with Odin I get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried mutiple times tried F.Reset Time checked. Any Ideas guy's. wife's phone have to get it working if you know what I meen. Thank's for any help. Hope the nands not corupt. Had a International S3 I9300 with that problem. Would like to save this and not shell out the money for a MBoard.
kennethcolman said:
Hi every one any help will be greatlly apreciated. First what happened we'll shut down and stuck at Galaxy Note II Screen and restarting itself until it stops frozen at the Galaxy Note II Screen. Was working fine for a couple months after my last flash froze some times but battery pull fixed it before. Now I can not get into CWM Recovery So I tried flashing factory rom with Odin I get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried mutiple times tried F.Reset Time checked. Any Ideas guy's. wife's phone have to get it working if you know what I meen. Thank's for any help. Hope the nands not corupt. Had a International S3 I9300 with that problem. Would like to save this and not shell out the money for a MBoard.
Click to expand...
Click to collapse
in download mode does it say n7100 in product code?
what you need to do if you will be using a pit file is use a factory emergency rom. sadly most the links are down.
i have a MJ9 Emergency rom from india which is 4.3. i will try upload it when i get home in 8 to 9 hours to mega.nz if that is ok.
what i have done is replaced the MJ9 bootloader with MJ5 in that firmware.
if you can't wait, you need a firmware that has BL,AP, CP and CSC all split so you can put them in all the boxes. if i get a chance at lunch i might try find a pre uploaded link for you. just remain calm and don't start flashing stuff randomly
I have searched and searched online and cant seem to nail down a solution to this issue.
My Download Screen displays:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
I hope that my Note II is not bricked. I have tried 100's of times with stock, custom recovery's, CWM, I get some kind of error no matter what I do.
my Sammy just doesn't want to work with me.
I hope that we can put together a solution.
El_Nino9 said:
in download mode does it say n7100 in product code?
what you need to do if you will be using a pit file is use a factory emergency rom. sadly most the links are down.
i have a MJ9 Emergency rom from india which is 4.3. i will try upload it when i get home in 8 to 9 hours to mega.nz if that is ok.
what i have done is replaced the MJ9 bootloader with MJ5 in that firmware.
if you can't wait, you need a firmware that has BL,AP, CP and CSC all split so you can put them in all the boxes. if i get a chance at lunch i might try find a pre uploaded link for you. just remain calm and don't start flashing stuff randomly
Click to expand...
Click to collapse
Thanks I am very patient. Oh and yes it says GT-N7100 in product code under warranty bit: 1 binary:yes status: custom under binary download: Yes (6 counts)
Teckin said:
I have searched and searched online and cant seem to nail down a solution to this issue.
My Download Screen displays:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
I hope that my Note II is not bricked. I have tried 100's of times with stock, custom recovery's, CWM, I get some kind of error no matter what I do.
my Sammy just doesn't want to work with me.
I hope that we can put together a solution.
Click to expand...
Click to collapse
kennethcolman said:
Thanks I am very patient. Oh and yes it says GT-N7100 in product code under warranty bit: 1 binary:yes status: custom under binary download: Yes (6 counts)
Click to expand...
Click to collapse
to both you guys:- what bootloader are you on/were you on? Kenneth I think you've taken your bootloader above MJ5 as you say your warranty bit is 1. you can't downgrade bootloader at all! flashing the MJ5 bootloader with the file I've uploaded won't help. you will only get FAIL in odin. you need to tell me which bootloader you've been to so I can try arrange a package for you if I can.
Teckin, I need you to answer the above too
El_Nino9 said:
to both you guys:- what bootloader are you on/were you on? Kenneth I think you've taken your bootloader above MJ5 as you say your warranty bit is 1. you can't downgrade bootloader at all! flashing the MJ5 bootloader with the file I've uploaded won't help. you will only get FAIL in odin. you need to tell me which bootloader you've been to so I can try arrange a package for you if I can.
Teckin, I need you to answer the above too
Click to expand...
Click to collapse
First off thanks for your help. Here's the deal I had this installed: DN3_v3.2_by_E-Team_(Vegeta_Edition) Thats a Jelly Bean for the past 2 month's so what ever bootloader works with that is what it had. I was tying to flash an OEM KK: BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar I figured we'll since I have this problem let me flash DN5 but in oder to do this I would have to upgrade my bootloader KK that's why I flashed this BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar Now I say again The problem was not a result of flashing. My wife was using Skype while on the DN3 and it froze she pushed the wake button once or twice it went black and then gave the reboot logo that I mentioned above. So then I proceeded to try to flash to fix and upgrade in the process. And it gave me the odin results above No PIT Partition
https://mega.co.nz/#!5ZlXFbrR!GoNuuuDwKrp3QG8X7p4eV5v5ViOZR51kXgTtcptkGBo
here's the file I've uploaded.
you may well still have taken the device to MJ5 only.
flash all files in here at the same time using odin. let me know how you get on?
I find this method works best for me:
phone is off, load odin, load all the files in, pit, bl, ap, cp, csc no messing around with any ticking other boxes. AP will probably cuase odin to crash for a few seconds when loading just let it do its thing.
then put phone into download mode( I put battery in hold down, menu and power) if the drivers have been installed using that port previous it finds the device in odin instantly and i start the process.
If your flash is successful but doesn't load rom, your data might need to be wiped. i mean if your device is has been stuck on a Samsung screen for 10 minutes after odin said everythings fine don't panic. take battery out, go into recovery (volume up+menu+power) and then wipe data. it should now load the rom.
El_Nino9 said:
https://mega.co.nz/#!5ZlXFbrR!GoNuuuDwKrp3QG8X7p4eV5v5ViOZR51kXgTtcptkGBo
here's the file I've uploaded.
you may well still have taken the device to MJ5 only.
flash all files in here at the same time using odin. let me know how you get on?
I find this method works best for me:
phone is off, load odin, load all the files in, pit, bl, ap, cp, csc no messing around with any ticking other boxes. AP will probably cuase odin to crash for a few seconds when loading just let it do its thing.
then put phone into download mode( I put battery in hold down, menu and power) if the drivers have been installed using that port previous it finds the device in odin instantly and i start the process.
If your flash is successful but doesn't load rom, your data might need to be wiped. i mean if your device is has been stuck on a Samsung screen for 10 minutes after odin said everythings fine don't panic. take battery out, go into recovery (volume up+menu+power) and then wipe data. it should now load the rom.
Click to expand...
Click to collapse
Thanks but no prize.
Download and tried it Failed
Odin Said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N7100DDEMJ9_REV08_CL1423182.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ODD_N7100ODDEMK1_2099172_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N7100XXUEMK4_2099172_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you think I should check erase nand I won't do it till some body who I trust tells me I should don't want things worse.
Ok so here is the deal on my GT-N7100. I bought it this way, but have not been able to flash it back to stock to start from scratch. so to answer your question, I have NO CLUE.
Seller told me that It would only boot into dl screen with usb...So I thought hmm I can re-flash it with stock software and move forward from that point.
Thank you all for the suggestions!
Teckin said:
Ok so here is the deal on my GT-N7100. I bought it this way, but have not been able to flash it back to stock to start from scratch. so to answer your question, I have NO CLUE.
Seller told me that It would only boot into dl screen with usb...So I thought hmm I can re-flash it with stock software and move forward from that point.
Thank you all for the suggestions!
Click to expand...
Click to collapse
you can try the above files if you want.
kennethcolman said:
Thanks but no prize.
Download and tried it Failed
Odin Said this:
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you think I should check erase nand I won't do it till some body who I trust tells me I should don't want things worse.
Click to expand...
Click to collapse
don't click erase.
mate i think you've flashed a new bootloader than MJ5 hence why it fails at that stage.
i am checking to see if i can get hold of a kitkat rom for you that's split to so you can flash pit.
i have never tried it with kitkat mate. plus i don't use odin to flash anymore. i use my octoplus box so files are in a .oct format
Sorry for delay in replying.
again i think youhave a newer bootlaoder if it shows warranty bit.
El_Nino9 said:
you can try the above files if you want.
don't click erase.
mate i think you've flashed a new bootloader than MJ5 hence why it fails at that stage.
i am checking to see if i can get hold of a kitkat rom for you that's split to so you can flash pit.
i have never tried it with kitkat mate. plus i don't use odin to flash anymore. i use my octoplus box so files are in a .oct format
Sorry for delay in replying.
again i think youhave a newer bootlaoder if it shows warranty bit.
Click to expand...
Click to collapse
I have a buddy who has a box would that be the safest rout?
kennethcolman said:
I have a buddy who has a box would that be the safest rout?
Click to expand...
Click to collapse
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5
in ap only without pit ofcourse.
does odin allow you to do this?
El_Nino9 said:
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5
in ap only without pit ofcourse.
does odin allow you to do this?
Click to expand...
Click to collapse
I believe I tried that same thing happened. Fail no pit partition
kennethcolman said:
I believe I tried that same thing happened. Fail no pit partition
Click to expand...
Click to collapse
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
I tried that file as well. Still same issue. I did talk with a guy that does jtag services and he advised me that it's either the eMMC or motherboard issue. He wants to sell me a eMMC Flash service for $75.00. What do you guys think I should do....
---------- Post added at 10:32 PM ---------- Previous post was at 09:51 PM ----------
El_Nino9 said:
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash "goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5"
in ap only without pit ofcourse.
does odin allow you to do this?
Click to expand...
Click to collapse
I will try this as well..
Did try that last file as well still no go...
Thank you all for your efforts.
El_Nino9 said:
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
Click to expand...
Click to collapse
We're you able to find the KK files for the N7100 odin flashable? and a little off topic here but I have been dabbling with the idea of unlocking cells. I live in the Dominican Republic and cells here are mostly GSM wondering if you we're to purchase 3 box's to do the widest range of phones which 3 would you buy and from where? Sorry everybody for the off topic.
El_Nino9 said:
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
Click to expand...
Click to collapse
I beleve I figured out why the Rescue Firmware you sent me didn't work. What I need is Android 4.3 MK9 Bootloader and Do you have this and if so can you upload it to me mega would be fine. Thanks Just like the other just MK9 Based with pit and etc. Thanks for all your earlier help I am pretty sure this wil work.
kennethcolman said:
I beleve I figured out why the Rescue Firmware you sent me didn't work. What I need is Android 4.3 MK9 Bootloader and Do you have this and if so can you upload it to me mega would be fine. Thanks Just like the other just MK9 Based with pit and etc. Thanks for all your earlier help I am pretty sure this wil work.
Click to expand...
Click to collapse
sorry for the lack of activity. deadlines for work have kept me away from here.
i have a MK4. i will send it to you now. i will hunt for MK9 in the mean time if MK4 fails. plus i'll answer your other question about boxes in few minutes.
Teckin said:
I tried that file as well. Still same issue. I did talk with a guy that does jtag services and he advised me that it's either the eMMC or motherboard issue. He wants to sell me a eMMC Flash service for $75.00. What do you guys think I should do....
---------- Post added at 10:32 PM ---------- Previous post was at 09:51 PM ----------
I will try this as well..
Click to expand...
Click to collapse
that's note a bad price for the service i'd say. they have to use a rework station to pull the emmc off and then reball the new one on. however i'd suggest you try flashing a new firmware on first. i will try to dig a new firmware out for you to try but if they keep failing then the only route is emmc and make sure they load a firmware below 4.3 knox free if you want custom roms again
Hi there,
I hope that somebody can help me.
My Galaxy Note 2 stopped working all of the sudden. It was running without any problems when it suddenly restarted without a reason. Since then it does not boot anymore, any attempt ends on the screen where it shows "Samsung Galaxy Note II GT-N7100". The only chance to switch it off after this is removing the battery. The phone was not rooted, it was running stock Android 4.3 before the crash.
Pressing Home and Volume-up during power-on doesn't show the menu so I'm not able to do a factory reset. Instead it shows the android robot and the text "Downloading... Do not turn off target!!"
I was hoping to have a chance to get a copy of the data of the internal memory so I followed the instructions to install the "Heimdall suite". When I start the phone in download mode (or what's left of it) I get the following responses to Heimdall commands:
Code:
C:\Note-2\Heimdall Suite>heimdall detect
Device detected
Code:
C:\Note-2\Heimdall Suite>heimdall print-pit
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
To make sure my setup is correct I've tested it with with a working Galaxy S3 which doesn't give me the error messages after the second command.
Is there any way to get access to the data that is stored on the internal memory?
The phone is still under warranty so if there is a way to get access I'd prefer one that doesn't void the warranty...
Thank you very much for any hint!
Regards -- Markus
Battery buy a new one... I had the same prob awhile back Connected to the charger it would fully boot but as soon as you pull the cable it will power off then be stuck at Samsung logo till you pull the battery.
I borrowed a battery to test and sure enough and then ordered one.
mjakobi said:
Hi there,
I hope that somebody can help me.
My Galaxy Note 2 stopped working all of the sudden. It was running without any problems when it suddenly restarted without a reason. Since then it does not boot anymore, any attempt ends on the screen where it shows "Samsung Galaxy Note II GT-N7100". The only chance to switch it off after this is removing the battery. The phone was not rooted, it was running stock Android 4.3 before the crash.
Pressing Home and Volume-up during power-on doesn't show the menu so I'm not able to do a factory reset. Instead it shows the android robot and the text "Downloading... Do not turn off target!!"
I was hoping to have a chance to get a copy of the data of the internal memory so I followed the instructions to install the "Heimdall suite". When I start the phone in download mode (or what's left of it) I get the following responses to Heimdall commands:
Code:
C:\Note-2\Heimdall Suite>heimdall detect
Device detected
Code:
C:\Note-2\Heimdall Suite>heimdall print-pit
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
To make sure my setup is correct I've tested it with with a working Galaxy S3 which doesn't give me the error messages after the second command.
Is there any way to get access to the data that is stored on the internal memory?
The phone is still under warranty so if there is a way to get access I'd prefer one that doesn't void the warranty...
Thank you very much for any hint!
Regards -- Markus
Click to expand...
Click to collapse
Joshua79 said:
Battery buy a new one... I had the same prob awhile back Connected to the charger it would fully boot but as soon as you pull the cable it will power off then be stuck at Samsung logo till you pull the battery.
Click to expand...
Click to collapse
Hi Joshua79,
thanks for your reply. The phone doesn't even if it's connected to the charger...
Any other hints?
Still looking for a way to access the internal storage of the phone...
Cheers -- Markus
hi,
i also have similar problem with my N7100.
phone stuck in Samsung GT-N7100 logo.
unable to go to Recovery Mode, but download mode OK.
tried to flash Stock Firmware with Odin, but failed
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
tried to flash PhilZ Touch 6 Recovery, but failed. :crying:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried swap battery with friends, friends phone work well with my battery, but mine still the same even with my friends battery.
from the log, it seem like Odin unable to write. anyone know whats the problem?
tried looking for help from [GUIDE][Troubleshoot a failed ODIN flash] and similiar problem also reported here, but seem like no solution :crying:
please help, I'm too broke to get new phone :crying:
mjakobi said:
Hi there,
I hope that somebody can help me.
My Galaxy Note 2 stopped working all of the sudden. It was running without any problems when it suddenly restarted without a reason. Since then it does not boot anymore, any attempt ends on the screen where it shows "Samsung Galaxy Note II GT-N7100". The only chance to switch it off after this is removing the battery. The phone was not rooted, it was running stock Android 4.3 before the crash.
Pressing Home and Volume-up during power-on doesn't show the menu so I'm not able to do a factory reset. Instead it shows the android robot and the text "Downloading... Do not turn off target!!"
I was hoping to have a chance to get a copy of the data of the internal memory so I followed the instructions to install the "Heimdall suite". When I start the phone in download mode (or what's left of it) I get the following responses to Heimdall commands:
Code:
C:\Note-2\Heimdall Suite>heimdall detect
Device detected
Code:
C:\Note-2\Heimdall Suite>heimdall print-pit
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
To make sure my setup is correct I've tested it with with a working Galaxy S3 which doesn't give me the error messages after the second command.
Is there any way to get access to the data that is stored on the internal memory?
The phone is still under warranty so if there is a way to get access I'd prefer one that doesn't void the warranty...
Thank you very much for any hint!
Regards -- Markus
Click to expand...
Click to collapse
It's been a long time since I dealt with a Note 2 (since mine broke), but I'll try to help.
That sounds like a corrupted .pit file. You'll have to research more on your own, but I think you'll have to flash a new .pit file, then flash the stock ROM.
P.S. If you have a warranty, why don't you use it? lol.
thongkh said:
hi,
i also have similar problem with my N7100.
phone stuck in Samsung GT-N7100 logo.
unable to go to Recovery Mode, but download mode OK.
tried to flash Stock Firmware with Odin, but failed
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
tried to flash PhilZ Touch 6 Recovery, but failed. :crying:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried swap battery with friends, friends phone work well with my battery, but mine still the same even with my friends battery.
from the log, it seem like Odin unable to write. anyone know whats the problem?
tried looking for help from [GUIDE][Troubleshoot a failed ODIN flash] and similiar problem also reported here, but seem like no solution :crying:
please help, I'm too broke to get new phone :crying:
Click to expand...
Click to collapse
Seems like a similar issue as the guy above. Your download isn't corrupted based on the successful MD5 check. I'll try and research more into your issue.
P.S. You rooted? Any modifications?
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Irwenzhao said:
It's been a long time since I dealt with a Note 2 (since mine broke), but I'll try to help.
That sounds like a corrupted .pit file. You'll have to research more on your own, but I think you'll have to flash a new .pit file, then flash the stock ROM.
P.S. If you have a warranty, why don't you use it? lol.
Click to expand...
Click to collapse
Hello Irwenzhao,
thanks for replying.
I haven't rooted my phone yet and so I'm not familiar with flashing, so please excuse my questions. I've read pretty much about flashing in the last few days and (as far as I've understood) flashing things to my phone will erase my data from the phone.
My problem is that I've accidentally stored data on the internal memory instead of the external SD-card . SInce I didn't realize that before the crash there's some stuff on the phone I'd like to have back if this is possible.
Of course I will use the warranty to have the phone repaired but my data will most likely be gone from the phone when I get it back.
That's the reason why I'm trying to find out if there's a way to access the internal memory of my phone before having it repaired.
Cheers -- Markus
mjakobi said:
Hello Irwenzhao,
thanks for replying.
I haven't rooted my phone yet and so I'm not familiar with flashing, so please excuse my questions. I've read pretty much about flashing in the last few days and (as far as I've understood) flashing things to my phone will erase my data from the phone.
My problem is that I've accidentally stored data on the internal memory instead of the external SD-card . SInce I didn't realize that before the crash there's some stuff on the phone I'd like to have back if this is possible.
Of course I will use the warranty to have the phone repaired but my data will most likely be gone from the phone when I get it back.
That's the reason why I'm trying to find out if there's a way to access the internal memory of my phone before having it repaired.
Cheers -- Markus
Click to expand...
Click to collapse
Your data should be (probably) gone. I highly doubt the possibility that a method to access your internal storage exists. It could be just a bad motherboard. Just let the Samsung Service Centre folks do their job, nothing much you can do.
P.S. your files may already be gone. (unfortunately)
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Irwenzhao said:
Your data should be (probably) gone. I highly doubt the possibility that a method to access your internal storage exists. It could be just a bad motherboard. Just let the Samsung Service Centre folks do their job, nothing much you can do.
P.S. your files may already be gone. (unfortunately)
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Click to expand...
Click to collapse
I don't need my data, and my phone was not rooted. Stock kitkat firmware.
U mention is motherboard failure? My phone no longer got warranty cover. Pls tell me it's not hardware failure
thongkh said:
I don't need my data, and my phone was not rooted. Stock kitkat firmware.
U mention is motherboard failure? My phone no longer got warranty cover. Pls tell me it's not hardware failure
Click to expand...
Click to collapse
Have you tried updating via Kies?
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Irwenzhao said:
Have you tried updating via Kies?
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Click to expand...
Click to collapse
thanks for the reply.
tried with kies (v2.6.3.14074_11), its said device not responding :crying:
anymore suggestion?
thongkh said:
thanks for the reply.
tried with kies (v2.6.3.14074_11), its said device not responding :crying:
anymore suggestion?
Click to expand...
Click to collapse
What was your Android version before this happened?
Sent from a Nameless fellow licking Lollipop.
Singaporean Oppo Find 7a
Click that "Thanks" button if I helped you!
Irwenzhao said:
What was your Android version before this happened?
Sent from a Nameless fellow licking Lollipop.
Singaporean Oppo Find 7a
Click that "Thanks" button if I helped you!
Click to expand...
Click to collapse
didnt really checked, but should be kidkat
thongkh said:
didnt really checked, but should be kidkat
Click to expand...
Click to collapse
Not sure if you can flash a .pit file with Knox, but you can try. Search it up on Google.
Sent from a Nameless fellow licking Lollipop.
Singaporean Oppo Find 7a
Click that "Thanks" button if I helped you!
there is a pit file here for N7100 16gb
http://forum.xda-developers.com/showthread.php?t=1927983
extract it and flash in odin. that's the file i used when i messed up with my partition and my phone doesn't boot.
this is the exact problem we had last month with our note 2, working fine then bang.
I tried everything but was unable to revive the machine.
Samsung repaired the phone under warranty even though it was over two years old, a new mainboard was fitted as the emmc chip had failed.
Give them a call you have nothing to lose at this point, our phone was gone for a total of 3 working days.
Unlike the other threads I've read here so far, I wasn't upgrading or downgrading anything on my phone. Last night, I was playing Scrabble (lol) and the phone blacked out and now won't power on. I've tried booting to Download mode and can't even do that. The battery was running low at the time, but that's normal for late at night. I believe I had about 9% battery.
The symptoms of my phone are now:
When I have the battery installed, plugging in the charger doesn't seem to do anything (no charging light).
When I remove the battery, plugging in the charger lights the LED as red for 90 seconds.
Plugging the phone into my computer via USB (without battery), the phone connects (as a device for which I do not have drivers) for 90 seconds (same duration as the red light) and then disconnects.
If I hold the power button in for 12-13 seconds (without battery with charger connected), the red light will go out. As soon as I release the power button, the red light comes back on and the 90-second timer restarts. If I have the phone connected to my computer while trying this, the phone disconnects when the red light goes out and reconnects to the computer (as the same device from above) when I release the power button.
Overnight, I left the phone (with battery) plugged in hoping to fully charge the battery and that would somehow miraculously bring my phone back to life this morning -- it did not. Unknown if the battery is fully charged now or not.
Any suggestions on what I might try next?
See if this helps:
http://forum.xda-developers.com/showthread.php?t=2549068
Lithium ion batteries are at their least stable when they're low on charge like you indicated yours was. How old is your battery? Does it have any bulges you can see or feel? If you put in on a table and flick it on the corner does it spin around? The spin test is by no means conclusive that a battery won't function, but it is indicative of some damage. My original Samsung battery spins like a top, but it still holds a charge and makes an ok backup in a pinch. If you know someone else with a working S3 try their battery in your phone. Otherwise, if there is a Batteries Plus or somewhere like that convenient, pop in and try a replacement. Most replacement batteries I've bought for phones or cameras usually come partially charged so you can probably test it right in store; the guys in the stores might know a thing or two as well as a lot of battery shops have started replacing phone screens and batteries that aren't as readily removable like that other variety of smartphone.
The debrick threads suggested above are a good idea too, but like you pointed out, those are usually for people who tried to downgrade our wonderful secure bootloaders.
If none of that pans out, a repair shop might be able to jtag it back to life.
Good luck.
Update
I was reading this unbrick thread and downloaded this debrick img for I747U. I applied the debrick img to a 32GB microSD card and I got the phone to at least do something. What I see is:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
WRITE 159488 SECTORS..
[COLOR="Red"]FLASH WRITE FAILURE
ODIN MODE[/COLOR]
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE[/COLOR]
[COLOR="Red"]Warranty Bit: 1[/COLOR]
[COLOR="Silver"]BOOTLOADER RP SWREV: 2[/COLOR]
I can now see the phone in ODIN when I connect with USB.
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
audit13 said:
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
Click to expand...
Click to collapse
I'm hoping to reflash the stock rooted MJB so I don't lose everything that I had on the phone.
Hossy923 said:
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Click to expand...
Click to collapse
When I try and flash with the file above with ODIN v3.07, I get:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
At the same time, I get two additional lines on the screen of the phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)
ODIN : flash read failure[/COLOR]
Looking inside the .tar.md5, I do see a PIT file in there.
---
If I flash with ODIN v1.85, I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)[/COLOR]
Flashing via Odin is almost guaranteed to require a full wipe to boot.
audit13 said:
Flashing via Odin is almost guaranteed to require a full wipe to boot.
Click to expand...
Click to collapse
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Hossy923 said:
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Click to expand...
Click to collapse
Re-partition is unchecked?
I get the same error in Odin3 with Re-Partition checked and unchecked.
You used a debrick image for the i747u? Did you try an i747 de-brick image?
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Hossy923 said:
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Click to expand...
Click to collapse
I've come to believe now that my internal SD card has died. All attempts I've made to flash, whether with ODIN or Miracle Thunder have failed. I get a bunch of errors on the screen talking about errors reading or writing firmware/flash. I even tried doing a nand erase with ODIN and that failed. Unless someone has a better idea, I believe the device has hardware damage.
Hi, I've searched hi and low for help, but can't find anything that seem to apply to my phone or case. I have a Canadian Mobilicity S3 model SGH-T999V that just bricked itself. Everything is official other than I unlocked it to switch to Wind: Binary Count = 0.
The Story: Last week (Tuesday Sep 22nd 2015) The phone restarted a few times for no apparent reason, then the next day errors about missing files started to pop up to the point that I had to reset the phone to be able to use it. Start fresh all good for a week, then one restart yesterday (Sep 30) and this morning I have a screen that says: "Device Memory Damaged - the data partition has been corrupted.you need to reset your device to factory defaults.this will erase all your date. (reset device button)" I press the button nothing happens, so I take out the battery, leave it while at work, then try again: same thing - I try to reboot into recovery but fail: I get a down android with an open belly cover and a red triangle picture for a bit and the phone reboots back to the damaged memory screen. I can get into the download mode, but Odin doesn't see the phone.
Any advice on how to proceed from here would be greatly appreciated.
I've used Odin before on my Nexus S, but that was many moons ago, it's dead now...
Thanks in advance.
Can you get into download mode? If you can, yet flashing the stock ROM from sammobile.com and flash it using Odin.
Thanks for the reply.
Odin doesn't see the phone and I don't remember exactly how to use it either, but I know it's very model specific, as to files and ROMs to download and install, hence the advise seeking. I guess I'm hoping someone in the know can tell me "follow the instructions for such [more popular] model #, that will work on the 999"...
The T999v is a very popular model in Canada as it was used by Wind and Videotron.
Are you able to boot the phone into download mode? The Samsung drivers are installed? Are you using a Win7 machine?
Yes it boots into Download mode but not into recovery. I have Kies installed along with the drivers, could reinstall that just in case. Running Windows 10 Pro Preview, in the process of upgrading to the final release.
I recommend grabbing the latest firmware from sammobile.com for the phone and flash it in Odin 3.07 with the phone in download mode. I would not bother with Kies.
I've updated my build of Windows 10, that may have been one of my problems, now Odin reacts to the phone but fails:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNH2_T999VYVLFNH2_T999VVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says in red: "Secure Check Fail: aboot
So much for that! guess it's fried at the hardware level.
I'm thinking you are suffering from a hardware failure as stated by the message you mentioned before. It has happened to others and I can't recall anyone having much success in restoring functionality.
If you want to try again though, uninstall kies from your computer as it interferes with Odin. There is also a newer version of Odin, but I doubt that would make much difference on the S3.
If you are unable to get it working again and want a relatively cheap fix, search ebay for a used motherboard or a device that has a broken screen but otherwise works. Then swap out the board.
Sent from my SGH-T999 using Tapatalk
The update is failing because the ROM you are flashing has a bootloader that is older than the version currently installed on the phone as verified by the following stop error in Odin:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
I have a feeling DocHoliday77 is probably right, I've bought a new phone from my provider for 9$ (Alcatel onetouch Pop D3) and posted a wanted ad for broken S3 ... not ready to completely give up on the S3 just yet, but neither do I have high hopes.
Getting rid of Kies
The firmware is the most recent for the SGH-T999V on sammobile.com - I can try without the V maybe
Only T999V firmware will work on the T999V.
If you are selling it and it has a good working display you should be able to get a decent amount for it still. Not sure how much they are going for these days but it's always been the most expensive and in demand part for the device.