Hi,
I had my S5 rooted after I bought it.
When I updated to the latest firmware (using KIES as OTA was not working) I lost root.
CF autoroot won't root my phone anymore. How can I get root back?
Thanks
J
Try updating using Odin.
Michael_P said:
Try updating using Odin.
Click to expand...
Click to collapse
Not sure I understand what you mean.
What I did!
Bought S5. Rooted with CF autoroot.
On 24.5. a firmware update was available from Samsung.
Installation OTA not possible due to root.
Samsung firmware updated using KIES.
After update root was gone.
Odin and CF autoroot fails now:
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
Any ideas?
The button in Odin does not go to yellow as mentioned.
ScubaInstructor said:
Not sure I understand what you mean.
What I did!
Bought S5. Rooted with CF autoroot.
On 24.5. a firmware update was available from Samsung.
Installation OTA not possible due to root.
Samsung firmware updated using KIES.
After update root was gone.
Odin and CF autoroot fails now:
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
Any ideas?
The button in Odin does not go to yellow as mentioned.
Click to expand...
Click to collapse
I got it to work again.
-> I removed the SDCARD and disabled the Reactivation Lock.
Related
Hello people, I bought a second hand galaxy note today, using Samsung keyboard, when I press the letter keys, instead of getting the corresponding letter I am getting "null" on the screen. Other keyboard works fine.
You need to flash CSC according ROM you have installed
Give this detail from setting - about phone
Baseband ?
Kernel ?
version ?
as well dial this
*#1234#
and input result here
Baseband: N7000XXLPT
Kernel: 3.0.15-N7000XXLQ2-CL605927
[email protected]#3
Build number: IML74K.XXLQ2
PDA: N7000XXLQ2
Phone: N7000XXLPT
CSC: Unknown
I bought this phone second, the previous owner must have flash it without CSC
Flash the same ROM again with putting the ROM file in the [Cash] option in Mobile Odin.
Search for this ROM - UK I guess - in dr.ketan topic.
Good luck
Is it important to have csc?
FinancialWar said:
Is it important to have csc?
Click to expand...
Click to collapse
If you don't want it to do what it's doing it is. It contains other boots and bobs to do with the region your in.
Sent from my GT-N7000 using Tapatalk 2
FinancialWar said:
Baseband: N7000XXLPT
Kernel: 3.0.15-N7000XXLQ2-CL605927
[email protected]#3
Build number: IML74K.XXLQ2
PDA: N7000XXLQ2
Phone: N7000XXLPT
CSC: Unknown
I bought this phone second, the previous owner must have flash it without CSC
Click to expand...
Click to collapse
find lq2 rom and flash csc by selecting pda tab in odin. remembet yoy will lose data, so backup first.
Sent from my GT-N7000 using xda premium
I had look at your thread, does that mean I have to buy Mobile Odin Pro for the newer ICS firmware?
you can flash csc.with pc.odin too.
mobile odin have some.extra benifit like keep root while flashing. it is hassle free from pc connection.
so it is not must, just optional.
Sent from my GT-N7000 using xda premium
I am confused. I just bought the Mobile Odin and am getting
" superuser access is needed but could not be acquired . are you rooted and did give permission.
what am I supposed to do?
have you open supersu appl and updated binary?
if your root is proper, first time it will ask to grant permission.
Sent from my GT-N7000 using xda premium
dr.ketan
I went through the root process in your "When all other method fails to root your device"
after everything was done, I am stuck on the Welcome to GT-N7000 screen.
Keeps on getting error messages popping up, then the phone would go blank and then slowly display this weird greenish screen.
here is the message report from Odin
OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
FinancialWar said:
dr.ketan
I went through the root process in your "When all other method fails to root your device"
after everything was done, I am stuck on the Welcome to GT-N7000 screen.
Keeps on getting error messages popping up, then the phone would go blank and then slowly display this weird greenish screen.
here is the message report from Odin
OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
yes it is common, b'coz kj1 hav old kernel. now. just flash newer cf root kernel like lb1 .
Sent from my GT-N7000 using xda premium
dr.ketan said:
yes it is common, b'coz kj1 hav old kernel. now. just flash newer cf root kernel like lb1 .
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
How do I flash the newer cf root kernel?
Sent from Samsung Galaxy Note
I think the question needs to be asked, do you actually want root and non standard firmware/kernel?
If you just want a standard phone but want to solve the problem you originally asked about then just download and flash factory firmware from Sammobile.com using pc odin.
Sent from my GT-N7000 using XDA
FinancialWar said:
How do I flash the newer cf root kernel?
Sent from Samsung Galaxy Note
Click to expand...
Click to collapse
Download this and flash with Mobile odin
http://download.chainfire.eu/149/CF-Root/SGN/CF-Root-SGN_XX_OXA_LB1-v5.0-CWM5.zip
scotthubbard said:
I think the question needs to be asked, do you actually want root and non standard firmware/kernel?
If you just want a standard phone but want to solve the problem you originally asked about then just download and flash factory firmware from Sammobile.com using pc odin.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
it won't work because my kernel is too old? I tried that already and I get error messages
dr.ketan said:
Download this and flash with Mobile odin
http://download.chainfire.eu/149/CF-Root/SGN/CF-Root-SGN_XX_OXA_LB1-v5.0-CWM5.zip
Click to expand...
Click to collapse
That seems to do the trick, the note is now running the ICS firmware probably.
dr.ketan said:
You need to flash CSC according ROM you have installed
Give this detail from setting - about phone
Baseband ?
Kernel ?
version ?
as well dial this
*#1234#
and input result here
Click to expand...
Click to collapse
Android Version: 2.3.5
Baseband: N7000XXLA4
Kernel Version: 2.6.35.7-N7000XXKJ1-CL627135 [email protected] #2
Build: GingerBread.XXKJ1
PDA: N700XXKJ1
Phone: N7000XXLA4
CSC: Unknown
What do i do? Im also facing the same issue with the keyboard? Let me know ASAP Explain in noob language please
Flash csc this way
Open pc odin - select csc tab - point to rom file which you hav flashed.
Flash.
Sent from my GT-N7000 using xda premium
So I was running omnirom and everything was running smoothly but I some how messed up the music applications on my phone and I wanted to do a backup however my phone couldn't mount my external sd card so I wiped everything on my phone and now the phone is bricked... I install odin and tried to flash to stock but it keeps failing. This is message log.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Someone pleased help me! Thank you!
Sorry for the obvious question..but if you can boot into DL mode...can you boot to recovery and at least flash a ROM you have saved?
"Remember if you say Please....be sure and Hit Thanks!!!"
Flash stock rom using odin and then do a factory reset(data wipe) in recovery.
Make sure u have everything(cooper v1.0 and stock rom zip file) and up to date odin
Sent from my MT27i using xda app-developers app
yeah I flash the stock rom for my phone but it fails. Should I flash the pit file for my phone?
Can you boot in recovery?
Sent from my MT27i using xda app-developers app
btoddweber said:
Sorry for the obvious question..but if you can boot into DL mode...can you boot to recovery and at least flash a ROM you have saved?
"Remember if you say Please....be sure and Hit Thanks!!!"
Click to expand...
Click to collapse
I can boot into DL mode but I can't boot into recovery.
Nick123194 said:
yeah I flash the stock rom for my phone but it fails. Should I flash the pit file for my phone?
Click to expand...
Click to collapse
let me guess before omni ROM you were on MJA or MK2 and are trying to Odin MF9, MDL, or MDC tar?
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
let me guess before omni ROM you were on MJA or MK2 and are trying to Odin MF9, MDL, or MDC tar?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I have no idea. First when I got my phone I went from android 4.2.2 then downgrade to 4.3 (Allowed Knox to void my warranty smfh) then I flashed to CM 11 then to beanstock then finally omnirom. I believe I'm trying to MDC tar but not sure.
Nick123194 said:
I have no idea. First when I got my phone I went from android 4.2.2 then downgrade to 4.3 (Allowed Knox to void my warranty smfh) then I flashed to CM 11 then to beanstock then finally omnirom. I believe I'm trying to MDC tar but not sure.
Click to expand...
Click to collapse
that's your problem. you were on 4.3 with Knox tripped. once on 4.3 you cannot go back to 4.2.2 via odin. grab yourself a MJA or MK2 tar and Odin it. that should boot up your phone.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
that's your problem. you were on 4.3 with Knox tripped. once on 4.3 you cannot go back to 4.2.2 via odin. grab yourself a MJA or MK2 tar and Odin it. that should boot up your phone.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Thank you so much. Wow I don't know why I tried to go back to 4.2.2 :silly:
Nick123194 said:
Thank you so much. Wow I don't know why I tried to go back to 4.2.2 :silly:
Click to expand...
Click to collapse
that was the first Odin fine to become available (MDC), so most folks have it. NP
Sent from my SPH-L720 using Tapatalk
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south.
Could I be flashing a bad file? Is the CWM.tar.md5 not the correct file to flash?
I've tried several different versions of both Odin and CWM. Is there something else that I have to do before this step? I've read a lot about the S4 being a pain to load custom roms onto.
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!
Your boot loader is locked. So, no custom recovery and kernel. The only working recovery we have is safestrap.
More info - http://forum.xda-developers.com/showthread.php?t=2616221
misterbreadcrum said:
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2!
Click to expand...
Click to collapse
I see this above but need more info... Are you completely stock right now?
You will NOT be able to Odin any CWM to this phone. See below for other brief info for you to look into for CWM/TWRPand how to install IF on MDB or MDL firmware. Or if MF3 Your ONLY OPTION is Safestrap and limited to TouchWiz based Roms.
If you are then when you go to Settings/More/About Phone what does your Baseband say? Does it end with MDB, MDL, MF3?
IF it ends with MDB or MDL the look up Casual Root with TWRP. This will allow you to flash ANY Roms.
IF it ends with MF3 Then look up Safestrap for MF3. This will allow you to flash Safestrap versions of Roms.
ALSO IF it is MF3 you might as well update to MK2 or NB1 then use their safestrap version for root
Sent fron I337 Red BadAss Themed ShoStock 7.0
can someone help me how to root n9005 lollipop version and how to install CWM to lollipop n9005? thanks....
Use Odin. pda.
kenny1991 said:
Use Odin. pda.
Click to expand...
Click to collapse
Can you please elaborate? I am a noob to the note 3 root on Lollipop. on the new Odin there is no PDA option, is there a newer up too date thread somewhere of how to do this please?
---------- Post added at 09:07 PM ---------- Previous post was at 08:36 PM ----------
Nico231995 said:
can someone help me how to root n9005 lollipop version and how to install CWM to lollipop n9005? thanks....
Click to expand...
Click to collapse
Did you get yours rooted? I need help getting mine done.
DevilsArc said:
Can you please elaborate? I am a noob to the note 3 root on Lollipop. on the new Odin there is no PDA option, is there a newer up too date thread somewhere of how to do this please?
---------- Post added at 09:07 PM ---------- Previous post was at 08:36 PM ----------
Did you get yours rooted? I need help getting mine done.
Click to expand...
Click to collapse
on laster Odin (V3.09 or v3.10)
PDA is AP
download the laster TWRP or phliztouch link for TWRP: http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.8.3.0-hlte-4.4.img.tar
place in AP on odin and flash
And download the zip flashable by chanfire and flash on recovery http://download.chainfire.eu/644/SuperSU/BETA-SuperSU-v2.42.zip
done
And my phone is not the root
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
My Phone N9005 and Lollipop 5.0 N9005XXUGBNL8 installed.
Odin when I go to install v3.10 twrp or CR with getting the above error.
Debugging active.
I run the Odin as administrator.
V3.7 I get the same error message.
ZeoN1907 said:
My Phone N9005 and Lollipop 5.0 N9005XXUGBNL8 installed.
Odin when I go to install v3.10 twrp or CR with getting the above error.
Debugging active.
I run the Odin as administrator.
V3.7 I get the same error message.
Click to expand...
Click to collapse
I have flashing TWRP 2 times, it's work very well (odin 3.09)
I'm on GBNL8 too
Bruno saa said:
I have flashing TWRP 2 times, it's work very well (odin 3.09)
I'm on GBNL8 too
Click to expand...
Click to collapse
I'm so tired I'm sorry.
I wonder?
The email address you download Odin,
Can I get the address or the address you're TWRP version and download version or download supers? If possible?
You send them to a compressed file or via email?
I tried many ways but I'm having trouble.
My English is not good. Forgive me. Please.
Port USB
ZeoN1907 said:
My Phone N9005 and Lollipop 5.0 N9005XXUGBNL8 installed.
Odin when I go to install v3.10 twrp or CR with getting the above error.
Debugging active.
I run the Odin as administrator.
V3.7 I get the same error message.
Click to expand...
Click to collapse
Hi,
I had the same problem and same message for a long time.
And one day i tried to do that with another usb port. It WORKED ! simple as that
Cheers
My phone: SM-N9005 (Philippines) Knox 0x1 ; Custom Status
Before, it was it was rooted with KitKat 4.4.2 and I got SuperSU by using CF auto-root. (CF-Auto-Root-hlte-hltexx-smn9005.tar) here is the file name to be sure, then knox was tripped.
later a few months. I accidentally accepted a auto software update. Biggest mistake! After, the update was done. My SuperSU is gone and I lost root permission. Yet my status is still Custom.
I tried flashing CF auto root again to my phone with Odin 3.09 and 3.07. Both Failed! I tried approx 15 times. Then I flashed to 5.0 lollipop (N9005DXUGBOF1_N9005OLBGBOF1_XTC) thinking that might work, then I tried flashing it again with CF auto-root, still failed though! Then I was thinking maybe, CF auto-root didn't work because of a 5.0 bootloader. I went back to 4.4.2 KK (N9005XXUGNI4_N9005OLBGNL1_XTC) again, and i tried flashing CFAR again with Odin 3.09 and 3.07, and guess what?! I still failed. Please HELP! it's been a long day!
kenmante said:
My phone: SM-N9005 (Philippines) Knox 0x1 ; Custom Status
Before, it was it was rooted with KitKat 4.2.2 and I got SuperSU by using CF auto-root. (CF-Auto-Root-hlte-hltexx-smn9005.tar) here is the file name to be sure, then knox was tripped.
later a few months. I accidentally accepted a auto software update. Biggest mistake! After, the update was done. My SuperSU is gone and I lost root permission. Yet my status is still Custom.
I tried flashing CF auto root again to my phone with Odin 3.09 and 3.07. Both Failed! I tried approx 15 times. Then I flashed to 5.0 lollipop (N9005DXUGBOF1_N9005OLBGBOF1_XTC) thinking that might work, then I tried flashing it again with CF auto-root, still failed though! Then I was thinking maybe, CF auto-root didn't work because of a 5.0 bootloader. I went back to 4.4.2 KK (N9005XXUGNI4_N9005OLBGNL1_XTC) again, and i tried flashing CFAR again with Odin 3.09 and 3.07, and guess what?! I still failed. Please HELP! it's been a long day!
Click to expand...
Click to collapse
Can you install this APP and add screenshots pls?
Ok!
kenmante said:
Ok!
Click to expand...
Click to collapse
Seems all ok.
1. Try to flash TWRP custom recovery via ODIN.
2. Flash this file via TWRP.
Do I really need to be in 4.4 Kitkat?
kenmante said:
Do I really need to be in 4.4 Kitkat?
Click to expand...
Click to collapse
Are you insane, dude? Remove your ****ing imei?
Joku1981 said:
Seems all ok.
1. Try to flash TWRP custom recovery via ODIN.
2. Flash this file via TWRP.
Click to expand...
Click to collapse
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)