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
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 am planning on rooting my friend's stock i317 running the MC3 stock firmware. He recently got a carrier replacement i317 due to a hardware issue but I had also previously rooted his other i317 and installed a CM10.2 nightly ROM. Upon using the same method of rooting his first phone on the new one, I ended up soft bricking his second phone. I basically used ODIN to flash a few different recoveries but when I would boot to recovery each time then the Galaxy Note II logo would start flickering for a few seconds and then the screen would go blank. I tried using ODIN to restore to JL2 and upon successfully restoring, I couldn't get past the boot animation. I told my friend to replace the phone again as I couldn't even get the phone to boot up successfully no matter what I tried doing to fix it. Maybe I had to find and ODIN the MC3 firmware to successfully boot the device so please let me know what I did wrong which prevented the device from booting successfully.
I don't know whether there was recently a major AT&T firmware update that changed the security on the device which prevented previous methods of root from working so please update me on any changes. My friend just got a new i317 today and I would like to root it successfully as the AT&T warranty center was nice enough to replace his phone but had to void his warranty due to looking at the flash counter. I just found an app called Framaroot which looks much simpler to use
http://forum.xda-developers.com/showthread.php?t=2130276
I have been rooting and flashing ROMs on various Android devices for a long time now so I am up for using any root methods no matter how advanced they may be including using ADB. I did not have enough time to research about the i317 so it was my fault that I could not successfully root his device. Any help would be much appreciated.
Thank you
For rooting purposes start HERE:
http://forum.xda-developers.com/showthread.php?p=33854391
For recovery look HERE:
http://forum.xda-developers.com/showthread.php?p=33867032
Add I prefer TWRP recovery over CWM!!
From everything you said you did it sounded right. Cuz you even tried going back too the original firmware that was shipped with the device!! But I didn't seed that after you flash the Rom,, did you try to do a factory data reset. Sometimes that's all it takes to fix that bootloop problem.
One other thing if you can get into download mode then the phone is fixable. Think it was just over your head on the process on how to get it back to fully functioning... lol
We've all been there. Think it's because we panic when something isn't working the way we want it TO..
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Okay here is the problem guys. I have my note three for three weeks now. Rooted it day one. But It seems with every phone I have addiction with flashing roms. I change around a lot. I have owned four devices this year. S4, note 3, nexus 4 and galaxy nexus. Rooted every device never had an issue that couldn't be fixed by flashing the stock tar via odin. The other day I flashed compulsion kernel and put me in a boot loop. So I did the natural thing and download the stock tar and flash via odin. First time was a bust. It said it was successful. Still put me in boot loop so I downloaded the stock tar from another location and tried again. Still no dice and still have boot loop. Tried flashing a custom rom after flashing the stock tar. Nothing still boot loop and I've also tried different recoveries and still nothing. I know its not hard bricked because I can still boot into recovery. I am actually a sales rep at a corporate tmobile store and did a warrarnty exchange and they are overnighting me another note three and I am going to send this one back. Little concerned as to having the rooted status on the device is going to go over. A couple times after I flashed the stock tar I got it to boot but then it would say "process system stopped responding wait or ok" then after clicked okay it reboots. I really hope there is someone out there with a solution.
HELP
This isnt your usual soft brick. If someone could please help I would appreciate it!!
Dude my phone out of nowhere bricklooped today like literally. I installed different roms no dice. 3 backups including the stock one and nothing still bootlooped I tried the brickloop fixer on jovys darthstalker v6 and I'm back up and running but if I reboot or turn off phone and reboot it goes into same bootloop he's a smart, brilliant dev I'm sure he can help me out as well as you
Sent from my SM-N900T using xda app-developers app
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 :/
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
+1 on that, I'm stuck in an exact same situation. No help from Samsung either. After rooting with Kingroot my tab started acting like crazy with flickering screen and random reboots, did exactly like you did.
There are many with similar issue and as per my research most of them have given up. Getting a system image dump from a rooted tab running 4.4.2 might be the only way out. Unless of course Samsung/AT&T decides to release full odin flashable image.
I was in a similar situation from trying to fix a eff problem and took my sgh-i467 to a Samsung Experience Center located in many Best Buys and they fixed it free of charge. They were not able to fix my issue with a corrupted EFF file that is keeping my 4G from working though as I had hoped. If you have a Best Buy around with the Samsung Kiosk in it I would give it a try. I ended up trying a few different ones to fix the eff issue and some of the employees at the Samsung centers were about as smart as a head of cabbage (they laughed at me when I said my Note 8 was the issue and said "you can't have a Note 8 the Note 5 just came out") but some were at least helpful and listened when I told them they have the tools to fix my tab (reflash it back to life) and they did. Hopefully they can help you.
man Im in the same exact situation.. And I cant seem to find any help anywhere. I cant locate a stock 4.4.2 kit kat odin flashable file anywhere for the n5120
Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
please help me i need de 4 files repair from this tablet
Try the forum thread started by djjiz, https://forum.xda-developers.com/galaxy-note-8-0/help/i467-4-4-2-t3537302... He posted the files and yes I was able to bring back my previously bricked AT&T Note 8.