I have been trying to root my galaxy note pro 12.2 that I have received for work (in China so Chinese ROM), simply so I can install the Play Store, I am following the below procedure:
http://androidcentral.us/2014/03/root-samsung-galaxy-note-pro-12-2/
I have the wifi version so I am using the SM-900 CF-root.
Kies is installed, debugging mode set on USB.
But I keep getting the error in Odin:
complete(write) operation failed
I am suspecting its something to do with the connection via USB, I have some problems with transferring files to the pad. I am unable to check the "media device" option under USB connection settings, Kies has been able to restore my pad after the flash fails but it doesn't find my device, it has suggested I use Smart Switch but I dont agree to Samsung collection my personal information when i connect the pad to my PC so I cant use that. I had already downloaded the Samsung drivers for USB but I have never really had much success with the samsung drivers to be honest (had an S3 for several years).
All I want to do is run Play store and transfer files via USB
I am also using windows 7.
Your help will be appreciated.
Try uinstalling the usb drivers and reinstall. Do the same with kies, turn off all Anti virus as well.
Have you tried Towelroot?
Sent from my SAMSUNG-SM-P907A using XDA Premium HD app
* Does you've enabled USB-Debug in the developer settings ?
* Does you've kicked Kies out of Memory, before you try it ?
* Does you've boot your device into Fastboot, before you try Auto-root ?
* If Odin is crashed during the prozess, use Odin 3.10.x ?
* Does you've enabled USB-Debug in the developer settings ?
* Does you've kicked Kies out of Memory, before you try it ?
* Does you've boot your device into Fastboot, before you try Auto-root ?
* If Odin is crashed during the prozess, use Odin 3.10.x ?
Click to expand...
Click to collapse
* Second time I tried yes, this was the obvious cause for my first failure but still got the same error on the 2nd try
* No, how to do this?
* Fastboot? Auto root?
* Odin isnt crashing its just failing to write, I have tried 3.07 and 3.09, both with the same result.
I have managed to flash an Australian rom onto the tablet which has solved my play store problem which was the main reason for rooting in the first place, I may try to root this one in the future but I really dont have the knowledge about this to be confident, plus I have already voided the warranty on a brand new tablet just to get the Play store working so I am not too keen on messing with things any further.
Thanks for the suggestions anyway.
What does you see on the screen from the tablet till the Problem occurred?
What does you see on the screen from the tablet till the Problem occurred?
Click to expand...
Click to collapse
During the flash at some point the screen on the tablet would have yellow and white vertical strips across the screen, then I would see failed in Odin.
After that The screen would just say "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". From there I would have to power off then quickly get into download mode or the tablet will just turn on again with the above message. I recovered once through Kies, then I flashed the Australian ROM with Odin and that solved my problem, but haven't tried to root since.
Related
Hi everyone,
I have currently some big issue with my GT-N8010.
My custom rom wasn't running very well so I decided to reset my tablet and go back to a new fresh installation.
I downloaded the latest firmware of the tablet on sammobile and started to update it with Odin PC, but in the middle of the transfert I got an error and now my tablet is stuck on the "Firmware upgrade encoutered an issue. Please select recovery mode in Kies & try again.".
I have no idea how to fix it! And I can't go back to download mode anymore. On top of that, my tablet seems not to be recognize by my computer (I tried to install Kies and the samsung usb driver several times but it keeps saying that's the driver is not ok)...
Can someone help me please ?
Thank you in advance!
What custom rom did you had ? 4.4.2 or 4.1.2 ?
KoRoZIV said:
What custom rom did you had ? 4.4.2 or 4.1.2 ?
Click to expand...
Click to collapse
It was a 4.1.2 (HD Revolution) and I tried to flash with odin the N8010XXUCMK2_N8010XSACNA2_XSA
First uninstall kies and all usb drivers. Restart your computer.
If you can get in download mode (power+volume down then volume up when asked) :
Install some drivers from the sticky topics here on xda. Download the firmware again from another location if possible. Use a different usb port.
If you can't get in download mode, you have to try with kies. I never had success whit it, and i really need it. But it says that n8010 does not support initializing or something like that. Maybe someone else can help with kies.
Sent from my GT-N8010 using Tapatalk
I don't know where it comes from...
I tried everything, uninstall/reinstall Kies/Usb driver, put a VM with Win7 (As I am under Windows 8.1), put Win7 in dual boot to maybe fix the compatibility issue but nothing seems to work! And of course I don't have any other computer to use...
That's maybe the reason the tablet get broken as I used to use Odin on another PC and I didn't check if the usb driver was installed on this one??
I just know that Odin recognized my tablet so I was able to launch the installation of the new firmware.
I feel really bad...Hope the tablet is not definitly dead!
Faulty USB cable perhaps ?
Sent from my GT-N8010 using Tapatalk
Ok so I went to a Samsung store and they told me that I have to send my tablet to the repair center in the country where I bought the device.
It's a big issue for me as I am now living in Australia and my tablet has been bought in France.
On top of that the guy from Samsung explained me that now it's normal if my tablet is not any longer recognize by my computer...
I heard about JTAG, I don't have any idea about the subject but may it fix my problem?
Does someone know how samsung is able to fix the tablet, so I may fix it myself instead of sending to them...?
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
kitchenspoon said:
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
Click to expand...
Click to collapse
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
erica_renee said:
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
Click to expand...
Click to collapse
Hi, cheers for the response,
I have tried all of what you have said but unfortunately no PC will see my device, not even an "unrecognized device". I have access to android system reocvery <e3> and Download mode (Odin) but the pc just won't recognized, tried new leads and so forth, nothing.
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Use the latest version of Odin
kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
try diffrent USB ports on the computer and diffrent signal cords
kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
Did you enable usb debugging? Oh my bad, scratch that, try connecting your phone to your pc b4 you open Odin (using the latest Odin and run as admin)
kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
hi! i have the same problem , did you find a solution please? thanks
That secure download enable thing is normal mine has the same thing. Your phone is not connecting for whatever other reason
Try flashing exact stock firmware with odin.
SMG920I
POWERED BY INSUFFICIENT RAM
TUNED BY TEAM PINGPONG
DRIVEN BY KFORKAI
darksimo said:
hi! i have the same problem , did you find a solution please? thanks
Click to expand...
Click to collapse
Yeah i got it flashed. Turned out that i used an old odin also you have to get a firmware which has the same csc or one that it compatible with your device. Info on samsung csc can be found on the net, look for multi csc codes if you wanna change to software from another carrier.
Sent from my VS980 4G using XDA Free mobile app
Before you start flashing always disable reactivation lock. Othervise flashing may fail.
ODIN won't detect Galaxy S5 G906K [KT]
Hello All,
I've been having the same issues as people in this thread but have been unable to come up with a solution so far. I've tried to the whole battery trick which sometimes works with other Samsung devices but have been unable to solve this problem. It seems that ODIN just won't detect the 906K while it is on the recovery mode window. However if the phone is booted normally ODIN sees its fine.
i.imgur.com/boK57io.jpg
Can anyone provide some assistance?
Thanks in advance..
ODIN Version: Odin3_v3.10.7
Device Model: Samsung Galaxy S5 SM-G906K [kt]
Resolved.
nano-dev said:
Hello All,
I've been having the same issues as people in this thread but have been unable to come up with a solution so far. I've tried to the whole battery trick which sometimes works with other Samsung devices but have been unable to solve this problem. It seems that ODIN just won't detect the 906K while it is on the recovery mode window. However if the phone is booted normally ODIN sees its fine.
i.imgur.com/boK57io.jpg
Can anyone provide some assistance?
Thanks in advance..
ODIN Version: Odin3_v3.10.7
Device Model: Samsung Galaxy S5 SM-G906K [kt]
Click to expand...
Click to collapse
So after an entire day of investigation and logging I've figured out that this was an issue related to a carrier update by Olleh (KT). For anyone who runs into the same problem on the SM-G906K I recommend KingRoot as a means of getting started for root. CWM/TWRP are also methods that I tested with success.
I hope this helps someone who has the same problem down the road.
kingroot not working!
nano-dev said:
So after an entire day of investigation and logging I've figured out that this was an issue related to a carrier update by Olleh (KT). For anyone who runs into the same problem on the SM-G906K I recommend KingRoot as a means of getting started for root. CWM/TWRP are also methods that I tested with success.
I hope this helps someone who has the same problem down the road.
Click to expand...
Click to collapse
.................................................................................................................................................................................................
kingroot was working when they released V.4.5.0 but now not working anymore :crying:
sorry for my bad English
kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
try using box tools like z3x to see if problem would be solved
Update: i fix it by unmouting checking and mounting back the phone...weird a part or idk had to be not well attached.
Hello
I was trying to root Samsung galaxy grand prime G530H. But it has stucked in 'downloading...'
Secure Download : Enable in blue
Why can't I unlock the bootloader on FZ? There is just no such option in Dev Mode.
Hi there, have Samsung sm-G935F..stuck at Samsung logo..tried 2 flash file available from z3x team, shell. When using Odin to flash the programme freezing, when using Samsung tool to flash, it's reading the device and file but it's gerring error. Any advice on this?
Feyaad said:
Hi there, have Samsung sm-G935F..stuck at Samsung logo..tried 2 flash file available from z3x team, shell. When using Odin to flash the programme freezing, when using Samsung tool to flash, it's reading the device and file but it's gerring error. Any advice on this?
Click to expand...
Click to collapse
You could always try the S7 edge specific forums.
Not being sarcastic
root the chines root
i have sm-n9006 i cant root my phone
also have the secure download enadled in blue
any help ??
my phone is a chinses version ... which doesnt have the play store
Hello
Do you have your bootloader blocked, the new version of firmware enabled this option, you need to go to development options and enable the option of OEM, and that's it, you can flash whatever you want
I installed some cyanogen rom on my tablet and now everytime I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile odi n(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically its useless and I do now know what do to... Please, someone just help me out here >.< :crying:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
ashkineeeeee said:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
Click to expand...
Click to collapse
Yes I tried to enable debugging still did not work... I can not flash it because it doesn't get recognized by any computer.
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
john99ap said:
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
Click to expand...
Click to collapse
I tried already the root app simply keeps trashing no matter what-
dionex2k said:
I installed some CyanogenMod on my tablet and now every time I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have Samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile Odin(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically it's useless and I do now know what do to... Please, someone just help me out here >.<: crying:
Click to expand...
Click to collapse
Basically, because what you get is a CyanogenMod, which does not relate to any piece of the Samsung Driver. All you need is Google USB Driver which supports almost all Android phones in the world. A thread in XDA talks about 15 seconds Google USB Driver Program for Windows which can be found somewhere in the XDA thread world.
And more here, for the problem about root access, have you tried installing a SuperSu flashable zip through your recovery yet? That should work a lot. Then, if you update your firmware using recovery without using an OTA update manually, apps may not be compatible and will crash. Reinstalling all your crashing apps from the Google Play Store should help.
Finally, if you want to update your phone through recovery, not an OTA-received ROM, please make sure not to install many apps on it, because when it crashes, you can do nothing but to reinstall it. although, all add-ons (Such as GApps, SuperSu, Xposed Framework, et cetera) need to be reinstalled so you don't lose them during a manual update, so don't delete your flashable add-on zips once you installed, you might need them forever.
Recovery is like a mobile version of Odin, use a Desktop version of Odin so you can get yourself out. A tutorial might be found somewhere on YouTube.
Hope you have a good day,
Shippo
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
dionex2k said:
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
Click to expand...
Click to collapse
There is a tool called Forget Windows Use Linux in which all necessary drivers come preinstalled and your tab should be recognised from your pc with no problem if it's a driver issue. Try it
Try this slide down from upper left of the screen. If the window indicates charge only, click on it. It should then offer file transfer. In order to get adb to see the tablet turn on deveper options and enable USB debug mode. Hopefully that works for you.
hello
there is something very very very very very old which is called cf autoroot
every needed is in the zip use it
regards
Edit: It seemed as it solved itself, look in the replies for details
So i have had my gs7 rooted for a year or longer. Yesterday i rebooted my phone and got the error message "Custom binary blocked by FRP lock". Sadly, when i enter download mode and plug it into a pc with odin installed, it is not recognised. Odin does not say anything about a phone plugged in, and windows says the usb is not recognized.
What i think have caused this:
I downloaded an app that allowed me to record internal audio
I turned off developer options, and my stupid ass did not realize that is where oem unlock is located.
What i have tried:
Resetting to factory settings (from recovery mode)
Deleting cache (from recovery mode)
Using odin, but odin does not even recognize my phone
Tried using another computer with odin
tbh, looking at the other posts, i think i messed up. I dont want to send it in for repairing because i will have to pay a lot of money. I have tried sending it in for repairing a while ago. Then my problem was that i could not call with it, but they wanted me to pay the price for a new phone to repair my old phone, since i had rooted it. I did not accept it so i got my phone back, and managed to fix the issue myself. I hope i manage to fix the issue this time aswell.
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
10krlan said:
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
Click to expand...
Click to collapse
Please pay attention to guides when messing about with your phone, OEM and Debugg are critical to being able to modify.
Look here for a solution.
https://www.mobikin.com/android-backup/computer-does-not-recognize-android-phone.html
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
SOLVED!
The issue fixed itself, im not sure what i did. I was suddenly able to connect my phone to odin. Just incase someone reads this with the same problem. This is what i did: installed smart switch and rebooted my computer. Uninstalled and reinstalled samsung usb drivers.
Before i did those things the issue was still there, i was ready to use smart switch, but i tried odin one last time and it worked. Now samsung pass tells me my phone is rooted, even though it is not (my root dissapeared after resetting my phone), its not that big of an issue, just thought id let you know