Hey all, have the Vibrant with root and lagfix. Got a popup today and I got so stoked that I hit accept without disabling the lagfix. I have read here that there are issues trying to install a new rom on lagfixed phones. I have no idea what odin is, and im using stock recovery which I can boot into. The phone hangs at the Vibrant screen but I hear the TMO jingle.
How do I go about bringing this phone back to stock so I can apply the update without lagfix/root?
Thanks
Use Odin..
OTA with RyanZA laf fix still applied
So I did the OTA update with RyanZA lag fix still applied (root as well), did lock up on Galaxy S screen for a while but ended up pulling out of it and loaded everything fine. (remember, the update did state that it would take ten minutes) Eventually, I noticed that the media scanning of the external sd card is stuck scanning. Wont let me access media or media hub. Everything else seemed to work. Shut down phone but phone got stuck on custom shut down. (droid peeing on apple). I pulled battery, restarted with custom I9000 startup...same thing..stuck on media scanning with a line through a SD icon on the top left that I havent seen before...any suggestions?
***Update****
For some reason I had to reformat my 8 gig SD card after OTA update, now working fine. I now have access to Media Hub which by the way...is the ****!! I cant wait to show iphone users....Also, HD recording, voice with swype, still running 2100 on quadrant, task manager now available, GPS seems to be working fine. In all, the update looks good! I did with RyanZA lag fix still applied. Not sure if that created the problems but after a couple of hard resets everything is working fine. VIBRANT ROCKS!!
It's not Froyo. It is 2.1-update1 in the Firmware. It is probably the GPS fix released earlier this week.
I just got it applied to my phone. It got stuck on the "S" screen for a LONG time. I finally pulled the battery and tried again. It got stuck for a few more minutes, but finally pulled through.
Hmm, looking further down, yea, it is the GPS fix. Build #: ECLAIR.UVJI6
my screen is stuck at samsung vibrant ive been messin with it all night how do i get out of this i hit the update while still rooted and lagfix applied ive already asked for a new phone but i would prefer to fix this one if possible someone please help us!!!!!
ODIN ODIN ODIN! There are at least 20 posts with these same problems. Read up on odin. Learn to use it. Its incredibly simple. It will be your best friend!
Hello, I'm having the same problem and took the advice given in this thread and gave Odin a shot. For PIT I used T959UVJFD.tar and for PDA I used s1_odin_20100512.pit
I hit start and nothing happens except for I get the following message:
<OSM> All threads completed. (succeed 0 / failed 0)
Odin does seem to be the way out of the dark but this was not the desired outcome. What gives?
jshug said:
Hello, I'm having the same problem and took the advice given in this thread and gave Odin a shot. For PIT I used T959UVJFD.tar and for PDA I used s1_odin_20100512.pit
I hit start and nothing happens except for I get the following message:
<OSM> All threads completed. (succeed 0 / failed 0)
Odin does seem to be the way out of the dark but this was not the desired outcome. What gives?
Click to expand...
Click to collapse
Sooooo, you put the .pit file in the PDA field and the .tar file in the PIT field???
Go here http://forum.xda-developers.com/showthread.php?t=734475
Download the 512 pit and the JFD image
In ODIN put the JFD image (tar file) in the pda field
Put the 512 (pit file) in the pit field)
Make sure you see the yellow com box light up. If it doesnt, you need the samsung drivers.
Hit start
I meant to say that I had the .tar in the pda and the pit in the pit. It looks like I needed the drivers, it's working now. Thank you so much!
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!
ok so 3 adderall and 27 hours later i finally fixed my tmo vibrant which would go to a black screen after the galaxy s screen. only the soft nuttoms would light up. problem was because of voodoo lag fix
BACKGROUND:
1) unlocked my phone so it could be used for att. used the galaxy s unlock in the market place.
2)tried downloading a voodoo lagfix and when i applied it thats when the problem arose.
3)app store never worked for me because in the process of unlocking my imei had changed some how. BUT that was not all a bad thing because i got $10 unlimited data.....
********ALLL FILES NEEDED FOR THIS********
zshare.net/download/
93177944169ab713/
FIX
ok so basically what i started doing is i started flashing the JFD through odin by putting the phone in download mode. i tried with and w/o pit file and unchecked and checked the repartion button. so it would run through all of it as it should and it passed the tests. but when the phone would load it would go to to last galaxy s screen pause for a minute and directly lead to a black screen with the soft buttons still lit up. at this point i thought the phone was gone. but then theree was light.
first of all this is something called eugene no brick froyo fix. i think this eugene guy was a foreigner cuz his directions were ****.
1)download odin 1.7 make sure its for vibrant.
2) EVERY FILE USED IS ATTACHED IN A NEAT LITTLE .RAR PACKAGE. THANK YOU
3) ok so start odin. im on win7 x64 btw. i didnt even run as administrator (it was giving me errors when i did).
4) where it says PIT load the xxxxxxxx512.pit file (x's are the starting of the file callled s1_ something that i cant recall because my brain is fried)
5) in the pda location add the .tar i gave you called EUGENE373_SamsungS_Froyo_PDA. make sure the re-partiton is checked
6) put the phone in download mode. (power down, remove battery, replace batt, hold vol up/dwn, connect usb). make sure you have the drivers for the vibrant. do a simple google search
7) it should say its in the download mode on the screen and a yellow box should appear in odin. if not search xda. on odin hit start. go do some push ups, or ask for a blow job from your wife and in the mean time let odin work. should take no more then 10 min.
8) after that is done the phone is going to reboot. the screen will change from VIBRANT SAMSUNG to VIBRANT i9000 or whatever. dnt worry its working.
9) its going to then goto an odd out of place looking screen and there are going to options that you will want to click. please do not.
10) at this point just pull the battery out and replace it and dont turn on phone......yet
11) enter odin again this time dont add a pit file and in PDA spot insert the included JFD file (.tar) called T959UVJFD
12) click start let that run and BAM it will load up perfectly.
13) you should flash again to JI6 by just following the simple rules explained at step 11. just instead of adding JFD add JI6. JI6 adds HD camcorder and better GPS.
FINISHED
END NOTES.
my phone was still unlocked as it was before this fiasco. idk how it stayed that way but it did AND the android market is now working but this morning i checked an its not !!! GREAT DAY
post things if you have any questions. ill try my best.
That's using Odin...you can learn this from the n00b guide ...
Sent from my SGH-T959 using XDA App
Some Help Please
Link for files is not working anymore. Can you upload this again please?
I have the same problem you listed, Galaxy S vibrant will go to black screen after finishing the boot and showing the pulsating S, only the soft touch butons will be on, the phone is dead and I have tried all things possible and losted all over the web to revive it, I can't get it to wor, it is a sad thing the phone is in great condition but something went wrong and i can't figure out how to bring it back to life
Maybe if you laid off the speed.............
I just realized this thread is from a year ago. I hate bumped old threads.
You were just sliced bread before you were burnt by the toaster.
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!
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.
Hello everyone.
Last week my phone got an OTA update from Sprint and went to android 4.4.2 . I have a stock Samsung Galaxy Note 2 never rooted or rommed it before. After the update the phone acted weird right away. It would freeze up or restart or icons disappeared. About an hour after it shut down then went into this loop of it starts goes to the Samsung Note 2 Model splash and that was it. I would have to pull the battery to turn it off. I tried restarts about 2 dozen times yanking battery holding start button then reinserting battery same thing every time. I also tried 4 different batteries to make sure it wasn't a battery issue.I made sure to pull my sd card to make sure that wasn't an issue. Finally I figured oh well Ill just do a full factory wipe and install. It took a bit but I was able to get into the recover panel.. Its weird when I went in there it went through a whole bunch of red talking about E:failed to mount/cache no such file ...or something to that. I went ahead choose wipe data/factory reset.....This said that failed.....I tried to wipe the cache which seemed to work then tried reset again...same thing failed.. I tried powering off and do this a few times but nothing. I then went on to see if maybe odin would work.. I have odin 3.10, have my samsung drives loaded,kies is not on my machine. I found the sprint tar fil for my note 2 believe its 4.3 . I put my phone in odin dl mode...I opened odin as admin....I selected AP (in new vesion its this old versions was pda)..I went ot my unzipped tar file loaded that in...phone is shown on com4..odin says md5 completed successful so I hit start.....It sits for awhile log says something to likes of communicating..Then after about 15 minutes I get the failed sign.......Can anyone help me fix this and tell me what happened. The phone was fine until that damn ota.....Below are a few images showing the different times I mentioned....I do notice when I put my phone in odin dl mode I have 2 lines I dodnt see if I look at others images of their phone in odin dl mode... One is something about Knox Warranty Void:0 and under that AP:SVREV:A3 .........OK I dont see how to put images in here .I click the add image and it wants a link so I cant getr them from my computer...If anyone knows how Ill add them
Flash 4.3 oder 4.4 Fule via odin. But you need the 3-part firmware and the PIT. Then it works perfectly.
battlekaier said:
Flash 4.3 oder 4.4 Fule via odin. But you need the 3-part firmware and the PIT. Then it works perfectly.
Click to expand...
Click to collapse
Can you explain more Im not real sure how to do what your saying? Where do I get the files your talking of? Thanks for responding....ps just for updates I can not longer get into recovery mode only odin DL mode
Bump..anyone?