Related
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked
Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.
Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
I'm having the same problem were you able to fix it?
jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.
I too require the passwords to be able to extract these files if someone would be so kind.
Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.
tried the suggested file still get the error that the OP got in the first screen
oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.
I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!
can anyone help?
I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..
Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA
I have done hours of researching and this isn't my first time i bricked a phone so I kind off have some experince fixing the phone but this seems harder than before.
I first tired to flash a kernel through odin on my captivate because i wanted to try out cyanogen mod but somehow the kernel had failed on me. When i tried to restart my phone, I got the phone---!---pc logo.
So i did some research on how to get the phone out of the soft brick. First thing I did was trying to get into recovery mode with the 3 buttons, but didnt work out. After that I tried to get into download mode and it worked. My first thought was too use odin and reflash, and that is what i did. Now the problem is, I had put the correct pit file and stock rom, because I had reflashed using these two same files before, but the thing is, it gets stuck on "set partition". So I did everything from, trying on different computers to changing usb cables to using different versions of odin and finally to taking out the sim card and sd card and taking out and placing the phones battery back in. And i had everything checked too so that wasn't the problem. The following were checked: Auto Reboot, Check Re-Partition and F.Reset Time.
If anyone knows the solution can you please help me out, thank you in advance!
When you check repartition, you need to load a pit file in the pit slot/tab for Odin. You have two options.
1) Flash froyo stock(kb2), if you don't want/need Gingerbread Bootloaders. The Heimdall package from Adam Outler is an easy 1 click solution.
2) Flash KF1 if you need GB bootloaders. This will also fix ant previous 3 button combo problem you may have. Use the package with a pit file and bootloaders.
It also sounds like you may need ajig to get into download mode, but if you follow the Captivate sig link below, you should be able to find everything you need to get going.
Thank you !
Thanks a lot mrhaley30705 ! I have gone through of some guides and done more research about these two, and I was thinking of flashing kb2 on to my phone but I'm really worried if it might brick my phone, because the captivate I have is the rogers one not the ATT&T one.
I just had a few questions like, before I do the Heimdall One-Click, is it required to install the Zadig file ? because it had came up before I opened up the Heimdall One Click program. I think i had used the Heimdall One-Click before (the video that is posted on youtube) by outleradam, but the thing was, it wasn't recognizing my phone. So I'm guessing it has something to do with Zadig file, because I made sure I ran it as Administrator also so I'm kinda lost.
My other question was, the consequences, if this program would not work for me, would it hard brick my phone? I really want to make sure I go ahead with it.
And my last question is, if I were to go ahead with this, it said on the forum I would have to reset my APN settings, so would that be applying another software to the phone or can i configure that manual ?
And Thanks again for all your help !
If you want the Canadian firmware, search for TRusselo's stock threads. He has a full set of Canadian firmware.
Anytime you flash bootloaders there is a chance of hard bricking your phone, either from an interruption in communication between your phone and computer (think power outage or bad cable) or accidentally mismatching bootloaders (think the old 3 button fix on top of GB bootloaders). Just follow all of the precautions you can when flashing bootloaders.
APN editing is done manually.
Oh alright I got how put the APN information, thank you.
And oh okay, that makes more senses.
And for the Canadian firmwares, that's what I pretty much did with Odin, I took his stock firmware and tried to flash it with Odin but wasn't passing the "set partition" part like I mentioned before. I followed his instructions too. So, that's why I'm a bit confused now, because I'm guessing if Odin doesn't work then I would have to use the Kb2 link that is posted on your Sig. Do you have any suggestions maybe ?
The canadian version of the captivate will flash the US verson, it just changes your boot screen and kernel splash to an att one. I would flash the KB2, then if you absolutley had to have the canadian version, flash it.
Thank you !
Thanks a lot once again ! and I will give it a try and let you know how it goes !
Maybe try NOT checking re-partition. This sometimes can cause a problem, in fact most tutorials i have seen always say DO NOT check re-partition. It's worth a try
Hey guys,
In a bit of a pickle at the moment. I grabbed an S1 off a friend to try and teach myself about rooting and flashing custom ROMs and such using Odin. With the final intent getting it to run ICS. Not a very hard challenge, but evidently it is for me.
I'll explain what I did, and if you can help without investing too much of your time I would be very grateful.
When I got it, it was running 2.3.3, all the tutorials I read told me to update it to 2.3.6 before doing anything more. I managed to root the phone easy enough, no issues there. But when I tried to put 2.3.6 on via Mobile Odin, (which I used to flash my S2 to ICS, long story) it had seemed to freeze on 'flashing flash kernel' for a good 15 or so minutes.
Being the daft monkey that I am, I exited the program...by removing the battery (don't judge me please). When I went to turn it on, it wouldn't load past the "Samsung Galaxy S" screen.
It goes into Download mode fine, and I've tried to flash an abundance of different Gingerbread ROMs onto the phone and Odin has just been getting stuck on the "setup connection" every time I've tried to flash.
I have tried using different USB ports which is readily suggested by most people and seems to work, using my laptop instead, different cords as well. No luck. Nothing happens when I press volume UP + home + lock like it used to, so I can't even factory reset or anything =\
I did find somewhere that suggested adding a PIT file to Odin and selecting repartition but every one yells at each other when 'repartition' gets mentioned, lol.
I hope this is in the right place, please bare with me if I used any wrong terminologies, I am relatively new to this.
Has anyone got some suggestions that may help me with my problem? =\
Thank you!
Taylor
sigh...here's my recovery kit, unzip, read .txt file, proceed
http://db.tt/MOGZx01S
Credits to nitr8 and chainfire
Thanks, sorry for being such a hassle...
Twinning92 said:
Thanks, sorry for being such a hassle...
Click to expand...
Click to collapse
No problems, was teasing ya! You will end up with root and custom recovery, if you then go to slim website and read and follow installation instructions you will then have lush ics
So anyone figure out why some ROMs fail to flash on to some devices?
I have a theory, I think it has something to do with "fastboot flash partition gpt_main0.bin" failing to flash on certain devices depending on which rom it's sourced from, also depending on which the device currently has already flashed successfully..
Although this is beyond my comprehension, I don't know the reasoning and or the correct wording. Perhaps someone with more knowledge could shed some insight..
I.E. I can successfully "fastboot flash partition gpt_main0.bin" on my device using MX retail, Bell and AT&T versions/copies will fail to flash on my device and I think it is because the last complete successful flash I was able to do with RSDlite was MX retail.
Anyone got any ideas?
The Atrix HD can be a pain
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
TheJeremyWhite said:
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
Click to expand...
Click to collapse
Fails to downgrade.
clockcycle said:
Fails to downgrade.
Click to expand...
Click to collapse
Haha, you're absolutely right. Thanks for pointing that out.
Sent from my MB886 using XDA Premium 4 mobile app
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
[OP] Photo of Camera Issue
Here is a photo of what I mean by the Camera color dilation. Demonstrated by a couple of Multi-Color Expo markers.
Download the G900A_Downgrade_to_NCE.tar from here:
https://www.androidfilehost.com/?fid=23622183712464416
Use Odin 3.09 and flash in AP slot. Once it is done then take the OTA for NG3 then OA1
Thanks to @muniz_ri
Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.
ElectricBiskitz said:
Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.
Click to expand...
Click to collapse
Did you use the same file from the link I provided?
Sent from my SAMSUNG-SM-G900A
I have used the same link you provided.
ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
*UPDATE*
Fingerprint scanner does not work anymore either. Camera fixes itself if you change a setting and put it back.
[OP] It's Fixed!
ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.
ElectricBiskitz said:
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.
Click to expand...
Click to collapse
I have the same issue exactly it says my bootloader is fused or something I have to flash the newest kernel to get it too boot up . I think I tried this already but can't hurt to try again .