Let me just start out by saying that I am a noob at this stuff, and that I don't have much experience, hence why I am here, cause i screwed up.
Basically, I have a player 4.0 that i am trying to get the stock ROM reinstalled on that is not being "cooperative". I have followed many different XDA forum guides, downloaded about a dozen different files, and nothing is working. Here is what works/doesnt work:
- I can access the Download function (hold down volume and plug into computer)
- I have a windows 7 computer
- I downloaded and tried three different versions of Odin, all with no success.
- Downloaded about 6 different files of the stock rom, each in a .tar or other compressed (i think) file type (even tried Icy Fusion, no luck).
- Downloaded heimdall and tried to make the partitions myself, no success.
I am hoping someone on this forum can please help me through the process of restoring my droid back to either the stock ROM or some other ROM, I just want my droid working again.
Also, I have read a multitude of similar XDA forums on this issue (yes I saw the "your a noob XDA" video and i am only making a thread because im desperate) and have had no luck.
Thanks in Advance,
TechnoD11
TechnoD11 said:
Let me just start out by saying that I am a noob at this stuff, and that I don't have much experience, hence why I am here, cause i screwed up.
Basically, I have a player 4.0 that i am trying to get the stock ROM reinstalled on that is not being "cooperative". I have followed many different XDA forum guides, downloaded about a dozen different files, and nothing is working. Here is what works/doesnt work:
- I can access the Download function (hold down volume and plug into computer)
- I have a windows 7 computer
- I downloaded and tried three different versions of Odin, all with no success.
- Downloaded about 6 different files of the stock rom, each in a .tar or other compressed (i think) file type (even tried Icy Fusion, no luck).
- Downloaded heimdall and tried to make the partitions myself, no success.
I am hoping someone on this forum can please help me through the process of restoring my droid back to either the stock ROM or some other ROM, I just want my droid working again.
Also, I have read a multitude of similar XDA forums on this issue (yes I saw the "your a noob XDA" video and i am only making a thread because im desperate) and have had no luck.
Thanks in Advance,
TechnoD11
Click to expand...
Click to collapse
Well first of all, welcome to XDA. Hmm, it's better that you use the heimdall method of reflashing to stock ROM.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Well first of all, welcome to XDA. Hmm, it's better that you use the heimdall method of reflashing to stock ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the welcome! I would like my droid working ASAP, so where do i start? remember, i can access the download function. i have the samsung usb drivers installed. If someone could post some detailed, step-by-step instructions, that would be great!
TechnoD11
TechnoD11 said:
Thanks for the welcome! I would like my droid working ASAP, so where do i start? remember, i can access the download function. i have the samsung usb drivers installed. If someone could post some detailed, step-by-step instructions, that would be great!
TechnoD11
Click to expand...
Click to collapse
Check on the reference(all-in-one) thread in the development section. In the recovery section, click the first link. I can't post the link because I'm on my tablet.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Check on the reference(all-in-one) thread in the development section. In the recovery section, click the first link. I can't post the link because I'm on my tablet.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
This link (from the recovery section) brings me to a guide i already tried that did not work for me. when i perform those instructions, my droid boots into "android system recovery <3e>". from there, i reboot, or try to wipe the cache, or data (factory reset), or both. after reboot, just goes back into recovery. There is an option for applying update from SD card. is it possible i can load the rom on my SD card and flash it through there?
TechnoD11
Don't call an android device a droid unless you actually own a droid device (Motorola Droid Razr, Droid X, etc.) It drives people like me bonkers
Anyways, the best way to handle this is to solely use Heimdall. This thread should take you through the steps quite nicely, thanks to zaclimon. However, you have to read everything carefully, as you don't want to flash the wrong files within heimdall. If you own an International device (the one with the physical home button), follow the INTL walkthrough. If not, use the US one.
All you will need is the PIT file and the full recovery package, never the Odin. I recommend you try it again if you already have, as you may have done something wrong. If the problem still prevails, I will give you step by step instructions, if not done so already.
LuthicaBlue said:
Don't call an android device a droid unless you actually own a droid device (Motorola Droid Razr, Droid X, etc.) It drives people like me bonkers
Anyways, the best way to handle this is to solely use Heimdall. This thread should take you through the steps quite nicely, thanks to zaclimon. However, you have to read everything carefully, as you don't want to flash the wrong files within heimdall. If you own an International device (the one with the physical home button), follow the INTL walkthrough. If not, use the US one.
All you will need is the PIT file and the full recovery package, never the Odin. I recommend you try it again if you already have, as you may have done something wrong. If the problem still prevails, I will give you step by step instructions, if not done so already.
Click to expand...
Click to collapse
First try: Heimdall Crashed
Second try: heimdall crashed again
I have included the Status log for viewing:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
(removed link cause im a noob)
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
(removed link cause im a noob) lol
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
here is the list of files i am using (that I downloaded from a different post):
PIT: ypgi1cb.pit
CACHE: cache.rfs
PARAM: param.lfs
DBDATA: dbdata.rfs
FACTORYFS: factoryfs.rfs
KERNEL: zImage (listed in windows as just a 'file')
following the heimdall crash, my SAMSUNG GALAXY PLAYER (cough cough droid cough) reboots and enters...drumroll.... recovery mode!
If someone could explain to me what i might have done wrong, or if there is something else i should try, let me know
thanks for the help,
TechnoD11
THANK YOU COMMUNITY!!!
well, i decided to try it for a third time, and third time is the charm!. It, for some unknown reason, decided to work, and the stock ROM is now back on my droid!
Again, thanks all for your help.
Lesson learned: don't download stuff for the Galaxy player 5.0 thinking it will work on yours (4.0).
TechnoD11
Oh, and administrators, you can delete this thread.
Related
I'm a mac user, and Kies is still in beta and can't perform updates, (its a pos anyways and I wanna refrain from using it either way).
So the only other alternative for Kies is Heimdall which is similar to Odin, but doesn't have much documentation for the newer version 1.3 other than the readme file that came with it that I have read but still am not confident enough to flash anything.
So can someone please write up a tutorial on how to use it or link me to one. I mainly only want to update my firmware keeping it stock and possibly root with CF-Root while I'm at it, if CF-Root is gonna even work with heimdall.
Thanks in advance.
This should cover it
Woaw. Thank you very much buddy ^_^
Not to hijack the OP's thread, but I have another and related question regarding Heimdall for mac:
When unraring archives either from Intratech or Samfirmware, all the extracted files are of the type .bin and/or .img. I really can't figure out how to get the proper .rfs files that should be used for flashing. Anyone able to show me in the right direction for the answer? I've searched up and down both on the forum and on Google
As of the time being I have a Bootcamp partition only for the sake of using Odin, and I would really like to have those 20GB's back as it should be unnecessary to use Odin in Windows when Heimdall looks like a great tool for the mac (when the proper files are used )
Hrti said:
Not to hijack the OP's thread, but I have another and related question regarding Heimdall for mac:
When unraring archives either from Intratech or Samfirmware, all the extracted files are of the type .bin and/or .img. I really can't figure out how to get the proper .rfs files that should be used for flashing. Anyone able to show me in the right direction for the answer? I've searched up and down both on the forum and on Google
As of the time being I have a Bootcamp partition only for the sake of using Odin, and I would really like to have those 20GB's back as it should be unnecessary to use Odin in Windows when Heimdall looks like a great tool for the mac (when the proper files are used )
Click to expand...
Click to collapse
Heimdall should flash the .bin's or .img's, Heimdall should flash just about anything.
I dont have an OSX machine and havent had time to build a virtualbox img so i cant test
I tried to follow your instructions @veyka but heimdall won't work
When I try to get heimdall to detect my phone it just says "FRONTEND ERROR: Heimdall crashed!"
I tried uninstalling/reinstalling heimdall, still didn't work, then uninstalled Kies cuz it might be interfering but it still doesn't work!
Man I really want this to work....
hank00k said:
I tried to follow your instructions @veyka but heimdall won't work
When I try to get heimdall to detect my phone it just says "FRONTEND ERROR: Heimdall crashed!"
I tried uninstalling/reinstalling heimdall, still didn't work, then uninstalled Kies cuz it might be interfering but it still doesn't work!
Man I really want this to work....
Click to expand...
Click to collapse
Just.. weird...
I do wish I could be more help, but I have no OSX machine to test it on.
Are you on 10.5? As another thread says that it wont run on it, but just crashes, but an upgrade to 10.6 made it work.
Yeh.. Im recommending upgrading your OS to fix a flashing issue, go me.
veyka said:
Just.. weird...
I do wish I could be more help, but I have no OSX machine to test it on.
Are you on 10.5? As another thread says that it wont run on it, but just crashes, but an upgrade to 10.6 made it work.
Yeh.. Im recommending upgrading your OS to fix a flashing issue, go me.
Click to expand...
Click to collapse
I'm on 10.7
I think its not compatible with 10.7 cuz some other apps had to be updated to work properly, including stupid Kies... So I guess downgrading is the solution lmao or waiting for it to be updated
And you've been plenty help by linking me to your other post, now at least I know that it should work...
hank00k said:
I'm on 10.7
I think its not compatible with 10.7 cuz some other apps had to be updated to work properly, including stupid Kies... So I guess downgrading is the solution lmao or waiting for it to be updated
And you've been plenty help by linking me to your other post, now at least I know that it should work...
Click to expand...
Click to collapse
Well, Im not sure, no one in that thread got it to work in the end, but I know people on linux who have flashed with it, and I have on windows so it should work!
Odin might be a iffy PoS but its a iffy PoS that works most of the time.
I've got Ubuntu Linux on an old ibm laptop, so I'll give it a try later.
And I only dream of using Odin but I don't have Windows unfortunately...
I have tried v1.0 and v1.85 of Odin to fix my boot loop. Both said they were successful but in fact it just changed the boot loop's process. Now all that loops is black screen then the Vibrant screen (which I had never seen before). I also tried one click un-brick but the program will not stay open.
I can not enter recovery mode but can still enter DL mode.
This is all a result of trying to install the cyanogenmod using their wiki site (can't post links yet). I had completed installing Clockworkmod recovery as directed by the wiki site. It started when rebooting after installing Cmenard's Overstock Kernel.
Anyone who experienced this and was successful in fixing please do help.
Which file did you used when you used odin?
I used 2. The T959UVJFD.TAR and the 512.rar. I used winzip to extract them for Odin.
I did pretty much exactly what the link says. I tried checking repartition on the 4th try or so as well, sorry I can't post links yet....
http ://androidspin.com/2010/08/09/ how-to-restore-or-recover-your-samsung-vibrant/
Ummm usually reverting back to stock jfd through odin always works..
Many of us have been in bootloops before this one is different simply because CM7 is typically an easy flash. You may want to get different files they may not have downloaded to your computer correctly and then try to flash them using Odin. That's the only thing I can assume is the issue at this point.
Sent from my SGH-T959 using XDA App
yup, try a different file. You might want to try odin 1.3 too. Never failed for me.
Sent from my SGH-T959 using XDA App
iynfynity said:
yup, try a different file. You might want to try odin 1.3 too. Never failed for me.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Not really sure what other files to use. Every search I do for restoring to factory settings finds the ones I used. I will try them with odin 1.3 until I find new files.
Wondering if my samsung driver isn't installed properly. Will Odin even read it if it's not?
OK so, I screwed up. I have a sgs4g, DOH. Gona make a thread in the sgs4g section but help is still appreciated if anyone has some.
Exact same issue.
I had the same issue. Actually got it to boot and everything but everything past the Modem step was scrubbed everytime in Odin because the wrong partition was applied. You get this issue if you use the PIT from a Galaxy Vibrant on a Galaxy S 4G.
I was under the impression that the phone I was modding was a Vibrant. Took me a few hours but I eventually got to the bottom of it after reading every Vibrant thread from beginning to end. Here is a link to the post that saved my night.
http://forum.xda-developers.com/showpost.php?p=12806682&postcount=15
The proper PIT file for the Galaxy S 4G. So everyone with this issue just continue as normal and install a current ROM with this PIT.
On a side note.... all these damn Galaxy phones are confusing. No wonder I never wanted one. I am just fine with Motorola devices... The Optimus series is at least a bit better with the letter branding for each carrier. Galaxy series are all just galaxy...
I have tried to read as many posts on this topic as possible, and I haven't found a proper solution. I've found a few threads where the issue was apparently fixed but they never bothered posting how they did it. If there is a thread that addresses and fixes this issue, my apologies and please redirect me.
First off, I've had my phone rooted since February and it has been working fine. I forget exactly what I rooted with but I have the super user app icon. Last week my Fascinate crashed and re-booted into startup wizard, and all my apps were erased, and I kept getting the force close error boxes. I dont know exactly what caused this but think I might have erased super user when I was going through and deleting apps to free up space. When I reboot everything erases and I go into the start up wizard. My internal memory is 0 and I cannot download any apps. I tried to do factory reset but the data could not be wiped. I tried flashing with odin all the possible .tar packages out there and they all get stuck on the movinand.bin file and fails. I've tried flashing in heimdall but couldnt get it to reboot at all. I've booted into cwm, and every time I try to factory reset/wipe data i get the "error mounting data!" message. I know there's definitely a memory problem and a data problem that has been consistent, and everything I've tried can't get around it.
My current temporary fix has been installing the cyanogen mod, which allows me to use the basic phone functions without the force close boxes. I still have the memory issue and cannot receive text messages, and my network settings are deleted when I reboot. Again, I've read quite a bit of threads on this topic and there seems to be a consensus that I might need the original.mbr and stock.zip files, which I tried downloading from that link everyone posts and they dont work. CWM says the .zip file is bad. Also, the link is like 2 years old as well as most of the threads on this topic, and I havent found anything recent. I've also read about using adb shell to address the issue in the HOW TO guide, and it seems i really need those files. Sorry this was long, I just want to make sure I'm not repeating something that has already been addressed and fixed. Please help. Thanks.
JSlice said:
I have tried to read as many posts on this topic as possible, and I haven't found a proper solution. I've found a few threads where the issue was apparently fixed but they never bothered posting how they did it. If there is a thread that addresses and fixes this issue, my apologies and please redirect me.
First off, I've had my phone rooted since February and it has been working fine. I forget exactly what I rooted with but I have the super user app icon. Last week my Fascinate crashed and re-booted into startup wizard, and all my apps were erased, and I kept getting the force close error boxes. I dont know exactly what caused this but think I might have erased super user when I was going through and deleting apps to free up space. When I reboot everything erases and I go into the start up wizard. My internal memory is 0 and I cannot download any apps. I tried to do factory reset but the data could not be wiped. I tried flashing with odin all the possible .tar packages out there and they all get stuck on the movinand.bin file and fails. I've tried flashing in heimdall but couldnt get it to reboot at all. I've booted into cwm, and every time I try to factory reset/wipe data i get the "error mounting data!" message. I know there's definitely a memory problem and a data problem that has been consistent, and everything I've tried can't get around it.
My current temporary fix has been installing the cyanogen mod, which allows me to use the basic phone functions without the force close boxes. I still have the memory issue and cannot receive text messages, and my network settings are deleted when I reboot. Again, I've read quite a bit of threads on this topic and there seems to be a consensus that I might need the original.mbr and stock.zip files, which I tried downloading from that link everyone posts and they dont work. CWM says the .zip file is bad. Also, the link is like 2 years old as well as most of the threads on this topic, and I havent found anything recent. I've also read about using adb shell to address the issue in the HOW TO guide, and it seems i really need those files. Sorry this was long, I just want to make sure I'm not repeating something that has already been addressed and fixed. Please help. Thanks.
Click to expand...
Click to collapse
Is your sdcard broke? Try another if you have...
Use this guide! http://forum.xda-developers.com/showthread.php?p=17050028 you'd want section 2....Use Odin and follow the directions to a tee. You want to restore...so use how to flash eh03
DROID DOES, Apple did...like I forgot when
I don't think my sd card is broken, as I can still save files and music to it. That is how I was able to install cyanogen mod - I did it through clockwork recovery and then install from .zip. Could there still be something wrong with it?
Also, are you absolutely sure I'll be able to flash the eh03 in Odin without it getting stuck on "movinand.bin" ? Every .tar file I've tried so far has had that happen.
JSlice said:
I don't think my sd card is broken, as I can still save files and music to it. That is how I was able to install cyanogen mod - I did it through clockwork recovery and then install from .zip. Could there still be something wrong with it?
Also, are you absolutely sure I'll be able to flash the eh03 in Odin without it getting stuck on "movinand.bin" ? Every .tar file I've tried so far has had that happen.
Click to expand...
Click to collapse
when using Odin, try different USB port, different USB cable, be sure battery is out..
Also, are you using Odin to flash a stock tar? you should be, and if so are you using the v2.2 pit with the repartition box checked?
See also, droidstyles guide in the fascinate general section
Sent from my SCH-I500 using xda premium
neh4pres said:
when using Odin, try different USB port, different USB cable, be sure battery is out..
Also, are you using Odin to flash a stock tar? *you should be, and if so are you using the v2.2 pit with the repartition box checked?*
See also, droidstyles guide in the fascinate general section
Click to expand...
Click to collapse
I've used all my USB ports and 2 different cables, including the one that came with my phone
Here are all the files I've tried:
CI500_VZW_ED05_FROYO_REL.tar
CI500_VZW_EH03_GB_CM.tar
eh03_full_odin.tar
DI01package3.tar
stock_kernel.tar
I'm also using atlas_v2.2.pit
All of the .tar files get stuck at movinand.bin for about half an hour then it fails. I've tried checking and unchecking the re-partition box with the same result.
Pixelation also recommended the droidstyle guide, I was just afraid of running into the same issue with the movinand.bin file. I've found numerous other threads about people having this same problem and never found a clear solution. I think one person was able to get it fixed with help from adrynalyne, but it was through IRC, so it was never posted in the thread. Any other ideas on what I should try?
Cloyne venlyt
Update: Trying Section 2 of droidstyle's guide. Currently stuck at 99% on movinand.bin, trying to flash the PowerWashed 2.3.4 eh09 rom
ahhhhh!!!! Why, God?
I really don't know. Besides glitched usb drivers on the computer.. Did you try setting up drivers for the fascinate on another pc yet? There is always unbrickable mod if no other fix works
Sent from my SCH-I500 using xda premium
I've tried it on another computer and it still hangs on movinand.bin. It's definitely not a computer issue, since I rooted the phone in February just fine. I think something must have happened when I accidentally deleted the superuser app last week. The only files that I've been able to flash successfully are atlas_v2.2, cwm4-bml-i500, and cwm3_voodoo.tar. Then from clockwork I can install cyanogen from the sd card so I sort of have a working phone. What's the unbrickable mod?
JSlice said:
I've tried it on another computer and it still hangs on movinand.bin. It's definitely not a computer issue, since I rooted the phone in February just fine. I think something must have happened when I accidentally deleted the superuser app last week. The only files that I've been able to flash successfully are atlas_v2.2, cwm4-bml-i500, and cwm3_voodoo.tar. Then from clockwork I can install cyanogen from the sd card so I sort of have a working phone. What's the unbrickable mod?
Click to expand...
Click to collapse
Well, first you don't flash the atlasv2.2pit. that file is a partition map. It repartitions the phone when combined with a factory image. when doing so you need to have the repartition box checked.
The unbrickable mod by adam outler is a hardware mod that allows you to recover from a brick. Google it.
Sent from my SCH-I500 using xda premium
As some possible help, Have you tried sixstringsg one click. Not sure if it re-partitions but here's the link! EH03 Heimdall One-Click
Also you say the tar's are failing at 99%, have you tried flashing them individually? IE: extract the tar and use the following!
Code:
heimdall flash --repartition --pit atlas_v2.2.2.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin --recovery recovery.bin
neh4pres said:
Well, first you don't flash the atlasv2.2pit. that file is a partition map. It repartitions the phone when combined with a factory image. when doing so you need to have the repartition box checked.
The unbrickable mod by adam outler is a hardware mod that allows you to recover from a brick. Google it.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Oops sorry, I didnt actually flash the atlas.pit file. I meant the only files I got to PASS in Odin were the ones mentioned. The unbrickable mod looks way to complicated, and I dont feel comfortable taking apart my phone and soldering it.
What do you know about unbricking via adb? I just installed it yesterday so I dont know all the shell commands. If my phone can't wipe or mount data, i cant get past this damn movinand.bin in odin, and my internal memory is zero - is there a folder i need to go in and delete in adb that is preventing me from flashing in odin? Can't I just delete all data so I'm free to flash anything? It seems like something is still present in my phone to be showing 0 internal memory and not letting me wipe data that needs to be removed.
JSlice said:
Oops, sorry man , I didnt actually flash the atlas.pit file. I meant the only files I got to PASS in Odin were the ones mentioned. The unbrickable mod you mentioned requires that I need to take the phone apart and solder the hardware, is that correct? If that's the case, then I'll go ahead and cross that out as a possible solution.
What do you know about unbricking via adb? I just installed it yesterday so I dont know all the shell commands. If I my phone can't wipe or mount data, i cant get past this damn movinand.bin in odin, and my internal memory is zero - is there a folder i need to go in and delete in adb that is preventing me from flashing in odin? Can't I just delete all data so I'm free to flash anything? It seems like something is still present in my phone to be showing 0 internal memory and not letting me wipe data that needs to be removed.
Click to expand...
Click to collapse
I'm just a user, I think your looking for a 1337 mofo.
I think you need to get familiar with irc, and contact the overlords
Sent from my SCH-I500 using xda premium
I seriously doubt that all this was caused by deleting Superuser. You likely have a corrupt filesystem. Have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1705257
Step 1. Player in Download mode
Step 2. Search for device on Heimdall
Step 3. Name file to save too
Step 4. Start Download
Step 5.. Fail
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
I have tried everything!
I am trying to backup my PIT from my EURO Galaxy Player 4.0 YP-G1CW/XEZ
I damaged another one..
I am trying to fix the Digitizer that touch sensor is flipped.. Digitizer is operating in reverse..
Absolutely no one has done or shown proof to fix this problem..
I don't need ideas or theories.. please
If you can, please show me how to repair this problem..
thank you..
have you tired using Odin instead, or uninstalling all 4.0 drivers, and just installing heimdalls? Or maybe just remove all drivers, let the kids drivers install fully, then run zagig.exe a few times. The entire theory behind xda support is getting helpful theories/ideas from members that have experienced similar issues. Your issue seems to be isolated, so not many people will have step-by-step solutions for you.
Also, thus *does* belong in general, not development. I want to help you, but can you please post this kind if thing in general in the future?
Yes wrong section!
but quick answer:
Pit is the same for every 4.0 int'l sized version.
All the pits and everythings are available here
http://forum.xda-developers.com/showthread.php?t=1720457
Thanks Zaclimon
Forget using Heimdall if you are not Heimdall expert like me (kidding), come back to odin, like me .
Rgds
lolo9393 said:
Yes wrong section!
but quick answer:
Pit is the same for every 4.0 int'l sized version.
All the pits and everythings are available here
http://forum.xda-developers.com/showthread.php?t=1720457
Thanks Zaclimon
Forget using Heimdall if you are not Heimdall expert like me (kidding), come back to odin, like me .
Rgds
Click to expand...
Click to collapse
Heimdall isn't that necessary for intl devices.
To use heimdall on a windows PC, you need to install Zadig's libusb drivers. I've posted a step-by-step walkthrough over in the Q&A section. It covers the entire process of flashing a new rom on a USA device, but the section on heimdall and libusb drivers should work for any device.
I couldn't find any threads that sounded similar to this, so I had no choice but to make a new thread. I apologize if my title is misleading in any way, however, I'm not sure of what else to call it. Also, sorry if I typed anything that didn't make sense, It's late, I'm tired, and I'm in trouble.
So, I had the Dream Ultima ROM flashed on my YP-G1/Player 4.0, and my sister was complaining about insane lagging and whatnot. Before I decided to flash back to stock, I had decided to clean up the internal memory.
I transferred some photos and music from the device to my computer as backup, and then decided to factory reset it, and I think that's where things went wrong.
The device rebooted itself, and booted into stock recovery, saying that it couldnt wipe a few things.
I didn't think much of it at first, and just booted into download mode and continued onto flashing back to stock using Heimdall. When it finished, it booted me into recovery again (can't remember whether it was stock or CWM, I think it was CWM). I didn't think much of that either, so I just rebooted. When it rebooted itself, the Download mode screen showed up, with the progress bar full, and then switched to the steve's kernel icon, and then once again, booted into recovery.
A few more reboots, and I end up getting a forced download mode icon. Reflash.
After a few more tries, doing the same thing over and over again, I ended up not being able to get into recovery at all. When the device boots up, it looks like this:
See attached thumbnail
Oh yes, I should probably add that, none of the times where I tried to flash back to stock were successful, and that I have tried it with Odin as well, with Zaclimon's FullRestore.tar, it claimed to be successful, however, nothing really ended up changing. I can also still get into download mode, but not recovery.
LuthicaBlue said:
I couldn't find any threads that sounded similar to this, so I had no choice but to make a new thread. I apologize if my title is misleading in any way, however, I'm not sure of what else to call it. Also, sorry if I typed anything that didn't make sense, It's late, I'm tired, and I'm in trouble.
So, I had the Dream Ultima ROM flashed on my YP-G1/Player 4.0, and my sister was complaining about insane lagging and whatnot. Before I decided to flash back to stock, I had decided to clean up the internal memory.
I transferred some photos and music from the device to my computer as backup, and then decided to factory reset it, and I think that's where things went wrong.
The device rebooted itself, and booted into stock recovery, saying that it couldnt wipe a few things.
I didn't think much of it at first, and just booted into download mode and continued onto flashing back to stock using Heimdall. When it finished, it booted me into recovery again (can't remember whether it was stock or CWM, I think it was CWM). I didn't think much of that either, so I just rebooted. When it rebooted itself, the Download mode screen showed up, with the progress bar full, and then switched to the steve's kernel icon, and then once again, booted into recovery.
A few more reboots, and I end up getting a forced download mode icon. Reflash.
After a few more tries, doing the same thing over and over again, I ended up not being able to get into recovery at all. When the device boots up, it looks like this:
See attached thumbnail
Oh yes, I should probably add that, none of the times where I tried to flash back to stock were successful, and that I have tried it with Odin as well, with Zaclimon's FullRestore.tar, it claimed to be successful, however, nothing really ended up changing. I can also still get into download mode, but not recovery.
Click to expand...
Click to collapse
Yeah well the odin's method isn't that sucessfull compared to the heimdall one. Try the heimdall one, You will have a better rate of success.
zaclimon said:
Yeah well the odin's method isn't that sucessfull compared to the heimdall one. Try the heimdall one, You will have a better rate of success.
Click to expand...
Click to collapse
Sorry if I wasn't clear, I actually tried the heimdall one first, but the problem is, no matter how many times I try, heimdall won't upload the kernel or anything to the device.
Sent from my SPH-D710
LuthicaBlue said:
Sorry if I wasn't clear, I actually tried the heimdall one first, but the problem is, no matter how many times I try, heimdall won't upload the kernel or anything to the device.
Sent from my SPH-D710
Click to expand...
Click to collapse
Do you have some kind of error? If yes were you in download mode during that time and what does heimdall showed you?
zaclimon said:
Do you have some kind of error? If yes were you in download mode during that time and what does heimdall showed you?
Click to expand...
Click to collapse
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Failed to send file part packet!
KERNEL upload failed!
Ending session...
Yes, I was in downloadmode. It's the only thing i can boot into, besides the picture attached to the OP.
LuthicaBlue said:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Failed to send file part packet!
KERNEL upload failed!
Ending session...
Click to expand...
Click to collapse
Wait, don't upload your kernel with this. Restore your device totally with the full restore and don't forget to re-partition (your SGP looks like a tv? )
zaclimon said:
Do you have some kind of error? If yes were you in download mode during that time and what does heimdall showed you?
Click to expand...
Click to collapse
zaclimon said:
Wait, don't upload your kernel with this. Restore your device totally with the full restore and don't forget to re-partition (your SGP looks like a tv? )
Click to expand...
Click to collapse
I've been using the full restore.... anyways....
Sir, I have enough reason to believe that you are the man. I actually tried repartitioning once, but it didnt work the first time, I'm assuming it might've been because some of my usb ports are a little odd. Repartitioning it fixed it right up for me. Thanks alot!
LuthicaBlue said:
I've been using the full restore.... anyways....
Sir, I have enough reason to believe that you are the man. I actually tried repartitioning once, but it didnt work the first time, I'm assuming it might've been because some of my usb ports are a little odd. Repartitioning it fixed it right up for me. Thanks alot!
Click to expand...
Click to collapse
Oh sorry, I tought you always used odin soo... Anyway no problem for the help.
so we are lucky to have zaclimon in this section the real hero that saves our device
Sent from my YP-G1 using xda premium
rockerblood said:
so we are lucky to have zaclimon in this section the real hero that saves our device
Sent from my YP-G1 using xda premium
Click to expand...
Click to collapse
Yeah, he should be made the official device savior or something, lol! For future reference people, it might be simpler to simply use zaclimon's thread then starting a new thread for every bricked device.
Sent using Tapatalk
I was in the same situation. Go to the Dev area make sure you get the 7 zip file use hemidall. Extract all the files. Open hemidall load your pit file check repartion follow the order in the OP for US player. Check your list before flashing the Partition files. I had the same problem i just had top really read what he was saying. It does work. PM me and i will try to help
Samsung Epic 4G Touch on xda premium