Hello World,
I'm new on the forum and my first topic is this
I have a very big problem. I installed the custom rom Hyperion 7, last week. Today, I wanted test a tutoriel to unlock up to 900 MHz..So..
at the beginning, I did a backup with ClockWorkMod of my rom if I had a problem.
I did the tutoriel without probleme until the reboot :/
My phone reboot automatically on Android System recovery, at the bottom of screen, it's write with blue characters :
"very/log
E:failed to mount /cache
(Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Cant' open /cache/recovery/last_log"
However, I tested all, I wiped data/factory reset, I wiped cache partition, I tested to re-install Hyperion 7, nothing, nothing at all, my phone is lock on the Android System recovery.
Impossible to boot on ClockWorkMod. It's very strange
I don't know What do.. What Shall I do ? Please Help-me !
Thank you very much
(Sorry for the mistakes, i'm french )
Well bonjour lol anyways you gonna need to flash stock rom using Odin the link below explains it all
http://forum.xda-developers.com/showthread.php?t=1465800
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
search for ext4 to rfs converter in the development section
flash via cwm.. chose rfs and reinstall you rom
even if you flash stock rom you eill probably get bootloops unless you flash the ext4 to rfs converter zip
did u mounted data nd other stuf..?
**rooting is new for me...and i am noob to root...**
menewtoroot & tingtingin.. please check your pm's
_________________________________
[HELP THREAD]Any Questions! Ask here
Judge a man by his questions rather than his answers.
Gregoirercz said:
Hello World,
I'm new on the forum and my first topic is this
I have a very big problem. I installed the custom rom Hyperion 7, last week. Today, I wanted test a tutoriel to unlock up to 900 MHz..So..
at the beginning, I did a backup with ClockWorkMod of my rom if I had a problem.
I did the tutoriel without probleme until the reboot :/
My phone reboot automatically on Android System recovery, at the bottom of screen, it's write with blue characters :
"very/log
E:failed to mount /cache
(Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Cant' open /cache/recovery/last_log"
However, I tested all, I wiped data/factory reset, I wiped cache partition, I tested to re-install Hyperion 7, nothing, nothing at all, my phone is lock on the Android System recovery.
Impossible to boot on ClockWorkMod. It's very strange
I don't know What do.. What Shall I do ? Please Help-me !
Thank you very much
(Sorry for the mistakes, i'm french )
Click to expand...
Click to collapse
well buddy first u need to get back to ur device to work as it was earlier..for this you have to go back to stock rom.........heres the link
http://forum.xda-developers.com/show....php?t=1465800
now aftr going back to stock if u want to install hyperion pre 7x follow these steps
1)reboot to recovery by pressing vol up+power button+cebter/home button
2)get into cwm
3)wipe data and cache
4) go to advanced option in cwm
5)wipe dalvik cache and battery stat
6) go back and select install zip from sd card
7)choose zip and navigate to ur hyperion zip file in sd card
8)install it
9)after installing reboot back to recovery
10) again do steps 2-5
11)go to advanced and select REBOOT RECOVERY
12) it will boot u into recovery
13) clear cache again and simply boot ur device.....hyperion is installed and wil wrk grt...wait fr 2-3 min as its first boot is bit slow
PRESS THANKS IF U LIKE MY EFFORT:good:
tingtingin said:
Well bonjour lol anyways you gonna need to flash stock rom using Odin the link below explains it all
http://forum.xda-developers.com/showthread.php?t=1465800
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
Click to expand...
Click to collapse
Ok, but I don't know which choose. I'm in France.
After going through the tread I am not sure myself since France is in Europe and he has plenty European builds u should flash 1 of the multi language builds
P.s if u flash a firmware that isn't from your region your phone will still function normally the only problem u may get is connection problems like connecting to 3g and such so I'd just flash 1 as long as no connectity problems are present ur golden so just try 1
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
tingtingin said:
After going through the tread I am not sure myself since France is in Europe and he has plenty European builds u should flash 1 of the multi language builds
P.s if u flash a firmware that isn't from your region your phone will still function normally the only problem u may get is connection problems like connecting to 3g and such so I'd just flash 1 as long as no connectity problems are present ur golden so just try 1
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
Click to expand...
Click to collapse
Thank you very much ! But now :/ my phone isn't reconized with Odin 3 v1.85.
Samsung Kies is Off and I tested to change USB wire and plug.
What shall i do ?
Install samsung USB drivers check the link I gave u earlier he should have a link to the drivers
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
tingtingin said:
Install samsung USB drivers check the link I gave u earlier he should have a link to the drivers
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
Click to expand...
Click to collapse
Thank's ! it's working !
I've a last problem, in the package I downloaded (Europe S5360_XXLK1_OXFLK1_XXLH2) there aren't a Pit file.
So, in Odin, it's wrote:
" <ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLK1.tar.md5 is valid.
<OSM> MODEM_S5360_XXLH2.tar.md5 is valid.
<OSM> CSC_S5360_OXFLK1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)"
What is the problem ? I don't understand
It's good, I succeed.
I went here: phonandroid. com/forum/liste-des-versions-d-odin-avec-les-fichiers-ops-pit-t12123.html
All is Ok, Thank you everybody, thank you very much.
Don't say thanks hit it
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
Gregoirercz said:
It's good, I succeed.
I went here: phonandroid. com/forum/liste-des-versions-d-odin-avec-les-fichiers-ops-pit-t12123.html
All is Ok, Thank you everybody, thank you very much.
Click to expand...
Click to collapse
m from india ..can i flash this europe stock rom S5360_XXLK1_OXFLK1_XXLH2 is there any problem that i will b facing ??
kshashank said:
m from india ..can i flash this europe stock rom S5360_XXLK1_OXFLK1_XXLH2 is there any problem that i will b facing ??
Click to expand...
Click to collapse
Nope.. It will be just fine..
** rooting is new for me,
nd i am a noob to root....**
Related
Hi guys,
My friend flashed my phone and there was a problem with the backup of the original firmware (for some reason) so we did not do it.
Unfortunately days after updating (and only days after I got the phone) there was a hardware problem in the form of a pink discolouring (leak?) in the screen which has spread from a tiny pink dot to the majority of the lower half of the screen. Due to this I need to return the phone for repair hence the need to return it back to factory firmware.
I have tried flashing to older firmware in order to upgrade my phone with Kies (and bricked my phone in the process forcing me to make a jig ) however even after flashing to 2.1 Update 1 and trying to trick Kies with the patcher there does not seem to be an update available from Vodafone Australia for the device.
Could a kind fellow aussie please help me out by uploading a backup of the original Vodafone Australia Samsung Galaxy S firmware, I assure you that your kind deed will not go unrewarded.
Thank you!
I9000DTJG4|2.1|2010 July|Download
I9000DTJP5|2.2|2010 November|Download
Vodafone FW: HVJH1 – http://www.multiupload.com/U7OG0XQYJF
Vodafone JH1 CSC only: http://www.multiupload.com/ZJ6TMSF0H7
password: asgardxda
Wow, I feel like such a noob.
After spending so much time trying to find this firmware I was convinced that it was not out there but now I can see where you have found it.
Thank you so much! As promised I will have to reward you, feel free to PM me your PayPal e-mail address so that I can give you a small token of my appreciation (Or to a cause of your choosing if you prefer.
Thanks again.
Ran into some trouble with the following error.
E:Cant mout /dev/block/st110
(invalid argument)
E:copy_dbdata_media:cant mount DBDATA:
copy default media conent failed.
Had to flash JM9 with repartitioning then the Vodafone firmware with no repartitioning as shown in THIS THREAD.
Everything is good now, taking my phone in for warranty for an LCD issue tomorrow .
Let me know how it goes.
I'm on Virgin, but I just want to know if they do make any excuses (and they would love to) so that I could have a good comeback if my phone happened to have the same fate as yours.
Cheers
aditya104 said:
Vodafone FW: HVJH1 –
Vodafone JH1 CSC only:
password: asgardxda
Click to expand...
Click to collapse
Thanks heaps for this.. Do you happen to have the Froyo ROM HVJP3 ?
Forum_Member said:
Thank you so much! As promised I will have to reward you, feel free to PM me your PayPal e-mail address so that I can give you a small token of my appreciation (Or to a cause of your choosing if you prefer.
Thanks again.
Click to expand...
Click to collapse
Check your PM
Need some help, Trying this method to bring my firmware back to 2.1 AUS Voda but after first flashing JM9 with 512 pit, i try to flash ADD_VAU.tar but Odin keeps failing with the following message:
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VODA_AU_CSC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
fix it by running Odin in compatability for XP SP3 and also as an admin. should work
Check this out
Hey guys
I have got my SGS flashed to JM9, however when I flash it to JG4, it fails every time. Would someone be able to tell me exactly what file to load in what section in Odin to make sure I've done it all right?
Chris
Hi all. I am helping a friend restore his phone back to standard to send back to voda.
I am assuming when you say flash jm9 you are talking about this.
http://forum.xda-developers.com/showthread.php?t=802909
also once this is done how to you go about flashing the voda firmware? do you just flash the ADD_VAU.tar in odin? also if this is correct what section do you flash it in. PDA? Sorry bout this just not really sure.
was going to use
Vodafone FW: HVJH1
Do i need to use Vodafone JH1 CSC only as well?
Thanks in advance.
My friend recently bricked his phone by flashing another mobiles ROM.
I can able to boot in to Download mode.
But no recovery mode.
I tried to flash stock firmware through Odin.
But failed with this error:
Code:
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLK2_S5360ODDLK1_S5360DDLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Set PIT file..
<ID:0/019> DO NOT TURN OFF TARGET!!
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> sbl.bin
<ID:0/019> NAND Write Start!!
<ID:0/019> BcmCP.img
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried another firmware buy same problem.
Any solution?
Sent from my Galaxy Nexus using xda app-developers app
Drivers are nt installed...
Disable/uninstall kies ... Download samsung galaxy y drivers from sir doky's thread.. Install them nd try again...
I am sure it'll boot..
** rooting is new for me,
nd i am a noob to root....**
menewtoroot said:
Drivers are nt installed...
Disable/uninstall kies ... Download samsung galaxy y drivers from sir doky's thread.. Install them nd try again...
I am sure it'll boot..
** rooting is new for me,
nd i am a noob to root....**
Click to expand...
Click to collapse
If drivers weren't installed Odin never would have even detected his phone
Anyways try another usb port
PHONE SLOW CLICK ME?
_____________________________________
"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"
TingTingin said:
If drivers weren't installed Odin never would have even detected his phone
Anyways try another usb port
PHONE SLOW CLICK ME?
_____________________________________
"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"
Click to expand...
Click to collapse
This time try with pit file and bootloader.. It will surely boot up
Sent from my GT-S5360 using Tapatalk 2
TingTingin said:
If drivers weren't installed Odin never would have even detected his phone
Anyways try another usb port
PHONE SLOW CLICK ME?
_____________________________________
"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"
Click to expand...
Click to collapse
Have u seen that bricked ur phone..post here thread.???
There were 5-6 people who got the same problem nd there problem was fixed only by installing drivers...
** rooting is new for me,
nd i am a noob to root....**
Lol I got the same problem yesterday! I changed the port, installed new drivers and rebooted my phone 2-3 times then it worked!
menewtoroot said:
Have u seen that bricked ur phone..post here thread.???
There were 5-6 people who got the same problem nd there problem was fixed only by installing drivers...
** rooting is new for me,
nd i am a noob to root....**
Click to expand...
Click to collapse
If drivers are not installed your pc has no way of recognizing your device
And yes I've seen the bricked phones thread and I've commented there quite frequently and never saw someone with Odin recognizing a device without the drivers also this guy has the drivers installed or he would have responded with asking I what the drivers were
PHONE SLOW CLICK ME?
_____________________________________
"No one lives in the slums because they want to. It's like this train. It can't run anywhere except where its rails take it."- Cloud[FFvii]"
I don't think it was a driver problem.
But I tried to reinstall the drivers, same problem, stops at BcmCP.IMG.
Any other solution?
Sent from my Galaxy Nexus using xda app-developers app
Try again.. Or get another package..
Sent from my GT-S5360 using xda app-developers app
I tried two package.
Both had same problem.
Sent from my Galaxy Nexus using xda app-developers app
Try other package of other baseband
ROM EVOLUTION X3
KERNEL HELL FUSION
ALINS JB THEME + EVOLUTION S3 STATUS BAR.
Want To Ask Question? Ask Here
svprm said:
I tried two package.
Both had same problem.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
On Windows I have noticed this bug I would say... Which operating system do you have??
Try this_
Don't move the cable no matter what happens while using Odon you'll easily get a fail
Don't multitask ... This used to give me fail and I was talking about this bug.. Don't know though..
If you get a fail don't reset rather exit and open Odin again
Hope it helps
Sent using xda app-developers app
Maybe this could help..
Try to flash system.img,boot.img first they must install all the boot files into your mob.
Now try to install BcMBoot an totoro.pit file.This is very important in this case.
Then Install csc files or modem files.Now you might get to boot.
Source:My personal experience.
As you get to recovery mode dont forget to wipe cache and data
Ty,
Optimusinc
Just now I tried to flash a custom kernel.
It flashed successfully.
Anybody having system.img ?
Just now I checked,I can't able to extract the Odin package.(tar.md5)
Is this normal?
Sent from my Galaxy Nexus using xda app-developers app
svprm said:
Just now I tried to flash a custom kernel.
It flashed successfully.
Anybody having system.img ?
Just now I checked,I can't able to extract the Odin package.(tar.md5)
Is this normal?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If u mean the the zip file which contains 3 zip file..
Then no...
Its corrupted or uncomplete ..
Download it again
** rooting is new for me,
nd i am a noob to root....**
I extracted the zip,it has only one file ....HOME.tar.md5
Sent from my Galaxy Nexus using xda app-developers app
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...
I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:
K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...
amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.
You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers
Hi there,
This is what I get in Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?
In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Are you trying to Root ur phone or Flash Stock ROM?
Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.
amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?
Please Help i tried flashing stock with odin for ATT Galaxy S5 But it said failed and i dont know what to do, I want to get rid of root, also i tried rebooting and using a root application but they all crash.
Joshua.n said:
Please Help i tried flashing stock with odin for ATT Galaxy S5 But it said failed and i dont know what to do, I want to get rid of root, also i tried rebooting and using a root application but they all crash.
Click to expand...
Click to collapse
Are you using the latest stock firmware?
1monday said:
Are you using the latest stock firmware?
Click to expand...
Click to collapse
Yes I got it from here http://samsung-updates.com/device/?id=SM-G900A
Did you perform a wipe/factory reset in recovery before flashing?
Also, since you tried to flash and failed, are you no longer able to boot normally? If you can, have you tried unrooting via supersu?
1monday said:
Did you perform a wipe/factory reset in recovery before flashing?
Also, since you tried to flash and failed, are you no longer able to boot normally? If you can, have you tried unrooting via supersu?
Click to expand...
Click to collapse
OK I'm fully unrooted from super su, I tried to factory reset but there is a font that is still stuck on and the boot up says custom, please help!
Joshua.n said:
OK I'm fully unrooted from super su, I tried to factory reset but there is a font that is still stuck on and the boot up says custom, please help!
Click to expand...
Click to collapse
Sounds like the Knox counter. The system status displays as custom when Knox detects that you are running a custom ROM. What ROM were you running before you unrooted? By successfully flashing the latest stock firmware, the status should switch to official. However, once the Knox counter is tripped, there is no way to reverse it as of yet. So your device will always report that it was once modified even after a full unroot and flashing back to 100% stock
1monday said:
Sounds like the Knox counter. The system status displays as custom when Knox detects that you are running a custom ROM. What ROM were you running before you unrooted? By successfully flashing the latest stock firmware, the status should switch to official. However, once the Knox counter is tripped, there is no way to reverse it as of yet. So your device will always report that it was once modified even after a full unroot and flashing back to 100% stock
Click to expand...
Click to collapse
But I just want to flash a stock rom to get rid of the font when i tried before with odin on pc it failed Any idea?
Have you tried flashing stock after you did the factory reset?
1monday said:
Have you tried flashing stock after you did the factory reset?
Click to expand...
Click to collapse
No but ill try again, Downloading fresh stock right now
Joshua.n said:
No but ill try again, Downloading fresh stock right now
Click to expand...
Click to collapse
I'll wait to hear results...
Joshua.n said:
But I just want to flash a stock rom to get rid of the font when i tried before with odin on pc it failed Any idea?
Click to expand...
Click to collapse
Lots of ideas, but you aren't good at answering questions. We can't see your phone, we have no magic wands. You will only get good advice if you describe your situation better. We are trying to help you & it would be in your best interests to provide a lot more detail.
What do you mean by "font"?
Paste the exact Odin error message for us
What is your Knox status?
If you don't know, boot to download (Odin) mode & it will say 0x0 or 0x1 on the screen
You linked to a firmware site, not a specific firmware. What is your firmware version?
You didn't answer the question about wiping the cache
Odin can be fussy about USB. Did you try usimg a different USB cable & port?
And ideally, describe step by step how you tried to flash with Odin.
.
1monday said:
I'll wait to hear results...
Click to expand...
Click to collapse
Thank you so much for helping me out btw, I really appreciate it
fffft said:
Lots of ideas, but you aren't good at answering questions. We can't see your phone, we have no magic wands. You will only get good advice if you describe your situation better. We are trying to help you & it would be in your best interests to provide a lot more detail.
What do you mean by "font"?
Paste the exact Odin error message for us
What is your Knox status?
If you don't know, boot to download (Odin) mode & it will say 0x0 or 0x1 on the screen
You linked to a firmware site, not a specific firmware. What is your firmware version?
You didn't answer the question about wiping the cache
Odin can be fussy about USB. Did you try usimg a different USB cable & port?
And ideally, describe step by step how you tried to flash with Odin.
.
Click to expand...
Click to collapse
Font as in the text on the apps on the home screen and words in ceartain apps
If i get another fail i will paste the error
Knox says 0x0
firmware is 4.4.2
how do i wipe the cache?
No but im pretty sure its not the usb port
I put my phone into download mode, Then plugged it in opend odin pc. clicked Ap And Directed path to the .tar.md5 And hit start
Joshua.n said:
Thank you so much for helping me out btw, I really appreciate it
Click to expand...
Click to collapse
No problem man. Although, fffft does make a valid point. Providing a detailed summary of your experience and circumstances would go a long way in helping to solve the issue. I also wondered what you meant by "font", what your Knox counter reads, and what the Odin error message reads
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
Joshua.n said:
Font as in the text on the apps on the home screen and words in ceartain apps
If i get another fail i will paste the error
Knox says 0x0
firmware is 4.4.2
how do i wipe the cache?
No but im pretty sure its not the usb port
Click to expand...
Click to collapse
Wiping the cache can be done in recovery. And although your usb port may be perfectly fine, trying another one solves the problem in some cases so it is worth a try
This is the error
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<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)
This is the font I mean
Joshua.n said:
This is the font I mean
Click to expand...
Click to collapse
Have you simply tried changing the font in Settings?
Settings > Display > Font > Font Style
Joshua.n said:
Font as in the text on the apps on the home screen and words in ceartain apps
If i get another fail i will paste the error
Knox says 0x0
firmware is 4.4.2
how do i wipe the cache?
No but im pretty sure its not the usb port
I put my phone into download mode, Then plugged it in opend odin pc. clicked Ap And Directed path to the .tar.md5 And hit start
Click to expand...
Click to collapse
Thanks for the extra detail. And good to hear that your Knox flag is normal (0x0).
One more question for you.. this is an original ATT (SM-G900A) phone, right? Not something else e.g. a TMobile S5 with ATT firmware? Or an unlocked ATT developer model?
You want to change the system font
Setings menu > Device > Display > Font > Default
(a factory reset + successful flash would also default the font)
To clear the cache, pull your battery out for ten seconds to assure that your phone is off. Then go to the recovery mode (volume up + home + power)
You will see an onscreen menu that will include a choice to wipe your cache
Now about your failed flash. Odin can be picky, but with a little patiemce and a few tries you can get it to flash. The Odin error you had is "Auth" or authorization fail. That could be caused by several things. Make sure that you are flashing the same version firmware as is on the phone if you can. Do not flash an older version.
That error can also be caused by a borderline USB cable or timeout (PC under load or using USB hub for example). Turn off your PC antivirus temporarily.. and don't game or use the computer for anything else during the flash. And maybe try a different cable and USB port just in case.
Here is a good flash method:
Backup any files, etc that are important to you
Then do a system reset (this will delete user files!)
Settings menu > General > Backup & reset > Factory data reset > Reset my device
Then clear the cache from recovery mode (vol up + home + power)
Then reboot to dowload mode
Ensure that you have Auto Reboot and F. Reset checked in Odin,
& try flashing Odin again
If it still fails, then do not close Odin
Remove the phone battery and USB cable for ten seconds, then go to download mode again and try running the flash again. It will almost always work the second time, even though it failed the first time.
There are more aggressive settings that we can use to force a flash if we have to. But try this normal way above first. And a differemt USB cable if you have to.
.
fffft said:
Here is a good flash method:
Backup any files, etc that are important to you
Then do a system reset (this will delete user files!)
Settings menu > General > Backup & reset > Factory data reset > Reset my device
Then clear the cache from recovery mode (vol up + home + power)
Then reboot to dowload mode
Ensure that you have Auto Reboot and F. Reset checked in Odin, & try flashing Odin.
If it fails, then do not close Odin
Remove the phone battery and USB cable for ten seconds, then go to download mode again and try running the flash again. It will almost always work the second time, even though it failed the first time.
.
Click to expand...
Click to collapse
:good: Excellent advice. I wish this was incorporated into an unroot/restore message in the towel root thread. I can not even count how many times I have had to give this method to folks running into issues reverting to stock on the ATT variant.
bailey37821 said:
:good: Excellent advice. I wish this was incorporated into an unroot/restore message in the towel root thread. I can not even count how many times I have had to give this method to folks running into issues reverting to stock on the ATT variant.
Click to expand...
Click to collapse
I have tried this as well, but my baseband is: G900AUCU2ANG3 and the only file I can find on SamMobile and elsewhere is apparently an older version (G900AUCU1ANCE). Thus, my attempt to Odin this back to stock is failing.
Anyone have any thoughts as to how I can proceed? My Odin counter is 0x0, so that's good. However, the status is showing custom and even though I know for sure that I could get the local AT&T device center to reflash it to stock, I'm not sure they would because of the "custom" status.
After sending my Note 5 into a bootloop (first one ever in my history of flashing & rooting 6+ Android devices ... first time for everything but not a record I wanted broken!!) following a "guide" posted by another user here, I figured I'd try to throw something a little clearer out here for all us n00bs looking to rec 'n' root their rockin' phone.
IMPORTANT STUFF BEFORE YOU START!!!
1. These steps worked for the Malaysian variant of the Note 5. *** IT MAY NOT WORK FOR YOU. *** (In theory, it should work for any phone with similar basebands; but then again, it may not.) This guide works perfectly for Note 5s with the following specs (Settings > About device > Software info):
Android version : 6.0.1
Build number: MMB29K.N9208XXU2BPD4
2. I'm just an amateur trying to eke a little more mileage out of what is (by most standards) an already decent phone and because I do have a love (and patience) for tinkering around with this stuff. *** I AM NOT A DEVELOPER, LET ALONE A PROFESSIONAL *** and I take no responsibility for your phone bootlooping, getting bricked, bursting into flames, or infecting patient zero. Fixing your phone will almost always take 100^ longer than the amount of time you spent messing it up in the first place - terradune's law.
3. Samsung has gone out of their way to be extra douchebaggy this time by hard-baking in bloatware that can't be removed/frozen even with TiBu, such as Smart Manager (com.samsung.android.sm, which is not visible in TiBu). If you think that rooting is going to be the answer to all your bloatware woes on the Note 5 (as it once was), this is your only warning that this time, it won't be.
-- BEWARE ALL YE WHO ENTER HERE --
-- LAST CHANCE TO EXIT THIS THREAD --
-- NO SERIOUSLY, I STAYED UP TILL 5AM TRYING TO FIX THE BOOTLOOP AND WAS SOUNDLY REMINDED WHY I'D BEEN SO WARY OF GETTING A PHONE WITH A NON-REMOVABLE BATTERY (my first, to boot ... ) --
Still here? Fine, here goes nothing:
GUIDE:
Part A - Rooting:
1. Backup, backup, backup. I started with a Note 5 fresh out of the box and updated straight away to Marshmallow before rooting, but if you didn't, then there may be apps / data you want to save & carry over. Once you're done with your backups (and have a copy of those backups somewhere safe like on your PC, in case things really go south), go on to Step 2 below.
2. {OPTIONAL STEP} Find and download the stock firmware applicable to your variant at Sammobile so that in case things go wrong, you'll have it close at hand to quickly restore your phone to working order.
3. At this point, if you're on Lollipop (Android version 5.1.1), you can decide if you want to update to Marshmallow. Because, in case you skipped the whole section of "IMPORTANT STUFF" above, this guide is for an N9208 on Marshmallow ONLY.
4. Head over to Chainfire's website and search for "nobleltextc".
5. Check (again) that your Build number matches the Build ID (MMB29K.N9208XXU2BPD4) - if it does, go ahead and hit Download.
6. Boot your phone into download mode (Power off completely, then press and hold Vol Down+Home+Power buttons all at the same time).
7. Extract the zip {CF-Auto-Root-noblelte-nobleltextc-smn9208} that you just downloaded into a folder.
8. In the folder, right-click on "Odin3-v3.10.6" (or whatever Odin version was included) and select "Run as Administrator".
9. Plug your phone in. One of the panels on the left side of the Odin window should light up blue. (If it doesn't, Google for a solution as you have an issue quite unrelated to this guide.)
10. Click on the "AP" button (DON'T TOUCH ANYTHING ELSE!!), navigate to the CF-Auto-Root folder and select "CF-Auto-Root-noblelte-nobleltextc-smn9208.tar".
11. Hit the "Start" button.
12. Wait for phone to reboot (this may take a while).
13. Enjoy rooted goodness.
14. {OPTIONAL STEP} Donate to Chainfire for being The One True Rooter of your Note 5.
Part B - Recovery:
*** If you don't know what recovery is, you probably don't need it. Rooting is often enough for most users' needs so you can stop right here unless you know what you're doing next. ***
1. Noblelte is the applicable TWRP version for the N9208 Marshmallow, so head over here and download {twrp-3.0.2-1-noblelte.img.tar}. There may be a newer version, but this is what's working for me. YMMV.
2. Go back to the CF-Auto-Root folder, right-click on "Odin3-v3.10.6" (or whatever Odin version was included) and select "Run as Administrator".
3. Plug your phone in. One of the panels on the left side of the Odin window should light up blue. (If it doesn't, Google for a solution as you have an issue quite unrelated to this guide.)
4. Click on the "AP" button (DON'T TOUCH ANYTHING ELSE!!), navigate to the folder where you downloaded {twrp-3.0.2-1-noblelte.img.tar} and select that file.
5. Hit the "Start" button.
6. Wait for phone to reboot (this may take a while).
7. Power off and boot into recovery.
8. Wipe cache and Dalvik cache. Reboot.
9. Enjoy your brand-spanking new Team Win recovery.
SOME DON'TS TO FINISH OFF:
1. Many N9208 rooting guides out there advise that you need an app called "CROM services" to unlock your phone, and that it is downloadable from the Galaxy Apps store. If you do a search in the Galaxy Apps store on your phone and come up empty (as I did), YOU (PROBABLY) DON'T NEED IT. Enabling OEM Unlock and USB Debugging in Developer Options is enough to allow you to gain root. Don't go Googling for the CROM services apk (as suggested) as the few sites providing a download link look somewhat dodgy and there is no guarantee that it would be a verified apk download of this app (translated: you might wind up downloading malware).
2. If you've followed this guide exactly, you have SuperSU and you DO NOT need to flash it separately (as some other guides advise). As such, DO NOT flash over SuperSU even if the TWRP recovery offers to do it. SuperSU was already installed when you rooted the phone in the first part of the guide above. (If you'd read the scrolling phone logs while CF-Autoroot was being installed, Chainfire provides the same warning.)
I hope that at least some of you Note 5 owners out there found this guide useful. Toodles!
Excellent tutorial. Works very well for Indian Note 5 Duos too
Great guide! Very detailed. I'm actually downloading from SamMobile the Philippine update for marshmallow. After the download I'll try to root it using this guide of yours and give you an update. Thanks again!
Edit: My build number ends in PE2 and chainfire doesn't have an auto-root for this version. sad.
Akia Azriel said:
Great guide! Very detailed. I'm actually downloading from SamMobile the Philippine update for marshmallow. After the download I'll try to root it using this guide of yours and give you an update. Thanks again!
Edit: My build number ends in PE2 and chainfire doesn't have an auto-root for this version. sad.
Click to expand...
Click to collapse
Nope, chainfire has autoroot for mm firmware
Sent from my SM-N9208 using XDA-Developers mobile app
If the Build Number is not match?
Same is SM-N9208 marshmallow, but with the Build Number end with PE2
Can I use the CF Root file with different Build Number but same Marshmallow, will it causing any problem?
Doesn't seem to work on a BRI device. Here my Odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> cache.img
<ID:0/005> RQT_CLOSE !!
I can confirm that this worked on my Note 5 N9208 Duos with build number MMB29K.N9208XXU2BPE3 (Country: Philippines, Smart). I used the the downloadable file MMB29K.N9208XXU2BPD4 for CF-Auto-Root from the link mentioned above. Thanks! Great job!!!
thank you for this tutorial it worked on my n9208xxu2bpd5. hope i can now fix my battery draining problem.
*update: it fixed my battery draining problem. 0.7-0.9% per hour from 7% per hour.
thanks!
dosada said:
Doesn't seem to work on a BRI device. Here my Odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> cache.img
<ID:0/005> RQT_CLOSE !!
Click to expand...
Click to collapse
It doesnt work because you need the CROM Service apk to unlock your bootloader. I am in the same boat as you
EDIT: Found the file, see my thread: http://forum.xda-developers.com/note5/general/unlocking-bootloader-tiawanese-sm-n9208-t3434961
nursefrail said:
thank you for this tutorial it worked on my n9208xxu2bpd5. hope i can now fix my battery draining problem.
*update: it fixed my battery draining problem. 0.7-0.9% per hour from 7% per hour.
thanks!
Click to expand...
Click to collapse
I have a slightly different build number( ending in PG3) and it solved my draining problem the instant I got root! It's a life saver!
PatelCartel said:
I have a slightly different build number( ending in PG3) and it solved my draining problem the instant I got root! It's a life saver!
Click to expand...
Click to collapse
Hi there.. Urs is PG3 and u using the same nobleltextc file to root?
Also wanna ask this root will increase the knox counter, I survey around forum said that counter could void warranty. (I am new to root).
Thanks.
may i know how to add TWRP without root?
weikit24 said:
Hi there.. Urs is PG3 and u using the same nobleltextc file to root?
Also wanna ask this root will increase the knox counter, I survey around forum said that counter could void warranty. (I am new to root).
Thanks.
Click to expand...
Click to collapse
This is my first time rooting too! And yes I used the root file for the build number which ended in PD4 (nobleltextc) while my phone was PG3. I used it because it had the same model number and the Android version as my Note. And I installed TWRP so I'm not sure how to check the Knox counter but a long time ago before I successfully got root I was trying to install TWRP and I believe it tripped the Knox counter. So if you're trying to preserve your warranty I don't recommend rooting or installing TWRP. I didn't have to worry about warranty so I did it. If you have any further questions just reply to this post. I'll he happy to help if I can!
---------- Post added at 03:36 PM ---------- Previous post was at 03:23 PM ----------
hairulnizams said:
may i know how to add TWRP without root?
Click to expand...
Click to collapse
Hey Hairulnuzams! So to add TWRP without root you use the same tutorial that the original poster of this thread gave at the end of his first post after the rooting instructions. That method does not require root but you will have to download Odin separately since you won't be downloading the root file. A WORD OF CAUTION: DO NOT DO THIS IF YOU DON'T WANT TO TRIP YOUR KNOX COUNTER! AND THERE'S NO GUARANTEE THIS WILL WORK! I tried to do this after checking out many tutorials but it did not work for me. However after getting root it worked perfectly. So it's up to you to take the risk if you choose to.
Here's the XDA Developers page for getting TWRP: http://www.xda-developers.com/how-to-install-twrp/
and here's another non-XDA page for using Odin: http://androiding.how/how-to-install-twrp-recovery-using-odin/ ( I personally turned on OEM Unlock AND USB Debugging)
jyeahhh...thx for this guild method bro..ur the man..i already root my samsung SM N9208 that i follow ur instruction and also download link..be sure all need to read carefully and use searching any forum to not wrong install that can brick phone. I also already brick my phone 1st time that try to root on lollipop..i upgrade to marchmallow and try to root and yeah done and already install TWRP and custom kernel SICKNESS...baterry almost very2 save use SICKNESS kernel.. +1 ur reputation bro..
sorry im from malaysia and this method work on me..
Buildnumber
N9208XXU2BPF1
Android Version
6.0.1
smeth_90 said:
jyeahhh...thx for this guild method bro..ur the man..i already root my samsung SM N9208 that i follow ur instruction and also download link..be sure all need to read carefully and use searching any forum to not wrong install that can brick phone. I also already brick my phone 1st time that try to root on lollipop..i upgrade to marchmallow and try to root and yeah done and already install TWRP and custom kernel SICKNESS...baterry almost very2 save use SICKNESS kernel.. +1 ur reputation bro..
sorry im from malaysia and this method work on me..
Buildnumber
N9208XXU2BPF1
Android Version
6.0.1
Click to expand...
Click to collapse
No problem! I'm glad to help!
PatelCartel said:
No problem! I'm glad to help!
Click to expand...
Click to collapse
Btw thanks again bro..hurmm i need suggestion bro..seems after i root my device and done with custom recovery install also kernal install at my device..when i try to play my game KRITIKA name..the game detect illigel program hack detected?can u advice how to hide root or any command can edit?because i already done with super su,hide root,set to prompt and clear play store cache,reboot and play the game but not success..i not want loose root with success this method to safe battery life with MM android..thanks in advance..
Sent from my SM-N9208 using Tapatalk
I would love to help but unfortunately I'm not familiar with how to do that. However someone is bound to reply to your post and if not you should post this question in another forum on XDA more suited to this question. Meanwhile you can check out this web page: http://www.makeuseof.com/tag/trick-apps-android-rooted/ I haven't tried any of these methods so I'm not responsible if they don't work or damage your phone. I recommend you research more into these methods and be careful! I hope I helped!
PatelCartel said:
I would love to help but unfortunately I'm not familiar with how to do that. However someone is bound to reply to your post and if not you should post this question in another forum on XDA more suited to this question. Meanwhile you can check out this web page: http://www.makeuseof.com/tag/trick-apps-android-rooted/ I haven't tried any of these methods so I'm not responsible if they don't work or damage your phone. I recommend you research more into these methods and be careful! I hope I helped!
Click to expand...
Click to collapse
Wow thanks in advance..alright i will try to more research..[emoji3]
Sent from my SM-N9208 using Tapatalk
I cant root this always happens:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flash new firmware bro..but wait what firmware ver you using?i also have this problem before..
Sent from my SM-N9208 using Tapatalk
---------- Post added at 02:32 AM ---------- Previous post was at 02:27 AM ----------
smeth_90 said:
Flash new firmware bro..but wait what firmware ver you using?i also have this problem before..
Sent from my SM-N9208 using Tapatalk
Click to expand...
Click to collapse
Which firmware you using MM or lolipop?dont download wrong root package..because this file CF autoroot is two file for MM and lolipop ver firmware..also read carefully OP(orginal post) thread..dont forget to enable OEM LOCK AND USB DEBUGGING..[emoji106]
Sent from my SM-N9208 using Tapatalk