Ok so I think I bricked it really good.
First off some back ground.
Rooted Note II running Synergry Rom...Freaking love it.
Knox was removed/disabled via Kango
Been running like a champ since november
But....
the home button works occasionally/worn out
So I decided to return it to sprint.
So I ran triangle away cuz I had a count of 5
and used odin to return to stock.
but I used the stock 4.3 img
Now the problem it only loaded half way and will not get passed the samsung logo
it did reload knox and will not let me get passed it. all roms/imgs fail. I can get into twrp
How can i disable knox when I can't get into the rom or load the stock....
rccwill said:
Ok so I think I bricked it really good.
First off some back ground.
Rooted Note II running Synergry Rom...Freaking love it.
Knox was removed/disabled via Kango
Been running like a champ since november
But....
the home button works occasionally/worn out
So I decided to return it to sprint.
So I ran triangle away cuz I had a count of 5
and used odin to return to stock.
but I used the stock 4.3 img
Now the problem it only loaded half way and will not get passed the samsung logo
it did reload knox and will not let me get passed it. all roms/imgs fail. I can get into twrp
How can i disable knox when I can't get into the rom or load the stock....
Click to expand...
Click to collapse
ok I got it fixed. I was able to download the stock rom with the counter reset from http://forum.xda-developers.com/showthread.php?t=2086769
That got my phone to at least boot to the samsung screen. once there i took it to the sprint store that they reset it for me and took care of the Home button that was failing.
With the home button it sometimes has build up by depressing it alot. So they cleaned it out. Now working phone.
Related
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
jay-red said:
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
Click to expand...
Click to collapse
Im stuck in the same boat with my S4
which ODIN version are you using and are you using the links from SAMMOBILE to get the firmware you need ? also what are your methods of procedure and is odin giving out any errors or saying pass and still no boot ?
I rooted my phone with GALAXY NOTE 2 Toolkit. It was working fine for few months. Recently I noticed a problem when I tried to reboot it, but I pulled the battery out and after reinserting all went OK. then Next day or two another time when I tried to reboot, I got to the point where I cannot boo the phone anymore. I get to the initial T-MOBILE screen and that's where it gets stuck.
I tried to upload a recent ROM through Odin. It worked fine, no errors, no problems, but when I try to boo the same thing happens.
I also tried to get to the other menu ( Power+Home+VolumeUp). It shows the menu with some options but I'm not sure how can I use those. I treid few things but it does not work.
I need to use the phone for work every day so I am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
SAME HERE!!!
aklisiewicz said:
i rooted my phone with galaxy note 2 toolkit. It was working fine for few months. Recently i noticed a problem when i tried to reboot it, but i pulled the battery out and after reinserting all went ok. Then next day or two another time when i tried to reboot, i got to the point where i cannot boo the phone anymore. I get to the initial t-mobile screen and that's where it gets stuck.
I tried to upload a recent rom through odin. It worked fine, no errors, no problems, but when i try to boo the same thing happens.
I also tried to get to the other menu ( power+home+volumeup). It shows the menu with some options but i'm not sure how can i use those. I treid few things but it does not work.
I need to use the phone for work every day so i am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
Click to expand...
Click to collapse
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
go to recovery mode if you can
kim621973 said:
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
Click to expand...
Click to collapse
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
kim621973 said:
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
Click to expand...
Click to collapse
While Knox is a problem, the bootloader is the booger that won't allow return to 4.1.2. Sammy hosed us on that little bit of trickery.
If my wife didn't have a GS3 that I maintain I might have OTA'd. I have been watching their "upgrade" process for a while and knew that there was trouble in the OTA.
It will be painful for a while as people migrate in with problems that have been covered several times. We'll get through it.
Hastily spouted for your befuddlement
I normally work stuff like this out, but i'm having difficulties.
Note II i317, Was running rooted 4.4.2, knox tripped. (rooted it before we had facilities not to trip knox) I was prepping it for trade in, so I ran the back to stock zip instructions from the main forum. UCALJ2 went in fine, it booted and worked, and then OTA happened and now I'm frozen at the Galaxy Note 2 logo in the bootloader.
I have sdk, odin and can access download mode/flash, but can't get in to recovery (it never gets that far) .
I've tried re-flashing stock kies, i've tried a number of roms. I suspect that don't quite understand enough about knox or the bootloaders. I would think if download still works it's still fixable, but reflashing the stock includes a fresh boot loader and it still hates me. It's like it got something in the OTA that the flashes aren't touching.
Any ideas would be greatly appreciated, I've decided to keep it instead of trade but my note 4 is still a couple of days out.
Noting like posting a question to figure out wtf
http://forum.xda-developers.com/showthread.php?t=2596256 seems to have me going in the right direction
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 :/
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