hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though
Related
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Fearborn said:
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Click to expand...
Click to collapse
So is it stuck on the AT&T Logo? Or Samsung Logo?
UnknownTroll1 said:
So is it stuck on the AT&T Logo? Or Samsung Logo?
Click to expand...
Click to collapse
It was the AT&T logo, it's currently the Odin. If I flash it again with the stock ROM, it'll be the AT&T logo again, but it doesn't completely load the AT&T logo. The Samsung one loads and then the AT&T starts to load, but doesn't finish playing.
Anyone?
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jblparisi said:
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If this works (I'll try it when I get home) I will be so grateful! BTW, do you happen to have a decent link to a stock ROM? If not, I'll Google it tonight.
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?
Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app
Experienced Galaxy rooter here. I used Odin Mode on the Sg3 as well as my gf Pro tab 8.4 and my 10.1 as well. Ive never had problems until now. So here's what happened today:
This morning
I decided to install Twrp using Flashify. Having been rooted for months, it worked. I then installed Cm 11 using TWRP. I wiped cache and installed gapps from goo manager. Everything went smooth. I played around with it for about an hour. No problem.
Then I installed Team freezes ROM. I used flashify. Everything seemed normal, then I realized I couldn't get past Samsung title screen. So i plugged up to Odin and installed stock Recovery. Nothing. Reinstalled TWRP... can't get into Twrp. Used Odin again to install Phillz.. Nothing.
Once again I installed original stock through Odin. Here I am again stock at the Samsung boot screen. I can only do three things 1. Turn off 2. Reset 3.odin mode
What do i do?
I just want to get this thing to boot so i can see what happened or at lest into some sort of recovery where i can load from sd
If you're in Download (Odin) Mode....
Make sure you have S/N on hand.
Enter Download Mode and run KIES3, choose Firmware Upgrade and Initialization
Enter model number and S/N
Returning to bone stock may take an hour, so make sure the battery is fully charged. Moreover, YOUR TAB WILL BE TOTALLY WIPED AND GO BACK TO BONE STOCK!
mingkee said:
If you're in Download (Odin) Mode....
Make sure you have S/N on hand.
Enter Download Mode and run KIES3, choose Firmware Upgrade and Initialization
Enter model number and S/N
Returning to bone stock may take an hour, so make sure the battery is fully charged. Moreover, YOUR TAB WILL BE TOTALLY WIPED AND GO BACK TO BONE STOCK!
Click to expand...
Click to collapse
Thanks for this. I lost my system due to System Cleaner 2 fudgin' it up on reboot. I was about to hassle Best Buy into an exchange but gave this a try. I thought I had it made by doing a factory reset but even that didn't work. Luckily Kies came to the rescue after I figured out they wanted a generic model SM-T320, not the rest of it. Again thanks to you mate!
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/