Hi all,
A classmate of my son has a bricked GPS 4.2 (YP-GI1CW/XEN). Another classmate tried to root it. But it got wrong.
By reading and searching guides here, i have rooted some htc phones and succesfully tried several roms, so i offered to take a look.
I did not know this player before and i dont know what happened to it. The only think my son has heard is: someone rooted it, installed a rom, made it empty again, searched for the right software (rom), but could not find it.
When we got the phone it only showed the logo of galaxy S2. There is no sd-card inside.
I spend hours of reading, finding the download mode (3-button), odin, heimdall, kies etc.
Tried everything, but can't get it done
Could anyone please help me?
Download method works
The 3-button method works and gets the player in download mode.
Info on screen: (WITHOUT usb connection!)
Odin mode
Product name: YP-GI1
Custom binary download: yes (13 counts)
Current binary: custom
downloading....
do not turn off target!!
Click to expand...
Click to collapse
I tried and maybe did stupid things
I have tried heimdall and kies. Kies does not see the player. Heimdall does, but it did not work or i could not work with it.
Installed and uninstalled Heimdall following their textfile.
I unstalled Kies also. Cleaned up my computer. Updated java. Used ccleaner. etc. Removed unused devices, with 'device remover'
Once or twice i clicked the "re-partition" in odin. With or without PIT-file. Now I read, that this could brick your phone. :silly:
I tried all tabs, now i know i should only use the PDA-tab.
I might have done more stupid things.
I found "one-click" in http://forum.xda-developers.com/showthread.php?t=1153310
It took me a while before seeing that not all things where good for this player type. When rooting htc, a wrong rom won't brick your phone, so i did not take it too seriously.
I tried 1 or 2 roms, before seeing that they where for other player versions.
I tried the GalaxyPlayer-Bootloader.zip from http://forum.xda-developers.com/showthread.php?t=1386669
Now i see it is specially for player 5.0.
Here i also used the partition file.
At last i did:
Installed samsung usb drivers again: "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0.exe"
From: http://forum.xda-developers.com/showthread.php?t=961956
When connecting the player to the computer (while already in download mode), windows start 'downloading' the samsung drivers again...
Dont know why and if this can be a problem.
Tried ADB in command, but 'adb devices' does not give a list, but odin seems to work at first.
Odin (3 v3.07) recognizes it and says:
<ID:0/010> Added!!
and: "0:[com100]"
Now in Odin I first uncheck ALL checks like: repartition, auto reboot and refresh time and the others.
I did try the "NAND ERASE" option. Erasing looks to hang, but at last Odin comes back and gives a fail on flashing.
Between every odin try, I remove the battery, unconnect usb and restart the download mode, then connect again, then start Odin again.
Now I tried 3 roms/kernels:
- CWMStockGI1 kernel.tar (http://forum.xda-developers.com/showthread.php?t=2198444)
- yp-gi1cw.factoryfs.rooted.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
- yp-gi1cw.kernel.stock.tar (http://forum.xda-developers.com/showthread.php?t=1884071)
Odin responds when flashing:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> normalboot.img
<ID:0/010> NAND Write Start!!
Click to expand...
Click to collapse
Then nothing.....
On unconnecting:
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
I am out of options
Please help. :crying:
Stop before you actually brick it!!!
STOP EVERYTHING RIGHT NOW!!! First thing's first, this is a samsung device and not a HTC device. You screw up flashing this with the wrong device rom and you are screwed. right now, you are lucky in that the state of the device is currently in the state of what is called a softbrick or download only. you need to get stock files for this exact device, preferably able to be used with odin. then after that you can focus on rooting the device. honestly, dont touch the device right now, post a fourm under q and a asking for who has stock recovery files for a 4.2 international version, (i am guessing that you have the international version due to what your location is set as.) once you get those, then flash them with odin. then once it is working again, you can use this exploit to root it.
http://forum.xda-developers.com/showthread.php?t=1312859&highlight=rooting
good luck.
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
joly said:
Thanks for your reply.
I was indeed aware that i should not touch the player, until i got feedback
Though I am a bit suprised that flashing a wrong rom could get me into a hard brick.
I will look for the recovery software you mentioned or ask for it.
Click to expand...
Click to collapse
in terms of the recovery images, your going to need to ask someone with a 4.2 to get them off of theirs and send them to you. odin and hemidall are avaiable in the galaxy player all in one forum at the top of the development page.
interms of the wrong image hard bricking a device, it is possable with samsung devices (i've done it once before and have learned to be carefull). Most samsung galaxy player roms not only contain the rom, but also a kernel. if a kernel that was not made for your device is flashed on to it. it might as well be a hard brick because with out a jtag box, you will never get it working again.
I hope you are able to obtain the files and i wish you the best of luck.
Related
Hi there!
I am desperate!
Can't root my new SG2!
Here is what comes in odin:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<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> zImage
it freezes there and the phone stays in download mode forever.
I also used Gingerbreak 1.10 but it stays in epxloit phase forever...
The phone is baught in Greece, provider is Cosmote and Kernel is:
[email protected] #2
I cant root it!!!!
OK some more info.
It stays in Download mode forever. When I remove battery and start it it starts and boots fine (not rooted though)
Every method fails!
I even used the automated odin 185 process again failed and froze at zimage
I also downloaded the patched KF3 tar for my kernel, used odin in download mode, again frozen forever!
Nothing I can do!!!!
It doesn't seem like you read or followed any guide.
Go to the dev forum, cf-root thread and follow the instructions. Make sure you installed Kies to get the drivers and then close Kies and kill EVERY process in task manager that belongs to Kies. Now you can use Odin, according to the guide!
Sent from my GT-I9100
d3l1 said:
It doesn't seem like you read or followed any guide.
Much more fun if they totally fail to read any instructions and make it up as they go along .
jje
Click to expand...
Click to collapse
Instead of throughing accusations on people having problems try to be more helpful or dont post at all.
I was the owner of a Samsung Galaxy S and now a S G 2.
I am also the Head IT and the man responsible for a group of S.A. companies that have over 250 mobile connections.
I have rooted many devices before S G 2 (HTC mainly and a few S Galaxy S) and it's something I can do very easily thanks to the very helpful guides that exist here in this forum that even non-experienced users can very easily follow.
The S G 2 was the first phone to cause such a problem to me!
The answer to my problem has been found by me and it was no other than the USB ports I used.
For some reason they were stuck and when the process would begin at odin it would freeze at the zimage task and stay there forever. The Gingerbreak 1.10 doesnt seem to work anyway for my kernel.
After switching USB port for the third time the whole process completed successfully.
Installing a fresh Kies copy (I never use it but the usb drivers are there) was something I did even before receiving the phone from the post.
A different solution would be to use 32 bit O.S. because 64bit O.Ses have such problems in other devices as well (a week ago I tried jailbreaking an IPhone 4 and a thousand errors occured while trying to upgrade to 4.3.3. When I installed Itunes in XP everything was perfect and everything was done flawlessly)
So there u have it ppl if you get such error in rooting try switching usb port or use 32 bit operating systems.
S G 2 Rooted (d3l1 - JJEgan thanks for nothing I guess)!
With the lack of information you provided there was hardly anything to help you with. So I assumed and started explaining the basics. My fault if it offended you, it wasn't meant that way!
And it's correct to assume a software problem given the very little information in post 1 which mostly is forgetting to end the Kies processes causing Odin to hang/crash.
So maybe you should provide more information as to what can be ruled out, post 1 gives us nothing to rule out.
I admit that the information I gave could not make things clear on what my knowledge and my experience is. However if you wanted more info you could ask and I would be happy to provide. Your post was not that offending but the next one was...I found it very upseting asking for help and getting replies like that. Perhaps my lvl was unclear....but someone can always ask. Your post alone wouldnt bother me so much. I guess its the combo with the next one. Anyway no prob mate!
Sent from my GT-I9100 using XDA App
I am also the Head IT and the man responsible for a group of S.A. companies that have over 250 mobile connections
?????????????????????
So there u have it ppl if you get such error in rooting try switching usb port
Thats plastered all over the forum mate though i will agree that you need to use the search button and read a lot of disjointed posts to get a lot of information .
I apologise for putting in print my thoughts that you are an idiot .
jje
You are So pathetic... So my guess is that if from software point of view everything is perfect and u get the yellow COM signal in Odin and u have selected the correct patch for your Kernel and Odin starts fine and freezes at some point in a PC you have rooted several other phones your guess would be the usb port. Send me a CV and I will pass it to my boss so that you can take my job! Looking forward to it!
p.s. Find a girlfriend. A real one not Lara Croft. Might help u a bit and relax your mind!
Sent from my GT-I9100 using XDA App
I have gone through just about everything I can think of, scouring the forums included to figure out my issue but nothing has worked. My phone can connect through my pc with Odin, but only enough to install a rooted rom (currently running jellybeans), and only a handful actually stick. However I try and connect my device to run Adam's unlock steps and the phone won't even try and go to MTP mode. When I plug it into a computer it just charges nothing else. I have tried on several machines and it has given me same issue. I have gone through every driver under the sun, nothing seems to work. Please, can anybody help me?
MRJ88 said:
I have gone through just about everything I can think of, scouring the forums included to figure out my issue but nothing has worked. My phone can connect through my pc with Odin, but only enough to install a rooted rom (currently running jellybeans), and only a handful actually stick. However I try and connect my device to run Adam's unlock steps and the phone won't even try and go to MTP mode. When I plug it into a computer it just charges nothing else. I have tried on several machines and it has given me same issue. I have gone through every driver under the sun, nothing seems to work. Please, can anybody help me?
Click to expand...
Click to collapse
Have you tried what fixed my issue? Using ODIN to PDA the Revision3 and follow steps from there?
kaminczak said:
Have you tried what fixed my issue? Using ODIN to PDA the Revision3 and follow steps from there?
Click to expand...
Click to collapse
Can you please direct me to the revision 3 I keep hearing referenced? Thanks
I haven't had any success installing revision3. I just moved from root66 over to jellybeans. For some reason my phone's being very particular over what roms it takes. I get errors trying to install just about any rom, the stock image included. Jellybeans and root66 are the only roms my phone has taken without issue. I'm really hoping it's not the damn phone, since verizon recognizes it as a 4g test device they won't replace/service it :/
Error I get from revision3:
<ID:0/003> Added!!
<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.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> FAIL!
NB2A said:
Can you please direct me to the revision 3 I keep hearing referenced? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2039411
It's essentially the closest to stock image that's available, I believe.
Revision 3 issue to start
kaminczak said:
http://forum.xda-developers.com/showthread.php?t=2039411
It's essentially the closest to stock image that's available, I believe.
Click to expand...
Click to collapse
Thanks but my problem seems to be as per the instruction and video it should be a tgz file
when unzipped it is not though
MRJ88 said:
I haven't had any success installing revision3. I just moved from root66 over to jellybeans. For some reason my phone's being very particular over what roms it takes. I get errors trying to install just about any rom, the stock image included. Jellybeans and root66 are the only roms my phone has taken without issue. I'm really hoping it's not the damn phone, since verizon recognizes it as a 4g test device they won't replace/service it :/
Error I get from revision3:
<ID:0/003> Added!!
<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.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> FAIL!
Click to expand...
Click to collapse
When you load Odin, do you load the Rev3 using the PDA? Without any bootloaders or pit files..
Yes I do.
MRJ88 said:
I have gone through just about everything I can think of, scouring the forums included to figure out my issue but nothing has worked. My phone can connect through my pc with Odin, but only enough to install a rooted rom (currently running jellybeans), and only a handful actually stick. However I try and connect my device to run Adam's unlock steps and the phone won't even try and go to MTP mode. When I plug it into a computer it just charges nothing else. I have tried on several machines and it has given me same issue. I have gone through every driver under the sun, nothing seems to work. Please, can anybody help me?
Click to expand...
Click to collapse
I have the same issue connecting to my computer after I installed adb shell and unlocked my phone. I tried to fix this myself but I haven't found "actual fix" for it. However, I can temp fix it, and it works every time. First, make sure debugging mode is unchecked. After that, connect the device as PTP(If your computer is trying to install a driver to your computer, let it install). If autoplay pops up from your computer, switch the connection to MTP. If it doesn't work, reboot your computer and try again. I hope this works.
dcdgoth said:
I have the same issue connecting to my computer after I installed adb shell and unlocked my phone. I tried to fix this myself but I haven't found "actual fix" for it. However, I can temp fix it, and it works every time. First, make sure debugging mode is unchecked. After that, connect the device as PTP(If your computer is trying to install a driver to your computer, let it install). If autoplay pops up from your computer, switch the connection to MTP. If it doesn't work, reboot your computer and try again. I hope this works.
Click to expand...
Click to collapse
I don't have access to mtp and ptp mode. When I plug it into my computer it shows up as a qualcomm device without drivers and just charges. No amount of playing with drivers has fixed it.
MRJ88 said:
I don't have access to mtp and ptp mode. When I plug it into my computer it shows up as a qualcomm device without drivers and just charges. No amount of playing with drivers has fixed it.
Click to expand...
Click to collapse
PM me.... I think I can help you with this
Yeah I've given up on this phone. I'm taking the Verizon replacement route. Thanks for everybody's input.
Hey everyone, so I've been using a Cyanogenmod S2 for the past few months and everything was great.
Until recently it started to reboot by itself,
until one day when I woke up "Kernel panic upload mode" was on the screen.
I rebooted the phone,
and then was greeted with a black screen after the Samsung Galaxy S2 screen.
The buttons do light up, but nothing else could be done.
I entered download mode to flash a new firmware,
but then somehow it failed and then it says connect to computer to redownload firmware or something when I boot it on right now.
I can't get it to flash anything at all, whenever I use odin it gets stuck at setup connection,
I installed Kies but it doesn't recognize my phone as well, neither does my computer....
Need help. Desperately. :crying::crying::crying:
Can u enter cwm
Sent from my GT-I9100 using xda premium
stopro said:
Can u enter cwm
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No I can't..
Can only enter Download mode
Then you need to flash a stock rom with Odin. You don't really have any other option.
MistahBungle said:
Then you need to flash a stock rom with Odin. You don't really have any other option.
Click to expand...
Click to collapse
<OSM> T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's the problem, I can't seem to get Odin to flash no matter what, I've already tried different versions of Odin,
but they always end up with either this (failure) or stuck at setup connection..
Any ideas, please?
There's been many threads re: this issue on here over the past week listing the troubleshooting steps to go thru when Odin won't work, search for those threads (Immortalneo has listed them, go through his posts as a shortcut).
Edit - Hang on a minute, what model number do you have; what's the sticker on the phone chassis under the battery say ?
MistahBungle said:
There's been many threads re: this issue on here over the past week listing the troubleshooting steps to go thru when Odin won't work, search for those threads (Immortalneo has listed them, go through his posts as a shortcut).
Edit - Hang on a minute, what model number do you have; what's the sticker on the phone chassis under the battery say ?
Click to expand...
Click to collapse
I'm using a GT-i19100
I'm going through immortalneo's posts but so far nothing's up..
Am currently following this guide but to no avail, (no .pit file in the compressed .rar file) http://forum.xda-developers.com/showthread.php?p=40154030&highlight=+pit#post40154030
Edit: I think it's a GT-i19100G because I vaguely remember such a thing on the startup screen...
If you've got an I9100, why are you trying to flash firmware for T-989 ?? I suggest you go back to Samfirmware & get an I9100 stock rom for starters.
Ignore that guide; your phone isn't bricked. However, it may well be if you try & flash a PIT file (Although, if you've somehow flashed firmware for a different model including PIT, you may need to at some point. Just not yet). OK. This is the first & last time I'm posting this stuff for the next month:-
Stuff to try when Odin doesn't work
-----------------------------------
*Must run Odin as administrator in Windoze.
*Ensure Kies & all it's processes aren't running in Windoze task manager. Kill them if they are (choose 'kill process tree').
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Check the rom/kernel you download for corruption. Programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all this fails, try a different PC. And if it won't work first time on another PC, go thru the above steps on that PC.
Hello everyone ..
It could solve the problem? I am in a very similar, and have helped me a lot, but none of the options so far have been effective. I'm starting to resign myself to use it as a paperweight, but still have not lost hope.:crying:
Geeenie said:
I'm using a GT-i19100
I'm going through immortalneo's posts but so far nothing's up..
Am currently following this guide but to no avail, (no .pit file in the compressed .rar file) http://forum.xda-developers.com/showthread.php?p=40154030&highlight=+pit#post40154030
Edit: I think it's a GT-i19100G because I vaguely remember such a thing on the startup screen...
Click to expand...
Click to collapse
Stop Now :0 ! You are trying to install a T-Mobile T989 firmware.It's a Galaxy s2 too,but from T-Mobile.It's not the same.Search on Sammobile for an I9100 firmware,preferable Android 4.0.3 or 4.0.4.Of course it gives an error,because it's not the right firmware.
Now this thread is just fun!
Sent from the little guy
Hi guys,
I'm in a bit of trouble. A few weeks ago I successfully installed CM 10 and everything was fine and working normal.
Then (I can't remember how) I must have somehow repartitioned or corrupted the file system on the device.
I am now stuck in a boot loop and can only go as far as download and recovery mode.
The message I get in recovery is 'E: failed to mount EFS'. I can see my EFS directory has been deleted/moved/corrupted and I believe I have done way more damage to the phone trying to repair it than before.
I have tried everything I can think of, stock ROM, different ROM, nandroid back up etc.
Although I can still get to recovery and download mode im pretty sure its done.
I have tried various tool kits such as the Samsung galaxy s3 toolkit and EFS professional etc, aswell as using the Android SDK and runing ADB commands through that to no avail. Half of the solutions I find on here that have helped other require USB debugging mode to be enabled, and I can't enable it because I cant turn the phone on, and there doesn't seem to be a command in ADB that will allow me to (Failsafe from Samsung).
I then arranged for teh phone to be serviced but I need to reset the flash counter. I cant use triangle away as I can't get into the phone and I can't seem to be able to do it through ADB. I don't think USB jigs reset the flash counter on the S3.
Its very frustrating as I seem to get somewhere then realise I need something else which I don't have access to.
If I can't repair the phone then I can send it off, but I need to be able to reset the flash counter,
Is their anyone here that could help me out? I have learned more about phones in this short period and its very interesting. well if your phone works..
I would be extremely grateful, Thank you
Rashpalio said:
Hi guys,
I'm in a bit of trouble. A few weeks ago I successfully installed CM 10 and everything was fine and working normal.
Then (I can't remember how) I must have somehow repartitioned or corrupted the file system on the device.
I am now stuck in a boot loop and can only go as far as download and recovery mode.
The message I get in recovery is 'E: failed to mount EFS'. I can see my EFS directory has been deleted/moved/corrupted and I believe I have done way more damage to the phone trying to repair it than before.
I have tried everything I can think of, stock ROM, different ROM, nandroid back up etc.
Although I can still get to recovery and download mode im pretty sure its done.
I have tried various tool kits such as the Samsung galaxy s3 toolkit and EFS professional etc, aswell as using the Android SDK and runing ADB commands through that to no avail. Half of the solutions I find on here that have helped other require USB debugging mode to be enabled, and I can't enable it because I cant turn the phone on, and there doesn't seem to be a command in ADB that will allow me to (Failsafe from Samsung).
I then arranged for teh phone to be serviced but I need to reset the flash counter. I cant use triangle away as I can't get into the phone and I can't seem to be able to do it through ADB. I don't think USB jigs reset the flash counter on the S3.
Its very frustrating as I seem to get somewhere then realise I need something else which I don't have access to.
If I can't repair the phone then I can send it off, but I need to be able to reset the flash counter,
Is their anyone here that could help me out? I have learned more about phones in this short period and its very interesting. well if your phone works..
I would be extremely grateful, Thank you
Click to expand...
Click to collapse
I don't think that you can now recover it by yourself. have you tried pit file to repartition it again, i think your partitions are deleted.. why don't you once try pit file to repartition the phone, else you wont have any other option than paying money to repair it..
Imo you flashed with wrong pit. Try m0.pit.
GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
Thanks guys.
Is this the correct pit?
uploaded.net/file/f4544vm0
S3 white 16gb gt 19300
Also, is their anyway to reset the flash counter without using triangle away or to force run triangle away through ADB (which I doubt as I don't think ADB will automatically start the required function etc as its not booted into adroid)?
Rashpalio said:
Thanks guys.
Is this the correct pit?
uploaded.net/file/f4544vm0
S3 white 16gb gt 19300
Also, is their anyway to reset the flash counter without using triangle away or to force run triangle away through ADB (which I doubt as I don't think ADB will automatically start the required function etc as its not booted into adroid)?
Click to expand...
Click to collapse
that one is for samsung galaxy s3 64GB version. i have uploaded that earlier, get it from here: http://goo.gl/X64R6O
suyash1629 said:
that one is for samsung galaxy s3 64GB version. i have uploaded that earlier, get it from here: goo.gl/X64R6O
Odin seems to be stuck at 'Set Partition'
'<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMC3_I9300NEEEMC1_I9300XXEMB6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> tz.img
<ID:0/003> NAND Write Start!! '
Now someone's gonna say 'I9300XXEMC3_I9300NEEEMC1_I9300XXEMB6_HOME.tar.md5' is wrong haha.
I'm trying to use 'GT-I9300_mx_20120220.pit'
Thanks
Click to expand...
Click to collapse
Now it wont boot into recovery..
Is there anyway I can further break the phone so they can't get into download to check the binary count. Or is that inconsequential...
Rashpalio said:
Now it wont boot into recovery..
Is there anyway I can further break the phone so they can't get into download to check the binary count. Or is that inconsequential...
Click to expand...
Click to collapse
that only happens if the motherboard is completely dead, like in SDS(not sure because i think phone boots into download mode showing product name nil), you cant do it yourself.. is your product code nil? have you checked maybe that can be SDS..
Sent from my GT-I9300
suyash1629 said:
that only happens if the motherboard is completely dead, like in SDS(not sure because i think phone boots into download mode showing product name nil), you cant do it yourself.. is your product code nil? have you checked maybe that can be SDS..
Sent from my GT-I9300
Click to expand...
Click to collapse
Im sure its not SDS just bricked from the start and more damage done to repair it. Now it won't boot into recovery after trying the .pit which was a last resort. I need to send it off to Samsung but the count is 15, ROM is Samsung Official and the last line is custom. (Im not with my phone I'm just remembering.)
Im sure its beyond repair i just need to reset the flash counter.
Thanks
i got you bro use this pit file it will fix it
[Q] SII (Vodafone NL) with "Download mode" only, stuck on NAND Write Start!!
Hi all,
I have a SGS II from Vodafone NL that was not vendor locked, unfortunately I don't know more about it as I didn't care about firmware, kernel and the such. The phone is 2y 9m old. It all started with a low battery reboot, battery was at 0% and while plugged in was restarting shortly after boot, some too demanding applications that wanted to do their thing immediately after boot. This happen 2 or 3 times, on one of the boots I saw the android updated (green robot with spinning mesh), it was really short and I recall something about updating one file or so. Didn't pay much attention, the phone booted up properly when the battery reached 1%. After a few hours in which I used the phone a few times I found the phone shutdown and on boot I had the boot logo loop. Not knowing what to do I went into "Recovery mode" (Vol up + Home + Power) and issued a factory reset. It did something and I didn't pay much attention to it. There were a lot of errors related to /system /cache and something else that was not accessible. I was thinking that the on-board emmc might have died or at least part of it is. After the factory reset the phone has only the battery logo and "Download mode" (Vol down + Home + Power) only. I don't know what kernel I had nor what OS version it was on, I've updated via Kies some time ago, autumn 2013 maybe.
I've downloaded from sammobile:
I9100BULPG_I9100VDFLP9_I9100BULP8_HOME.tar.md5 Feb 2013 Ver 4.1.2
I9100BULPG_I9100VDFLP9_I9100BULP8_HOME.tar.md5 Sep 2012 Ver 4.0.3
When trying to upload them with Odin 1.85, 3.04 and 3.07 they fail at "NAND Write Start!!" with no other error message, just the normal succeed 0 / fail 1 which I find kinda dumb. Tell me what the error was, the device surely has said something or it timed out. I've tried this on 2 different computers both with Windows7.
After all this failed I tried flashing:
Siyah-s2-v4.1.5.tar
Same error from Odin but something changed in the "Download mode", now it says "CUSTOM BINARY DOWNLOAD: YES (1 counts)", before it was 0. The current binary is still saying Samsung official. The phone is still not booting and the "recovery mode" is still not there.
My questions:
Is there any way I can connect to it via adb and maybe have a shot at looking at it's disk layer? Saw that dd can be used within the adb shell IIRC. I do have some linux/unix filesystem recovery experience.
I saw that they use the .PIT file to change the sector allocation and avoid the damaged parts of the emmc. In order to do that I need to somehow give it a booting kernel. Is there any way of doing that? Maybe boot another device that can attach the emmc.
Should I try heimdall? Can it connect to the device even in "download mode"? I need to install one linux machine for this as I have only windows and BSDs around.
Is there any way for me to reliably find out the model of phone I have?
Are there any other things I can try to recover it or can I consider it's emmc dead?
Thank you.
Pit files can help ...as u already knw..
No pit file flashing doesn't needs working recovery..
U can flash pit file by odin itself...
Did u tried flashing a pit file?
andrei693 said:
Is there any way for me to reliably find out the model of phone I have?.
Click to expand...
Click to collapse
Sticker on phone chassis under battery.
doctor_droid said:
Pit files can help ...as u already knw..
No pit file flashing doesn't needs working recovery..
U can flash pit file by odin itself...
Did u tried flashing a pit file?
Click to expand...
Click to collapse
Haven't tried a pit file as I thought that I need to know which part must be taken out from the sector allocation first. Is it just trial and error?
If yes, which pit files should I try?
Thanks.
MistahBungle said:
Sticker on phone chassis under battery.
Click to expand...
Click to collapse
On the sticker I have:
Model: GT-I9100
SSN: -I9100GSMH
FCC ID: A3LGTI9100
IMEI and S/N
Don't know what to make out of these tough.
Why ? It's pretty self explanatory. It says you have an I9100, so you have an I9100. The rest of that stuff on the sticker is irrelevant.
So...if you do decide to flash a PIT, make sure it's an I9100 PIT or you'll definitely end up with a 116gm plastic paperweight.
MistahBungle said:
Why ? It's pretty self explanatory. It says you have an I9100, so you have an I9100. The rest of that stuff on the sticker is irrelevant.
So...if you do decide to flash a PIT, make sure it's an I9100 PIT or you'll definitely end up with a 116gm plastic paperweight.
Click to expand...
Click to collapse
I found this thread with PIT files http://forum.xda-developers.com/showthread.php?t=1667886, but as I said, I'm clueless as which of the I9100 models this is and which archive should I chose, don't really remember if 8GB/16GB/32GB, plus there is a i9110g there. I know this sounds ignorant but I was with my phone, will not happen in the future.
Also there is this link: http://forum.xda-developers.com/showthread.php?t=1823918, which is supposed to be a partition scanner but I find it confusing. In my case I can't flash anything on the phone so it seems impossible to use the scanner, is that correct? Are there cases in which parts of your emmc can die but you'll still be able to boot a kernel or have/use "recovery mode"?
Status update.
I tried to flash Siyah-s2-v5.0.1.tar with both Odin 3.07 and 1.85.
3.07 said the same error immediately after NAND Write Start!! I had to close Odin, remove battery and upon restart the phone has the triangle present but only download mode works. It incremented the CUSTOM BINARY DOWNLOAD and CURRENT BINARY has changed to CUSTOM.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
1.85 just stayed for ~20 min on "NAND Write" and had to close it myself. Again had to remove battery has phone was not rebooted by Odin. Again the "BINARY DOWNLOAD" counter was increased. The phone still has "download mode" only and the triangle present on normal start.
I don't understand why Odin fails to reboot the phone and returns error upon writing.
I'm still a bit reluctant to use PIT files as I still don't know for sure which one to chose. Keeping it as a last resort tough.
Will try different kernels and I'm still searching for a bootloader to try and write, maybe somehow I can get it to "recovery mode" so I can use adb to see the partitions it has. Can't find any link for this.
I didn't backup EFS partitions and this is my biggest concern in using PIT files. If I understood correctly writing a new PIT file will delete all partitions. Is it possible then to still recover the device?
If anyone has any ideas ...
andrei693 said:
Status update.
I didn't backup EFS partitions and this is my biggest concern in using PIT files. If I understood correctly writing a new PIT file will delete all partitions. Is it possible then to still recover the device?
If anyone has any ideas ...
Click to expand...
Click to collapse
Here' s the bible, did you read it? http://forum.xda-developers.com/showthread.php?t=1457458
Every single word there is important.
Also http://forum.xda-developers.com/showthread.php?t=2345831 has some good tips, but you might have already read it
Here's my experience with a very similar problem: i got the same Odin error, nothing could be written and eventually decided to flash PIT file... Result: phone HARD bricked, no download mode anymore. I suppose the PIT file flashing failed as all of the rest.
IT's the last resort as, if it fails, your phone wil be completely dead (at least for the software part), no charging anymore, no download mode, and you will either need to revive it with a JTAG or change the motherboard.
SO before doing it, try and try everything slowly and using your mind.
Now going back to my problem, it was an emmc hardware problem, even JTAG riff box couldn't revive it (errors pointed to hardware fault) and i had to change the mainboard. I bought a phone with broken display for around 50$ and replaced my mainboard. In a service center you will likely be asked at least 150$.