Related
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
all.
I have an i9505 on 3 UK that has been rooted for over 6 months. I've been running the excellent TW based Echo Rom but wanted to try an ASOP rom but quickly wanted to revert.
I tried to restore my Nandroid but this failed and screwed up the phone (dont ask)so back to ODIN and i flashed back to stock 4.4.2 firmware for the UK via Sammobile (NG8)
Now back to square 1 so attempted to reroot with CF Autoroot again via ODIN. all show pass and i get the black screen on the phone with the red android logo and line stating stock recovery restored. I then used ODIN to flash Philz recovery again shown as Pass, however when i try to get into recovery i get some small white text on the bkack background that is there too briefly to read before the phone reboots as normal.
The Su superuser app is there but states the Su binary is outdated and the phone has no root access.
Ive read a few methods to get round this but they all seem to follow the same process ive tried a few times now.
The Rom for Echoe is auto root so id have thought if i could get to recovery somehow i could just flash this ?
Any one any views or have i screwed up for good ? .
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Lennyz1988 said:
You will be fine.
If you want to flash a custom rom anyway the shortest way would be to just flash the custom recovery. You don't need root for that.
Uncheck auto-reboot before you flash the recovery and it should work.
Click to expand...
Click to collapse
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
robinta said:
so i reflashed Philz recovery and unchecked auto reboot. This then gives me PASS in ODIN. I guess then i unplug and try and activate recovery - but still nothing...it just boots up normally ?
Click to expand...
Click to collapse
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Lennyz1988 said:
What is the model descriped when you are in download mode?
What is the exact version of Philz you are trying to flash?
Click to expand...
Click to collapse
GTI9505...(Bootloader i9505xxegng8)
Originally I tried philz_touch_5.15.8-i9505.tar.md5
and then updated to philz_touch_6.23.9-i9505.tar.md5 with no avail.
Try redownloading it. If you say that if passes, then it should just work.
If it still fails then try TWRP. Uncheck auto-reboot before flashing.
Could it be connected to me flashing a generic unlocked UK firmware on a 3 UK handset ?
That's sorted it ! Flashed CWM recovery and am now running Echoes v28.
Thanks for the help. I was really panicking for a while.
I wont be changing roms for a while but I guess if I did I won't lose root ?
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
elliwigy said:
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
Click to expand...
Click to collapse
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
gr8wing said:
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
Click to expand...
Click to collapse
Youre doing too much.. supersu disables knox and uninstaling anything knox related is all you can do.. messing around with stuff you dont know about you WILL end up bricking your phone
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
robertb9657 said:
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
Click to expand...
Click to collapse
Here you go!
https://www.androidfilehost.com/?fid=23622183712474060
Tulsadiver and gr8wing you guys are life savers! Thanks so much! I "ODINed" the firmware only, and then the modem only. after the phone downloaded each, it did not get past boot either time, but I was calm and hopeful. I odined the multi cert file and although it took a lot longer than I thought it would, it worked to perfection and my phone is fully functional and back to where it was two days ago.
I had NI2 rooted, then accidentally did the NK2 OTA update, which lost root. I finally got around to rerooting and decided to get rooted lollipop. I now have changed course and will sit happily with rooted NK2 kitkat.
Thanks!
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
// Edit:
// It is a German Device from Telekom.
// If that helps or makes a little difference.
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Try Samsung care
R3dRacoon said:
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Click to expand...
Click to collapse
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Battlehero said:
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Click to expand...
Click to collapse
Thanks for the response.
What can I do to get a correct working System back? (Theoretically, I got time and bandwidth.)
Since flashing the Stock ROM did not quiet work.
medo sator said:
Try Samsung care
Click to expand...
Click to collapse
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
R3dRacoon said:
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
Click to expand...
Click to collapse
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
medo sator said:
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
Click to expand...
Click to collapse
I've already tried to flash TWRP via Odin, but I've never seen it.
Flashed recovery was for trltexx.
Getting to Recovery should be the same as getting to Download Mode, or?
Anyways. Will try it with tbltetmo and report back.
// Just installed the tbltetmo.
// Can't see how to get into the recovery.
// Am I missing something?
Update:
Just signed up at sammobile and downloaded the BOB6 (4.4 i think) for T-Mobile.
Flashed via Odin.
Seems like it does work again.
Currently its installing like 260 Apps.
Let's see.
// Edit: Nah. It got even worse.
// But I got a Recovery. So that's something.
IT ****ING WORKS NOW
Went into the recovery and cleared cache and data. (Kinda stupid I did not do it inb4)
Do a clean install in Odin. Since it came with stock android 5.1.1, then flash the 5.1.1 stock firmware in Odin. If you have a locked device of a specific carrier it will be even better to use the firmware made for that carrier only. And check the "Nand erase all" option in odin before hitting the start button to flash. That will erase all the data from ur phone and will do a clean install. Your phone must then boot normally. Also note that android 5.0 root file may not work for 5.1. Also check the model number before flashing.
I need this fixed asap as I need my phone for school.. I have no idea what Happened honestly, I just restarted my phone and it started doing this. The only thing i recall doing is possibly disabling SuperSU on accident before I restarted my phone.
All I've done so far is download the stock firmware from SamMobile and attempted to flash it, but when i do i get an (auth) failed code from Odin, I've been searching for hours and haven't found anything that has helped..
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Can you help with a newer model?
*Detection* said:
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Click to expand...
Click to collapse
i don't have anything recovery installed, its jsut the normal android recovery. I thought about reflashing supersu but I'm not sure how without a recovery..
Have you tried the factory reset from normal recovery?
*Detection* said:
Have you tried the factory reset from normal recovery?
Click to expand...
Click to collapse
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
What about a SM-G900P?
TheAgonistxX said:
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
Click to expand...
Click to collapse
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
*Detection* said:
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
Click to expand...
Click to collapse
Tried flashing TWRP with the same end result.. This is dumb really frustrating -.- is there any way to install Supersu without a recovery?
CF Auto Root, but it'll likely fail too due to the bootloader
II have been working on mine same model and it is because once you screw up ,which i did,the locked boot loader wont let anything by. a relative pretty much started the problem by flashing a ROM and erasing everything. this one wont even go into recovery. still wont give up until I figure out a way just because.......