So, I have a problem Houston.
Tablet - GT-P7510 wifi only - ROM prior to problem :
I let my power drain from my device and I let is sit cold for over a week. When I started it after a complete power recharge the tablet only went to a battery icon that did not move. After about an hour and a couple of resets (power + volume Up) - same result; power + Volume down - DL mode, I begin trying to recover the tablet.
I have been trying for over 2 days now using D/L mode and Odin. I am getting nowhere and I have not yet lost D/L mode. I don't commonly post unless I have a problem, and I just can't seem to sort this one out. I have a laundry list of things I have tried, but I cannot seem to get CWM, or any other combination to work. It appears that Odin delivers the files, the device resets, but upon Power + volum up it alsways delivers to battery icon, or I can get to D/L mode using Power + volume down.
I am trying to go back to square one and re-step through things using Odin only as I cannot seem to gain access to recovery.
I have just re-loaded samsung firmware file:
P7510XABLPL_P7510UELPL_HOME.tar.md5 - from samfirmware
Odin dump -
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7510XABLPL_P7510UELPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.img
<ID:0/009> NAND Write Start!!
<ID:0/009> recovery.img
<ID:0/009> system.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> bootloader.bin
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
And now it just sits there like a pretty paperweight until i switch it to d/l mode.
I am hitting head against wall and it just plain hurts (PEBKAC)....argh! All I keep finding anywhere are now recovery based (which I normally use; well I switched to CM 10.1 JB 4.2.1 and was doing nightly updates via the utility).
Will anyone point me to an Odin described process? I need to do a sanity check and verify and identify the mistake I am making in the sequence.
Thanks in advance! Sorry for the length.
miracleboy;448http://forum.xda-developers.com/showthread.php?t=2142268http://forum.xda-developers.com/showthread.php?t=2142268http://forum.xda-developers.com/showthread.php?t=214226821009 said:
So, I have a problem Houston.
Tablet - GT-P7510 wifi only - ROM prior to problem :
I let my power drain from my device and I let is sit cold for over a week. When I started it after a complete power recharge the tablet only went to a battery icon that did not move. After about an hour and a couple of resets (power + volume Up) - same result; power + Volume down - DL mode, I begin trying to recover the tablet.
I have been trying for over 2 days now using D/L mode and Odin. I am getting nowhere and I have not yet lost D/L mode. I don't commonly post unless I have a problem, and I just can't seem to sort this one out. I have a laundry list of things I have tried, but I cannot seem to get CWM, or any other combination to work. It appears that Odin delivers the files, the device resets, but upon Power + volum up it alsways delivers to battery icon, or I can get to D/L mode using Power + volume down.
I am trying to go back to square one and re-step through things using Odin only as I cannot seem to gain access to recovery.
I have just re-loaded samsung firmware file:
P7510XABLPL_P7510UELPL_HOME.tar.md5 - from samfirmware
Odin dump -
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7510XABLPL_P7510UELPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.img
<ID:0/009> NAND Write Start!!
<ID:0/009> recovery.img
<ID:0/009> system.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> bootloader.bin
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
And now it just sits there like a pretty paperweight until i switch it to d/l mode.
I am hitting head against wall and it just plain hurts (PEBKAC)....argh! All I keep finding anywhere are now recovery based (which I normally use; well I switched to CM 10.1 JB 4.2.1 and was doing nightly updates via the utility).
Will anyone point me to an Odin described process? I need to do a sanity check and verify and identify the mistake I am making in the sequence.
Thanks in advance! Sorry for the length.
Click to expand...
Click to collapse
Here's a link I think will help.. http://forum.xda-developers.com/showthread.php?t=2142268 ..look at post 4 as well.. The steps look good to me.. He forgot to say to unchecked the reset time box,but that's it.. Hop it helps..
Gil81 said:
Here's a link I think will help.. http://forum.xda-developers.com/showthread.php?t=2142268 ..look at post 4 as well.. The steps look good to me.. He forgot to say to unchecked the reset time box,but that's it.. Hop it helps..
Click to expand...
Click to collapse
Thanks for the lead, I am calling it a night. I will report back tomorrow, as I'd like to see my thread close. I think the NAND is hosed, but from what I can tell, you can't really completely brick the p7510. I am using a windows machine, or a mac with win(x) in a VM to use odin, I may give heimdall a swing or straight terminal through linux, but that means yet another VM.
I have repart'ned the NAND and re-installed bootloaders, recoveries and official Sammy firmware in various combinations. I am still able to return to D/L mode, so onward the battle between me and the pretty little paperweight continues. We've had a good two years together, i', hoping she ain't pissed at me now.
Thanks again for the lead, will chase on the flip side. Feedback to follow.
Cheers!
miracleboy said:
Thanks for the lead, I am calling it a night. I will report back tomorrow, as I'd like to see my thread close. I think the NAND is hosed, but from what I can tell, you can't really completely brick the p7510. I am using a windows machine, or a mac with win(x) in a VM to use odin, I may give heimdall a swing or straight terminal through linux, but that means yet another VM.
I have repart'ned the NAND and re-installed bootloaders, recoveries and official Sammy firmware in various combinations. I am still able to return to D/L mode, so onward the battle between me and the pretty little paperweight continues. We've had a good two years together, i', hoping she ain't pissed at me now.
Thanks again for the lead, will chase on the flip side. Feedback to follow.
Cheers!
Click to expand...
Click to collapse
OK buddy.. Try Odin again from the link and if that doesn't work I'll continue to dig around.. You're problem kinda sounds like an issue I had a couple weeks ago, but I could get to cwm.. But tablet would not boot and I had no computer close. So I re-flashed my ROM and before reboot I wiped the sdcard...I know, crazy right. But I figured a trip to Odin was next so I threw up a hellmary...lol. Hoping it was a bad file not letting it boot and Bang.. She booted right up..When you do you're next Odin you might try not checking the auto-reboot.. When its done,instead of booting to ROM try to boot to cwm. If that works you got it licked.. Keep me posted.
This just does not make sense. I am in a circle, like the Griswolds in European vacation
So reset:
Steps I have taken.
1. Charged device overnight
2. Put in D/L mode using Volume + down
3. plug in device to computer (mac os/ win(x))
4. Launch Odin - Odin identifies Com Port
5. Select firmware from sammobile
a. I have tried these variants - listing by filenames:
1. P7510XABLPL_P7510UELPL_HOME.tar.md5
2. P7510XABKMP_P7510UEKMP_HOME.tar.md5
3. Samsung-Updates.com-GT-P7510_XAB_1_20120808105431_sr3nx29c5t.zip - d/ling from samsung updates
6. Run Odin (with Auto Reboot checked and unchecked)
7. Upon restart the Samsung Galaxy tab 10.1 splash page comes up
8. If I hold power plus volume up
a. It pauses, presents the battery icon with absolutely no animation and sits there
9. If I hold power plus volume down, I can ALWAYS get to D/L mode (knock on wood)
Resources used include:
http://forum.xda-developers.com/showthread.php?t=2142268 - Post 1 and Post 4,
http://forum.xda-developers.com/showthread.php?t=1556276 - reading through the thread
What sticks out as odd to me, upon reboot it should auto-load into the CWM or scroll through some text. In older pphones as android was first coming on, a specific bootloader, and subsequent matching .img files were required. It seems to me I am missing a file, even if they are to be all included in the .tar files.
Out of curiosity i was on a nightly CM 10.1 which is the newer 4.2.1 version. If I flashed to this originally when things broke, would the HC, ICS path the odin .tars use be out of sequence?
It just seems like something is missing in the sequence when the flash runs via odin. perplexed. If I could locate a odin .tar for a cm 10.1 nightly I think I might be able to overcome things. This is just a thought since i CANNOT arrive at a recovery to get in and do a wipe etc. I DO NOT see the screen http://www.youtube.com/watch?v=gJ6VZGCdRSo seen at approx 2:16 in the link. grrr....
not sure what my next step should be. Chasing NVFlash next? http://forum.xda-developers.com/showthread.php?t=1689199
miracleboy said:
This just does not make sense. I am in a circle, like the Griswolds in European vacation
So reset:
Steps I have taken.
1. Charged device overnight
2. Put in D/L mode using Volume + down
3. plug in device to computer (mac os/ win(x))
4. Launch Odin - Odin identifies Com Port
5. Select firmware from sammobile
a. I have tried these variants - listing by filenames:
1. P7510XABLPL_P7510UELPL_HOME.tar.md5
2. P7510XABKMP_P7510UEKMP_HOME.tar.md5
3. Samsung-Updates.com-GT-P7510_XAB_1_20120808105431_sr3nx29c5t.zip - d/ling from samsung updates
6. Run Odin (with Auto Reboot checked and unchecked)
7. Upon restart the Samsung Galaxy tab 10.1 splash page comes up
8. If I hold power plus volume up
a. It pauses, presents the battery icon with absolutely no animation and sits there
9. If I hold power plus volume down, I can ALWAYS get to D/L mode (knock on wood)
Resources used include:
http://forum.xda-developers.com/showthread.php?t=2142268 - Post 1 and Post 4,
http://forum.xda-developers.com/showthread.php?t=1556276 - reading through the thread
What sticks out as odd to me, upon reboot it should auto-load into the CWM or scroll through some text. In older pphones as android was first coming on, a specific bootloader, and subsequent matching .img files were required. It seems to me I am missing a file, even if they are to be all included in the .tar files.
Out of curiosity i was on a nightly CM 10.1 which is the newer 4.2.1 version. If I flashed to this originally when things broke, would the HC, ICS path the odin .tars use be out of sequence?
It just seems like something is missing in the sequence when the flash runs via odin. perplexed. If I could locate a odin .tar for a cm 10.1 nightly I think I might be able to overcome things. This is just a thought since i CANNOT arrive at a recovery to get in and do a wipe etc. I DO NOT see the screen http://www.youtube.com/watch?v=gJ6VZGCdRSo seen at approx 2:16 in the link. grrr....
not sure what my next step should be. Chasing NVFlash next? http://forum.xda-developers.com/showthread.php?t=1689199
Click to expand...
Click to collapse
I would try to use Odin to put a recovery on it and uncheck auto reboot.. After Odin does the flash, unplug device and try to boot to cwm. If you can get this far you can wipe the device clean and start new with Odin and a ROM of choice. I think you have something bad on you're storage. If you've tried this already, I'll start hunting around. But being honest..this might be above my paygrade... Scratch this...I watched the spot you referenced in the video. If its not writing I'm lost.
---------- Post added at 09:03 PM ---------- Previous post was at 08:14 PM ----------
So just so I know I'm right with this.. You can't get to cwm recovery. When on the bootloader screen and you pick the box on the left it goes to stock recovery.
no worries, this is what has me stumped. i queried droidbasement (pershoot's lair) earlier and stepped through things as one should, and that's why I am suspecting one of two things now: 1 - I am an idiot and missing the most obvious step in the world, or 2) NVFlash is hosed and this is part of the Emmc bug which sammy is even replacing chipsets when turned in for service. I am going to stew for a day or two before deciding on an RMA etc. Thanks for the try, for me it's a great sanity check which I desparately needed to keep me from chucking the device at a wall
miracleboy said:
no worries, this is what has me stumped. i queried droidbasement (pershoot's lair) earlier and stepped through things as one should, and that's why I am suspecting one of two things now: 1 - I am an idiot and missing the most obvious step in the world, or 2) NVFlash is hosed and this is part of the Emmc bug which sammy is even replacing chipsets when turned in for service. I am going to stew for a day or two before deciding on an RMA etc. Thanks for the try, for me it's a great sanity check which I desparately needed to keep me from chucking the device at a wall
Click to expand...
Click to collapse
Don't chuck it at a wall yet...lol. Its got me mad now.. I just can't figure out,if you have download mode and Odin a recovery, why it won't stick. Or Odin a ROM and it won't boot. I've never had Odin fail over and over. I had a Odin flash on my epic touch take over 20 minutes to boot one time but it booted..anyway..I seen this thread,not sure if it applies really but you might give it a browse. http://forum.xda-developers.com/showthread.php?t=1478361
Have you used Odin in "standard" mode (leave what is checked, checked) and with repartition checked and with a .pit file and with standard stock Sammy firmware? I'm a bit tired and confused at the moment (working nights) but was a bit lost by you expecting to see cwm after having used Odin and a stock rom or have I misread?
sent from my still superb Google I/O 7510 (xda hd)
stinky73 said:
Have you used Odin in "standard" mode (leave what is checked, checked) and with repartition checked and with a .pit file and with standard stock Sammy firmware? I'm a bit tired and confused at the moment (working nights) but was a bit lost by you expecting to see cwm after having used Odin and a stock rom or have I misread?
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
+1...
stinky73 said:
Have you used Odin in "standard" mode (leave what is checked, checked) and with repartition checked and with a .pit file and with standard stock Sammy firmware? I'm a bit tired and confused at the moment (working nights) but was a bit lost by you expecting to see cwm after having used Odin and a stock rom or have I misread?
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
@ Stinky, yes. In fact I am re-doing just that prior to chasing the idea from the link from Gil81 http://forum.xda-developers.com/showthread.php?t=1478361.
My original try was using Odin3 v1.85. I left EVERYTHING 'standard' or default,
select the .pit [android_fastboot_emmc_full_p4_16G_32G.pit],
select using the PDA button a stock Sammy Firmware [P7510XABLPL_P7510UELPL_HOME.tar.md5]
Once the auto Reboot occurs, I unplug the device and watch. It currently sits with a perfectly black screen with a little bit of luminescence from the back light. If I hit power, it then only displays the Samsung Galaxy tab 10.1 splash page and goes nowhere for the next (insert arbitrary amount of time) and it ONLY allows me to power up and go to download mode using the power + volume down combination.
Get some sleep man!
let the battery drain commence, power button taped. Fingers crossed that in 24-36 hours, I will be able to use Odin and install the following stock rom file: [P7510XABLPL_P7510UELPL_HOME.tar.md5].
Thanks!
Ah, the old battery drain approach to reset everything but you might find it takes a week to completely empty the thing depending on charge state when you started , tho not sure why you want to do that before using Odin... When you do don't forget if you use .pit that you must tick repartition in Odin
Keep us posted and hope it goes flat soon
sent from my still superb Google I/O 7510 (xda hd)
miracleboy said:
let the battery drain commence, power button taped. Fingers crossed that in 24-36 hours, I will be able to use Odin and install the following stock rom file: [P7510XABLPL_P7510UELPL_HOME.tar.md5].
Thanks!
Click to expand...
Click to collapse
Yep...yep.. I thought that might be the only option left to try if you can't get Odin to do anything..good luck.. I'll keep peaking in to see how it goes..
plug in one, no plug splash...tape goes back...drain drain drain....
Ok I don't want to get ahead of myself, but, after the power drain....the android buddy came up - falash screen animation with the droid and newton's electron floating in his belly. Then an audio ding I haven't heard since honeycomb. Now an alternative SAMSUNG splash, with pulsing animation (I vaguely remember stock, eerie thoughts --eik.
Letting it sit a bit to see what it does. once I feel I have given it sufficient rest, I will try for recovery and then proceed. Progress, but one step at a time. The battery drain is well worth the wait.
Thanks @Gil81 for the post, more progress updates or /facepalms to come. Fingers crossed that this thread is going to close soon.
Gil81 said:
Yep...yep.. I thought that might be the only option left to try if you can't get Odin to do anything..good luck.. I'll keep peaking in to see how it goes..
Click to expand...
Click to collapse
Looks like the battery drain did the trick, not out of the darkness yet, but i was able to get to recovery, then odin'd a fresh version of stock. Now waiting for it to completely load. Installing applications now. So, step one has been achieved. now to see what version of stock this is, since I haven't seen that since like Sept 2011, when I had my original screen serviced for the dust particle fogginess thing.
Thanks for hanging' with me, now to choose another ROM. I will probably go back to CM10.1 unless there are other ROMS to persuade me otherwise. Now to write a summary post. Thanks @Gil81. Cheers mate!
miracleboy said:
Ok I don't want to get ahead of myself, but, after the power drain....the android buddy came up - falash screen animation with the droid and newton's electron floating in his belly. Then an audio ding I haven't heard since honeycomb. Now an alternative SAMSUNG splash, with pulsing animation (I vaguely remember stock, eerie thoughts --eik.
Letting it sit a bit to see what it does. once I feel I have given it sufficient rest, I will try for recovery and then proceed. Progress, but one step at a time. The battery drain is well worth the wait.
Thanks @Gil81 for the post, more progress updates or /facepalms to come. Fingers crossed that this thread is going to close soon.
Click to expand...
Click to collapse
No problem.. When I first started out in the e4gt forum I read and read, much like you have.. I only asked question's as a last resort, much like you.. I received almost no flaming.. and a lot of help from some great guys/gals.( e4gt forum is awesome ).. I'm not a flamer ,but if I had been. I would have decided right then to be a helper instead.. I'll push that search button right through this tab if its going to help somebody .. No Man Left Behind..
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
miracleboy said:
Looks like the battery drain did the trick, not out of the darkness yet, but i was able to get to recovery, then odin'd a fresh version of stock. Now waiting for it to completely load. Installing applications now. So, step one has been achieved. now to see what version of stock this is, since I haven't seen that since like Sept 2011, when I had my original screen serviced for the dust particle fogginess thing.
Thanks for hanging' with me, now to choose another ROM. I will probably go back to CM10.1 unless there are other ROMS to persuade me otherwise. Now to write a summary post. Thanks @Gil81. Cheers mate!
Click to expand...
Click to collapse
Just a my opinion..but infamous carbon 4.3 flies on my tab..running right now..Google search is goofy... Just have to turn off hotword search in setting...but that is it...
So to summarize folks.
GT-P7510 Samsung Tablet
Rooted and flashed with non-stock CM10.1 nightlies.
Problem summarized:
Powered tablet and unplugged. Left alone until power drain. Let sit cold for 3-4 days. Plugged in and the power icon with no animation appeared. Further, only the soft back-light glow was present. After trying to get to recovery, only d/l mode was available.
Steps to resoultion
1. Realized I need a sanity check and ask for help on XDA after 3 days of fiddling with no resolution
2. Identified the solution in this thread: http://forum.xda-developers.com/showthread.php?t=1478361
3. Perform recommended steps
4. Be patient and find other things while battery drains
5. Power up using Samsung and power from wall
6. My device booted as I already had a recovery and rom by stock, if you are unable
6b. follow thread instructions explicitly, obtain odin and flash
7. Should have recovered rom so you may proceed
Good luck and again thanks to those in XDA, I don't develop anymore for mobiles due to my choices in profession however, this community has ALWAYS been stellar even with Out of Life devices. Ya I know, I need the next generation of a tablet but with Sammy and Apple crushed in litigation blackness, this little workhorse is all I need for now, well and my SIII mobile phone.
Thanks again. Please close this thread!
Glad it's resolved and good sum up post. In another thread I'm subscribed the OP also went for the tried and trusted disconnect battery by draining technique except he removed the back and unplugged the battery!! Same happy outcome!
Power to the old relic tab! Ciao
sent from my still superb Google I/O 7510 (xda hd)
Related
Let's see, where to start......hmmm a bit of backstory
Okay I bought my phone on the 7th of this month, 150$ used but in mint condition with a clean ESN, I haven't added phone service to it yet, but I've been messing with new it since then. My brother has a Vibrant so he was helping me with stuff, installing, rooting, changing roms, and helping me out with apps he's bought.
So the last few days Ive been trying a couple new roms with very little knowledge to say the least. I went from stock to root with odin then installed Evil Fascinate http://forum.xda-developers.com/showthread.php?t=1035420 . Then after a very long day of messing around with launchers and stuff with(and with my brother bugging me about it) I moved on to try Cyanogen http://forum.xda-developers.com/showthread.php?t=1116424 and played with that for a couple of days.
Man, was cyanogen snappy and smooth feel real nice actually then for some reason I was having problems with installing swipe (which over the last couple of days I learned to love) and after about a day I decided that since it was still much in early stages with no GPS/mms or swipe I would just go back to evil and be happy.
All was good until I decided to go back to Evil
Saturday morning I ask my brother about how I go about going back and he said something about can't "go back the direct way" something about file systems being completely different or something. He basically hand led me to go from Cyanogen to Landshark http://forum.xda-developers.com/showthread.php?t=1048380 and told me to get the ED01DB_DO_SHARK.tar. I flashed all was well (or so I think) and I asked him "so now I can jump back to Evil right?" he responded with "yeah or just try it out so get get to try out more roms" so I flash backed to Evil.
I thought all was good until I tried to sign into my google account and it gave me an error and I realized I hadn't set up my wifi settings yet. I set everything up and to connect to my wifi and my phone basically loops trying to connect but I never see the icon on the top that shows wifi is on but I know it's working because it still picks up my ssid. Rebooted a few times and gave it time to settle but nothing, it just kept looping. I also noticed my gps didn't work at all.
My brother was at the race track all day yesterday so I was able to get little help from him and he's also in OR (I'm in CA) so he couldn't just come over to help me later so I figured I'd try to fix it myself lol
I tried different radios, ED01/ED09/DL09/EC01, also tried switching roms to landshark then back to evil but nothing and I also tried to re apply the peanut butter jelly kernel, but again nothing. I finally used this http://forum.xda-developers.com/showthread.php?t=1046377 from imnuts and now I'm back to stock but again no wifi or GPS
My question what do I do now? I work graveyards so my normal sleep cycle is coming up but I'll check forum the second I'm up. I hope someone can help me and thank you for your time.
Junkboy0 said:
Let's see, where to start......hmmm a bit of backstory
Okay I bought my phone on the 7th of this month, 150$ used but in mint condition with a clean ESN, I haven't added phone service to it yet, but I've been messing with new it since then. My brother has a Vibrant so he was helping me with stuff, installing, rooting, changing roms, and helping me out with apps he's bought.
So the last few days Ive been trying a couple new roms with very little knowledge to say the least. I went from stock to root with odin then installed Evil Fascinate http://forum.xda-developers.com/showthread.php?t=1035420 . Then after a very long day of messing around with launchers and stuff with(and with my brother bugging me about it) I moved on to try Cyanogen http://forum.xda-developers.com/showthread.php?t=1116424 and played with that for a couple of days.
Man, was cyanogen snappy and smooth feel real nice actually then for some reason I was having problems with installing swipe (which over the last couple of days I learned to love) and after about a day I decided that since it was still much in early stages with no GPS/mms or swipe I would just go back to evil and be happy.
All was good until I decided to go back to Evil
Saturday morning I ask my brother about how I go about going back and he said something about can't "go back the direct way" something about file systems being completely different or something. He basically hand led me to go from Cyanogen to Landshark http://forum.xda-developers.com/showthread.php?t=1048380 and told me to get the ED01DB_DO_SHARK.tar. I flashed all was well (or so I think) and I asked him "so now I can jump back to Evil right?" he responded with "yeah or just try it out so get get to try out more roms" so I flash backed to Evil.
I thought all was good until I tried to sign into my google account and it gave me an error and I realized I hadn't set up my wifi settings yet. I set everything up and to connect to my wifi and my phone basically loops trying to connect but I never see the icon on the top that shows wifi is on but I know it's working because it still picks up my ssid. Rebooted a few times and gave it time to settle but nothing, it just kept looping. I also noticed my gps didn't work at all.
My brother was at the race track all day yesterday so I was able to get little help from him and he's also in OR (I'm in CA) so he couldn't just come over to help me later so I figured I'd try to fix it myself lol
I tried different radios, ED01/ED09/DL09/EC01, also tried switching roms to landshark then back to evil but nothing and I also tried to re apply the peanut butter jelly kernel, but again nothing. I finally used this http://forum.xda-developers.com/showthread.php?t=1046377 from imnuts and now I'm back to stock but again no wifi or GPS
My question what do I do now? I work graveyards so my normal sleep cycle is coming up but I'll check forum the second I'm up. I hope someone can help me and thank you for your time.
Click to expand...
Click to collapse
Here is your solution. Put this in the PDA section of Odin:http://adrynalyne.us/files/stuff/CI500_VZW_DL09_ECLAIR.tar.md5
And put this in the Pit section of Odin:http://download180.mediafire.com/md83yqhqv4og/26xbh796jmwvwqb/atlas_v2.2.pit And put a check in the "repartition" box in Odin and then hit start. Let this run it's course and your phone will be fixed on stock DL09. From there, Odin cwm recovery and flash whatever rom you want.
And if you decide to go from Evil to Com Rom (or other Touchwiz based rom), you don't need to do all that stuff. Just wipe the big three and flash the zip. You just have to odin with the pit file and repartition from JT's AOSP rom.
Edit: and once you are on DL09, you'll probably want to update your radio, as roms don't come with radios. There is a thread in I think the development thread regarding updating radios
Sent from my SCH-I500 using XDA Premium App
^ Thank you, I will try that and get back to you after they finish downloading and I flash it.
Fail
It failed
This is what I got, and I made sure to click partition.
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> Enter CS for MD5..
<ID:0/009> Check MD5.. Do not unplug the cable..
<ID:0/009> Please wait..
<ID:0/009> Checking MD5 finished Sucessfully..
<ID:0/009> MD5 hash value is invalid.
<OSM> All threads completed. (succeed 0 / failed 1
*edit* Wait wait, I tried it again and it seems to be going through.
Junkboy0 said:
It failed
This is what I got, and I made sure to click partition.
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> Enter CS for MD5..
<ID:0/009> Check MD5.. Do not unplug the cable..
<ID:0/009> Please wait..
<ID:0/009> Checking MD5 finished Sucessfully..
<ID:0/009> MD5 hash value is invalid.
<OSM> All threads completed. (succeed 0 / failed 1
*edit* Wait wait, I tried it again and it seems to be going through.
Click to expand...
Click to collapse
Just saw your edit. Glad it worked.
Try redownloading and flash it again. Your file might be incomplete.
I flashed but no wifi
Yeah it went through just fine but my Wifi is still not working properly. The phone scans wifi just fine because it sees my ssid and two wep default ones from my neighbors but I try to connect and on this stock rom it doesn't even say connecting just stays on "disconnecte"
Also this morning before I went to sleep I used titanium backup and restore gps test and it showed like gps did work say 10 and connected to 8 had me down to 6 feet. I'll be downloading google maps on the pc then put it on the phone see if it does work.
Ok downloaded both google maps and gps test maps won't work but gps test see and works fine
Anyone have any ideas? At this point I'm thinking of going back to Cyanogen see if wifi still works there. Thoughts?
Bump Anyone?
Update
So I just got home a bit ago from work and decided to try the phone and wifi was still off and gps didn't work.So I bumped the thread and I was gonna flash Cyanogen when I decided to see if since GPS Test worked and Maps didn't if there was some kind of setting or place I could click to see if it would activate anything like a link to their creators in about or something. Sure enough I found their chatcross.co.uk link in about clicked on it and I was immediately taken to their site in less than a second thanks to my WNDR 3700 and 30Mbit connection.
It seems letting it sit for a few hours of it being off and GPS Test somehow kicked stuff on somehow and considering before I check GPS test maybe 18 minutes before that I had tried Navigation, maps and web browser, but nothing worked untill GPS Test.
So thanks so much for helping me out guys I really appreciate it I'll be flashing to evil in a bit and again thanks a bunch.
I was having problems with my tablet freezing and making me hold the power button and reset multiple times a day so I wanted to flash it back to stock and just use it that way and see if the problem is still there. When I went to flash it back to stock I originally tried to flash it using CWM and put "hc-3.1_ota-full_sam_tab_10.1" from the thread "LOOK" Here First {List} Roms/Kernels/Mods/Themes/FAQ'S *Update 25/08/11* After flashing that It would no longer power on. I'd also done a few master resets before starting this whole process. I wasnt able to get that to flash successfully. Since I wasnt having any luck I flashed the [Solution] HC 3.1 OTA Stock ODIN link right below what I was flashing. Still having a problem booting up but also no longer have CWM on the tablet. Later I saw the download file was PDA_SIGNED_P7105.tar and my tablet is p7510 so I figured that could be why as well. I reflashed CWM onto the tablet but im pretty sure it was just the CWM files because its only 5mb. I went over to http://www.samfirmware.com/WEBPROTECT-p7510.htm but its only got the Arabic and Europe versions. I tried to mount my SD storage using CWM and it gives me a error so I cant put normal ROM's back onto the tablet.
SOOO long story short if anyone has any tips to get past this booting screen were it just says "Samsung Galaxy Tab 10.1" they would be much appricated! and I'm also looking for where I can download the stock or any ROM basically for the 7510 that I can flash using Odin because I cannot get it to mount my SD card.
UPDATE: after flashing tons of different files in odin and no success I thought I'd give it a try this morning and finally got it work by flashing the PDA_SIGNED_P7105 which I had done before not sure why it hadn't worked but at least its powering up into the setup. I guess I'll just have to see if the problem comes back. Thanks for the help cleblanc92 though!
Update: I followed the steps in [ROM][STOCK][ARABIC][AUG'13]W/ Official TOUCHWIZ Galaxy Tab 10.1 (WIFI) P7510JPKG5 but still no luck in getting past the boot screen. I did the PDA and CSC it all went through successfully but still didn't get past boot screen. I'm starting to feel like its just bricked or I'm missing something...
What's your full tab detail before I try to whack at this with you? Wifi or 3g? US GT-P7510 yes?
cleblanc92 said:
What's your full tab detail before I try to whack at this with you? Wifi or 3g? US GT-P7510 yes?
Click to expand...
Click to collapse
yeah, its the Wifi GT-P7510 US version.
Thanks for the help I'm kinda stumped here I even called samsung lol but obviously all they had me do was a factory reset and setup a call back when tier 2 tech is open but I dont see them being able to help either.
at the moment I don't have CWM and it should be all stock. I can put it on if need be though.
just for some more information. the more the better I would assume I had the starburst ROM on then put Bonsai on which included a kernal I dont think the kernal would cause problems. Not sure if it would even still be on there. I'm about to try and reflash bonsai back onto the tablet. If I can find a way to do it on Odin.
So you used the steps from this post:
http://forum.xda-developers.com/showthread.php?t=1119492
To apply this ODIN version: http://www.megaupload.com/?d=DDN6BYB2
with the notes steps:
Flash the below with ODIN (thanks to bonzai3558), extract the .md5 file from the zip, and in odin choose PDA and point to that file, keep everything else blank/default. Connect Tab with USB (after it is in download mode by power on +Volume down then volume up, so it shows the yellow android with shovel) then hit Start.
Did that error at all? If you did not apply all those steps with success please retry and comment?
cleblanc92 said:
So you used the steps from this post:
http://forum.xda-developers.com/showthread.php?t=1119492
To apply this ODIN version: http://www.megaupload.com/?d=DDN6BYB2
with the notes steps:
Flash the below with ODIN (thanks to bonzai3558), extract the .md5 file from the zip, and in odin choose PDA and point to that file, keep everything else blank/default. Connect Tab with USB (after it is in download mode by power on +Volume down then volume up, so it shows the yellow android with shovel) then hit Start.
Did that error at all? If you did not apply all those steps with success please retry and comment?
Click to expand...
Click to collapse
Alright I'll redownload the Odin version and the md5 and see if i get any errors. Should I post the log from Odin?
Shouldn't take too long to download already at like 80% should be done in a min.
Also right now. It gotten past the "samsung galaxy tab 10.1" screen but is still getting stuck at the like page with the stars and swirls.
*IF* the ODIN process above works then you can apply CWR via ODIN from here:
http://forum.xda-developers.com/showthread.php?t=1150732&highlight=odin+cw
This should get you back to a Stock with CWR support. I am on StarBurst with the latest Pershoot Kernel and I don;t thing either of those are a factor in your recovery success but you did not some other items that I have not touched at all.
Elumis said:
Alright I'll redownload the Odin version and the md5 and see if i get any errors. Should I post the log from Odin?
Shouldn't take too long to download already at like 80% should be done in a min.
Also right now. It gotten past the "samsung galaxy tab 10.1" screen but is still getting stuck at the like page with the stars and swirls.
Click to expand...
Click to collapse
Is it bootlooping? aka restarting the boot process images over and over
cleblanc92 said:
*IF* the ODIN process above works then you can apply CWR via ODIN from here:
http://forum.xda-developers.com/showthread.php?t=1150732&highlight=odin+cw
This should get you back to a Stock with CWR support. I am on StarBurst with the latest Pershoot Kernel and I don;t thing either of those are a factor in your recovery success but you did not some other items that I have not touched at all.
Click to expand...
Click to collapse
Yeah I got that file for CWR I just have a problem with getting a ROM onto the tablet to actually use it.
Here is the log for flashing the PDA_SIGNED_P7105.tar.md5
it says PASS! at the top so far after its restarted it still sitting at the samsung galaxy page. I'll let it sit for a little bit longer but something tells me its not going anywhere.
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_SIGNED_P7105.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> system.img
<ID:0/012> recovery.img
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/012> Removed!!
<ID:0/011> Added!!
Click to expand...
Click to collapse
cleblanc92 said:
Is it bootlooping? aka restarting the boot process images over and over
Click to expand...
Click to collapse
Yeah it was bootlooping but its back to just showing the samsung galaxy tab logo. I can probably get it back into the bootloop if that's better?
Elumis said:
Yeah I got that file for CWR I just have a problem with getting a ROM onto the tablet to actually use it.
Here is the log for flashing the PDA_SIGNED_P7105.tar.md5
it says PASS! at the top so far after its restarted it still sitting at the samsung galaxy page. I'll let it sit for a little bit longer but something tells me its not going anywhere.
Click to expand...
Click to collapse
If it sits for 5-10 mins and goes no further let's try booting into CWMR then
1) wipe cache partition
2) advanced / Wipe Dalvik Cache
3) wipe data/factory rest
4) reboot
...miracles happen.
[ I do HATE the SDCARD is not a real accessible card. Next tab will need that for me as it's an extra recovery tool we just don't have. ]
cleblanc92 said:
If it sits for 5-10 mins and goes no further let's try booting into CWMR then
1) wipe cache partition
2) advanced / Wipe Dalvik Cache
3) wipe data/factory rest
4) reboot
...miracles happen.
[ I do HATE the SDCARD is not a real accessible card. Next tab will need that for me as it's an extra recovery tool we just don't have. ]
Click to expand...
Click to collapse
something interesting I got the screen were it lets me choose download or recovery. I clicked on download on accident the first time and it opened. Restarted to get into recovery and it just shows a black screen. The backlight is still on so the tablet is still on. I'll try just flashing CWR onto it again yeah agree with the SD card only thing I dont like about the tablet
cleblanc92 said:
If it sits for 5-10 mins and goes no further let's try booting into CWMR then
1) wipe cache partition
2) advanced / Wipe Dalvik Cache
3) wipe data/factory rest
4) reboot
...miracles happen.
[ I do HATE the SDCARD is not a real accessible card. Next tab will need that for me as it's an extra recovery tool we just don't have. ]
Click to expand...
Click to collapse
I put CWR on and was able to get into it. I factory reset, wiped cache partition, then went into advanced and clicked on wipe dalvik, before I had hit yes it said "E:unknown volume for path [/sd-ext]" but it still let me click yes and said "Dalvik Cache wiped.
EDIT: still not booting up past the samsung galaxy tab screen.
Okay...well I am not sure about the SD warning you noted or if it matters. I would expect some of the masters around here might be able to look at the post details thus far and offer some ideas. Hang in there, I will try to poke around for some ideas based on that error msg but it won't be until tomorrow....pending the hurricane (which is already slowing) doesn't tear up the power lines. Sorry we could not get there already.
cleblanc92 said:
Okay...well I am not sure about the SD warning you noted or if it matters. I would expect some of the masters around here might be able to look at the post details thus far and offer some ideas. Hang in there, I will try to poke around for some ideas based on that error msg but it won't be until tomorrow....pending the hurricane (which is already slowing) doesn't tear up the power lines. Sorry we could not get there already.
Click to expand...
Click to collapse
That's alright, thanks for all the help though! much appreciated. Hope the hurricane doesn't hit you're area too hard. I'll give you some "Thanks" and shoot you a donation
maybe Samsung tech support will know something as well lol. supposed to call me back sometime tomorrow morning. They will probably just make me mail it in for a few weeks...
Thanks very much. I think the SD warning is just generic since we do not have a card mounted in the expected location....but again someone will correct me if I am wrong on that.
I'll see what I can come up with Sat if no one finds the solution.
hey cleblanc92, I feel your misery, i finally found a solution! and the culpit to(atleast for me)
The Culprit is Busybox, at first I thought its the OC kernel that i installed then upon google surfing i found similar problems and yup its the #$Q!#$ application!! CONFIRMED
STAY AWAY FROM OPENVN RELATED STUFF
so here's the solution, after spending so much time my Galaxy tab is now reviewd.
First Download this for your PC
SAMSUNG DRIVER:
http://downloadandroidfiles.com/files/get/IwAZDRwKZz/gt-p7510-usb-driver-v1-3-2360-0-escape.exe
ODIN
http://downloadandroidrom.com/file/GalaxyTab10.1/rooting/tabrooteasy.zip
Then go to this site
http://www.samfirmware.com/fwandroid.htm
and search for your Tablet's Model
after that you will have several firmware to choose from depending on where your tablet is manufactured
look at the back of your tablet, find the "MADE IN: xxxxxxx" This will give you a hint (mine is KOREA so I download the asian Firmware)
After downloading all of that
Install the driver
Unzip tabrooteasy.zip
On your tablet, Push the Power Botton once until the Samsung galaxy Tab 10.1 logo appear, then imediately press the volume down button.
2 choices will appear, choose the one with the DOWNLOAD stuff in it
after that odin will start on your tablet, DO NOT PLUG THE CABLE YET!
Open the ODIN.exe on your PC and Then Connect the Cable
Click on PDA then navigate to the tabrooteasy folder and choose
recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5
do not change the settings then click start.
after that Reboot your tablet and do the ODIN process again, Click PDA again then navigate to the Firmware folder you downloaded a while ago,
there will be 3 files, choose the largest file and click start again, it will now install a new Fresh Official Firmware...
WAIT!!
We're Not done yet!
upon competion you tablet will reboot, it will bootloop once again dont worry I got it fixed
restart your tablet then go hold the volume down button agin but his time choose the other one we didnt choose a while ago, after that format your data, format your cache then hit reboot!
ang WHHHAAALLLA! Your Tablet is ALIVE again!!!
I effortly do this coz i know the feeling of being pissed desperately finding a solution. so I hope this help anyone who faced the same problem!!
Ciao! Im gonna sleep its 4:55 Am!
As the title states, I had to factory reset my S2. It was because I was giving it to my step dad after getting a new phone, I decided to wipe it for him, not considering I had rooted it already.
My current dillema would be that the phone gets stuck on an unpassable "Samsung Galaxy S II" splash screen when the phone turns on.
Does anyone have any suggestions, fixes, or general help?
I much appreciate it.
Doing a full wipe shouldn't cause it to get stuck at the logo. Try and supply a little more detailed info. Also boot into recovery and reflash what ever ROM
Well, it started happening when factory reset it.
I had flashed it, and put the rom on it or what ever, and then every the reset it does that.
At first, with a different battery, I had it on an infinite battery charging loop where It would power on the LED, say the battery is charging, and it would only become warm and not hold a charge.
I thought it was the battery, so I replaced it and now it gets stuck on a infinite logo boot splash. I have to keep trying to turn it on and off to get the splash to show more often.
What ROM? What kernel? And to be clear this is a sgh-i777 gs2?
MIrokux1337x said:
Well, it started happening when factory reset it.
I had flashed it, and put the rom on it or what ever, and then every the reset it does that.
At first, with a different battery, I had it on an infinite battery charging loop where It would power on the LED, say the battery is charging, and it would only become warm and not hold a charge.
I thought it was the battery, so I replaced it and now it gets stuck on a infinite logo boot splash. I have to keep trying to turn it on and off to get the splash to show more often.
Click to expand...
Click to collapse
See if you can enter download mode. If so, use the back to stock guide that's stickied.
Sent from my SGH-i777 using xda app-developers app
Shawn said:
See if you can enter download mode. If so, use the back to stock guide that's stickied.
Sent from my SGH-i777 using xda app-developers app
Click to expand...
Click to collapse
I cannot enter download mode. Holding Volume down and the power button only shows the splash again, and then it stays on a black screen.
In regaurds to the Kernal and Rom, I do not remember.It was the most popular ones I think, for what that's worth lol
OK....not to sound terse....but you haven't provided any info. ie...phone make and model, ROM and kernel There are several popular ROMs, it depends on your personal preference. A little safe advice is to search, read read and reread ....the stickies are a great source of information.
This forum is for the galaxy s 2 i777 with AT&T . Take out your battery and make sure it says you have an i777 under the battery. If you don't you're in the wrong forum.
MIrokux1337x said:
I cannot enter download mode. Holding Volume down and the power button only shows the splash again, and then it stays on a black screen.
In regaurds to the Kernal and Rom, I do not remember.It was the most popular ones I think, for what that's worth lol
Click to expand...
Click to collapse
Phalanx7621 said:
This forum is for the galaxy s 2 i777 with AT&T . Take out your battery and make sure it says you have an i777 under the battery. If you don't you're in the wrong forum.
Click to expand...
Click to collapse
Yeah, that is not the button combo for this device.
Sent from my Nexus 7 using Tapatalk HD
Odin back to stock.
Sent from my SGH-I727 using xda app-developers app
Phalanx7621 said:
This forum is for the galaxy s 2 i777 with AT&T . Take out your battery and make sure it says you have an i777 under the battery. If you don't you're in the wrong forum.
Click to expand...
Click to collapse
Cmon now, Im not that ignorant. I do have the right forum for the right phone.
I got it to go to download mode by holding the volume keys and the power key.
I want to get it back to stock.
I used Cyanogen or something.
I used CWM and Odin I think
Its been so long!
MIrokux1337x said:
Cmon now, Im not that ignorant. I do have the right forum for the right phone.
Click to expand...
Click to collapse
you have no idea how many times we get skyrocket i727 and i9100 users here....
MIrokux1337x said:
Cmon now, Im not that ignorant. I do have the right forum for the right phone.
I got it to go to download mode by holding the volume keys and the power key.
I want to get it back to stock.
I used Cyanogen or something.
I used CWM and Odin I think
Its been so long!
Click to expand...
Click to collapse
Read the stickies....all the info is there, I checked for you....enjoy.....and pirateghost is right.
lilbigdude1 said:
Read the stickies....all the info is there, I checked for you....enjoy.....and pirateghost is right.
Click to expand...
Click to collapse
So, I followed the Back to Stock guide in the stickies.
This is my issue
"<OSM> All threads completed. (succeed 0 / failed 0)
<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> cache.img
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
"
In ODIN
MIrokux1337x said:
So, I followed the Back to Stock guide in the stickies. This is my issue...
(succeed 0 / failed 1)
Click to expand...
Click to collapse
This is somewhat difficult to address, mostly because you don't remember what custom firmware you had put on it, and because you did not give a detailed description of what caused the problem (at least not detailed enough anyway.)
The stock package that you flashed from the back to stock guide is missing bootloaders. The first thing to try is: Go to the Download Repository (link in my sig) and get the full stock distribution and flash that. See if that works.
creepyncrawly said:
This is somewhat difficult to address, mostly because you don't remember what custom firmware you had put on it, and because you did not give a detailed description of what caused the problem (at least not detailed enough anyway.)
The stock package that you flashed from the back to stock guide is missing bootloaders. The first thing to try is: Go to the Download Repository (link in my sig) and get the full stock distribution and flash that. See if that works.
Click to expand...
Click to collapse
Which of those should I be downloading?
MIrokux1337x said:
Which of those should I be downloading?
Click to expand...
Click to collapse
I'd suggest you try flashing the I777UCKH7-CL503881 Stock Binaries. This is the original 2.3.4 Gingerbread that came with the phone when it first came out. See if that flash will go all the way through and boot.
Possible same type of issue and need to cohijack this thread.
OK so let me start off with, great site. I have read a ton of information but this is the only thread in my searches that I feel (and I could be wrong) is about 100% on with my issue.
First: Siyah 4.3.3 (Latest) Kernel
ROM; SHOstock3 v2.5.9
Issues:
Today I decided to encrypt my device while also doing a sim pin lock. Of course I shouldn't have messed with it but we had just finished discussing encryption, cryptography, and securing mobile devices in my Cryptography and Hashing Algorithm MSIT class. Well so I did that today and it went fine. When I did the pin for my sim lock it was a 4 pin number. Well later on I went to unlock it and it wouldn't take it in the PUK saying I needed an 8 number pin. Well I didn't create an 8 number pin just a 4 number one. After trying multiple combinations I sim locked my phone and had to go to AT&T to get a new one (thank goodness my phone actually went back to the stock 4.0.3 update I had on there originally) Well I tried to revert back to SHOstock3 v2.5.9 and it kept asking for my encryption password. I put the right password in and it wouldn't take it. So I tried another password and it looked like it accepted it, went the cool yin/yang purple fish symbol then rebooted again and now it is stuck at the Samsung Galaxy S2 white letter splash screen. It doesn't go black at all and just stays on there. I have taken out the sim card, battery, and microSD card and tried several methods (3 button combo, 2 button combo, 1 button with USB plugged into computer, OneClick Unbrick Software ((doesn't work for some reason in Win 7x64 and Win 8x64 it doesn't do the drivers even though I have them installed and I Cannot get to recovery or download mode))) and no luck. I cannot get to download mode that I know of unless that actually is where I can select (with a warning) to download a custom OS or push the down arrow to reboot. Well I am stuck in that or the splash screen and I cannot get out of it or fix anything. It seems the password wasn't correct, the encryption deleted all the files (or whatever it said), and I am now in limbo.
I do know that when I get to (what I assume) may actually be download mode??? that it says ODIN (I am using MobilOdin Lite) and it says Samsung OS on it (I believe that is what it said).
Any help is greatly appreciated it. While in that mode my computer doesn't see the phone, using the OneClick I cannot load any drivers for the phone using the Zardig or whatever it is, or anything like that. I may be totally missing something easy on the boards to fix this issue but it has been driving me nuts! Any help is appreciated.
Apologies to the OP and if I am in the wrong or out of place or line I apologize and please let me know. Feel free to email me if need be.
Thanks.
Eagle.
creepyncrawly said:
I'd suggest you try flashing the I777UCKH7-CL503881 Stock Binaries. This is the original 2.3.4 Gingerbread that came with the phone when it first came out. See if that flash will go all the way through and boot.
Click to expand...
Click to collapse
Now it is giving me this:
"<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.bin
<ID:0/003> sbl.bin
<ID:0/003> param.lfs
<ID:0/003> cache.img
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
"
All I remember about what I did was I think it was CyangenMod, it was ICS, because everytime I booted the phone, the start logo was a purple ellipse with ICS text in it, it used apolo music and had TouchWiz, I dont think I did custom binaries, my download mode says Samsung Official, And the phone worked fine until I factory reset the phone. That is litterally what happen.
MIrokux1337x said:
Now it is giving me this: ...(succeed 0 / failed 1)
All I remember about what I did was I think it was CyangenMod, it was ICS, because everytime I booted the phone, the start logo was a purple ellipse with ICS text in it, it used apolo music and had TouchWiz, I dont think I did custom binaries, my download mode says Samsung Official, And the phone worked fine until I factory reset the phone. That is litterally what happen.
Click to expand...
Click to collapse
I've never used CyanogenMod, except to try it out for a few days when ICS first appeared, so I'm not very familiar with the problems that it can cause. I have seen numerous instances of people reporting some variety of soft brick problem after using CM over the past year+. I don't usually read the threads about problems with CM either. Therefore, this may be more difficult to trouble shoot. Maybe someone with more experience with CM can jump in and help.
First, you need to determine whether the problem is in the phone or in some other part of the system. So try to eliminate other possible sources of the problem, such as: use a different usb cable, different port on your computer, a different computer, etc. Any of these external things that could cause a flash to fail.
If you're sure that the problem is in the phone, then you should probably try flashing just individual parts of the firmware, such as just the kernel, etc.
---------- Post added at 09:38 AM ---------- Previous post was at 09:33 AM ----------
WarEagleUS said:
OK so let me start off with, great site. I have read a ton of information but this is the only thread in my searches that I feel (and I could be wrong) is about 100% on with my issue.
First: Siyah 4.3.3 (Latest) Kernel
ROM; SHOstock3 v2.5.9
Issues:
Today I decided to encrypt my device while also doing a sim pin lock. Of course I shouldn't have messed with it but we had just finished discussing encryption, cryptography, and securing mobile devices in my Cryptography and Hashing Algorithm MSIT class. Well so I did that today and it went fine. When I did the pin for my sim lock it was a 4 pin number. Well later on I went to unlock it and it wouldn't take it in the PUK saying I needed an 8 number pin. Well I didn't create an 8 number pin just a 4 number one. After trying multiple combinations I sim locked my phone and had to go to AT&T to get a new one (thank goodness my phone actually went back to the stock 4.0.3 update I had on there originally) Well I tried to revert back to SHOstock3 v2.5.9 and it kept asking for my encryption password. I put the right password in and it wouldn't take it. So I tried another password and it looked like it accepted it, went the cool yin/yang purple fish symbol then rebooted again and now it is stuck at the Samsung Galaxy S2 white letter splash screen. It doesn't go black at all and just stays on there. I have taken out the sim card, battery, and microSD card and tried several methods (3 button combo, 2 button combo, 1 button with USB plugged into computer, OneClick Unbrick Software ((doesn't work for some reason in Win 7x64 and Win 8x64 it doesn't do the drivers even though I have them installed and I Cannot get to recovery or download mode))) and no luck. I cannot get to download mode that I know of unless that actually is where I can select (with a warning) to download a custom OS or push the down arrow to reboot. Well I am stuck in that or the splash screen and I cannot get out of it or fix anything. It seems the password wasn't correct, the encryption deleted all the files (or whatever it said), and I am now in limbo.
I do know that when I get to (what I assume) may actually be download mode??? that it says ODIN (I am using MobilOdin Lite) and it says Samsung OS on it (I believe that is what it said).
Any help is greatly appreciated it. While in that mode my computer doesn't see the phone, using the OneClick I cannot load any drivers for the phone using the Zardig or whatever it is, or anything like that. I may be totally missing something easy on the boards to fix this issue but it has been driving me nuts! Any help is appreciated.
Apologies to the OP and if I am in the wrong or out of place or line I apologize and please let me know. Feel free to email me if need be.
Thanks.
Eagle.
Click to expand...
Click to collapse
The first thing to try is to perform a wipe data/factory reset from recovery. Since you are encrypted, you may get a password dialog. If so, enter the wrong number continuously until you have gone through the dialog, I think it is 5 times, and then it should let the phone reset. See if that clears things up for you.
Btw, your problem is not similar to the op.
Hey guys, so I'm having some trouble with my Verizon Samsung Galaxy S4. Let me tell you what's going on.
A couple nights ago I was using my phone and it just SHUT OFF. No overheating, no water damage. At first I thought the battery had died, but then I remembered that I still had about 40% left before it shut off. Either way, I swapped out my battery with my fully charged one (I carry around a fully charge spare), but my phone still wouldn't turn on. When I got home, I plugged my charger into my phone and it vibrated, but the only thing that showed up on the screen was a grey battery cell and a little white loading circle icon, but the loading circle wasn't rotating or moving at all, just still. This would show up on my screen for about 30 seconds, and then go black, and then the phone would vibrate again and the same thing would appear on my screen. This cycle would just continue as long as the charger was plugged into the phone. The only other screen I could get to is the one that says "Odin Mode" at the top, and says "Downloading...Do not turn off target!!". I got to this screen by holding down the power button and volume down. Whenever I tried to hold down the power button and volume up to boot into "Recovery Mode", it would display the Samsung logo, and then shut off and go back to the battery cell and white loading circle cycle. Keep in mind that I can't get anything to display on the screen when the battery isn't plugged in.
I did some research and found that some other people have run into this issue before, and I've tried doing what worked for them, but no luck for me so far. I didn't really know a lot about what I was doing, but I followed directions very carefully. I've downloaded Odin for my computer, and I've downloaded a couple different firmwares from different sites. I've opened Odin, selected the firmware for PDA, and clicked Run, but each time I've tried this, I get something like:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I keep on getting a FAIL.
Now, whenever I plug in my phone, I get a screen that says
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I don't see the battery cell and white loading circle anymore. Also I can still get to the page that says "Downloading...Do not turn off target!!"
Help me fix this please!!!
The same exact thing happened to mine just two weeks ago. I tried many things to no avail. I was on CM10.2 at the time, was able to get to download mode ( pretty sure mine said "Download Mode", not"Odin Mode" ). I flashed stock, which for me was MDK, first with heimdall, them with Odin, no change. I ended up going to Verizon and they did a warrantee replacement, no problem.
I know it's a bummer, but it's probably hardware. I don't know why you're not able to flash, but were you using a factory tarfile? If not you should try that if only so that when you bring it back to Verizon you're back to stock even though I'm not sure it will make any difference given it won't turn on.
So sorry to be the bearer of bad tidings. For me at least there was a silver lining in that stock 4.3 seems to run much better thank CM10.2. Refurbs are all MDE(?) so I was able to root and the phone is working so well now I'm actually glad I can't flash! Also by the way I actually did two replacements as the first had a crappy Bluetooth antenna. Anyway good luck.
Sent from my SCH-I545 using XDA Premium 4 mobile app
cresny said:
The same exact thing happened to mine just two weeks ago. I tried many things to no avail. I was on CM10.2 at the time, was able to get to download mode ( pretty sure mine said "Download Mode", not"Odin Mode" ). I flashed stock, which for me was MDK, first with heimdall, them with Odin, no change. I ended up going to Verizon and they did a warrantee replacement, no problem.
I know it's a bummer, but it's probably hardware. I don't know why you're not able to flash, but were you using a factory tarfile? If not you should try that if only so that when you bring it back to Verizon you're back to stock even though I'm not sure it will make any difference given it won't turn on.
So sorry to be the bearer of bad tidings. For me at least there was a silver lining in that stock 4.3 seems to run much better thank CM10.2. Refurbs are all MDE(?) so I was able to root and the phone is working so well now I'm actually glad I can't flash! Also by the way I actually did two replacements as the first had a crappy Bluetooth antenna. Anyway good luck.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Aw man...How do I get the factory tarfile so I can try that?
I would make sure you're using a file which matches whatever you're on. If you were on ME1 and flashing MDK of course it's going to fail. I'm guessing you know that part. I would try using a different USB cable and different ports on your pc. For whatever reason, mine fails more than it's successful but eventually after 3 or 4 attempts it will complete successfully. It may not help in your case but it's worth a try if you have mdk. I even had one instance where I couldn't get Odin 3.09 to complete successful but installed 3.07 and it worked first try. The whole process seems to be very unstable.
troysbama1 said:
I would make sure you're using a file which matches whatever you're on. If you were on ME1 and flashing MDK of course it's going to fail. I'm guessing you know that part. I would try using a different USB cable and different ports on your pc. For whatever reason, mine fails more than it's successful but eventually after 3 or 4 attempts it will complete successfully. It may not help in your case but it's worth a try if you have mdk. I even had one instance where I couldn't get Odin 3.09 to complete successful but installed 3.07 and it worked first try. The whole process seems to be very unstable.
Click to expand...
Click to collapse
I actually don't know which file I am on right now...so if I could find out, I would match it and run that? I'm very new to all of this, and I don't really know what I'm doing.
Thanks for the help! I really appreciate it.
josephnosack said:
I actually don't know which file I am on right now...so if I could find out, I would match it and run that? I'm very new to all of this, and I don't really know what I'm doing.
Thanks for the help! I really appreciate it.
Click to expand...
Click to collapse
How long have you had the phone and do you know when was the last OTA update you took?
troysbama1 said:
How long have you had the phone and do you know when was the last OTA update you took?
Click to expand...
Click to collapse
I got the phone right around August 15, 2013. And the last update I did was probably a week before the phone stopped working, so around November 3rd.
josephnosack said:
I got the phone right around August 15, 2013. And the last update I did was probably a week before the phone stopped working, so around November 3rd.
Click to expand...
Click to collapse
In that case it sounds like you were on 4.3 since that update came out around Nov 1. Which would mean there's only one file you're going to have any success with. If I was you I would go for a warranty replacement. If you were on mdk and trying to keep an unlocked bootloader then I would try everything imaginable but in your case there's really nothing to lose. You're going to lose your data either way and there's no guarantee this won't happen again in a week if it's hardware related. That's your call though so here are a couple links which should help you get the file and possibly have success installing.
If you look at your first post you tried installing ME7 but I'm fairly certain MJ7 is the only one that's going to work in your case.
http://forum.xda-developers.com/showthread.php?t=2507253 - Odin file
http://forum.xda-developers.com/showthread.php?t=2290771 - Odin instructions
troysbama1 said:
In that case it sounds like you were on 4.3 since that update came out around Nov 1. Which would mean there's only one file you're going to have any success with. If I was you I would go for a warranty replacement. If you were on mdk and trying to keep an unlocked bootloader then I would try everything imaginable but in your case there's really nothing to lose. You're going to lose your data either way and there's no guarantee this won't happen again in a week if it's hardware related. That's your call though so here are a couple links which should help you get the file and possibly have success installing.
If you look at your first post you tried installing ME7 but I'm fairly certain MJ7 is the only one that's going to work in your case.
http://forum.xda-developers.com/showthread.php?t=2507253 - Odin file
http://forum.xda-developers.com/showthread.php?t=2290771 - Odin instructions
Click to expand...
Click to collapse
That Odin file worked!! So thank you for that!!
But now the phone is back to when it first broke down. It's vibrating once, displaying the empty battery cell with the little white loading circle, and shutting off, and repeating.
You're gonna have to warranty replace it then. Odin takes you back to stock image so there must be a hardware issue.
Sent from my SCH-I545 using Tapatalk
troysbama1 said:
You're gonna have to warranty replace it then. Odin takes you back to stock image so there must be a hardware issue.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Alright, thanks so much for the help. Do you think I'll run into any issues getting a replacement considering I've tried to root my phone before (but was unsuccessful)..? If so, what should I do before I bring it to verizon?
josephnosack said:
Alright, thanks so much for the help. Do you think I'll run into any issues getting a replacement considering I've tried to root my phone before (but was unsuccessful)..? If so, what should I do before I bring it to verizon?
Click to expand...
Click to collapse
You should be fine. Flashing the factory stock will have cleared the "Custom" flag, so even if they can get it to work, it'll look clean.
Hey XDA,
I'm a complete noobie when it comes to rooting/unrooting and all that.
My phone (Galaxy S2) was on Android 2.3.5 and it was acting slow and draining my battery.
I tried to fix it but after everything I was getting frustrated and tried to update it to the latest version.
Samsung Kies did not recognise my S2, but it did recognise my girlfriend's S3.
My problem started when I tried to put the SimpleUpgradeTool that Samsung provided onto my phone, everything worked, but during the installation, it said 'Error occured'. The phone died and now I'm stuck with a phone which doesn't turn on (Stuck on Samsung S2 screen with Yellow Exclamation Mark) and if I press Volume + Power + Home Button, it starts up the Clockwork Mod 4.0.0.2)
My phone isn't recognized by Odin or Kies now. =/
My question is; is my phone fixable? As far as I'm aware, the only thing on my phone at the moment is the Clockwork Mod.
I can't access anything else.
If any of you could help, that'd be very helpful. I've got something in 2 days and it'd be amazing if I could use my phone before then.
First, boot into recovery (the 'Volume + Power + Home Button' thing) & try a factory reset. If the problem persists, the only way you're fixing it is by flashing a stock rom with Odin.
As you can't seem to get your PC & phone to recognise each other, you need to find Hopper8's 'Odin troubleshooting' thread stickied in General, and do as many of the troubleshooting steps in that thread as many times as you need to until you get a successful flash of stock.
This is the only way you'll be fixing your phone for your 'something in two days'.
MistahBungle said:
First, boot into recovery (the 'Volume + Power + Home Button' thing) & try a factory reset. If the problem persists, the only way you're fixing it is by flashing a stock rom with Odin.
As you can't seem to get your PC & phone to recognise each other, you need to find Hopper8's 'Odin troubleshooting' thread stickied in General, and do as many of the troubleshooting steps in that thread as many times as you need to until you get a successful flash of stock.
This is the only way you'll be fixing your phone for your 'something in two days'.
Click to expand...
Click to collapse
First of all; thank you so much for replying!
I tried to 'jump start' my phone. Success! (I guess?) It's in Download Mode now.
After trying Odin v1.8.5 it recognised my phone and I downloaded a normal stock kernel (is that what it's called?)
Anyways; this happened:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Should I try it again or do you have any other advice?
I advise you to follow the advice I gave you in my previous post - Hopper's thread is 'the Bible' for these situations, and you need to go through as much of the stuff in his thread as many times as you need to until you get a successful flash.
We're not there with you looking over your shoulder seeing what you're doing right/wrong, so the best we can do in this situation is give you the tools the get the job done (I.E Hopper's thread), the rest is up to you.
MistahBungle said:
I advise you to follow the advice I gave you in my previous post - Hopper's thread is 'the Bible' for these situations, and you need to go through as much of the stuff in his thread as many times as you need to until you get a successful flash.
We're not there with you looking over your shoulder seeing what you're doing right/wrong, so the best we can do in this situation is give you the tools the get the job done (I.E Hopper's thread), the rest is up to you.
Click to expand...
Click to collapse
EDIT: Dear MistahBungle; I wish I could kiss you right now, as you've sorta helped me through out, after trying it a few times it gave me the 'Hello' blahblah menu and I could input my e-mail again.
God, I hope I never have to go through this again.
Trust me, you don't want to kiss me. That will probably make you very ill.
OK. So I take it that means you got a successful Odin flash, the phone rebooted after the flash, and took you to the phone setup screen you get when you input your Google account details, the timezone, etc, etc ?
Good.
And the best bit ? You fixed it yourself.
Ha ha lol......sounds like you have a fan there @MistahBungle
And @robinboelens.....feelin that satisfaction yet?
My wife says I'm a phone geek....She's probably right
keithross39 said:
Ha ha lol......sounds like you have a fan there @MistahBungle
And @robinboelens.....feelin that satisfaction yet?
My wife says I'm a phone geek....She's probably right
Click to expand...
Click to collapse
Honestly, I was stressed out and it took me all afternoon. It was just going downhill from the start untill I saw the light.
I still have 2 problems;
1. The phone acts like it is plugged in ALL THE TIME. I have had this problem for months, it kept looping the MTP initializing to MTP connected without me plugging it in. I believe this is part of the reason why I had such a massive battery drain problem.
2. When my phone is off and not plugged in; whenever I try to turn it on it shows the battery screen (as if it is charging) and it won't go on.
Sometimes this problem is persisted and it will start saying that it's overheating, but popping the battery out + plugging it in will fix this problem.
Very annoying.
Any ideas?
The fact that you have completed a successful odin flash kinda rules out a software issue....I guess the problems you are having now are similar to the problems you were having before the flash?
That being the case, I'd start to look at hardware......
The MOST common part to fail on the S2 is the USB port and board assembly....
The range of fault symptoms caused by this part failing *can* (but not always) include phantom charging/connection indicators.
If you click on my profile, you should come across "my topics"....
And there you will find a guide on replacing this part.....it's easy and cheap to do....but make sure you read it ALL......including the bit about rev versions.....VERY important to get that right.....
My wife says I'm a phone geek....She's probably right