First off, I would like to say thank you for any advice on fixing my Galaxy Player 5. I have looked through multiple posts to attempt to unbrick my SGP and while following the directions, I still could not fix it. I am currently have the stock kernel installed and I can get into recovery mode and download mode but I get stuck in a bootloop otherwise. I can even get Odin3 v1.83 to recognize it. I currently have the .PIT file downloaded and I have the stock ROM downloaded and I put them in the PIT section and PDA section respectively. I have the following options checked: Re-Partition, Auto Reboot, F. Reset Time, and Phone Bootloader Update.
The message output is:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_G70XXKPH_CL1013658_REV01_user_low_ship_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
Every time I attempt this, it will get stuck on SetupConnection.. forever (at least 30 min until I exit it)
It is important to note that I have the Samsung USB drivers installed and I do not have Samsung KIES installed.
I would be glad to provide more information if needed such as what software I installed and which threads I looked at.
My question is, what can I do to fix my device.
thewrongstuff said:
First off, I would like to say thank you for any advice on fixing my Galaxy Player 5. I have looked through multiple posts to attempt to unbrick my SGP and while following the directions, I still could not fix it. I am currently have the stock kernel installed and I can get into recovery mode and download mode but I get stuck in a bootloop otherwise. I can even get Odin3 v1.83 to recognize it. I currently have the .PIT file downloaded and I have the stock ROM downloaded and I put them in the PIT section and PDA section respectively. I have the following options checked: Re-Partition, Auto Reboot, F. Reset Time, and Phone Bootloader Update.
The message output is:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_G70XXKPH_CL1013658_REV01_user_low_ship_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
Every time I attempt this, it will get stuck on SetupConnection.. forever (at least 30 min until I exit it)
It is important to note that I have the Samsung USB drivers installed and I do not have Samsung KIES installed.
I would be glad to provide more information if needed such as what software I installed and which threads I looked at.
My question is, what can I do to fix my device.
Click to expand...
Click to collapse
what rom did you have on there before?
have you tried wiping data in recovery and booting up?
Check out this video I made awhile back. The trick is 2 get the player 2 shut off first.
https://www.youtube.com/watch?v=Uzu4uDTDL5k&feature=youtube_gdata_player
Sent from my YP-G70 using xda app-developers app
thewrongstuff said:
First off, I would like to say thank you for any advice on fixing my Galaxy Player 5. I have looked through multiple posts to attempt to unbrick my SGP and while following the directions, I still could not fix it. I am currently have the stock kernel installed and I can get into recovery mode and download mode but I get stuck in a bootloop otherwise. I can even get Odin3 v1.83 to recognize it. I currently have the .PIT file downloaded and I have the stock ROM downloaded and I put them in the PIT section and PDA section respectively. I have the following options checked: Re-Partition, Auto Reboot, F. Reset Time, and Phone Bootloader Update.
The message output is:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_G70XXKPH_CL1013658_REV01_user_low_ship_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
Every time I attempt this, it will get stuck on SetupConnection.. forever (at least 30 min until I exit it)
It is important to note that I have the Samsung USB drivers installed and I do not have Samsung KIES installed.
I would be glad to provide more information if needed such as what software I installed and which threads I looked at.
My question is, what can I do to fix my device.
Click to expand...
Click to collapse
I had a similar problem and got the device to stop bootlooping by restoring a nandroid. Also, try using Heimdall; whenever my Galaxy Player got bricked, Heimdall saved me Odin is horrible and I pray that I'll never have to use it again.
iurnait said:
what rom did you have on there before?
have you tried wiping data in recovery and booting up?
Click to expand...
Click to collapse
I had Paranoid Android here: (http://forum.xda-developers.com/showthread.php?t=2083052) installed and it worked fine. Then, I attempted to install the PAC-man ROM here: (http://forum.xda-developers.com/showthread.php?t=2235446) but the problem occurred when I installed the Sultan Kernel and then I installed the Intl-Kernel-4-19_iurnait.zip from his download link which he said not to install. I never actually installed the ROM. That is when all of these problems occurred.
To attempt to fix this problem, I used Heimdall to flash the stock ROM, and Kernel, using the appropriate .PIT file. It said that it installed correctly, but I could only get into recovery mode and download mode although the recovery screen changed after installing the new Kernel.
For your second question, I attempted wiping data and various caches but that hasn't worked.
I must also note that I have been spending hours trying to fix it and although I am by no means an expert with computers and android devices, I am usually good about following directions (except when I broke the SGP)
android1234567 said:
I had a similar problem and got the device to stop bootlooping by restoring a nandroid. Also, try using Heimdall; whenever my Galaxy Player got bricked, Heimdall saved me Odin is horrible and I pray that I'll never have to use it again.
Click to expand...
Click to collapse
This was one of those moments when I realized the importance of a nandroid backup which I never made for some stupid reason. I have also used Heimdall to successfully install the Kernel I think because I can change what recovery mode looks like when I flash a new kernel and rom, but it will never boot no matter which caches I clear or whatever else I do in recovery mode. It has been more useful than Odin3, but I have been trying to use that because that is what most of the tutorials use. Also, I am using the Samsung cable that came with the SGP and I plugged it into a USB port directly in the motherboard if that matters (some say it does).
To attempt to fix this problem, I used Heimdall to flash the stock ROM, and Kernel, using the appropriate .PIT file.
Click to expand...
Click to collapse
Did you mean stock gingerbread?
Nvm....
Sent from my YP-G70 using xda app-developers app
Meticulus said:
Did you mean stock gingerbread?
Nvm....
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
So I saw your video. I realized that that really isn't my problem. I used the wrong terminology. While it does bootloop when in charging mode with the battery icon, it just hangs at the Samsung logo if it is not being charged.
Also I assume it is stock gingerbread and not Froyo or something else. The ROM name is: CODE_G70XXKPH_CL1013658_REV01_user_low_ship_HOME.tar.md5
thewrongstuff said:
This was one of those moments when I realized the importance of a nandroid backup which I never made for some stupid reason. I have also used Heimdall to successfully install the Kernel I think because I can change what recovery mode looks like when I flash a new kernel and rom, but it will never boot no matter which caches I clear or whatever else I do in recovery mode. It has been more useful than Odin3, but I have been trying to use that because that is what most of the tutorials use. Also, I am using the Samsung cable that came with the SGP and I plugged it into a USB port directly in the motherboard if that matters (some say it does).
Click to expand...
Click to collapse
What about Heimdall in Linux?
android1234567 said:
What about Heimdall in Linux?
Click to expand...
Click to collapse
I was thinking of installing Linux but I do not have a spare computer. I could run it in VirtualMachine but I heard, and I forget where, that it would not work through a virtual installation, but if that is the only way to fix it, maybe it is worth finding a way to actually install Linux, or do you think that a VirtualMachine will work?
So you can get it in to download mode but when you go to flash it hangs at setting up connection.
Are you sure that you are in download mode? If I remember correctly Odin will detect your device in any mode but will only work in download mode.
Sent from my YP-G70 using xda app-developers app
---------- Post added at 09:34 PM ---------- Previous post was at 09:27 PM ----------
In my experience communicating over USB through a virtual machine is sketchy at best. I personally think it would be a better to install ubuntu using wubi if you want and installation that doesn't affect your current system and that you can easily uninstall.
Sent from my YP-G70 using xda app-developers app
thewrongstuff said:
I was thinking of installing Linux but I do not have a spare computer. I could run it in VirtualMachine but I heard, and I forget where, that it would not work through a virtual installation, but if that is the only way to fix it, maybe it is worth finding a way to actually install Linux, or do you think that a VirtualMachine will work?
Click to expand...
Click to collapse
Meticulus said:
So you can get it in to download mode but when you go to flash it hangs at setting up connection.
Are you sure that you are in download mode? If I remember correctly Odin will detect your device in any mode but will only work in download mode.
Sent from my YP-G70 using xda app-developers app
---------- Post added at 09:34 PM ---------- Previous post was at 09:27 PM ----------
In my experience communicating over USB through a virtual machine is sketchy at best. I personally think it would be a better to install ubuntu using wubi if you want and installation that doesn't affect your current system and that you can easily uninstall.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
You can create a Linux live USB so you can boot up your computer and run Linux from a flashdrive. You can create the live USB using the tool from here: http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
android1234567 said:
You can create a Linux live USB so you can boot up your computer and run Linux from a flashdrive. You can create the live USB using the tool from here: http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Click to expand...
Click to collapse
So I am in Xubuntu live cd and I have heimdall installed and the Frontend launched. I also have the necessary files in the right places but I cannot get it to detect my SGP. I haven't installed any drivers but I would not know where to find any anyway. Is that the problem?
thewrongstuff said:
So I am in Xubuntu live cd and I have heimdall installed and the Frontend launched. I also have the necessary files in the right places but I cannot get it to detect my SGP. I haven't installed any drivers but I would not know where to find any anyway. Is that the problem?
Click to expand...
Click to collapse
I like the command-line more What's Heimdall saying?
android1234567 said:
I like the command-line more What's Heimdall saying?
Click to expand...
Click to collapse
I was going to use the command line but I did not feel like learning the syntax because it is quite late here. The error is: "ERROR: Failed to access device. libusb error: 0" this occurs right after it says "Detecting device..."
thewrongstuff said:
I was going to use the command line but I did not feel like learning the syntax because it is quite late here. The error is: "ERROR: Failed to access device. libusb error: 0" this occurs right after it says "Detecting device..."
Click to expand...
Click to collapse
What version of Heimdall do you have? Only version 1.3.2 of Heimdall works with the Galaxy Player. Try flashing a kernel with Heimdall using the command line and see if that works. Copy the zImage you're going to flash to the home folder, open a terminal, and type
Code:
heimdall flash --kernel zImage
See what that does. If it keeps failing then keep trying to flash the zImage (in my case I kept rebooting the device between each try because I had THIS screen but I think (I'm not sure) forcefully rebooting the device while it's in download mode will get you to that screen and you really don't want that to happen). When my Galaxy Player was bricked it took me 3 tries with Heimdall to get it to flash and unbrick me. If it's taking you more than 5 tries just to flash a kernel with Heimdall 1.3.2 then I don't think Heimdall is going to work.
android1234567 said:
What version of Heimdall do you have? Only version 1.3.2 of Heimdall works with the Galaxy Player. Try flashing a kernel with Heimdall using the command line and see if that works. Copy the zImage you're going to flash to the home folder, open a terminal, and type
Code:
heimdall flash --kernel zImage
See what that does. If it keeps failing then keep trying to flash the zImage (in my case I kept rebooting the device between each try because I had THIS screen but I think (I'm not sure) forcefully rebooting the device while it's in download mode will get you to that screen and you really don't want that to happen). When my Galaxy Player was bricked it took me 3 tries with Heimdall to get it to flash and unbrick me. If it's taking you more than 5 tries just to flash a kernel with Heimdall 1.3.2 then I don't think Heimdall is going to work.
Click to expand...
Click to collapse
Well I found out that I have Heimdall 1.4.0 installed, but I wouldn't know how to install Heimdall 1.3.2 through apt-get. I did manage to find a precompiled .deb file for 1.3.2 but it was for i386 and not amd64 which is the one I have. I could download the i386 version of xubuntu though. I did find a 1.3.1 version that could work but if that doesn't support the SGP then I probably shouldn't download it.
If I recall correctly user ambrice created the version of hiemdall that works with our player. Should be a post about it in the archives somewhere...
Sent from my SAMSUNG-SGH-I577 using xda app-developers app
thewrongstuff said:
Well I found out that I have Heimdall 1.4.0 installed, but I wouldn't know how to install Heimdall 1.3.2 through apt-get. I did manage to find a precompiled .deb file for 1.3.2 but it was for i386 and not amd64 which is the one I have. I could download the i386 version of xubuntu though. I did find a 1.3.1 version that could work but if that doesn't support the SGP then I probably shouldn't download it.
Click to expand...
Click to collapse
No, you must have 1.3.2 and there is a way to install it: install multiarch. Open a terminal, type sudo apt-get install ia32-libs
Also, you need to uninstall Heimdall 1.4.0 before you install 1.3.2
Sent from my HTC Sensation 4G using xda app-developers app
android1234567 said:
No, you must have 1.3.2 and there is a way to install it: install multiarch. Open a terminal, type sudo apt-get install ia32-libs
Also, you need to uninstall Heimdall 1.4.0 before you install 1.3.2
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
I decided to use an i386 live cd instead. I think it will be easier.
Related
Hey, guys, I got a problem here, it's weird because I wasn't trying to flash when it started, the phone was ok, then froze, I tried to power off, but it didn't work, so I took off the battery. I put it on again, and the screen was freezing on the Samsung Galaxy S2 GT-I900I screen (EDIT: The right name is GT-i9100), I decided to flash to a stock rom with Odin, I put in the download mode, Odin recognized the phone but when I started to flash, Odin stuck in the middle of the process, I tried in all different usb ports of my laptop, I killed all the Kies processes, but it keeping sticking at the same point of the flashing. Please, somebody give me a hand here.
ps: I tried more than one rom, and it happens the same all the time.
I also uninstalled the usb ports and reinstalled, but nothing changes..
Try a different PC and or
[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.3.0 Available)
Never used it yet, but worth a shot?
UpInTheAir said:
Try a different PC and or
[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.3.0 Available)
Never used it yet, but worth a shot?
Click to expand...
Click to collapse
I'll try both methods. Thank you.
paumlhp said:
Hey, guys, I got a problem here, it's weird because I wasn't trying to flash when it started, the phone was ok, then froze, I tried to power off, but it didn't work, so I took off the battery. I put it on again, and the screen was freezing on the Samsung Galaxy S2 GT-I900I screen, I decided to flash to a stock rom with Odin, I put in the download mode, Odin recognized the phone but when I started to flash, Odin stuck in the middle of the process, I tried in all different usb ports of my laptop, I killed all the Kies processes, but it keeping sticking at the same point of the flashing. Please, somebody give me a hand here.
ps: I tried more than one rom, and it happens the same all the time.
I also uninstalled the usb ports and reinstalled, but nothing changes..
Click to expand...
Click to collapse
It seems that you have soft bricked the phone with a bad/interrupted flash.
Please, download this package : http://hotfile.com/dl/130600047/b70801e/I9100XXKI3.rar.html
And flash it.
Small guide :
IN ODIN :
1. Tick Re-partition, Auto-Reboot and F. Reset Time ( the top 3)
2. Put the .PIT file in the PIT section
3. CODE in PDA
4. MODEM in Phone
5. CSC in CSC
IN THE PHONE :
6. Turn it off
7. Enter Download mode
8. Connect to PC
9. Start Flashing
10. Wait, and DON'T INTERRUPT!
Good luck
Also try different USB cables
If you follow this method and download ROMs here: [ROM+Guide]Official i9100 Firmwares KG, KH, KI, KJ, KK1/2/5, KL1/2/3, LA2 Download
Pay particular attention to the Flashing Firmware with Odin Instructions step #5 "DO NOT PUT .PIT FILE AND DO NOT, I REPEAT, DO NOT TICK REPARTITION". This stuff is last resort or for those that are 100% sure what they're doing.
Guys, I think my phone is gone..
I tried with other cables, other computers, but I still got stuck at
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_THL_I9100DXKL3_I9100OLCKL2_I9100DXKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
I tried with the repartition and the pit file, but it seems that the phone doesn't want to flash... it got stuck too, I can't finish the process... any solution? I'm already looking for another one in eBay;
I haven't tried with Heimdall because I don't now how it works, somebody got a tutorial or something like this?
Question what is a I900I that is what is I model ???
As your problem reads like trying to flash a firmware for a wrong phone model .
jje
I wrote it wrong, the right name is GT-i9100
I think I got the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1218079
paumlhp said:
Guys, I think my phone is gone..
I tried with other cables, other computers, but I still got stuck at
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_THL_I9100DXKL3_I9100OLCKL2_I9100DXKL1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
I tried with the repartition and the pit file, but it seems that the phone doesn't want to flash... it got stuck too, I can't finish the process... any solution? I'm already looking for another one in eBay;
I haven't tried with Heimdall because I don't now how it works, somebody got a tutorial or something like this?
Click to expand...
Click to collapse
Alright then... Time to copy/paste my apparently-Holy solution
Flash this recovery package, which is XXKI3, 2.3.5, Open Europe http://hotfile.com/dl/130600047/b70801e/I9100XXKI3.rar.html
If that doesn't work or fails, flash this, which is a XXKI3 Kernel : http://www.multiupload.com/WDOO81L5H6. After that, re-flash the recovery package (with PIT and repartitiong, but be careful )
Report back if it doesn't work, and good luck!
If that doesn't work, flash the old bootloader : http://www.multiupload.com/LQQBRQVJUD in either the PDA or Bootloader section in ODIN. If that is successful, flash the Kernel again, and then the XXKI3 recovery package I gave you.
Thanks, Phistachio, for helping me..
so.. I tried the recovery method, no success (stuck), the kernel (stuck), the bootloader worked, then it came back to Samsung Galaxy S2 GT-i9100 screen, I put in download mode again, and tried the Kernel as you said, but.... stuck , tried the stock rom again, and continue sticking... I'm so sad, but the people say when get in the download mode, there is still hope, so...
by any chance, do you have another solution? I understand if you give up on me, it seems my problem is serious ;(
Did you try the Heimdall method I posted in post #2 ? Give it a try.
Sent from my GT-I9100 using xda premium
paumlhp said:
Thanks, Phistachio, for helping me..
so.. I tried the recovery method, no success (stuck), the kernel (stuck), the bootloader worked, then it came back to Samsung Galaxy S2 GT-i9100 screen, I put in download mode again, and tried the Kernel as you said, but.... stuck , tried the stock rom again, and continue sticking... I'm so sad, but the people say when get in the download mode, there is still hope, so...
by any chance, do you have another solution? I understand if you give up on me, it seems my problem is serious ;(
Click to expand...
Click to collapse
Are you using ODIN V1.83 or 85?
This can't be a hard brick.
Can you go to recovery mode? If so, wipe cache and data.
Then try to reflash
UpInTheAir, I didn't try the Heimdall method because I don't know how to flash with Heimdall, do you have anytutorial or simple guide how to use it?
Phistachio, I'm using Odin3 v.1.85. The recovery mode is the combo [vol up+home+power button] right? If so, it's not entering anymore, when I had the problem I could get in there, I tried to wipe all the things but it didn't work.
Do you guys think it could be a hardware problem?
OK, did a search for you, doesn't seem too difficult.......
Download here: http://www.glassechidna.com.au/products/heimdall/
For Windows, download:
1.Microsoft Visual C++ 2010 Redistributable Package (x86)
2. Heimdall Suite 1.3.1 (Binaries)
Maybe need to install the drivers, not sure. If your device is dected by Heimdall in Download Mode, maybe work.........
Guide for version 1.3.1 heimdall-frontend here: http://forum.xda-developers.com/showthread.php?t=1196179
EDIT: STEP BY STEP GUIDE FROM VEYKA
This is for I9000 but has been known to work with SGS2.
paumlhp said:
Phistachio, I'm using Odin3 v.1.85. The recovery mode is the combo [vol up+home+power button] right? If so, it's not entering anymore, when I had the problem I could get in there, I tried to wipe all the things but it didn't work.
Do you guys think it could be a hardware problem?
Click to expand...
Click to collapse
Maybe try just flash the kernel with Odin, so you can get recovery back.
You could also try flash one of Chainfire CF-root kernel to install CWM recovery, and then flash a custom ROM.zip directly from sdcard.
Got a feeling that your partitions are corrupted. That's why using PIT is not recommend and only last resort.
Sent from my GT-I9100 using xda premium
This doesn't sound bricked.
I reckon you can fix it via heimdall, flashing each partition individually...
Failing that, your last resort is to do a full repartition, using pit
pulser_g2 said:
This doesn't sound bricked.
I reckon you can fix it via heimdall, flashing each partition individually...
Failing that, your last resort is to do a full repartition, using pit
Click to expand...
Click to collapse
He already tried doing that...
It's not hard bricked, but a kernel flash SHOULD have been siccessful, since DL Mode is working...
Phistachio said:
He already tried doing that...
It's not hard bricked, but a kernel flash SHOULD have been siccessful, since DL Mode is working...
Click to expand...
Click to collapse
If you take a quick look at the recent posts, the OP had not indicated trying Heimdall as yet. He asked for a guide that I subsequently posted.
Sent from my GT-I9100 using xda premium
Guys, I downloaded Heimdall, installed .Microsoft Visual C++ and downloaded the 2.3.4 Heimdall firmware package for stock GT-I9000 firmwares, from the that thread, so I followed the guide, I removed all the stuff, but the Kernel one and tried to flash, that's the result:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
It seems like Heimdall doesn't detect the phone? Sorry for being a noob and I really appreciate all the effort from you guys, I really do.
EDIT:
I entered in the drivers session, put all devices, and it found some drivers of my pc and one called Gadget Serial, so I installed it, ok, back to Heimdall, I selected the stock 2.3.4 one, deleted all the stuff and left the Kernel, unchecked Repartition and now I got this:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
EDIT:
It looks live the phone is officially dead now, it doesn't turn on and it was very hot after I left the Download Mode. I'm gonna try to turn it on tomorrow and start look for a new one/warranty/what I can sell from this phone and etc...
Thanks again, guys, you were the best.
Bummer
Looks like you tried to flash 9000 firmware package, not 9100.
Edit: Maybe try remove battery for a few minutes, and download mode again, or USB jig to force it.
Sent from my GT-I9100 using xda premium
Ok so last night my phone froze up while I was browsing the web (it froze just after rotating, if that's of any significance) so I held the power button down until it turned off. Trying to turn it on again, it just sat at the galaxy s 2 logo before any bootanimations etc start playing.
I thought I'd try to just re-flash the ROM (CM10 nightly 26/9/2012) and it seemed to just freeze up near the end of the flash, so I left it to do it's thing.
When I returned to the phone, it was showing me a kernel panic screen, so I held the power button to turn it off again and since then it won't boot into the ROM, it won't boot into recovery, and until just now it wouldn't be recognised by odin in download mode.
I had tried installing the USB drivers for the phone etc and it wouldn't work, however while writing this topic I just got a notification on my PC saying USB drivers had been installed and Odin seemed to recognise my phone, so I tried flashing cm9 resurrection, however it seems to be stuck. These are the messages in Odin, for reference:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
and it's just been stuck there since I pressed start. There is no progress bar or anything on the phone either. Oh, and Odin's progress bar thing at the top just says "KERNEL" with a blank bar under it and "0:[com3]" with a yellow background below that.
Is it safe to unplug the phone and try again with a different USB cable?
EDIT: After trying different methods to recover it (with the same result from Odin):
Orkane1989 said:
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Click to expand...
Click to collapse
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
So it's safe to unplug the phone?
D3_ said:
So it's safe to unplug the phone?
Click to expand...
Click to collapse
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Orkane1989 said:
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Just tried this, getting the same thing, Odin gets the first "bar" in the progress bar completed and seems to get stuck. Same output as above.
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
You will have to consult someone with some more knowledge about this than me. You could have a corrupt data partition... but its honestly out of my league now lol. Sorry I couldn't help.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
Click to expand...
Click to collapse
According to the output it gives me (in the OP) it does successfully check the MD5 though.
I'll admit, I haven't actually used Odin since I first rooted this phone (back in december last year) so I'm back to knowing basically nothing about how it works.
Yes it does confirm the md5
But after that it sends the commands to start running the new kernel (basically installing it on the device firstly)
Which is where it gets stuck.
Sent from Jelly Fuelled SGS2
Just tried this: http://forum.xda-developers.com/showthread.php?t=1457458
Same issue with flashing those files.
I don't want to try the .pit because if it doesn't flash then I'll be pretty f*cked, right?
I would try what ever else you could find because if you get that guide wrong you could end up turning your phone into a paperweight. But if you so have to use the guide take note that you ahould try flashing the files WITHOUT .pit or repartition first. If that doesn't succeed than your last option is to use the .pit file and repartition.
Sent from Jelly Fuelled SGS2
I did try it, without the .pit/repartition as the guide says to try it without it first, but again, it won't flash anything (which is why I don't think I'll try the .pit/repartition)
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Sent from Jelly Fuelled SGS2
Problem:
My GSII was running normally on the latest RootBox version, Dorimax Kernel 7.46, I was using SD Maid Pro, to Optimize database, I didn't actually knew what the function do, but it has to do something with improving the performance of my phone, and i already used it before many times.
But this time it was stuck for like 10 minutes while optimizing database so i turned off my phone and turned it on again, and BAM, stuck on samsung logo, I couldn't access recovery, only download mode.
Steps I already took:
1. Flashed Dorimanx Kernel 7.45 .tar with Odin -> Odin Stuck at NAND Write Start
2. Flashed Stock Roms, ICS (I9100XXLPH and I9100XWLPG) and JB (I9100XWLS8_I9100FOPLS3) -> Odin Stuck at NAND Write Start (Failed)
3. Flashed it on a different Laptop (x86 and x64) -> Same results.
Here is the log from ODIN:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_XEU_I9100XWLPG_PRE-ROOTED_I9100XXLPX_I9100XEULP5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Step that I'm thinking of taking:
I suspected then that I had to go nasty and flash PIT and re-partition.
Basically this is the last solution for hopeless flashaholics, so based on these threads (1) (2) I downloaded the pit zip, but it contained lots of patched pit files, and each for different brick area.
The problem I cannot access recovery mode so I can't know the bricked part. I read in the thread that if I don't know i have to try each one (92 pit files).
And that was a solution for the MMC_CAP_ERASE brick, which actually is not present if i'm using Dorimanx Kernel or JB AOSP ROMs.
So now I'm not sure if flashing pit will be the correct solution, I was starting to think of flashing a bootloader as in thread
So fellow flashaholics, before I mess up with pit files, and f*ck my phone more, any more suggestions?
(Btw I don't have yellow triangle, so basically I can send it to repairing service or whatever, but actually staying without a smartphone for at least a week is quite impossible for me, if you know what I mean)
Download and flash with odin 1.3.
Sent from my GT-I9100 using xda app-developers app
Pit files should be regarded as a last resort.
Try all odin versions possible
Try all usb ports.
Try all usb cables.
Try all pc/laptops you can.
Try flashing various ROMs.
Try flashing various kernels via Odin.
Uninstall & reinstall Kies.
Sent from the little guy
Download and flash with odin 1.3.
Click to expand...
Click to collapse
Odin 1.3? I did try to flash with Odin 1.85 but didn't want to go older than that. But anyway I'm not loosing anything, so i'll give it a shot.
Pit files should be regarded as a last resort.
Try all odin versions possible
Try all usb ports.
Try all usb cables.
Try all pc/laptops you can.
Try flashing various ROMs.
Try flashing various kernels via Odin.
Uninstall & reinstall Kies.
Click to expand...
Click to collapse
Thanks for the advice, but the problem that it's just stuck at NAND bla bla bla, and not continuing, even thought I tried multiple ROMs, and Kernels, and Laptops. I already uninstalled Kies, it's useless anyway, I reinstalled USB drivers, basically i exploited every possible solution other than flashing a PIT file. But I'll keep trying.
silv3rfox said:
Odin 1.3? I did try to flash with Odin 1.85 but didn't want to go older than that. But anyway I'm not loosing anything, so i'll give it a shot.
Thanks for the advice, but the problem that it's just stuck at NAND bla bla bla, and not continuing, even thought I tried multiple ROMs, and Kernels, and Laptops. I already uninstalled Kies, it's useless anyway, I reinstalled USB drivers, basically i exploited every possible solution other than flashing a PIT file. But I'll keep trying.
Click to expand...
Click to collapse
I have exact same problem today, still trying to recover the NAND
I had the exact problem with two phones. I tried everything but with no luck. Than I downloaded odin 1.3 and that solved my problem. Try odin 1.3 you don't lose anything.
Sent from my GT-I9100 using xda app-developers app
GreatVortex said:
I had the exact problem with two phones. I tried everything but with no luck. Than I downloaded odin 1.3 and that solved my problem. Try odin 1.3 you don't lose anything.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
OK I'll try Odin 1.3
If it doesn't fly...keep trying with another versions.
Sent from the little guy
Nope. Doesn't work.
I can get into download mode
I cannot get into recovery mode
I can charge the battery if I connect the phone to PC/charger
All attempts stuck at NAND write
Is this motherboard problem?
Any help?
Flash siyah v5.
Sent from the little guy
Did try.
Siyah stuck at zimage.
I tried almost everything all day long. Is there any hard core way to reset this phone?
I read about .PIT file method to reset, but looks like no guide to do it here. Can you help me please?
kopiko09 said:
Did try.
Siyah stuck at zimage.
I tried almost everything all day long. Is there any hard core way to reset this phone?
I read about .PIT file method to reset, but looks like no guide to do it here. Can you help me please?
Click to expand...
Click to collapse
There are, but you really need to know what you're doing.
Are you sure you had tried everything and then tried it again?
If, and only if, YES, we can start talking about pit files.
Sent from the little guy
OK I'll try everything again once more. If still fail I'll let you know tomorrow. Thanks
Promise me (and your device) you'll try it ALL out again.
Sent from the little guy
OK I'll try everything again once more. If still fail I'll let you know tomorrow. Thanks
Click to expand...
Click to collapse
I tried to flash different ROMs with ODIN 1.3, it didn't get past the boot.bin, i retried with Odin 3.07, but still same old problem stuck at NAND Write bla bla bla!
Hope you'll get something, that'll give me some hope to retry again!
I had the exact problem with two phones. I tried everything but with no luck. Than I downloaded odin 1.3 and that solved my problem. Try odin 1.3 you don't lose anything.
Click to expand...
Click to collapse
What did you flash with Odin 1.3?
I flashed this: http://www.hotfile.com/dl/190226031/b214985/I9100XWLS8_I9100FOPLS3_FOP.zip.html
In Odin the only thing selected was auto reboot. All other things were unselected(unthicked).
This is the Odin that i used: View attachment Odin3_v1.3.rar
Sry for my english.
P.S. If you have kies installed Uninstall it before flash or make sure all kies process are stoped in task manager.
I'm trying with Odin 3.07 now
try all odins you can get your hands on.
Sent from the little guy
OK, one thing is sure. Odin 1.3 does NOT work. It stucks earlier than other version of odin. Not even get to NAND write step
Hey All,
I definitely hard bricked my phone, I've tried everything on XDA, every Odin, every stock and rooted rom in combination with different Pit's, baselines etc.. etc..
Not sure if I am rooted anymore or unrooted since I have installed so many Rom's.. My screen gets stuck on Samsung Logo, I can only get into Download Mode (Odin Mode) and I am sure of that.
I started off trying to install a custom rom, things went bad, after it all went bad i realized my mistakes reading, upon reading XDA.
My question for all you wonderful people on XDA is.. what do i do now with a paper weight? Do i keep trying and Beat it till it works, or replace the motherboard? & if i replace the mobo can i simply get an AT&T Mobo on this Verizon? (I have at&t, its an unlocked Verizon phone).. & where do I go to do it? (cheapest place please, totally not rich)
more info:
can't partition in odin/ i always encounter some sort of error in the middle of trying to do anything with odin.. I am only successful when i install the 66root file, and if I select the 'T Flash' option in odin it sometimes works with other roms.. but no matter what I still get stuck on the Logo Screen
list of what i have tried:
http://galaxynote2root.com/galaxy-n...o-install-custom-rom-on-rooted-galaxy-note-2/
http://www.androidayos.com/2013/04/...-note-2-sch-i605-original-firmware-stock-rom/
http://forum.xda-developers.com/showthread.php?p=39299305
http://forum.xda-developers.com/showthread.php?t=2118348
http://forum.xda-developers.com/showthread.php?t=2024207
& MUCH MORE.
I know i am dumb for how I went about doing all this so please keep it informational... thank you all!!
gnit0 said:
Hey All,
I definitely hard bricked my phone, I've tried everything on XDA, every Odin, every stock and rooted rom in combination with different Pit's, baselines etc.. etc..
Not sure if I am rooted anymore or unrooted since I have installed so many Rom's.. My screen gets stuck on Samsung Logo, I can only get into Download Mode (Odin Mode) and I am sure of that.
I started off trying to install a custom rom, things went bad, after it all went bad i realized my mistakes reading, upon reading XDA.
My question for all you wonderful people on XDA is.. what do i do now with a paper weight? Do i keep trying and Beat it till it works, or replace the motherboard? & if i replace the mobo can i simply get an AT&T Mobo on this Verizon? (I have at&t, its an unlocked Verizon phone).. & where do I go to do it? (cheapest place please, totally not rich)
more info:
can't partition in odin/ i always encounter some sort of error in the middle of trying to do anything with odin.. I am only successful when i install the 66root file, and if I select the 'T Flash' option in odin it sometimes works with other roms.. but no matter what I still get stuck on the Logo Screen
list of what i have tried:
http://galaxynote2root.com/galaxy-n...o-install-custom-rom-on-rooted-galaxy-note-2/
http://www.androidayos.com/2013/04/...-note-2-sch-i605-original-firmware-stock-rom/
http://forum.xda-developers.com/showthread.php?p=39299305
http://forum.xda-developers.com/showthread.php?t=2118348
http://forum.xda-developers.com/showthread.php?t=2024207
& MUCH MORE.
I know i am dumb for how I went about doing all this so please keep it informational... thank you all!!
Click to expand...
Click to collapse
If you can still access Download Mode then you arent truly hard bricked.
If you havent tried it you need to try flashing the PIT file. There is also the "alternative recovery method" that you should try. I think flashing the PIT file, which I believe is in one of Adams casual posts, will get you back on track but I might be wrong. Hopefully someone else will stroll through and be abke to give you a bit more help than me.
As for the first 2 urls, NEVER EVER EVER use root methods that are not on XDA. Not many people have experience with them and they could be potentially dangerous.
You also need to specify exactly what all you have tried out of those threads instead of just linking the thread.
Sent from my SCH-I605 using XDA Premium HD app
Alternative Retry
shangrila500 said:
If you can still access Download Mode then you arent truly hard bricked.
If you havent tried it you need to try flashing the PIT file. There is also the "alternative recovery method" that you should try. I think flashing the PIT file, which I believe is in one of Adams casual posts, will get you back on track but I might be wrong. Hopefully someone else will stroll through and be abke to give you a bit more help than me.
As for the first 2 urls, NEVER EVER EVER use root methods that are not on XDA. Not many people have experience with them and they could be potentially dangerous.
You also need to specify exactly what all you have tried out of those threads instead of just linking the thread.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
USB
gnit0 said:
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Click to expand...
Click to collapse
I've tried different USB Ports, Chords and Machines (win 7 64bit, win 7 32bit & XP)
gnit0 said:
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Click to expand...
Click to collapse
I had this problem.
And I just used another computer and it worked fine.
Sent from my SCH-I605 using xda app-developers app
barrackOBAMA said:
I had this problem.
And I just used another computer and it worked fine.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
thanks guys, I really do appreciate the help and I have no problem testing any method thrown my way, if you guys were to tell me to throw it at a pigeon, I probably would do it. I have tried on 3 different VM's.. not sure if thats really considered a "different machine" or not.. I am in the middle of restoring my old dell laptop to try it on that.
shangrila500 said:
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
ah dude.. tried it on a different PC and still stuck on this motherless error <ID:0/004> Get PIT for mapping..
Honestly think I did something to the emmc or whatever it is. I don't know if I'm violating TOS but I will donate 50 bux to whomever can help. If saying I will donate is a violation please forgive.
gnit0 said:
Honestly think I did something to the emmc or whatever it is. I don't know if I'm violating TOS but I will donate 50 bux to whomever can help. If saying I will donate is a violation please forgive.
Click to expand...
Click to collapse
Lemme ask you this, do you have Kies installed? My friend had the same issue with his N2 where it would freeze in Odin and do nothing else at all after it said getting PIT for mapping. He finally had to bring it over to me and use my computer to root it, his is the AT&T version, and even though he had Kies installed he couldn't get the phone to connect right. He finally had to install Kies and all the drivers and them reinstall Kies first then the standalone drivers that were linked and after that everything worked. That may be worth a shot. I also know a lot of people have issues using VM machines and Windows 8, it seems everything works smoothest on Windows 7.
As for boring the emmc, you may have but like I said earlier it's really hard to screw this phone up so I really think it is just an issue with VM ware or possibly you haven't flashed the right file that it needs yet. We'll figure it out though hopefully, it will just take some trial and error.
Have you tried the alternate restore method? If not I will link it, it seems to fix a lot of people's phones when nothing else will.
Honestly I think it is something with the computers you're using and the drivers being wonky as usual.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Lemme ask you this, do you have Kies installed? My friend had the same issue with his N2 where it would freeze in Odin and do nothing else at all after it said getting PIT for mapping. He finally had to bring it over to me and use my computer to root it, his is the AT&T version, and even though he had Kies installed he couldn't get the phone to connect right. He finally had to install Kies and all the drivers and them reinstall Kies first then the standalone drivers that were linked and after that everything worked. That may be worth a shot. I also know a lot of people have issues using VM machines and Windows 8, it seems everything works smoothest on Windows 7.
As for boring the emmc, you may have but like I said earlier it's really hard to screw this phone up so I really think it is just an issue with VM ware or possibly you haven't flashed the right file that it needs yet. We'll figure it out though hopefully, it will just take some trial and error.
Have you tried the alternate restore method? If not I will link it, it seems to fix a lot of people's phones when nothing else will.
Honestly I think it is something with the computers you're using and the drivers being wonky as usual.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Hey Shangrila, appreciate you helping me, I am going to try and completely uninstall all drivers for Samsung, uninstall kies, install drivers and test, if it doesn't work, re-install kies and drivers. I have tried to restore with and without kies, and all over again. I will try again but this time i will completely wipe all drivers and re-install note 2 drivers
May I ask what the first step that you did was that bricked it? You are stuck on the samsung logo flashing?
meat614 said:
May I ask what the first step that you did was that bricked it? You are stuck on the samsung logo flashing?
Click to expand...
Click to collapse
It started with a trade on craigslist. Traded my at&t iPhin 5 (i love you man insider) for this Verizon sch-i605 unlocked. I had no idea if it were able to accept custom roms or not, but i do know it was rooted (used supersu) i am a highly tech savvy guy but i don't know **** about android. I did a factory restore from setting, I then tried to install casual, downloaded it and ran it but it kept erroring so i then went and tried to upload a mod on sdcard and went to recovery mode wipe device and cache.. after that it stopped working. tried to install all sorts of roms, boot loaders, pits and what not. now all i get is error after error, either nand error or getting pit mapping halt. for some reason root66 is the only rom that is successfull but without pit file. and not sure what "T Flash" is on Odin, but some roms work while that is checked.
some roms i have tried:
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5
I605_VRALJB_Restore.tar.md5
cwm6-root-note2.tar
root66_VZW_stock_system.tar.md5
BootloaderBaseline2.tar.md5
TWRP2430VZW.tar.md5
gnit0 said:
Hey Shangrila, appreciate you helping me, I am going to try and completely uninstall all drivers for Samsung, uninstall kies, install drivers and test, if it doesn't work, re-install kies and drivers. I have tried to restore with and without kies, and all over again. I will try again but this time i will completely wipe all drivers and re-install note 2 drivers
Click to expand...
Click to collapse
If I can help I most definitely will. This sounds exactly like a driver issue thoug because it isnt able to communicate with the phone yo get the PIT for mapping. That was the same exact thing that happened with my friends phone on his laptop when I was setting everything up and showing him how to use Odin to root his phone, it would show up on a port and act like it would work but it would freeze every single damn time on the getting PIT for mapping part and wouldn't do anything else until I unplugged the phone and then it would say failed.
The main thing that helped him was wiping the drivers completely though and then just reinstalling Kies, I think he installed the other drivers after that but i can remember for sure, and it finally worked perfectly. I only have Kies on my laptop, I dont have the second set of drivers, but if you cant get it to work with just Kies try installing the other set and then test it again. You may even have to launch Kies for it to install the drivers correctly, it's been so long I can't remember that part either. Just install Kies first without the other set of drivers, launch Kies and make sure everything is set up with Kies, and see if that works. If not then install the 2nd set and try to use Odin again.
Also what OS are you doing all this on? If it's Windows 7 then it may take a little playing with the drivers to get it right. Also which version of Odin are you using? I cant get the newest version to work correctly on my laptop so that could also be part of it. Have you tried the alternative restore method? While I am 99% site it is the drivers it is always best to cover all bases.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
gnit0 said:
It started with a trade on craigslist. Traded my at&t iPhin 5 (i love you man insider) for this Verizon sch-i605 unlocked. I had no idea if it were able to accept custom roms or not, but i do know it was rooted (used supersu) i am a highly tech savvy guy but i don't know **** about android. I did a factory restore from setting, I then tried to install casual, downloaded it and ran it but it kept erroring so i then went and tried to upload a mod on sdcard and went to recovery mode wipe device and cache.. after that it stopped working. tried to install all sorts of roms, boot loaders, pits and what not. now all i get is error after error, either nand error or getting pit mapping halt. for some reason root66 is the only rom that is successfull but without pit file. and not sure what "T Flash" is on Odin, but some roms work while that is checked.
some roms i have tried:
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5
I605_VRALJB_Restore.tar.md5
cwm6-root-note2.tar
root66_VZW_stock_system.tar.md5
BootloaderBaseline2.tar.md5
TWRP2430VZW.tar.md5
Click to expand...
Click to collapse
Watch what you check in Odin. You are ONLY supposed to check what is told in the guide, NONE OTHER! Thats a really good way to mess things up and make it harder to fix!
Can you boot into recovery? If so is there a nandroid you could try restoring?
Sent from my SCH-I605 using XDA Premium HD app
aug ttaham
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
gnit0 said:
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
Click to expand...
Click to collapse
What do you mean by none stop? Did you mean non stop? Or they aren't stopping? Sorry for asking, just a little late and I had a long day.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
What do you mean by none stop? Did you mean non stop? Or they aren't stopping? Sorry for asking, just a little late and I had a long day.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I meant i have been trying those none stop, ive tried to restore with those files atleast 10 times..
I tried to uninstall drivers and kies and then restoring but i got nothing, then tried with newly installed kies... and nothing as well.. arggg
still stuck on Get Pit Mapping
& no, i cannot get into recovery... just stays at the samsung gn 2 logo screen, and if i hold up button home and power, it just shuts off and on again... even if i release power button when i see the logo... stays at logo
gnit0 said:
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
Click to expand...
Click to collapse
Also this is the alternative method I was talking about:
http://forum.xda-developers.com/showthread.php?t=2040264
In the first post there is a link that says alternative restore, it has a different sboot so it will leave you unlocked. It works a lot when the PIT doesnt, its worth a shot. I still think its drivers but im throwing everything I can out so maybe you'll be able to use your phone, I know how it is to not have one to use until you can fix yours.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 11:27 PM ---------- Previous post was at 11:24 PM ----------
gnit0 said:
I meant i have been trying those none stop, ive tried to restore with those files atleast 10 times..
I tried to uninstall drivers and kies and then restoring but i got nothing, then tried with newly installed kies... and nothing as well.. arggg
still stuck on Get Pit Mapping
& no, i cannot get into recovery... just stays at the samsung gn 2 logo screen, and if i hold up button home and power, it just shuts off and on again... even if i release power button when i see the logo... stays at logo
Click to expand...
Click to collapse
What OS are you using? Are you using VMware right now? It still sounds like a driver issue, is there any chance you have a different computer with Windows 7 installed that you could try if the alternative restore method I linked a minute ago doesn't work?
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Also this is the alternative method I was talking about:
http://forum.xda-developers.com/showthread.php?t=2040264
In the first post there is a link that says alternative restore, it has a different sboot so it will leave you unlocked. It works a lot when the PIT doesnt, its worth a shot. I still think its drivers but im throwing everything I can out so maybe you'll be able to use your phone, I know how it is to not have one to use until you can fix yours.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
that is the exact file i have been trying with odin 3.0.7 and the pit file.
shangrila500 said:
What OS are you using? Are you using VMware right now? It still sounds like a driver issue, is there any chance you have a different computer with Windows 7 installed that you could try if the alternative restore method I linked a minute ago doesn't work?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I am trying on a local windows 7 64bit machine.. i have 16gb ram, amd fx 8120 8-core processor, and a ssd hybrid.. my mobo is a asus m5a97.. stopped using the VM's
Hi guys, new poster here. After researching the threads on here and on other sites, I can't seem to find the exact solution to fix this. I've got a U.S. version that when trying to update the stock ROM from Gingerbread 2.3.5 to 2.3.6, I accidentally booted up my device during the initial install process through Odin. When I did that my device went into the forced download mode with the "Phone triangle to PC " error screen. I'm not exactly sure where to go from here, as I can't get into the normal (maintenance) download mode or Recovery Mode.
When I first tried to install the 2.3.6 software, guided by the instructions in the following thread title (can't post the link since it's my first time, sorry), "[How to] Upgrade SGP 5.0 to Android v2.3.6" posted by Sanchezhacker on anything but ipod's website, here is what I ended up with:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I'd like to be able to install 2.3.6 but I'm not exactly sure how to get out of the forced download mode first.
How do I get out of download mode and how can I install 2.3.6 from there?
Your input is greatly appreciated!!
Thank you, and God bless!!
International96 said:
Hi guys, new poster here. After researching the threads on here and on other sites, I can't seem to find the exact solution to fix this. I've got a U.S. version that when trying to update the stock ROM from Gingerbread 2.3.5 to 2.3.6, I accidentally booted up my device during the initial install process through Odin. When I did that my device went into the forced download mode with the "Phone triangle to PC " error screen. I'm not exactly sure where to go from here, as I can't get into the normal (maintenance) download mode or Recovery Mode.
When I first tried to install the 2.3.6 software, guided by the instructions in the following thread title (can't post the link since it's my first time, sorry), "[How to] Upgrade SGP 5.0 to Android v2.3.6" posted by Sanchezhacker on anything but ipod's website, here is what I ended up with:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I'd like to be able to install 2.3.6 but I'm not exactly sure how to get out of the forced download mode first.
How do I get out of download mode and how can I install 2.3.6 from there?
Your input is greatly appreciated!!
Thank you, and God bless!!
Click to expand...
Click to collapse
Forced Download Mode only happens when there is something critically wrong with the current state of your Player. I recommend that you return to stock
http://www.4shared.com/zip/hFJmoXTiba/YP-G70-UEKI8-Stock-USA-Meticul.html?
Meticulus, I really appreciate your help, thank you for it.
Well, when I tried to download your file in the link you gave me, I waited until 4shared's wait to download timer ran out and here's the message I got once it did, "Sorry, the file link that you requested is not valid. Sign error."
Any ideas for a workaround?
International96 said:
Meticulus, I really appreciate your help, thank you for it.
Well, when I tried to download your file in the link you gave me, I waited until 4shared's wait to download timer ran out and here's the message I got once it did, "Sorry, the file link that you requested is not valid. Sign error."
Any ideas for a workaround?
Click to expand...
Click to collapse
I just tried it, and it works... I suggest that you sign up for 4shared. Then download...
Meticulus said:
I just tried it, and it works... I suggest that you sign up for 4shared. Then download...
Click to expand...
Click to collapse
I'm actually signed in to 4shared via my Facebook, but that shouldn't prevent it from letting me download, should it?
International96 said:
I'm actually signed in to 4shared via my Facebook, but that shouldn't prevent it from letting me download, should it?
Click to expand...
Click to collapse
I'll download and re-up it at androidfilehost.com...
downloading now...
International96 said:
I'm actually signed in to 4shared via my Facebook, but that shouldn't prevent it from letting me download, should it?
Click to expand...
Click to collapse
@International96
https://www.androidfilehost.com/?fid=24651442761498983
Meticulus said:
@International96
https://www.androidfilehost.com/?fid=24651442761498983
Click to expand...
Click to collapse
Alrighty, I just downloaded the ZIP file, unpacked it, now do I run it through Odin? I have Odin 1.85 installed. I tried to run it in Odin's software using the PDA tab, plugged my device in and linked the file to Odin and clicked "Start", here's the results I got,
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> YP-G70-UEKI8-Stock-USA-Meticulus.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure why it failed... Any suggestions?
To be honest, some step-by-step instructions would help me a lot. Thank you.
Just curious to see if there's any update on this? I'm still not sure how to install the md5 file to my SGP using Odin, like I had mentioned above.
International96 said:
Just curious to see if there's any update on this? I'm still not sure how to install the md5 file to my SGP using Odin, like I had mentioned above.
Click to expand...
Click to collapse
Sorry, busy lately but it looks like you did it properly. Normally all you have to do is put the *.md5 file in PDA and hit start. Looks like you did that and it still did not work. I suggest that you download the first tar ( not zip ) file here: http://forum.xda-developers.com/showthread.php?t=1445840
This is a custom kernel with a custom recovery in it. flash the .tar file the same way you did with the .md5 file. Click PDA; select the tar file; click start.
See if that succeeds. If it does, attempt to get into recovery like this :
https://www.youtube.com/watch?v=Uzu4uDTDL5k
NOTE: Video shows how to get to download mode but just use the opposite volume key to get to recovery.
Then let me know what happens....:highfive::highfive:
Meticulus said:
Sorry, busy lately but it looks like you did it properly. Normally all you have to do is put the *.md5 file in PDA and hit start. Looks like you did that and it still did not work. I suggest that you download the first tar ( not zip ) file here: http://forum.xda-developers.com/showthread.php?t=1445840
This is a custom kernel with a custom recovery in it. flash the .tar file the same way you did with the .md5 file. Click PDA; select the tar file; click start.
See if that succeeds. If it does, attempt to get into recovery like this :
https://www.youtube.com/watch?v=Uzu4uDTDL5k
NOTE: Video shows how to get to download mode but just use the opposite volume key to get to recovery.
Then let me know what happens....:highfive::highfive:
Click to expand...
Click to collapse
It's okay, thanks for the follow-up, I appreciate it. Well, I downloaded the .tar file, flashed it in Odin and here's what I got... Seems like it just loves to fail, haha.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
International96 said:
It's okay, thanks for the follow-up, I appreciate it. Well, I downloaded the .tar file, flashed it in Odin and here's what I got... Seems like it just loves to fail, haha.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Has Odin ever worked for you?
Meticulus said:
Has Odin ever worked for you?
Click to expand...
Click to collapse
Come to think of it, I don't believe it has. Except for the process of getting it bricked, with my dumb move to try and power it up in the middle of the install process of 2.3.6, haha. That was a bad move on my part. But no, it hasn't.
International96 said:
Come to think of it, I don't believe it has. Except for the process of getting it bricked, with my dumb move to try and power it up in the middle of the install process of 2.3.6, haha. That was a bad move on my part. But no, it hasn't.
Click to expand...
Click to collapse
Are you familiar with Ubuntu and running linux? If I were you, I get on a linux box and see what you can do with heimdall....:good:
Meticulus said:
Are you familiar with Ubuntu and running linux? If I were you, I get on a linux box and see what you can do with heimdall....:good:
Click to expand...
Click to collapse
I know a little bit about it but not a lot. I think I tried doing that once before but I didn't know exactly how to set it up.
Soft Bricked Samsung Galaxy Player 5.0
Hello,
First, I am sorry to jump in this thread, but I am having the exact problem listed in this thread. I picked up this player at a hamfest in NC. The battery was dead. But when I plugged it in to charge, the screen was black with a little phone symbol, an orange triangle, and a computer.
I have tried all the instruction that were posted, with the same results. So if you have any other suggestions I'd appreciate it.
thank you
Hey Johnny, I figured you've been busy, but I'm still out of service with my Galaxy Player, I'm not sure exactly how to go about using Ubuntu and running Linux. I really appreciate your help thus far, but it's been almost a month and still no luck with the darn device... Maybe it's time to look for a replacement, possibly..
lostnubie said:
Hello,
First, I am sorry to jump in this thread, but I am having the exact problem listed in this thread. I picked up this player at a hamfest in NC. The battery was dead. But when I plugged it in to charge, the screen was black with a little phone symbol, an orange triangle, and a computer.
I have tried all the instruction that were posted, with the same results. So if you have any other suggestions I'd appreciate it.
thank you
Click to expand...
Click to collapse
International96 said:
Hey Johnny, I figured you've been busy, but I'm still out of service with my Galaxy Player, I'm not sure exactly how to go about using Ubuntu and running Linux. I really appreciate your help thus far, but it's been almost a month and still no luck with the darn device... Maybe it's time to look for a replacement, possibly..
Click to expand...
Click to collapse
I'm sorry guys; I've owned my Galaxy Player 5 since 2011 and I have bricked it several times since then and I have never come across a situation that I could not bring the player back from but, as a (self taught)developer I am pretty good at diagnostic and evaluation procedures. The first step in that is to gather as much information about the problem as possible.
There is a program called heimdall that is like odin but it works on the linux command line that can give more information about what is happening during a flash and it "might" give you a better idea about what is the problem.
The biggest problem that I have run across with this device is that the partition table gets mangled some how and therefore odin does not know where to put data. This can ususally be fixed by flashing a custom kernel like Entropy's Daily Driver and then booting into recovery and using partition tools to carefully reconstruct the table...
Then again, the hardware may actually be damaged...
Meticulus said:
I'm sorry guys; I've owned my Galaxy Player 5 since 2011 and I have bricked it several times since then and I have never come across a situation that I could not bring the player back from but, as a (self taught)developer I am pretty good at diagnostic and evaluation procedures. The first step in that is to gather as much information about the problem as possible.
There is a program called heimdall that is like odin but it works on the linux command line that can give more information about what is happening during a flash and it "might" give you a better idea about what is the problem.
The biggest problem that I have run across with this device is that the partition table gets mangled some how and therefore odin does not know where to put data. This can ususally be fixed by flashing a custom kernel like Entropy's Daily Driver and then booting into recovery and using partition tools to carefully reconstruct the table...
Then again, the hardware may actually be damaged...
Click to expand...
Click to collapse
Sorry for the bump, but as of August I've been enrolled in the Computer Information Systems program at my local technical school, so I've been really busy with that here lately. We're about to learn how to run Linux using VirtualBox for the first time in our Operating Systems Concepts class. I figured I'd let you guys know so I can maybe get somewhere with fixing my GP using Heimdall while running Linux.
I really hope the hardware isn't damaged.
Update: I downloaded VirtualBox on my laptop this past week and was able to successfully install Linux. I just need to install Heimdall using VirtualBox.