I tried to fix my phone using this method.http://forum.xda-developers.com/showthread.php?t=1975560
Prior to that the phone was stuck on the samsung galaxy logo, it would go
back and forth to the android dude and logo. After trying the method above now the android dude falls and there is a red triangle and it repeats that process.
My phone has never been rooted. I now have a knox warranty void: 1 but I don't care about that atm. I guess i will have to fix that if I want to root it. I don't think that I was supposed to use the method above unless my phone was previously rooted.
Ok so I really need some help fixing my phone. I don't know what happened to it. I know that by trying to fix it using this method, it didn't help or maybe my phone is just that messed up.
please help. I have tried several times using oden and other stock firmwares for my phone and nothing is helping.
Related
I used z4root to root the phone. I entered the code to hard reset, and after that it will stay in a boot loop showing the samsung logo and then rebooting again. I tried flashing with odin and the latest firmwares, it stays the same. I need help ASAP, it's not even my phone, and i don;t want to end up paying money to fix it.
bump bump bump
scristi said:
I used z4root to root the phone. I entered the code to hard reset, and after that it will stay in a boot loop showing the samsung logo and then rebooting again. I tried flashing with odin and the latest firmwares, it stays the same. I need help ASAP, it's not even my phone, and i don;t want to end up paying money to fix it.
Click to expand...
Click to collapse
Try flashing the I5500XWJP9 firmware from sammobile.com
Ok so i have a samsug galaxy note att and i bricked it. the screen wont come on no boot image or vibration i tried new charged battery nothing. it wont go into recovery or download mode however when attempting to do so the LED camera light flashes sparatically.... Odd ive never read or heard of that happening. my question is is there a solution to fixing this or should i send the phone in to samsung to have it replaced for i still have insurance on it. Unfortunately i cannot recall what ROM i was flashing to it because i am a flashoholic. Any information or advice is appreciated.
Thanks in advance.
I have this same exact problem ... but my phone is not under warranty anymore.
Can I ask you what happened to yours?
I also wasn't flashing a right before it happened ... basically mine was working fine for a while and one morning when i went to turn it on... NOTHING
Hi,
Today i tried to root my Bell samsung galaxy note 3 version number SM-900w8 using this Odin. The problem i am having is that my phone is constantly rebooting and it says "Recovery Booting" and "Recovery is not seandroid inforcing". I haha no idea what to do at this point, can someone please help me. Odin says that my phone pass
KNOX and Lost your Warranty
There is no harm to your phone except that sadly you've triggered the KNOX flag and now your phone is deamed NOT UNDER WARRANTY.
Now that you are already there!!!
My advice is feel Adventurous and Try yourself some Custom Roms and Stick to the one you like best!
Trust me!
Once you go with AOKP you won't go back to TouchWiz
Regarding the Notice....It's few seconda and your device will boot back to normal.
Had it for some time now and it's become and normal thingy for me.
So recently, I update my SGH-I337 via OTA and i started having call issues where I would keep having to restart the phone in order to make the phone calls work again. I then decided to root my phone in order to get the calls to work again and they did. I then decided that since my phone was now rooted, I would completely get rid of KNOX using Root Explorer. Doing this soft bricked my phone after a reboot. After some research, I found this post http://forum.xda-developers.com/showthread.php?t=2663545 and i got my phone working again using steps 1-7. I then took it a step further and used Odin3 v1.85 and flashed the JFLTE_USA_ATT_16G.pit file with ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 file and that in term bricked my phone again. So I repeated steps 1-7 again but wound up with a bootloop at the AT&T logo and now have no clue what to do. I have been at this for 3 days now so any assistance would be wonderful. Thanks.
EDIT: Got it fixed....removed battery and rebooted into recovery and performed a factory reset. it stayed at the AT&T logo screen for a couple minutes before it booted up.
Glad you were able to fix it on your own. Great job!
Thread closed
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