Hey, so I just bought a S6 to use Samsung Pay.
Received it today, fist thing I had to do was update it from 5.0.2. So I used the OTA update from t-mobile option (as it offered it as soon as I turned the phone on and connected to Wifi).
I click the "Restart and apply update" when it had finished downloading, set the phone down, browse the internet for a little and notice it was hanging on the Samsung logo.
I try to turn it off and on, nothing works. I try entering recovery mode, won't let me.
So I then download and try manually flashing 5.1.1 through ODIN.
Everything says "PASS" in ODIN, it reboots and gets to the Samsung logo, shows the android robot, says "installing updates" but when the bar reaches about 45% it switches to "erasing" then goes back to getting stuck on the Samsung Logo.
What can I do ? I really don't want to trip knox as Pay is the sole reason I bought this stupid phone, all other Stock ROMS now fail odin and G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME.tar is just doing the Install then erase thing.
ANY AND ALL SUGGESTIONS WELCOME !
You could try this
http://forum.xda-developers.com/showpost.php?p=63289213&postcount=42
Appreciate the link, tried again and again, but still, every time: the phone reboots, then starts with the "installing updates", it blocks at 33% and just switches to saying "erasing" and the progress bar empties ... until it reboots and hangs at the logo.
I'll try and get a video of it, it that helps at all.
alexnader said:
I'll try and get a video of it, it that helps at all.
Click to expand...
Click to collapse
If with smartswitch won't succeed don t even try anything else send back to Samsung they will repair or give you another one because if you modify the Knox the guarantee is avoid they really strict they don't even touch the phone to try to repair
Related
ok people...in need of help.
back story, my phone has been force closing and freezing frequently, but this is not unusual with this model phone....infuse 4g AT&T....i would have to restart my phone at least 4 or 5 times a day. that's not why i'm posting though... last night around 4am i used my phone for the last time before i went to sleep. it had 100% charge. today when i woke up it was on the samsung logo. i tried to restart for like half an hour trying various methods, hard boot, taking out battery, etc. nothing. still on samsung logo. then i tried to enter recovery and wipe/format.... kept getting an error...all options chosen kept giving me a fail to execute message. last resort, i tried to restore to stock using odin. i did this twice, first time with the re-partition checked (it got stuck), second time without it checked (worked, installed stock rom but still stuck on samsung logo) third time with re-partition checked and it got through the installation just fine, all passes all green lights. phone still boot loops but now not at samsung logo, at "rethink possible" screen. i try to go to ui menu before booting and i cant, it just takes me to recovery where none of the options work. i'll upload the screen that i get when i try to install or select any option. any help appreciated!
M
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
I just bought the S6 The day before yesterday. It was working fine until I received the official Firmware update from Samsung by going Settings> About device> Software updates. Downloaded the update then the phone needs to restart to complete the update. It doesn't complete it. It just gets stuck at whatever percentage it desires and then reboots and goes into the updating screen again. I tried going into recovery mode and it just doesn't work. as I can't turn the phone off. I tried making it discharge completely then recharge it and then boot it into recovery mode but it still doesn't work. The only thing that works is ODIN mode. So what should/Can I do about that?
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance
My Karbonn Sparkle V appears to have bricked itself, I don't know why, I don't know how to fix it, and I don't have the money or time to replace it. I turned it off when I was going to a job interview, prior to which it was working fine. Afterwards I tried to turn it back on, and for the last 12 hours I've been fighting to get it working again with no success.
I can get into recovery mode, but nothing more. If allowed to try a normal boot, then it will either stay on the "Karbonn Smart" logo screen forever and ever amen, or it will APPEAR to boot, but once it reaches the lock screen it dies on its arse. The best-case is that the lock screen will stay up for about 3 seconds, then the screen will go black for another 3 seconds, and then we go back to the lock screen and the process repeats. OR, the lock screen comes up, 3 seconds, and then we go back to the bouncing dots loading screen forever and ever amen.
I tried a hard wipe from recovery mode - it's made absolutely no difference.
This is a stock phone which has only ever received the OTA updates; I've never rooted it, I don't have a custom recovery installed, and I've never used ADB before today.
I've downloaded a number of "stock ROMs" for this phone, but none of them actually work for me; it doesn't seem to matter whether I try to install them through Recovery mode\Apply update from ADB, or put them on the SD card and try "Apply update from SD card". For most of them, I get the error "failed to verify whole-file signature" and it won't install; I tried to install the stock file from https://forum.xda-developers.com/crossdevice-dev/android-one-general/ota-links-t3287707 but that doesn't get me much further; The error becomes
"Package expects build thumbprint of 6.0.1/MMB290/2459718:user/release-keys or 6.0.1/MMB29K/2419427:user/release-keys; the device has 6.0.1/MOB31E/3142026:user/release-keys"
Click to expand...
Click to collapse
I have pretty much no idea what I'm doing here; Please help.