Model number: SM-N950F /DS (Exynos, I think. Correct me if I'm wrong.)
Serial number: R58JB5K68TP
Android version: 8.0.0
I tried using KingoRoot as it had worked before on my Lenovo A328 but it failed to root this one (Even the PC version).
So, how should I go about manually rooting my phone?
Also, how much risk is there in attempting this? (Especially for a beginner like me)
Do not use k9ngo root or kingroot, it is unsafe, as for rooting,, there are several threads regarding this, your model is exynos, so there is no problem finding a tutorial, read carefully, download everything as per imstructions, completely charge your phone, use the original cable, if you follow the instructions to the letter, all should be fine, some times things do not work out as intended, but, again, there are ways to fix them, so, also look for threads regarding this occurences, do not be afraid
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-note8-efs-backup-t3677038
Related
Hi still a newbie so please bare with me.
Have tried s hard reset no joy because it's saying that my P9 your device has failed verification and may not work properly.
This was after updating to 7.0 which worked for about 10 mins then this happened
Any help much appreciated thanks
Dc phonix is good software for all the problems
1. Are you or have you ever been rooted? if yes then see question 2. If no then you have bricked your phone somehow, need to restore using one of the methods described in the various threads in the forum. Download official image, use dload method etc.
2. Does the phone boot to Android? If yes then that message is normal. If no then see question 3
3. You need to restore the original boot image and relock your bootloader. If you don't know how to do either or what any of that means then refer to the alternative answer in question 1 and then stop messing with your phone until you learn how to do literally everything with it using the forum.
I realise that sounds harsh, but it's the truth. Too many people bricking perfectly good phones because they don't care to read or learn before they act.
My suggestion would be to rollback and flash b136 on MM then update.. but ensure u are on C432
Enviado desde mi EVA-L09 mediante Tapatalk
Hello,
I want to root my Huawei P9.
Information about the handy:
EMUI 5.0.1
EVA-L09
B397
CPU: Kirin 955
Bootloader is unlocked.
I tested a lot of things but it still dont work.
I hope, I got help here.
For help to finish, I want to pay a little bit as a bonus
https://theunlockr.com/2016/12/06/root-huawei-p9-p9-plus/ have you tried this?
You have omitted important part, your cust, is it c432 or what. I.e. full name of your build as it shows in About Phone, like EVA-L09c432b397 or what.
Forget advices about rooting P9 Plus (?!), you can easily brick your phone
There is search on XDA, you can find excellent topics about rooting (this one is for SuperSU, there are others for Magisk)
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Read the guide at the beginning and posts from last e.g. month at the end (up to date with the latest builds like yours). There is search and you can search through the topic, to find details applicable for your build, apps you need the root for, etc
And post your further questions there - e.g. that topic has 570+ posts, probably tens of experienced hackers who are watching - to the other side topics like this one get opened 5-10 new every day, and chance that somebody who is knowledagbe will spot it and dare to answer (every day sinilar questions are repeted by new users, who will answer to each and every of them, every day) are negligable ;(
PS: The guide above covers only the last part, flashing the correct ZIP for rooting. Before that you need to unlock bootloader and install TWRP for EMUI 5.x - search on XDA to find the guides about
Thank you, it still works now
Hi! I have completely F***cked up my USA SM-T813. First post, so im sorry if i get posting etiquette wrong.
##TL;DR I turned my tablet into an asian one with firmware and idk how to change it back##
So, since about march of this year (2018), I had a galaxy tab s2 (sm-t813) rooted with SuperSu. I have just recently heard about Magisk and really wanted to switch. well, from what i saw on switching, i had to (obviously) uninstall SU and install magisk. while i was reading, i read that i had to do some abd bull***t and other crap. well, i guess i did that wrong, which soft bricked my tablet. I managed to fix the soft brick, but now my tablet has the firmware of an asian one. i have no clue what i need to do to fix this. I have downloaded the correct (fingers crossed) firmware, but odin wont let me put it in. It stops at "connection *something*", which when i looked up probably means i need to install the drivers for this firmware. The problem is, i dont know what nationality this firmware is.
The file i downloaded was T713ZCU2BRA4_T713CHN2BRA4_CHN
the CHN at the end made me assume it was Chinese, but when i installed the chinese drivers, it still didnt work.
if anyone could help me get this fixed and (possibly) help me get magisk installed, that would be amazing.
thanks in advance!
Coltonious
P.S. the firmware change unrooted my phone. so supersu is gone. thats a plus i guess!
##TL;DR I turned my tablet into an asian one with firmware and idk how to change it back##
What now? T713 or T813? The chinese firmware you mention is for 713 and not the other one. USA you say? Well that should be Country code XAR: https://www.sammobile.com/firmwares/galaxy-tab-s2/SM-T713/XAR/ OR https://www.sammobile.com/firmwares/galaxy-tab-s2/SM-T813/XAR/ load the most recent of these fitting to your device. And yes, CHN is China. Odin drivers are not country specific. You get one working and all is fine. If you get these errors you mention then the driver is not working or is the wrong one for another device. I use the same Odin driver for all my devices I have and had from Samsung. Some more detailed error description would be useful though. If you have problems loading with reasonable speed from sammobile: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 try this tool.
I don't know if it matters but you stated you have the sm-T813 and you are trying to install firmware for the sm-T713.
grncherry said:
I don't know if it matters but you stated you have the sm-T813 and you are trying to install firmware for the sm-T713.
Click to expand...
Click to collapse
Yeah it matters quite much ^^
Specs:
T-Mobile-locked Samsung Galaxy Note 8 - N950U
Baseband version: N950USQU1AQI5
Build number: NMF26X.N950USQU1AQI5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
I recently purchased the above Note8. I have bookmarked a root method[1], but it requires bootloader v7. If I'm decoding my phone's baseband version correctly, its on v1, so probably won't work with this method.
I'm wondering, if I let it do an OTA update to Oreo (Android v8), will it hit the requisite v7 bootloader so I can, according to the instructions on that page, flash it back to a pre-rooted Nougat? ( If there's a better method than what I'm planning to follow, please advise. I'm all ears! )
[1] www (dot) the custom droid (dot) com/root-galaxy-note-8-snapdragon-n950u/
Just stay on firmware you are on and use the old Samfail root method
Sent from my SM-N960U using Tapatalk
Thanks, butchieboy. Would this be the process for this phone?
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
Yes [emoji106] The thread is closed but you should still be able to get the files you need. If not I still have them and when I find time I could send them to you with Mega...but you still should be able to get them from the thread.
Sent from my SM-N975U using Tapatalk
The links are still good in that post, but I'm a bit concerned about them. The SamFAIL downloads for the v1 bootloader are designated for N950F ("for the Samsung Galaxy Note 8(SM-N950F)"), which is the European firmware. Mine's N950U (US).
Does this SamFAIL root actually rely on the European firmware? How does that impact the Snapdragon? I thought the European phones/firmwares were designed for a different processor.
No dice
I followed the instructions on that post to the letter. The first flash didn't cause my phone to reboot (as the instructions say it will), so I rebooted it myself and got it back to the "Emergency" screen, whereupon I did the part #2 flash. It reset that time, and now it's stuck in an "Installing update" loop with the Android icon (with a "warning" icon above it) just appearing over and over.
What do I do now? Do I have to try and flash a stock ROM and see if I can recover the phone? Or is there something I can do from here that will help it continue?
Boot to recovery and factory reset
Sent from my SM-N975U using Tapatalk
And the angels sang!
Since I couldn't get the damn thing to shut off anyway, I left the phone in the "Installing" loop overnight (since that was the least risk of screen burn). This morning, the device was dead because the battery had drained to zero, so I put it on the charger. I left it there for only about 30 minutes so it had just enough juice for me to try and get it into recovery mode.
I must not have held the buttons correctly, because it went into a normal boot instead of going into Download or Recovery. I let it go, intending to just try again once it entered the "Installing" loop, and LO! the "SAMSUNG" logo came up. It hadn't done that before. I put the phone aside and didn't touch anything while the logo pulsated, and it eventaully dropped into the setup screen! :victory: Of course, it almost immediately shut down because the battery hadn't charged enough, but I think it somehow reset/corrected itself when it lost all power overnight.
I left it on the charger and monitored the level. It stopped increasing at 80%, which is the expected behavior with this solution. I powered it on again, and everything is as described in the rooting post (except that SuperSU did not prompt me multiple times to update it).
So, at this point, I'd say I'm good. Looks like it reset itself, and the root succeeded. Hopefully anybody coming along later with this same issue on the Note 8 will see this post.
Thanks again, butchieboy.
Hello,
First of all I'm new at XDA Forum's, so I'm not sure to be in the right thread, if so, let me know! I'm new too in mobiles stuff, so forgive me if I write something basic or absurd.
I'm trying to unlock the bootloader of a Samsung Galaxy Tab S2 (SM-T813, 2016) Android 7 (Nougat) unsuccessfully.
I've tried number of tuto's (Android & Samsung dedicated) without success: most of them appeal to fastboot command's included in the 'Android SDK Platform Tools' with adb but Samsung devices don't understand the fastboot commands. The recommended process tells to reboot in bootloader mode which actually is the Download mode at Samsung without any possibility to dialogue with the tablet and when i type in the windows command line any fastboot command, it gets stucked waiting for the device to answer. The only sane tuto that i found was on XDA Forum 'https://forum.xda-developers.com/t/...ng-galaxy-tab-s2-stock-to-android-10.4206561/' that describes on this particular device the process to upgrade the firmware from Android 7 to Android 10 i.e. from a device with a stock firmware which is my case, the only thing is that I don't want at the moment to upgrade the firmware but 'only' to unlock the bootloader of this tablet!
Could anyone who experienced this novice issue on this device or Samsung devices help me solve it? Thanks in advance for your answers.
Eric
Hi,
No one to help me in that matter?
How to unlock this Samsung device without using the fastbot commands, which Samsung devices don't understand?
Do you think that the process described in 'https://forum.xda-developers.com/t/...ng-galaxy-tab-s2-stock-to-android-10.4206561/' will also unlock the bootloader?
Rgds
Eric
edevoucoux said:
Hi,
No one to help me in that matter?
How to unlock this Samsung device without using the fastbot commands, which Samsung devices don't understand?
Do you think that the process described in 'https://forum.xda-developers.com/t/...ng-galaxy-tab-s2-stock-to-android-10.4206561/' will also unlock the bootloader?
Rgds
Eric
Click to expand...
Click to collapse
I am trying to root my samsung device too but it has been a headache too. I cannot even unlock bootloader, which is apparently necessary to root my device. I have a samsung s20 fe snapdragon with android 11. Have you found that option in "developers options"? It should be one of the first options.
Hello Space_Bear_77,
Though it is not the same device, I'll try to help you, I mean It's my own device and my own experiment.
Well, I have had a very productive talk on another forum: Phonandroid 'https://www.phonandroid.com/forum/t...sm-t813-gts210vewifi-t813xxs2btj4-xef.213632/' and learned by myself too.
Actually, it is not necessary to go through the phase unlock bootloader on Samsung devices, It is done when you flash a custom recovery, the custom firmware and the rooting App. Have a look at these links: 'https://forum.xda-developers.com/t/...ng-galaxy-tab-s2-stock-to-android-10.4206561/' and 'https://forum.xda-developers.com/t/rom-unofficial-10-lineageos-17-1-t713-t719-t813-t819.4070161/'.
Moreover, as you will see looking at these links, you'll have to take care at 2 characteristics of the custom firmware you'll choose to flash:
Choose a custom firmware that fit with your device. As an example, in my case, It is an SM-T813, gts210vewifi, T813XXS2BSG1, CSC = XEF (French CSC), you'll easily found lists of all CSC on the web and found which are yours related to your country.
I don't know the status of your device: did you already try to flash It or not? Anyway, you can use 'DevCheck' available on the Google Play Store, this App will give you all the characteristics I've listed above on a rooted device or not.
Regarding the 'developers options', again, I don't know Android 11 but on my device, one have just to authorize 'Déboguage USB' and 'Déverrouillage OEM'. Sorry, I'm French and I don't know how It is called in English but I think you'll find It easily.
Hoping that this will help you, don't hesitate to let me know and ask another questions or give me more precisions, I'll try to help.
Rgds
Eric