Rooting SM-N900 4.4.2 problem
I'm tring to root my Note 3 SM-N900 with cf-autoroot, but Odin get stuck on cache.img and the phone is bricked.
(usb debugging is ON, reactivation lock is OFF)
(i flashed twrp recovery, the phone is back to normal,original recovery is back, not twrp)
i tried with odin 3.07/3.09/3.10.7
changed usb cable, usb port, usb drivers
i tried with another cs-autoroot file downloaded from another location
but same problem
any solution please? or another method to root my phone?
cs-autoroot for sm-n900 is for 5.0 only or works also on 4.4.2?
C'mon... There are numerous threads on the web regarding this. Do you even read the instructions, or just download stuff and flash it ?
Dejan Sathanas said:
C'mon... There are numerous threads on the web regarding this. Do you even read the instructions, or just download stuff and flash it ?
Click to expand...
Click to collapse
i did read every single thread about rooting the sm-n900, all comments and every google result.
As i mentioned in my post, i tried different odin versions, and all usb cable related problems...etc
Factory reset and flash a stock rom via Odin .
Read the thread title .
http://forum.xda-developers.com/galaxy-note-3/help/qa-cf-auto-root-t2905153
i've seen that thread, only peolple with my problem but no solution
i already have a stock rom 4.4.2
i know how to recover from a failed flash, the problem is i cannot root the phone
Odin v3.07 results:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Related
Hi,
I am really new to this and basically stuck without a phone (noob move I know).
I wanted to upgrade to Kitkat and downloaded N9005XXUENB4_N9005DBTENB1_DBT and odin v3.09.
I started up in download mode and got the following failure:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I restore so I can even just start my phone. Currently I only get the error saying upgrade failed- connect to Kies. But I again being noob never setup kies backup before.
PLEASE PLEASE help.
Where do I get a stock firmware recovery to reflash
antz69 said:
Hi,
I am really new to this and basically stuck without a phone (noob move I know).
I wanted to upgrade to Kitkat and downloaded N9005XXUENB4_N9005DBTENB1_DBT and odin v3.09.
I started up in download mode and got the following failure:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I restore so I can even just start my phone. Currently I only get the error saying upgrade failed- connect to Kies. But I again being noob never setup kies backup before.
PLEASE PLEASE help.
Where do I get a stock firmware recovery to reflash
Click to expand...
Click to collapse
Flash NB4 again but this time also flash this pit file and check repartition. If phone is getting stuck at samsung logo upon reboot, boot to recovery and factory reset.
Well first what your model, this is n9005
is your download complete, did you have the drivers installed (kies installed but you need to kill it - in order to odin to work without issues)
go through this, page, it has detail procedure in odin flash of the same ROM.
http://androidromupdate.com/tag/n9005xxuenb4_n9005dbtenb1_dbt-zip/
@antz69 , hope that helps.
Hi guys I'm having problems trying to root my note 3, in fact i can't flash anything with odin.
It is a n900w8 from Telcel, with 4.4.2 stock rom.
I tried flashing to root it and tried to flash a custom recovery and nothing.
this is what odin shows:
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in the phone it shows in red letters : Secure check fail : recovery
I already checked the reactivation lock, and it isn´t checked.
Do you have an idea of what could it be?
If you need another info pleas tell me, i would appreciate any help thanks
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: HERE.
Joku1981 said:
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: .
Click to expand...
Click to collapse
thanks for the answer but i didn´t work , I can flash that rom but only that. I tried to flash the root and the same error.
I am trying to root my S5 using Odin for installing custom ROM but unable to root it. As soon as i start the root process, it gives the message of Failed.
help please?
Need a lot more info than that bud, model S5?
Method you are using step by step?
I have S5 SM-G900F
i am connecting it to my laptop in download mode with USB Debugging enabled
Odin is detecting the phone, i added the CF-Auto Root file to Odin
The Odin gave indication that this file is valid
Once i start the operation, it displays this in Message window of Odin
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The message that i get on my cell phone screen are
UDC START
SYS REV CHECK FAIL : No Version
SECURE MAGICODE CHECK FAIL : recovery
and the process ends up with a FAIL message in Odin
Are you running ODIN as Admin? (Right click > Run as Administrator)
And you've tried a couple different versions from 3.09 > 3.10.7 ?
-
If that still fails, you'll probably need to flash TWRP 2.8.7.0 with ODIN then SuperSU from TWRP recovery
Specifically version 2.8.7.0
And you don't need USB debugging enabled for flashing from download mode, only for connecting while the phone is booted into Android
Try another software
Try flashing already rooted ROM if not considered ?
Don't use kingroot !
regards
Max.
okay let me try this way now
NO DO NOT TRY KINGROOT
Only CF Auto Root or SuperSU from recovery
Anything else is likely to brick your phone
---------- Post added at 15:06 ---------- Previous post was at 15:05 ----------
stalker2106 said:
Try flashing already rooted ROM if not considered ?
Either, you could try KingRoot, it works on some devices,
but it is horribly slow.
regards
Max.
Click to expand...
Click to collapse
Don't give out advice that you have not personally tested on the S5
Are you going to fix his phone for him when you brick it?
I flashed my G900F using Odin3 but i rooted my tablet with KingRoot and it worked well, so i though he could give it a shot ! but if you say its not recommended then i will edit my post, sorry for inconvenience.
Rooting a tablet with kingroot has nothing to do with a Galaxy S5
Again, unless you have successfully performed what you are suggesting on the S5, do not suggest it, a tablet has nothing to do with an S5
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse
Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.
@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg
I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?
Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg
@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg
Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.
Hello all.
I'm having multiple problems with my Note 4.
Model is SM-N910F and the problems are:
Does not boot to OS
OS Flash works but does not do final stuff on the phone
When installing OS, it will just spit out failed to mount /efc (Invalid argument)
Tried Kies recovery, that fails too
Custom recovery does not work.
Is it safe to say that this device is officially dead and i should get a new phone?
JantsoP said:
Hello all.
I'm having multiple problems with my Note 4.
Model is SM-N910F and the problems are:
Does not boot to OS
OS Flash works but does not do final stuff on the phone
When installing OS, it will just spit out failed to mount /efc (Invalid argument)
Tried Kies recovery, that fails too
Custom recovery does not work.
Is it safe to say that this device is officially dead and i should get a new phone?
Click to expand...
Click to collapse
Flash 4files repair firmware with PIT file then do factory reset.
Get from link below
https://www.androidfilehost.com/?fid=24407100847294341
Extract thr file you will get 5 files ( BL/AP/CP/CSC/PIT
)
UPLOAD ALL FILES IN ODIN CORRECTLY AND GO TO ODIN OPTIONS CHECK "NAND ERASEALL".
HIT START
ONCE ODIN SHOWS PASS GO TO STOCK RECOVERY MAKE FACTORY RESET THEN REBOOT.
If this does not work then your eMMc chip need to replace from motherboard.
Hope this will help.
Trex888 said:
Flash 4files repair firmware with PIT file then do factory reset.
Get from link below
https://www.androidfilehost.com/?fid=24407100847294341
Extract thr file you will get 5 files ( BL/AP/CP/CSC/PIT
)
UPLOAD ALL FILES IN ODIN CORRECTLY AND GO TO ODIN OPTIONS CHECK "NAND ERASEALL".
HIT START
ONCE ODIN SHOWS PASS GO TO STOCK RECOVERY MAKE FACTORY RESET THEN REBOOT.
If this does not work then your eMMc chip need to replace from motherboard.
Hope this will help.
Click to expand...
Click to collapse
Hey Trex888.
ODIN fails with this message:
Code:
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So the eMMc chip is dead and needs to be replaced?
JantsoP said:
Hey Trex888.
ODIN fails with this message:
Code:
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So the eMMc chip is dead and needs to be replaced?
Click to expand...
Click to collapse
Try odin version 3.10.
Try restart your pc.
Make sure all files inserted correctly in odin.
Try different usb cable.
Do a factory reset from recovery before start flashing.
Trex888 said:
Try odin version 3.10.
Try restart your pc.
Make sure all files inserted correctly in odin.
Try different usb cable.
Do a factory reset from recovery before start flashing.
Click to expand...
Click to collapse
Did all that and no joy. Anything else i could try or should i just give up and get a new one?
JantsoP said:
Did all that and no joy. Anything else i could try or should i just give up and get a new one?
Click to expand...
Click to collapse
This method sounds weird but give it a try not kidding i am serious
Put your phone in a plastic airpack bag in freezer without battery for 2 or 3 hours or better if whole night then take out immediately go to download mode and flash stock firmware.
Dozens of note 4 users ware able to recover by this crazy method You can read more about this down below.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Trex888 said:
This method sounds weird but give it a try not kidding i am serious
Put your phone in a plastic airpack bag in freezer without battery for 2 or 3 hours or better if whole night then take out immediately go to download mode and flash stock firmware.
Dozens of note 4 users ware able to recover by this crazy method You can read more about this down below.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Click to expand...
Click to collapse
Now that sounds weird
Will try it