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!
Related
I was having problems with my tablet freezing and making me hold the power button and reset multiple times a day so I wanted to flash it back to stock and just use it that way and see if the problem is still there. When I went to flash it back to stock I originally tried to flash it using CWM and put "hc-3.1_ota-full_sam_tab_10.1" from the thread "LOOK" Here First {List} Roms/Kernels/Mods/Themes/FAQ'S *Update 25/08/11* After flashing that It would no longer power on. I'd also done a few master resets before starting this whole process. I wasnt able to get that to flash successfully. Since I wasnt having any luck I flashed the [Solution] HC 3.1 OTA Stock ODIN link right below what I was flashing. Still having a problem booting up but also no longer have CWM on the tablet. Later I saw the download file was PDA_SIGNED_P7105.tar and my tablet is p7510 so I figured that could be why as well. I reflashed CWM onto the tablet but im pretty sure it was just the CWM files because its only 5mb. I went over to http://www.samfirmware.com/WEBPROTECT-p7510.htm but its only got the Arabic and Europe versions. I tried to mount my SD storage using CWM and it gives me a error so I cant put normal ROM's back onto the tablet.
SOOO long story short if anyone has any tips to get past this booting screen were it just says "Samsung Galaxy Tab 10.1" they would be much appricated! and I'm also looking for where I can download the stock or any ROM basically for the 7510 that I can flash using Odin because I cannot get it to mount my SD card.
UPDATE: after flashing tons of different files in odin and no success I thought I'd give it a try this morning and finally got it work by flashing the PDA_SIGNED_P7105 which I had done before not sure why it hadn't worked but at least its powering up into the setup. I guess I'll just have to see if the problem comes back. Thanks for the help cleblanc92 though!
Update: I followed the steps in [ROM][STOCK][ARABIC][AUG'13]W/ Official TOUCHWIZ Galaxy Tab 10.1 (WIFI) P7510JPKG5 but still no luck in getting past the boot screen. I did the PDA and CSC it all went through successfully but still didn't get past boot screen. I'm starting to feel like its just bricked or I'm missing something...
What's your full tab detail before I try to whack at this with you? Wifi or 3g? US GT-P7510 yes?
cleblanc92 said:
What's your full tab detail before I try to whack at this with you? Wifi or 3g? US GT-P7510 yes?
Click to expand...
Click to collapse
yeah, its the Wifi GT-P7510 US version.
Thanks for the help I'm kinda stumped here I even called samsung lol but obviously all they had me do was a factory reset and setup a call back when tier 2 tech is open but I dont see them being able to help either.
at the moment I don't have CWM and it should be all stock. I can put it on if need be though.
just for some more information. the more the better I would assume I had the starburst ROM on then put Bonsai on which included a kernal I dont think the kernal would cause problems. Not sure if it would even still be on there. I'm about to try and reflash bonsai back onto the tablet. If I can find a way to do it on Odin.
So you used the steps from this post:
http://forum.xda-developers.com/showthread.php?t=1119492
To apply this ODIN version: http://www.megaupload.com/?d=DDN6BYB2
with the notes steps:
Flash the below with ODIN (thanks to bonzai3558), extract the .md5 file from the zip, and in odin choose PDA and point to that file, keep everything else blank/default. Connect Tab with USB (after it is in download mode by power on +Volume down then volume up, so it shows the yellow android with shovel) then hit Start.
Did that error at all? If you did not apply all those steps with success please retry and comment?
cleblanc92 said:
So you used the steps from this post:
http://forum.xda-developers.com/showthread.php?t=1119492
To apply this ODIN version: http://www.megaupload.com/?d=DDN6BYB2
with the notes steps:
Flash the below with ODIN (thanks to bonzai3558), extract the .md5 file from the zip, and in odin choose PDA and point to that file, keep everything else blank/default. Connect Tab with USB (after it is in download mode by power on +Volume down then volume up, so it shows the yellow android with shovel) then hit Start.
Did that error at all? If you did not apply all those steps with success please retry and comment?
Click to expand...
Click to collapse
Alright I'll redownload the Odin version and the md5 and see if i get any errors. Should I post the log from Odin?
Shouldn't take too long to download already at like 80% should be done in a min.
Also right now. It gotten past the "samsung galaxy tab 10.1" screen but is still getting stuck at the like page with the stars and swirls.
*IF* the ODIN process above works then you can apply CWR via ODIN from here:
http://forum.xda-developers.com/showthread.php?t=1150732&highlight=odin+cw
This should get you back to a Stock with CWR support. I am on StarBurst with the latest Pershoot Kernel and I don;t thing either of those are a factor in your recovery success but you did not some other items that I have not touched at all.
Elumis said:
Alright I'll redownload the Odin version and the md5 and see if i get any errors. Should I post the log from Odin?
Shouldn't take too long to download already at like 80% should be done in a min.
Also right now. It gotten past the "samsung galaxy tab 10.1" screen but is still getting stuck at the like page with the stars and swirls.
Click to expand...
Click to collapse
Is it bootlooping? aka restarting the boot process images over and over
cleblanc92 said:
*IF* the ODIN process above works then you can apply CWR via ODIN from here:
http://forum.xda-developers.com/showthread.php?t=1150732&highlight=odin+cw
This should get you back to a Stock with CWR support. I am on StarBurst with the latest Pershoot Kernel and I don;t thing either of those are a factor in your recovery success but you did not some other items that I have not touched at all.
Click to expand...
Click to collapse
Yeah I got that file for CWR I just have a problem with getting a ROM onto the tablet to actually use it.
Here is the log for flashing the PDA_SIGNED_P7105.tar.md5
it says PASS! at the top so far after its restarted it still sitting at the samsung galaxy page. I'll let it sit for a little bit longer but something tells me its not going anywhere.
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_SIGNED_P7105.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> system.img
<ID:0/012> recovery.img
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/012> Removed!!
<ID:0/011> Added!!
Click to expand...
Click to collapse
cleblanc92 said:
Is it bootlooping? aka restarting the boot process images over and over
Click to expand...
Click to collapse
Yeah it was bootlooping but its back to just showing the samsung galaxy tab logo. I can probably get it back into the bootloop if that's better?
Elumis said:
Yeah I got that file for CWR I just have a problem with getting a ROM onto the tablet to actually use it.
Here is the log for flashing the PDA_SIGNED_P7105.tar.md5
it says PASS! at the top so far after its restarted it still sitting at the samsung galaxy page. I'll let it sit for a little bit longer but something tells me its not going anywhere.
Click to expand...
Click to collapse
If it sits for 5-10 mins and goes no further let's try booting into CWMR then
1) wipe cache partition
2) advanced / Wipe Dalvik Cache
3) wipe data/factory rest
4) reboot
...miracles happen.
[ I do HATE the SDCARD is not a real accessible card. Next tab will need that for me as it's an extra recovery tool we just don't have. ]
cleblanc92 said:
If it sits for 5-10 mins and goes no further let's try booting into CWMR then
1) wipe cache partition
2) advanced / Wipe Dalvik Cache
3) wipe data/factory rest
4) reboot
...miracles happen.
[ I do HATE the SDCARD is not a real accessible card. Next tab will need that for me as it's an extra recovery tool we just don't have. ]
Click to expand...
Click to collapse
something interesting I got the screen were it lets me choose download or recovery. I clicked on download on accident the first time and it opened. Restarted to get into recovery and it just shows a black screen. The backlight is still on so the tablet is still on. I'll try just flashing CWR onto it again yeah agree with the SD card only thing I dont like about the tablet
cleblanc92 said:
If it sits for 5-10 mins and goes no further let's try booting into CWMR then
1) wipe cache partition
2) advanced / Wipe Dalvik Cache
3) wipe data/factory rest
4) reboot
...miracles happen.
[ I do HATE the SDCARD is not a real accessible card. Next tab will need that for me as it's an extra recovery tool we just don't have. ]
Click to expand...
Click to collapse
I put CWR on and was able to get into it. I factory reset, wiped cache partition, then went into advanced and clicked on wipe dalvik, before I had hit yes it said "E:unknown volume for path [/sd-ext]" but it still let me click yes and said "Dalvik Cache wiped.
EDIT: still not booting up past the samsung galaxy tab screen.
Okay...well I am not sure about the SD warning you noted or if it matters. I would expect some of the masters around here might be able to look at the post details thus far and offer some ideas. Hang in there, I will try to poke around for some ideas based on that error msg but it won't be until tomorrow....pending the hurricane (which is already slowing) doesn't tear up the power lines. Sorry we could not get there already.
cleblanc92 said:
Okay...well I am not sure about the SD warning you noted or if it matters. I would expect some of the masters around here might be able to look at the post details thus far and offer some ideas. Hang in there, I will try to poke around for some ideas based on that error msg but it won't be until tomorrow....pending the hurricane (which is already slowing) doesn't tear up the power lines. Sorry we could not get there already.
Click to expand...
Click to collapse
That's alright, thanks for all the help though! much appreciated. Hope the hurricane doesn't hit you're area too hard. I'll give you some "Thanks" and shoot you a donation
maybe Samsung tech support will know something as well lol. supposed to call me back sometime tomorrow morning. They will probably just make me mail it in for a few weeks...
Thanks very much. I think the SD warning is just generic since we do not have a card mounted in the expected location....but again someone will correct me if I am wrong on that.
I'll see what I can come up with Sat if no one finds the solution.
hey cleblanc92, I feel your misery, i finally found a solution! and the culpit to(atleast for me)
The Culprit is Busybox, at first I thought its the OC kernel that i installed then upon google surfing i found similar problems and yup its the #$Q!#$ application!! CONFIRMED
STAY AWAY FROM OPENVN RELATED STUFF
so here's the solution, after spending so much time my Galaxy tab is now reviewd.
First Download this for your PC
SAMSUNG DRIVER:
http://downloadandroidfiles.com/files/get/IwAZDRwKZz/gt-p7510-usb-driver-v1-3-2360-0-escape.exe
ODIN
http://downloadandroidrom.com/file/GalaxyTab10.1/rooting/tabrooteasy.zip
Then go to this site
http://www.samfirmware.com/fwandroid.htm
and search for your Tablet's Model
after that you will have several firmware to choose from depending on where your tablet is manufactured
look at the back of your tablet, find the "MADE IN: xxxxxxx" This will give you a hint (mine is KOREA so I download the asian Firmware)
After downloading all of that
Install the driver
Unzip tabrooteasy.zip
On your tablet, Push the Power Botton once until the Samsung galaxy Tab 10.1 logo appear, then imediately press the volume down button.
2 choices will appear, choose the one with the DOWNLOAD stuff in it
after that odin will start on your tablet, DO NOT PLUG THE CABLE YET!
Open the ODIN.exe on your PC and Then Connect the Cable
Click on PDA then navigate to the tabrooteasy folder and choose
recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5
do not change the settings then click start.
after that Reboot your tablet and do the ODIN process again, Click PDA again then navigate to the Firmware folder you downloaded a while ago,
there will be 3 files, choose the largest file and click start again, it will now install a new Fresh Official Firmware...
WAIT!!
We're Not done yet!
upon competion you tablet will reboot, it will bootloop once again dont worry I got it fixed
restart your tablet then go hold the volume down button agin but his time choose the other one we didnt choose a while ago, after that format your data, format your cache then hit reboot!
ang WHHHAAALLLA! Your Tablet is ALIVE again!!!
I effortly do this coz i know the feeling of being pissed desperately finding a solution. so I hope this help anyone who faced the same problem!!
Ciao! Im gonna sleep its 4:55 Am!
As the title states, I had to factory reset my S2. It was because I was giving it to my step dad after getting a new phone, I decided to wipe it for him, not considering I had rooted it already.
My current dillema would be that the phone gets stuck on an unpassable "Samsung Galaxy S II" splash screen when the phone turns on.
Does anyone have any suggestions, fixes, or general help?
I much appreciate it.
Doing a full wipe shouldn't cause it to get stuck at the logo. Try and supply a little more detailed info. Also boot into recovery and reflash what ever ROM
Well, it started happening when factory reset it.
I had flashed it, and put the rom on it or what ever, and then every the reset it does that.
At first, with a different battery, I had it on an infinite battery charging loop where It would power on the LED, say the battery is charging, and it would only become warm and not hold a charge.
I thought it was the battery, so I replaced it and now it gets stuck on a infinite logo boot splash. I have to keep trying to turn it on and off to get the splash to show more often.
What ROM? What kernel? And to be clear this is a sgh-i777 gs2?
MIrokux1337x said:
Well, it started happening when factory reset it.
I had flashed it, and put the rom on it or what ever, and then every the reset it does that.
At first, with a different battery, I had it on an infinite battery charging loop where It would power on the LED, say the battery is charging, and it would only become warm and not hold a charge.
I thought it was the battery, so I replaced it and now it gets stuck on a infinite logo boot splash. I have to keep trying to turn it on and off to get the splash to show more often.
Click to expand...
Click to collapse
See if you can enter download mode. If so, use the back to stock guide that's stickied.
Sent from my SGH-i777 using xda app-developers app
Shawn said:
See if you can enter download mode. If so, use the back to stock guide that's stickied.
Sent from my SGH-i777 using xda app-developers app
Click to expand...
Click to collapse
I cannot enter download mode. Holding Volume down and the power button only shows the splash again, and then it stays on a black screen.
In regaurds to the Kernal and Rom, I do not remember.It was the most popular ones I think, for what that's worth lol
OK....not to sound terse....but you haven't provided any info. ie...phone make and model, ROM and kernel There are several popular ROMs, it depends on your personal preference. A little safe advice is to search, read read and reread ....the stickies are a great source of information.
This forum is for the galaxy s 2 i777 with AT&T . Take out your battery and make sure it says you have an i777 under the battery. If you don't you're in the wrong forum.
MIrokux1337x said:
I cannot enter download mode. Holding Volume down and the power button only shows the splash again, and then it stays on a black screen.
In regaurds to the Kernal and Rom, I do not remember.It was the most popular ones I think, for what that's worth lol
Click to expand...
Click to collapse
Phalanx7621 said:
This forum is for the galaxy s 2 i777 with AT&T . Take out your battery and make sure it says you have an i777 under the battery. If you don't you're in the wrong forum.
Click to expand...
Click to collapse
Yeah, that is not the button combo for this device.
Sent from my Nexus 7 using Tapatalk HD
Odin back to stock.
Sent from my SGH-I727 using xda app-developers app
Phalanx7621 said:
This forum is for the galaxy s 2 i777 with AT&T . Take out your battery and make sure it says you have an i777 under the battery. If you don't you're in the wrong forum.
Click to expand...
Click to collapse
Cmon now, Im not that ignorant. I do have the right forum for the right phone.
I got it to go to download mode by holding the volume keys and the power key.
I want to get it back to stock.
I used Cyanogen or something.
I used CWM and Odin I think
Its been so long!
MIrokux1337x said:
Cmon now, Im not that ignorant. I do have the right forum for the right phone.
Click to expand...
Click to collapse
you have no idea how many times we get skyrocket i727 and i9100 users here....
MIrokux1337x said:
Cmon now, Im not that ignorant. I do have the right forum for the right phone.
I got it to go to download mode by holding the volume keys and the power key.
I want to get it back to stock.
I used Cyanogen or something.
I used CWM and Odin I think
Its been so long!
Click to expand...
Click to collapse
Read the stickies....all the info is there, I checked for you....enjoy.....and pirateghost is right.
lilbigdude1 said:
Read the stickies....all the info is there, I checked for you....enjoy.....and pirateghost is right.
Click to expand...
Click to collapse
So, I followed the Back to Stock guide in the stickies.
This is my issue
"<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
"
In ODIN
MIrokux1337x said:
So, I followed the Back to Stock guide in the stickies. This is my issue...
(succeed 0 / failed 1)
Click to expand...
Click to collapse
This is somewhat difficult to address, mostly because you don't remember what custom firmware you had put on it, and because you did not give a detailed description of what caused the problem (at least not detailed enough anyway.)
The stock package that you flashed from the back to stock guide is missing bootloaders. The first thing to try is: Go to the Download Repository (link in my sig) and get the full stock distribution and flash that. See if that works.
creepyncrawly said:
This is somewhat difficult to address, mostly because you don't remember what custom firmware you had put on it, and because you did not give a detailed description of what caused the problem (at least not detailed enough anyway.)
The stock package that you flashed from the back to stock guide is missing bootloaders. The first thing to try is: Go to the Download Repository (link in my sig) and get the full stock distribution and flash that. See if that works.
Click to expand...
Click to collapse
Which of those should I be downloading?
MIrokux1337x said:
Which of those should I be downloading?
Click to expand...
Click to collapse
I'd suggest you try flashing the I777UCKH7-CL503881 Stock Binaries. This is the original 2.3.4 Gingerbread that came with the phone when it first came out. See if that flash will go all the way through and boot.
Possible same type of issue and need to cohijack this thread.
OK so let me start off with, great site. I have read a ton of information but this is the only thread in my searches that I feel (and I could be wrong) is about 100% on with my issue.
First: Siyah 4.3.3 (Latest) Kernel
ROM; SHOstock3 v2.5.9
Issues:
Today I decided to encrypt my device while also doing a sim pin lock. Of course I shouldn't have messed with it but we had just finished discussing encryption, cryptography, and securing mobile devices in my Cryptography and Hashing Algorithm MSIT class. Well so I did that today and it went fine. When I did the pin for my sim lock it was a 4 pin number. Well later on I went to unlock it and it wouldn't take it in the PUK saying I needed an 8 number pin. Well I didn't create an 8 number pin just a 4 number one. After trying multiple combinations I sim locked my phone and had to go to AT&T to get a new one (thank goodness my phone actually went back to the stock 4.0.3 update I had on there originally) Well I tried to revert back to SHOstock3 v2.5.9 and it kept asking for my encryption password. I put the right password in and it wouldn't take it. So I tried another password and it looked like it accepted it, went the cool yin/yang purple fish symbol then rebooted again and now it is stuck at the Samsung Galaxy S2 white letter splash screen. It doesn't go black at all and just stays on there. I have taken out the sim card, battery, and microSD card and tried several methods (3 button combo, 2 button combo, 1 button with USB plugged into computer, OneClick Unbrick Software ((doesn't work for some reason in Win 7x64 and Win 8x64 it doesn't do the drivers even though I have them installed and I Cannot get to recovery or download mode))) and no luck. I cannot get to download mode that I know of unless that actually is where I can select (with a warning) to download a custom OS or push the down arrow to reboot. Well I am stuck in that or the splash screen and I cannot get out of it or fix anything. It seems the password wasn't correct, the encryption deleted all the files (or whatever it said), and I am now in limbo.
I do know that when I get to (what I assume) may actually be download mode??? that it says ODIN (I am using MobilOdin Lite) and it says Samsung OS on it (I believe that is what it said).
Any help is greatly appreciated it. While in that mode my computer doesn't see the phone, using the OneClick I cannot load any drivers for the phone using the Zardig or whatever it is, or anything like that. I may be totally missing something easy on the boards to fix this issue but it has been driving me nuts! Any help is appreciated.
Apologies to the OP and if I am in the wrong or out of place or line I apologize and please let me know. Feel free to email me if need be.
Thanks.
Eagle.
creepyncrawly said:
I'd suggest you try flashing the I777UCKH7-CL503881 Stock Binaries. This is the original 2.3.4 Gingerbread that came with the phone when it first came out. See if that flash will go all the way through and boot.
Click to expand...
Click to collapse
Now it is giving me this:
"<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> sbl.bin
<ID:0/003> param.lfs
<ID:0/003> cache.img
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
"
All I remember about what I did was I think it was CyangenMod, it was ICS, because everytime I booted the phone, the start logo was a purple ellipse with ICS text in it, it used apolo music and had TouchWiz, I dont think I did custom binaries, my download mode says Samsung Official, And the phone worked fine until I factory reset the phone. That is litterally what happen.
MIrokux1337x said:
Now it is giving me this: ...(succeed 0 / failed 1)
All I remember about what I did was I think it was CyangenMod, it was ICS, because everytime I booted the phone, the start logo was a purple ellipse with ICS text in it, it used apolo music and had TouchWiz, I dont think I did custom binaries, my download mode says Samsung Official, And the phone worked fine until I factory reset the phone. That is litterally what happen.
Click to expand...
Click to collapse
I've never used CyanogenMod, except to try it out for a few days when ICS first appeared, so I'm not very familiar with the problems that it can cause. I have seen numerous instances of people reporting some variety of soft brick problem after using CM over the past year+. I don't usually read the threads about problems with CM either. Therefore, this may be more difficult to trouble shoot. Maybe someone with more experience with CM can jump in and help.
First, you need to determine whether the problem is in the phone or in some other part of the system. So try to eliminate other possible sources of the problem, such as: use a different usb cable, different port on your computer, a different computer, etc. Any of these external things that could cause a flash to fail.
If you're sure that the problem is in the phone, then you should probably try flashing just individual parts of the firmware, such as just the kernel, etc.
---------- Post added at 09:38 AM ---------- Previous post was at 09:33 AM ----------
WarEagleUS said:
OK so let me start off with, great site. I have read a ton of information but this is the only thread in my searches that I feel (and I could be wrong) is about 100% on with my issue.
First: Siyah 4.3.3 (Latest) Kernel
ROM; SHOstock3 v2.5.9
Issues:
Today I decided to encrypt my device while also doing a sim pin lock. Of course I shouldn't have messed with it but we had just finished discussing encryption, cryptography, and securing mobile devices in my Cryptography and Hashing Algorithm MSIT class. Well so I did that today and it went fine. When I did the pin for my sim lock it was a 4 pin number. Well later on I went to unlock it and it wouldn't take it in the PUK saying I needed an 8 number pin. Well I didn't create an 8 number pin just a 4 number one. After trying multiple combinations I sim locked my phone and had to go to AT&T to get a new one (thank goodness my phone actually went back to the stock 4.0.3 update I had on there originally) Well I tried to revert back to SHOstock3 v2.5.9 and it kept asking for my encryption password. I put the right password in and it wouldn't take it. So I tried another password and it looked like it accepted it, went the cool yin/yang purple fish symbol then rebooted again and now it is stuck at the Samsung Galaxy S2 white letter splash screen. It doesn't go black at all and just stays on there. I have taken out the sim card, battery, and microSD card and tried several methods (3 button combo, 2 button combo, 1 button with USB plugged into computer, OneClick Unbrick Software ((doesn't work for some reason in Win 7x64 and Win 8x64 it doesn't do the drivers even though I have them installed and I Cannot get to recovery or download mode))) and no luck. I cannot get to download mode that I know of unless that actually is where I can select (with a warning) to download a custom OS or push the down arrow to reboot. Well I am stuck in that or the splash screen and I cannot get out of it or fix anything. It seems the password wasn't correct, the encryption deleted all the files (or whatever it said), and I am now in limbo.
I do know that when I get to (what I assume) may actually be download mode??? that it says ODIN (I am using MobilOdin Lite) and it says Samsung OS on it (I believe that is what it said).
Any help is greatly appreciated it. While in that mode my computer doesn't see the phone, using the OneClick I cannot load any drivers for the phone using the Zardig or whatever it is, or anything like that. I may be totally missing something easy on the boards to fix this issue but it has been driving me nuts! Any help is appreciated.
Apologies to the OP and if I am in the wrong or out of place or line I apologize and please let me know. Feel free to email me if need be.
Thanks.
Eagle.
Click to expand...
Click to collapse
The first thing to try is to perform a wipe data/factory reset from recovery. Since you are encrypted, you may get a password dialog. If so, enter the wrong number continuously until you have gone through the dialog, I think it is 5 times, and then it should let the phone reset. See if that clears things up for you.
Btw, your problem is not similar to the op.
How I got here:
Phone started bootlooping in my pocket/randomly locking (after occasionally a few apps crashed) within a few mins of startup.
No physical damage I'm aware of to my phone.
Tried to re-flash with Odin, which failed, and left me stuck on the "See if Kies can sort it out" message. Windows recognizes the phone on USB, but Kies never seemed to be able to connect. Download and recovery mode couldn't be loaded.
Went back to Samsung who returned both a quote for £135 repair and phone on same day - putting it down to user damage ("Octa LCD and USB Connector are damaged"). They're not. Screen works fine, USB charges and gets phone reconized by PC.
Phoned them to complain (i.e. they look fine) and eventually a month later managed to get them to take it back.
Was a very surreal conversation "We can't take it back, you broke the screen" - "No I didn't, it's on, it's next to me and doesn't have a scratch on it". "Yes sir, but my system says the screen is broken, so we can't take it back" etc etc
Came back today with "It's been tested, it's water damage and repair would exceed the cost of the handset" I'll just leave my feelings on this for now.
When the phone came back, I did suddenly realize that recovery mode now worked. Unfortunately the file system seems to be stuffed - load of errors along the lines of "E:Can't open /cache/recovery/log".
Tried to sideload via adb and got similar message that although the tranfer went fine, it couldn't be written to cache.
Likewise trying to nuke cache/return to factory settings just scroll up similar.
THEN download mode started working as well (hurrah). Tried to flash via Odin to see what would happen and got:
<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.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
Now assuming the file system is stuffed, then that would explain this - so was wondering if I could use a PIT to just repartition the memory and work up from there - but after a bit of googling, it appears if that was required, it would be telling me it couldn't find the PIT in Odin.
Behaviour seems to have changed yet again now. Regular start takes me to the 'Download' screen (as does trying to start recovery). Download mode works fine, but I'm moving way out of my comfort zone.
Questions are:
1) Has anybody got a clue wtf might be happening? Hardware/Software? (whilst it was running for 2 minute chunks at the top, it did flag my controller as being a dodgy eMMC, but (maybe unfortunately) just assumed it was a glitch in the app meant for S2s.
2) Any advice on what to try next? Just wasted a large part of the day swearing at this and I'm still at an utter loss
3) Anybody had issues like this before with Samsung (UK). First repairer (your screen's broken) was ANovo. Second (it's a write-off) was mentioned to me on the phone, but they seem to have returned it without mentioning it and have signed off as 'Samsung' on unheaded paper with no contact details.
My next step is to crack the damn thing open to see if there is any visible water damage inside. Can't see any water indicators inside the ports - and there's a little empty square under the battery where there should be one. There should be one, I checked on another phone, just I never seemed to get one. Now just wondering if they spotted this and assumed I'd removed it (and hence blaming water damage)...
..anyway. Not sure if anybody can be bothered reading down this far - but it's been cathartic for me (and it's an HTC next time).
I think your nand is dead
my advice would be, since u got nothing to loose
download latest odin, search for the pit file that suits your device and thick re-partion and clear nand, and see how it goes, also would be advisable to do a 3 file flash along side with all those options i said!
take care
SnowPluralism said:
I think your nand is dead
Click to expand...
Click to collapse
Curiously I'm indifferent to whether the phone is dead or not - just want to know
I'll have a crack at the full flash as you suggested, and if that fails take a peek inside the case to see whether it is really damaged or not.
thanks for the advice/support *weak smile*
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.
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!