I was running the safestrap that I installed off this guide: http://forum.xda-developers.com/showthread.php?t=2720163 -- hadn't changed it since. So yeah...today my phone started just randomly turning off. I figured nothing of it until it didn't want to turn on again. I played with it, tried to backup stuff when I could boot into it (got most personal stuff, so that's good), and yeah..I couldn't. So I thought I would try flashing back to stock via Odin. Well, I started to flash back, and all of a sudden it failed. So now, I have a problem. Instead of boot looping like it was before (battery in, would vibrate in a second, flash logo for about two seconds, then go black) - I put the battery in, it vibrates in about two seconds and says Firmare Upgrade Encountered an Issue. Please go into Kies recovery and try again or whatever. If I go into Odin mode, it goes there, and then basically shuts back off, so I can't even get Odin to work correctly with it.
Funny..the whole reason I had to upgrade from my S3 was because it did this same thing, battery in, booted, then flashed logo and went black. Couldn't 'unbrick' it. Only common link is the SD card...wonder if that did it.
Try what this guy did.......
http://forum.xda-developers.com/galaxy-s4-verizon/help/stuck-odin-mode-odin-flashes-failing-t2992063
I can't get it to stay in download mode without going to a black screen, as I mentioned.
EDIT: I was able to get it to quickly boot in there and get the pit file flashed. What should I do now?
It's still boot looping after the pit file. When I was in the OS, it crashed and restarted the phone.
Okay, well, I got it into Safestrap recovery and rebooted the phone to stock. It seems to have fixed it for now. What do I need to flash back to complete stock? Get rid of safestrap, root, etc.
I am probably going to get rid of this, I'm tired of Samsung's crap with this one. Maybe buy an LG G3.
EDIT: I type that, and go into settings and the POS just goes black. FFS.
I have Safestrap and the Eclipse rom, for what it is worth.
Phone didn't reboot all last night on the charger. Still on as of right now...but haven't done hardly anything on it.
It is on NC5 right now.
Did the same thing again, shut off, removed battery + turned back on, shut off again, now it is back on after same steps...this is past annoying.
GuitarrassDeAmor said:
Did the same thing again, shut off, removed battery + turned back on, shut off again, now it is back on after same steps...this is past annoying.
Click to expand...
Click to collapse
I am wondering if you have a physical hardware fault perhaps the NAND is on its way out
I know NC5 has some system crash issues related to knox I would try uninstalling knox via titanium backup or use the system server crash fix via xposed
Legitsu said:
I am wondering if you have a physical hardware fault perhaps the NAND is on its way out
I know NC5 has some system crash issues related to knox I would try uninstalling knox via titanium backup or use the system server crash fix via xposed
Click to expand...
Click to collapse
I do not see Knox in Titanium backup. Was able to get the phone to download that and browse somehow...reinstalled Xposed and rebooting after installing framework.
It is now screwed up still. Not wanting to boot, when it does, basically it seems if screen goes off it wants to reboot, etc.
all I can say is odin back to stock nk1
https://www.androidfilehost.com/?fid=95832962473399455
and don't touch anything else
if it still is crashing then its probably a hardware problem
flash using the odin pda and untick eveything else
Will try that when I get home. Hoping it isn't a hardware problem, but sounds like it. What is weird is this is the same thing my GS3 did, except I can't at all get that one to do any kind of booting back into anything without just restarting almost instantly (even Odin mode) so I assumed it was fully dead.
GuitarrassDeAmor said:
Will try that when I get home. Hoping it isn't a hardware problem, but sounds like it. What is weird is this is the same thing my GS3 did, except I can't at all get that one to do any kind of booting back into anything without just restarting almost instantly (even Odin mode) so I assumed it was fully dead.
Click to expand...
Click to collapse
it could be the partitions are messed up from using a pit
never screw with the partitions if you can help it its asking for trouble with a locked bootloader
There have been several posts about faulty power switches, sounds very familiar to what you are experiencing.
sent from a Galaxy S4 far far away.
gadget! said:
There have been several posts about faulty power switches, sounds very familiar to what you are experiencing.
sent from a Galaxy S4 far far away.
Click to expand...
Click to collapse
I had this exact same thought...I wonder.
Legitsu said:
it could be the partitions are messed up from using a pit
never screw with the partitions if you can help it its asking for trouble with a locked bootloader
Click to expand...
Click to collapse
Tried flashing...failed in the middle
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Dammit...will try again when I get back home.
GuitarrassDeAmor said:
I had this exact same thought...I wonder.
Tried flashing...failed in the middle
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Dammit...will try again when I get back home.
Click to expand...
Click to collapse
you could ask somebody running a stockrom Verizon nk1 to create PIT file for you using pit-magic I would but I am no longer running stock on any of my phones
http://forum.xda-developers.com/showthread.php?t=1916936
if you used a MDK or developer edition pit file this could indeed be a issue
also as silly as it may sound try using the original white samsung usb-cable
I got it back to completely stock just now using the "I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME" Image and the pit here (not the same place I got it from, but same one I believe) http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/.
We'll see how it goes...
It survived all night. I think the power button may be a/the problem - I press it now and it doesn't want to turn off the screen. It sometimes turns the power menu on after a few seconds. Going to try this when I get home. https://www.youtube.com/watch?v=pqBgbN8NLjI -- Not that it seems the safest, but already ordered a G3 so who cares I guess.
So interesting update. While my phone is working fine now, I mentioned the same thing was happening on my GS3 and that is why I upgraded. So, I opened it, played with the power button a bit, and voila, fixed. My G3 will be here on Monday, then I am done with Samsung now after the Fascinate, GS3, and GS4.
Related
I was following the guide listed at http://forum.xda-developers.com/showthread.php?t=849028 to get a different rom installed on my phone, and now am unable to boot. First step was to root the phone using the update.zip, which worked fine. I then purchased and installed the ROM manager app, and got it installed and working. I backed up using it, and rebooted. I then cleared all user data (since the phone had been someone else's, and I didn't want all of their apps and stuff) and was still able to boot fine. I then used the function in MOD Manager to partition my SD card (since it was a new 32gb one I had purchased just for this phone) and it rebooted into the green-text mode, seemed to partition fine, but won't start now.
Holding down the power button can cause it to try to start, going through the pick T-Mobile info and then the rainbow Galaxy S stuff, but then it turns off. Holding down the volume buttons while booting can still get me into the stock downloader, but not the CWM green text one. I tried using the thread info on using ODIN to try to restore my phone, but none of the links work anymore. Doing searches all resulted in people using ODIN, or one thread where no one responded but the OP was saying that the ODIN site was down.
My phone is a Samsung Galaxy S Vibrant, and originally (and still does kind of) had Android 2.2 installed (never got the 2.3 update). I'm on T-Mobile, and like I mentioned, using a fresh MicroSD card.
Please help, I'm not sure what steps to take next. I understand that the phone probably isn't bricked, but I sure don't know what steps to do next to try and get it booting up again.
~edit~
As an update, I decided to try taking out the MicroSD card, and all of the lights on the bottom lit up (where the touch buttons are). The screen stayed blank though. Holding down the power button restarted it again and now it is all black again.
Also, I would be willing to use ODIN to try and restore it if anyone had an alternative download location, I've just been unable to find one yet.
All the files you need including odin are here....
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Okay, thank you for your response. I have now downloaded the files and gone through the steps listed in the guide you linked, and am still not able to finish booting my phone. Even after using Odin to restore, it gets to the rainbow S screen, stays there for about a minute, then goes black again. Does this mean that my phone actually is done for broken?
~additional edit~
My phone doesn't seem to be off when it gets the black screen. Sometimes, and I'm still not sure what circumstances cause this, the touch buttons light up, and when I unplugged my phone after rebooting from the Odin restore, my phone made the noise that it does when it notices a disconnect, implying to me that the phone was still in communication with my computer even though I couldn't see anything.
Hey, your phone is still good, try reflashing through Odin again and leave it for 15 minutes. Then reboot. If that doesn't work, than you can try flashing froyo through odin.
Here is the log that it gave me when I tried reflashing it again this time, but I accidently left the auto-reboot on, so it did the whole boot to a black screen thing again. I'll try it again in a bit with the leave it off for 15 minutes idea.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
How do I turn it off without rebooting it? I turned off the auto-reboot, but now it's sitting at the digging android screen with the full blue progress bar saying "Do not turn of Target!!!"
I just re-read your post and realized that you might have messed up partitioning the phone with rom manager. I have read multiple times that it doesn't work. Anyways follow this thread and you should be back on track...
http://forum.xda-developers.com/showthread.php?t=745547
Links on that page are dead though. You have stock jfd files already from the link i posted. You can get Eugene's froyo that doesn't brick from here...
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
Good luck!
Steelstiletto said:
How do I turn it off without rebooting it? I turned off the auto-reboot, but now it's sitting at the digging android screen with the full blue progress bar saying "Do not turn of Target!!!"
Click to expand...
Click to collapse
Allow it to reboot after flashing, leave it alone, but if you did repartition using rom manager as Alex stated, you will need to fix that first because it doesn't partition your external sd card, but the internal memory.
Edit....flash the eugene froyo package posted above, that was my next suggestion.
Okay, I've followed the steps now up to the point where I am supposed to use the "adb reboot" command. That's actually what took me so long, I'm on a pretty slow internet connection so installing all of the Android SDK took a while, but I knew I had to do that first when I saw that adb was included as a step. But when I run the command, I get an error:
error: device not found
So right now, my phone is sitting in recovery mode and I can navigate up and down using the volume buttons, but I can't select to reboot, and I can't force a reboot with adb. I saw in another thread that someone suggested pulling the battery once the Eugene rom was flashed, but I just wanted to make sure that would be the proper step here? I don't want to do that only to find out that I won't be able to power back into download mode again if the buttons were changed to something that I don't have anymore.
~edit~
bah, apparently, fourth time is a charm, and adb finally recognized the device. Moving on to the next step now...
Oh man, the phone works again now! Thanks for your help guys, this is much appreciated. A few questions before I go forward though.
Is the phone back to it's completely factory default state? As in, the internal memory is partitioned correctly and doesn't need to be messed with?
Also, is the phone un-rooted and will need to be rooted again?
And, last question, since using Mod Manager to partition the SD card is a bad idea, is there anything special that I should do for a new SD card, or should it just be plug-and-play?
~Edit~
Oh, one more thing, should I have the SIM and SD cards that I plan on using already in the phone as I make the changes? I currently have my SIM card in my Nexus one so that I can tether internet. Otherwise I'm offline.
Glad you got your phone back.
Yes, phone is back to stock state, partitioned and such.
Yes, it is unrooted and you'd have to root it again.
I never had to do anything special for micro sdcard to work. Plug and play.
Not sure having sim card in there would make any difference. My guess would be no.
Okay, so I finally have everything working! Thanks for all of the help, I now have Revolution 1.5 installed and running!
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.
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)
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.
Backstory (skim through if you don't care to read):
Friday morning I woke up to find my phone was off. I had fallen asleep watching netflix the night before.
Hit the power button, nothing. Checked power plug, different cable, etc. Nothing seemed to turn it on.
Eventually found after jumping online that volume down + power would soft reset the phone.
That worked, phone goes to samsung logo and sits there. I reboot it a few times and it finally comes up. Stays on for 1-2 minutes then restarts on its own.
Basic search online shows to wipe the cache partition, I do that. Phone boots up ok, lasts about 5 minutes then reboots on its own.
I get all my data backed up (in between reboots) and decide to factory data/wipe via the menu ( volume up, bixby, power if I remember now)
After that...phone starts up as if new and I'm going through the setup. While going through the setup, phone reboots on its own.
I make it again halfway through the setup, and it reboots again. I can't get through setup of the phone at this point.
I repeat a few times of wiping cache, factory data reset.
Now the phone hangs on the Samsung screen and just boot loops. I go ahead and poke around online some more and download Odin plus a painstaking 24 hour download of the stock firmware for the SM-N950U1 (XAA) (Unlocked) Note 8 firmware, then proceed to run through Odin hoping that I can go ahead and just reflash the phone and basically re-install the OS to factory specs.
Low and behold, FAIL on the flash from Odin, it hangs on system.img.ext4 after about 5 minutes of running, says FAILED (auth) in Odin, and on the phone screen it says "Secure Check Fail : system"
Also, now when I boot into Download mode, I hit Volume Up for Continue and it says that an error has accured and to replace or re-install via Smart Switch (which I tried doing but can't get it to work, it says my device is not supported once I connect it)
Lastly, just turnign on the phone normally trying to boot up, it just loads a blue screen that says "Please re-install the factory image" or something to that effect.
I know this is long, but is there anything I can do to get this to take the stock firmware again? I can still connect to Odin and it will try to run through a process, it just fails every time.
Is there some special combination of Odin, USB drivers and firmware that might work? I keep reading that these phones are tricky and I've tried every cable and USB port that I can on my computer, reading that it could be as simple as that.
Anyways, I'm at a loss...any help would be appreciated. I know this was a long read.
Phone info -
Galaxy Note 8 - Model SM-N950U1 ZKAX (XAA based on Downloader info display)
Bought Unlocked from Samsung in October of 2017, have installed all OTA updates as they've come in. No other modding or messing around on this phone. I have rooted many phones in my time but haven't in a couple years.
Odin 3.13.1
Downloaded file was SM-N950U1_1_20190306182853_ecpwgsj7rn_fac.zip, 3.6 gigs, was supposed to be for XAA Unlocked Note 8 as of July of 2019, I'm assuming latest update?
I am update to date on my OTA updates, I an unlocked phone but on the Verizon network. I'm reading that I have to flash my phone with whatever build my phone was on, ie..not too new or too old, correct? Maybe the build I downloaded was too new? To my knowledge, I have no way of finding out what build I was on at this point...
Error report from Odin:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6043 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> abl.elf
<ID:0/006> bksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> tz.mbn
<ID:0/006> hyp.mbn
<ID:0/006> devcfg.mbn
<ID:0/006> pmic.elf
<ID:0/006> rpm.mbn
<ID:0/006> cmnlib.mbn
<ID:0/006> cmnlib64.mbn
<ID:0/006> keymaster.mbn
<ID:0/006> apdp.mbn
<ID:0/006> msadp.mbn
<ID:0/006> sec.dat
<ID:0/006> NON-HLOS.bin
<ID:0/006> storsec.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
UPDATE:
Out of nowhere I was able to use Odin 3.13b (patched) (used many times before with no success) and a May 2019 Andoird 9 XAA version of the firmware.
Odin PASSED and now I get the Samsung Galaxy Note 8 screen when it boots up...however it just boot loops this screen with two small vibrations in between reboots.
I have recovery mode again now, and Download mode is back to normal, but it still won't boot into Android.
Also randomly I'm getting pixels across the screen (a thin line) of red or white pixels that blink on and off, then go away once I'm fulling booted into either recovery or download mode. Just odd, never saw that before this all happened.
Where can I go from here? Now that I have somewhat of a restored phone, at least being able to get to all of the recovery/downloader menus like normal, what would you do from this point to actually boot into the OS?
Thanks!
playbacktri said:
UPDATE:
Out of nowhere I was able to use Odin 3.13b (patched) (used many times before with no success) and a May 2019 Andoird 9 XAA version of the firmware.
Odin PASSED and now I get the Samsung Galaxy Note 8 screen when it boots up...however it just boot loops this screen with two small vibrations in between reboots.
I have recovery mode again now, and Download mode is back to normal, but it still won't boot into Android.
Also randomly I'm getting pixels across the screen (a thin line) of red or white pixels that blink on and off, then go away once I'm fulling booted into either recovery or download mode. Just odd, never saw that before this all happened.
Where can I go from here? Now that I have somewhat of a restored phone, at least being able to get to all of the recovery/downloader menus like normal, what would you do from this point to actually boot into the OS?
Thanks!
Click to expand...
Click to collapse
Take it to a service or return it to Samsung for a repair or replacement. And if they ask you if you tempered with the OS, say that you didn't, just say that you were watching Netflix and then it randomly rebooted ( don't say that you fell asleep).
DankMemz said:
Take it to a service or return it to Samsung for a repair or replacement. And if they ask you if you tempered with the OS, say that you didn't, just say that you were watching Netflix and then it randomly rebooted ( don't say that you fell asleep).
Click to expand...
Click to collapse
I should have tried to do that today. Before you posted your reply, I tried to reflash again since it worked once, and it has failed every time since then and now I'm back to where I was before with the phone saying it needs to be recovered with the stock image, etc.
I know it worked once, so I've been just trying it 100 times waiting for it to finally take, no luck so far.
Could this be a corruption issue of the internal memory/sd card? Mine is the 64gb model.
It just hangs everytime saying the system.img.ext4 has an FAIL! (auth) and on the phone it says "Secure Check Fail : System"
It's as if it doesn't have the permissions to write the .img file.
playbacktri said:
I should have tried to do that today. Before you posted your reply, I tried to reflash again since it worked once, and it has failed every time since then and now I'm back to where I was before with the phone saying it needs to be recovered with the stock image, etc.
I know it worked once, so I've been just trying it 100 times waiting for it to finally take, no luck so far.
Could this be a corruption issue of the internal memory/sd card? Mine is the 64gb model.
It just hangs everytime saying the system.img.ext4 has an FAIL! (auth) and on the phone it says "Secure Check Fail : System"
It's as if it doesn't have the permissions to write the .img file.
Click to expand...
Click to collapse
There is something pretty wrong with your device... Can't say if its hardware or software... As I said, take it to a service or to Samsung, idk
DankMemz said:
There is something pretty wrong with your device... Can't say if its hardware or software... As I said, take it to a service or to Samsung, idk
Click to expand...
Click to collapse
Yeah I might do that. I'm about 1.5 hours away from any Official Samsung repair place, so I might find time to do it this week. I just figured this was the place to ask about these types of issues as its probably most common to find during rooting and modding.
playbacktri said:
Yeah I might do that. I'm about 1.5 hours away from any Official Samsung repair place, so I might find time to do it this week. I just figured this was the place to ask about these types of issues as its probably most common to find during rooting and modding.
Click to expand...
Click to collapse
Did you try the 4 file repair ?
https://www.windows4droid.tk/2018/12/4files-n950f.html
https://www.youtube.com/watch?v=8a95Tv--r4o
These links are just examples, don't give up - it seems it's soft brick, it can be done.
Good luck!
w41ru5 said:
Did you try the 4 file repair ?
https://www.windows4droid.tk/2018/12/4files-n950f.html
https://www.youtube.com/watch?v=8a95Tv--r4o
These links are just examples, don't give up - it seems it's soft brick, it can be done.
Good luck!
Click to expand...
Click to collapse
Thanks! That seems to be pretty much the same process I've already been running through via Odin and the firmware files that I downloaded from Sammobile. Mine differs where it gets 75% through and then says FAIL! (auth) right after system.img.ext4, haha...
Also, I can't download any files from that site that you linked - each one says "this domain cannot be opened on our server"
playbacktri said:
Thanks! That seems to be pretty much the same process I've already been running through via Odin and the firmware files that I downloaded from Sammobile. Mine differs where it gets 75% through and then says FAIL! (auth) right after system.img.ext4, haha...
Also, I can't download any files from that site that you linked - each one says "this domain cannot be opened on our server"
Click to expand...
Click to collapse
If you made it so far to write here on xda, maybe you can find also the note 8 forums.
For example - https://forum.xda-developers.com/galaxy-note-8/how-to/collection-firmware-rom-file-galaxy-t3676943
This thread has several references to your SM-N950U - and one specifically U1 - https://drive.google.com/file/d/0B9tyXbj7guLQYS1DdFFYUEpPUWs/view
They are hosted on gdrive.
Man do some research and get your phone back to life. I've got a note 4 910C which had the same issue, and today still works with no major complaints.
C'mon gimme sum good update
w41ru5 said:
If you made it so far to write here on xda, maybe you can find also the note 8 forums.
For example - https://forum.xda-developers.com/galaxy-note-8/how-to/collection-firmware-rom-file-galaxy-t3676943
This thread has several references to your SM-N950U - and one specifically U1 - https://drive.google.com/file/d/0B9tyXbj7guLQYS1DdFFYUEpPUWs/view
They are hosted on gdrive.
Man do some research and get your phone back to life. I've got a note 4 910C which had the same issue, and today still works with no major complaints.
C'mon gimme sum good update
Click to expand...
Click to collapse
You seriously think I just have been staring at my phone and came out here to ask questions without doing any research? Hilarious.
Well, I've downloaded about 20 different firmwares from sammobile, all for the XAA version of the U1 phone, any other firmwares crash instantly in odin. Also, several different odin versions and patched versions that supposedly help bypass the errors I'm getting but no luck. I've been researching this since Friday afternoon and have done nothing but work on this phone since then.
The link you sent is for build version 1, I'm on build 5. I believe the file you posted is from almost 2 years ago. Its not even remotely current to Android 9 or would be flashable with the current bootloader.
The other link you posted only has firmware for the ATT version of the phone and is also build 1 from a couple years ago, not my unlocked current XAA version, so again...no dice.
I also posted this in the Note 8 subforum of XDA, if you bothered to look. No-one has replied there either.
If you are trying to teach me a lesson by using the search tool, you are sorely mistaken, I've searched the forums high and low before finally posting 2 days after my phone bricked before bothering anyone else. Geez.
I just considered that your are a junior member with 11 posts. You didn't mention any of these info previously - hence my assumption about what I wrote.
I did not want to teach you a lesson, only tried to help. If it sounded to harsh - my apologies - I'm 51, maybe a bit outdated & old school of search before you ask.
Hope you'll find the solution for your phone.
Update:
I was able to do this in to a Samsung repair center the other day, they took one look at it and handed it back to me and said it wasn't something they could deal with. They recommended sending it to Samsung directly. I took it to a uBreakiFixit store, which is what Samsung recommended. I heard the guy in the back talking about it saying it needed to be re-flashed and the OS put back on and he handed it back to the front desk guy who relayed the message to me, hah!
Oh well, now its a paperweight...
Just an update...
I sent the phone to Samsung and they said it needs:
Std. Repair Fee : $64.95
LCD Repair Fee : $134.05
PBA Repair Fee : $409.00
Tax : $50.16
Total $658.16
I imagine this is pretty standard for them to just basically rebuild the phone when things are behaving normally, and just pass that cost onto the consumer instead of actually trying to fix anything, hah...
Oh well, phone done and I moved on to a non-samsung replacement. No reason the phone should have just tanked after not even 2 years. It has had its occassional drops (always in a case), never got wet or dunked in water, etc. I've had phones that are still operating today that have been through worse.
Time to move on!