Related
Hello, I was reading some of the root methods posted in the dev thread. I was wondering if any of those methods (being AT&T) will work on the Bell SGS III ?
I being a I727R user, found a one-click-method, that allowed me to root that phone when I did it. It was one batch file, which installed root and SU which was really nice.
I have not played around with ODIN too much and did not want to harm it. I know the SGS3 just released so things do take time. I was wondering if there will be a one click method to rooting the device, and in turn installing CWM.
Any suggestions would be great. Thank you
From what I've been heard and seen these days, I am 99% sure that all the Rogers/Bell/Telus/AT&T are the same model, which is I747M. So I assume that the rooting method is interchangeable.
I know the rooting method works on Rogers' one for sure.. I am going to do it tonight probably and report back.
noahattic said:
From what I've been heard and seen these days, I am 99% sure that all the Rogers/Bell/Telus/AT&T are the same model, which is I747M. So I assume that the rooting method is interchangeable.
I know the rooting method works on Rogers' one for sure.. I am going to do it tonight probably and report back.
Click to expand...
Click to collapse
Much appreciated, please let me know how it goes, as I have 2 (BELL) I747's here to root and install recovery. I would be interested in what method is used to get these going.
Thanks
EDIT: I found this too...
http://galaxys3root.com/galaxy-s3-root/how-to-root-sprint-galaxy-s3-sph-l710/
perhaps this is all you need to do ? I am not sure
This worked for me.
http://forum.xda-developers.com/showthread.php?t=1726960
you don't need to do the restore steps as we haven't pooched our devices.
fully compatible I'm on Telus. Use the new non counter trip methods in the att development forum
Sent from my SGH-I747M using Tapatalk 2
Woolios said:
fully compatible I'm on Telus. Use the new non counter trip methods in the att development forum
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
nice wanna link that, I saw y2 going to try that just verifying that we don't need to bother with the fixboot.tar
Have you actually used the non-counter-trip root method on your phone? I just got a Bell phone and so far Odin fails each time I try.
Instructions:
Root Method Starts Here.
** Get Odin like mentioned Above
** Make Sure you have all Samsung Drivers installed.
** Reboot your phone into download mode
* Hold down Volume Down, Home and then power until Warning!! message is displayed
* Press Volume Up to continue.
** Your phone should now be in download mode and displaying a green Android and say Downloading. If it is not, power off your phone by holding down the power button and then try to get into Download mode again. Do NOT progress until you have done so.
** Go into the folder you extracted Odin3 into and run Odin3 v3.04.exe
** Connect your phone to your computer via USB
** In Odin, the COM box all the way to the left should turn blue and it should say Added!! in the Message area.
** Click on PDA and in the Open window that pops up navigate to and open the Tar With CWM from below file you downloaded earlier
** Verify that Auto Reboot and F. Reset Time are checked
** Click Start. Once the process is completed you device should automatically reboot and there will be a green PASS! box in the upper left of the window. You can then close Odin.
** Power off your device and boot into Recovery mode
* To boot into Recovery mode: Hold down Volume Up, Home and then the Power button until you are in Recovery (it should say CWM-based Recovery at the top of the screen)
**. Install CMW_SuperUser_v3.07.zip that you copied onto your internal memory
* Navigating ClockWorkMod Recovery: Use the Volume Up and Down arrow keys to change the highlighted option and the home key to select an option. The Back softkey works, but will not be lit and will take you back one screen.
Installing a zip:
* Select "Install zip from sdcard" (Yes, I know it's on the internal storage.)
* Select "Choose zip from sdcard"
* Select the zip you want to install; in this case CWM_SuperUser_v3.0.7.zip
* Select "Yes" to begin installing
**. Once the process has completed use the Back arrow to get back to the main recovery screen (remember, it works, but it's not lit) and select "reboot system now." Once your device boots up you should now be 'Rooted,' but there's still a few more things to be done
15. Install BusyBox. There are actually several ways to do this, but the BusyBox app in the Google Play Market is quick and easy. Install it, grant it SuperUser permissions and it'll walk you through the rest and advise you when to update.
16. Update your Binaries.
* Open the Superuser app
* Get into settings (the wrench icon in the upper right of the screen)
* Select Su binary under the General section towards the bottom of the list
* Select Update
**.Your device is now rooted and all set.
---------------------------------------------------------------------------
That is all there is to root, as link above stated.... no need to flash 'fixboot.tar'
unibombz said:
That is all there is to root, as link above stated.... no need to flash 'fixboot.tar'
Click to expand...
Click to collapse
This method trips the counter, does it not?
frelnik said:
This method trips the counter, does it not?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1739426
read here for no trip. This is based on the AT&T model, Since I am using bell I did not bother, and followed the other method. I couldn't care if I tripped the counter... never have sent a phone in for warranty myself.
Since mine is i747M, I chose not to use the AT&T img just for my own reasons.
I just flashed cwm via odin, and SU via cwm
unibombz said:
http://forum.xda-developers.com/showthread.php?t=1739426
read here for no trip. This is based on the AT&T model, Since I am using bell I did not bother, and followed the other method. I couldn't care if I tripped the counter... never have sent a phone in for warranty myself.
Since mine is i747M, I chose not to use the AT&T img just for my own reasons.
I just flashed cwm via odin, and SU via cwm
Click to expand...
Click to collapse
It should work fine but ofcorse nothing is perfect.
Once Bell's firmware is availiable on samsungs servers I plan on injecting a copy with SuperSU root and will make it availiable to others in an odin flashable file that wont trip the counter for those that dont know how to do it themselfs.
Also the non trip method of recovery is pretty stright forward as ive done simular things like this too on bootloaders on my SGS2 I will test and report my findings and give instructions for others once I can get my hands on Bells firmware.
Sent from my SGH-I747M
Has anybody confirmed that the AT&T no-trip root works on a Bell S3? My friend said it should since the model numbers are the same so same hardware.
Also dbzgod, is there any eta on when the stock Bell firmware is available?
seaskimmer said:
Has anybody confirmed that the AT&T no-trip root works on a Bell S3? My friend said it should since the model numbers are the same so same hardware.
Also dbzgod, is there any eta on when the stock Bell firmware is available?
Click to expand...
Click to collapse
I havnt try'd myself but others have and said flashing the AT&T one works since the hardware is the exact same.
I have no clue. Bell has yet to post the firmware on Samsung kies server still waiting :/
Sent from my SGH-I747M
Alright thanks! I think I will give the AT&T version a try. I am a noob with Android after just making the switch to Android from iOS.
With the root, I will be able to uninstall any AT&T pre-included software right?
I can confirm it works, but it trip the counter, rooted, SU too, oh, well, it won't be to long until a fix for the counter is out.
hey guys,
I am fairly new to all of this so I am just wondering - what do we have to wait for before a bell specific root can be done?
softkey said:
I can confirm it works, but it trip the counter, rooted, SU too, oh, well, it won't be to long until a fix for the counter is out.
Click to expand...
Click to collapse
Just to clarify, the no-trip-counter method here http://forum.xda-developers.com/showthread.php?t=1739426 and it worked, but still tripped the counter?
Thank you [/QUOTE]
Have any of yous tried the triangle away app? It resets the trip counter to 0 and puts the custom binary download to official. I've used it a bunch no problems
Sent from my SGH-I747M using xda premium
this method works just fine:
http://forum.xda-developers.com/showthread.php?t=1739426
Forgive me for asking this question but I can't find a way to root this. Yes, I tried searching but it can't seem to find anything about this particular model.
It's the LTE version of the Tab 3 7.0 if anyone is wondering.
Thanks in advance.
I tried using http://www.kingoapp.com/ to root my SM-T215 and for some reason it did not work for me. Others have tried and had success.
Have you tried that yet? http://forum.xda-developers.com/showthread.php?t=2473747
SM-T215 Rooting
Am a noob and still learning but if u would like to try my method,i be happy that i could help u.No flashing of roms as my only intention of rooting is to get rid of those unwanted apps and boosting the speed/battery life.
SM-T215 Tab 3 7.0 LTE (8GB)
Rooting: Only Kingoapp works. (Provide root with supersu but no custom recovery)
Custom Recovery for backup/restore: Only TWRP (SM-T217S) flash through ODIN works.CWM gets bootloops.
No custom roms are found compatible/stable for the T215 so far but xPosed framework is an option.
amie2109 said:
Am a noob and still learning but if u would like to try my method,i be happy that i could help u.No flashing of roms as my only intention of rooting is to get rid of those unwanted apps and boosting the speed/battery life.
SM-T215 Tab 3 7.0 LTE (8GB)
Rooting: Only Kingoapp works. (Provide root with supersu but no custom recovery)
Custom Recovery for backup/restore: Only TWRP (SM-T217S) flash through ODIN works.CWM gets bootloops.
No custom roms are found compatible/stable for the T215 so far but xPosed framework is an option.
Click to expand...
Click to collapse
tried kingoapp, framaroot, zroot, and afew more but still cant get my tab to be rooted.
just bought this tab 3 7.0 SM T215 to replace my outdated modded galaxy apollo cm7 alpha 9 with the hope that i can explore more on modded roms on a better handset.
if only there is ROOTING for sm-t215 at the least..
8GB filled with bloatware is making my device suffocating and annoying.
sigh ~
crazyVato said:
tried kingoapp, framaroot, zroot, and afew more but still cant get my tab to be rooted.
just bought this tab 3 7.0 SM T215 to replace my outdated modded galaxy apollo cm7 alpha 9 with the hope that i can explore more on modded roms on a better handset.
if only there is ROOTING for sm-t215 at the least..
8GB filled with bloatware is making my device suffocating and annoying.
sigh ~
Click to expand...
Click to collapse
I have a Tab 3 7.0 LTE (SM T215) edition too, and i every rooting method doesnt work.. HELPP someone
Zetomono said:
I have a Tab 3 7.0 LTE (SM T215) edition too, and i every rooting method doesnt work.. HELPP someone
Click to expand...
Click to collapse
Flash or install universal root. If that does not work install vroot sure that this will have rooted your phone. You can then uninstall remplasarla by SuperSU smoothly and the other
Andromeda 90 said:
Flash or install universal root. If that does not work install vroot sure that this will have rooted your phone. You can then uninstall remplasarla by SuperSU smoothly and the other
Click to expand...
Click to collapse
Do you have the links to the methods that you've just suggested?
crazyVato said:
Do you have the links to the methods that you've just suggested?
Click to expand...
Click to collapse
All right.
1. Install this apk. https://mega.co.nz/#!bQwAlJiT!H04MbX-_Hp0o2sYo7RCaFG904_x_2sxLW0rTTsZlLSM
2. Before running the application, you must tick the boxes, usb debugging, allow mock locations, all in development options, and be connected to the internet.
3.-That done, you open the application, and click where it says open das, root, now there waiting to do their work, if all goes well, your phone will reboot.
4.-If you ever leave a message with Chinese letters before or after you restart your phone, give right click option. Always be on that, that is to give super user permissions.
5. as either root, replace the Chinese application SuperSU, qui this. https://mega.co.nz/#!CVx1BLSQ!g1lLufWuy7GzqxuEgYK2MSHFrqS6UGvelfvD24V_aFs
still not working
i tried that and doesn't work. installed the apk click root but still
How I root my SM-T215 (Singapore) at 4.2.2
Excuse me for being a Noob...
To enable USB Debugging is the same as Note 3. Tap on About Phone and the Baseband 7 times (I Think) as almost weeks ago when I tried.
Enable USB Debugging (tick) and all in this paragraph first before trying this website (namely Allow Mock Locations, etc) :
www . mgyun. com / vfroot
Download (立即下载) and Install the software into Desktop.
Need not turn off Tab 3, just connect and wait for the software to detect.
Then it will do its work to root it.
Tab 3 will reboot at least once, and when asked for ADB access, authorize it.
I managed to root my SM-T215 via this method without any knowledge of any programming knowledge.
I hope this helps. Have not checked on Knox yet but glad that I can remove some apps which slows down the Tab 3 LTE
does not work on my SM-T215.
Any other option for rooting SM T215.
Tried various root versions - none works.
www.mgyun.com download the root application and install it in ur pc, once u've launch the app and connect ur device, the app will automatically detect the model of ur device. just click on root.. once rooted, uninstall the chinese version of superuser but TAKE NOTE you need to keep the kinguser tool in your device or else no rooted is being done. once everything is installed, user rootchecker to double confirm that ur device has been rooted. it is not a full root, but it'll do for now. good luck
Sent from my SM-T215 using XDA Premium 4 mobile app
jaspore said:
Excuse me for being a Noob...
To enable USB Debugging is the same as Note 3. Tap on About Phone and the Baseband 7 times (I Think) as almost weeks ago when I tried.
Enable USB Debugging (tick) and all in this paragraph first before trying this website (namely Allow Mock Locations, etc) :
www . mgyun. com / vfroot
Download (立即下载) and Install the software into Desktop.
Need not turn off Tab 3, just connect and wait for the software to detect.
Then it will do its work to root it.
Tab 3 will reboot at least once, and when asked for ADB access, authorize it.
I managed to root my SM-T215 via this method without any knowledge of any programming knowledge.
I hope this helps. Have not checked on Knox yet but glad that I can remove some apps which slows down the Tab 3 LTE
Click to expand...
Click to collapse
samsung has finally released kitkat firmware for SM-T215, the update had factory resetted my device to stock. before i proceed with your www .mgyun. com / vfroot method, will your method still work? (just to be safe)
crazyVato said:
samsung has finally released kitkat firmware for SM-T215, the update had factory resetted my device to stock. before i proceed with your www .mgyun. com / vfroot method, will your method still work? (just to be safe)
Click to expand...
Click to collapse
Sorry for this late reply.
When I had rooted T215, my priority is remove bloatware which includes Software updates. Knowing that Tab 3 hardware will be stretched, I don't want any updates as it will make Tab 3 sluggish.
Thus I am still at 4.2.2. and staying it this way for now.
I am not at 4.4.2+ , so it is still strong with the root.
jaspore said:
Sorry for this late reply.
When I had rooted T215, my priority is remove bloatware which includes Software updates. Knowing that Tab 3 hardware will be stretched, I don't want any updates as it will make Tab 3 sluggish.
Thus I am still at 4.2.2. and staying it this way for now.
I am not at 4.4.2+ , so it is still strong with the root.
Click to expand...
Click to collapse
i've forgotten how i rooted my sm-t215 kitkat. If i'm not wrong, you only need to install/flash only the CWM recovery into your phone, and once you've successfully install/flash CWM recovery, go into recovery and choose reboot now. there will be an option for you to install superuser. choose that and your phone will be auto rooted.
here is the link.
http://forum.xda-developers.com/show....php?t=2674649
do it at your own risk, i won't be responsible for anything in case something goes wrong as this only based on my memory.
GOOD LUCK
how could i enable lte option
even it is 4glte .this particular option is missing in network mode
*Updated 3/2017 to include same for LL updated SM-T707A*
For anyone else who has the SM-T707A (tab s 8.4" AT&T LTE version) -
Issues with this tablet:
1. Upgrading to Lollipop - seems that without an actual AT&T sim card installed, you're not going to be able to upgrade from 4.4.2 (cannot download the OTA update, and I haven't been able to find a download of the firmware online ANYWHERE).
2. Locked Bootloader - possible to carrier unlock for any compatible GMS carrier (I'm using mine with a T-mobile sim card), but seems that there is no way to unlock the bootloader/install a custom recovery.
(**NOTE: DO NOT TRY AND INSTALL TWRP OR USE THE UNLOCK/RECOVERY UTILITIES FOR THE SM-T705 ... while it seems like they would effectively be the same devices, both have exynos cpu and identical specs...I have tested out the odin-flashable methods from the development section that are for the SM-T705, and THESE WILL SOFT BRICK YOUR DEVICE. A HUGE ISSUE, SINCE THE STOCK FIRMWARE IS REALLY REALLY REALLY DIFFICULT TO FIND..)
SILVER LININGS:
1. Even if you have to stay on 4.4.2, you should be able to root with Kingo Root.
2. If you are rooted with Kingo on 4.4.2, and want to switch to SuperSU app instead of the KingoRoot one, you can try this (worked for me):
**Update 3/2017 - this will also work on LL updated SM-T707A
1. Install SuperSU app through google play store (regular install...NOT an update via recovery). This means you will now have TWO Superuser apps installed on your phone. Only the Kingo Superuser will have the authority to grant SU permissions at this point. Now open SuperSU and make sure it is installed. It should ask you to update the SU binary (you won't be able to yet, but make sure you get the prompt).
2. Download a terminal emulator app, or enable usb debugging in dev options, connect phone to pc, and open an adb shell.
3. Follow the instructions for switching to SuperSU available on android forums (search for "bakageta" +" supersu to kingo" +"android forums" ).
4. Download @bakageta's zip file and put on your sd card. Then open your terminal emulator or adb shell as root (type "su" + press enter) and run the first command: "# ./step0.sh" Remember to leave your terminal emulator open when you move on to the next step (same goes for your adb window).
5. Uninstall the Kingo Root apps (your tablet will then ~likely~ auto-reboot, closing the terminal emulator...DON'T PANIC, THIS IS OK.)
6. After your tablet boots back up, you should still have root**, but now your Superuser app will be SuperSU.
**UPDATE (3/2017, running the LL updated SM-T707A) If you are doing this on LL, you may need to also run the subsequent bakageta script, "# ./step1.sh" after the initial reboot to get SuperSU root access.
--> If anyone here knows how I can make a backup of the firmware I currently have installed (rooted stock 5.0.1) that can be used as a restore image via odin, please let me know! I'd gladly upload the file for anyone who is having trouble unbricking their devices, since the stock files are so insanely difficult to find for this particular variant of the tab s.
--Thanks to @Kingxteam
--Thanks to @bakageta for the alcatel scripts
see PM
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
PAragao said:
chixvicious, did you ever managed to get those backups? I got a soft-bricked 707A and i also cant find the stock roms anywhere
Click to expand...
Click to collapse
still not allowed to post links, but files can be found at dropbox dot com/s/mjobo2sfa53x2dv/T707AUCU1ANH9_T707AATT1ANH9_4.4.4_USA_4Files.rar?dl=0
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
SuperlativeB said:
updated for anyone else playing with these / whom it may concern if they ever google up this old ass device , I confirm on 4.4.2 707a I have successfully root with kingo and them using SUPERSUME apk I have swtiched it fully to SuperSU . Also using online nandroid backup with the 805 LTE variant patch I was able to get a full backup. I think I'm in decent shape for experimentation as I'm on the lowest order firmware and hopefully , not sure but hopefully if anything goes badly i can just update to newer firmware. Going to attempt using SAFESTRAP recovery next
Click to expand...
Click to collapse
I still have 2 of these and am constantly disappointed at how much development there is for every other variants but this one.
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
pm me if you still have that!
SuperlativeB said:
Okay so I can confirm Galaxy Tab S 707a 8.4" LTE can be rooted in 4.4.2 with Kingo. It's goofy like kingo is , but it worked unfortunately that's not quite enough for myself as six axis never communicates w. Stock annnnd tmobile sucks and are being jerks can't use it without special plan so I'm putting my WiFi board back in. If any one wants rooted 4.4.2 unlocked motherboard......useless wasted tech here, all thanks to software restrictions.
Click to expand...
Click to collapse
PM me if you still have that! I randomly have an extra (shattered screen) Tab S 8.4" without a motherboard, and would play around with trying to unlock the bootloader on it if I had a mobo to put in it!
Thanks!
SuperlativeB said:
I got safestrap in , was able to reboot and see it but no luck due to se enforcing , I tried everything to get it to permissive but no luck. I went back to my WiFi model ha , oh well. Have to look for a 705 that has unlocked boot / better firmware
Click to expand...
Click to collapse
I could help get this permissive on kitkat, but not LL or MM.
ashyx said:
I could help get this permissive on kitkat, but not LL or MM.
Click to expand...
Click to collapse
What are your thoughts ? It's def still kitkat , but I've tried init'd stuff and all sorts crap. If i got permissive i could possibly get safestrap to boot and then try out roms intended for the regular LTE variant. It is just kind of useless for me as T-mobile it's device Id as tablet so they lock it out then if i just wanted to use it WiFi the TouchWiz stuff kills remote controls like six axis and stuff. Id prob use it daily if i could get past device id pickups / safestrap a way into better rom
anyone have the 6.0.1 firmware?
I was trying to root/custom rom/etc in a hurry and I was interrupted a million times, so I screwed up. SM-N910v. I started out on kitkat, 4.4.1. I tried this guide: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
I odin N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5. That upgraded me lollipop 5.5.1. I then follow a guide similiar to this: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Its not the exact one, but there is several guides that are the same. I temporary rooted with kingoroot, installed TWRP. One of the guides said not to let it boot normally, so I freaked out and made sure I didn't do that. I booted back into twrp. Using this guide: https://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I can't remember or find the exact guide I was on... But I flashed these files in the following order:
BETA-SuperSU-v2.71-20160331103524.zip
Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip (this was really dumb)
cm-13.0-20160919-UNOFFICIAL-trltevzw.zip
I tried to boot, I left it on for atleast 30 mins, and the clockworkmod logo kept animating abnormally fast.
I then installed N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 again (... doh ...).
Now it bootloops.... so I said.. 'ok, maybe I just need my TWRP recovery back'. Tried to install TWRP and fail....
I can boot into safe mode fine, but not normal mode. The problem with safe mode is you can't install apps.
I've tried factory reset, wipe cache, dalvik, etc etc. Nothing. I've also tried a different firmware I believe as well.. I am lost...
Current Android Info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2CPD1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
The information above indicates that I am still in this version: N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Ok so.. I just odin this file N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
Same story, I can boot into normal mode, but not safe mode.
I check my info:
5.1.1
security patch level: 2015-12-01
baseband version: N910VVRU2BPA1
Kernel version: 3.10.40 Jan 20 2016
Build Number: LMY47X.N910VVRU2BPA1
Factory reseting now... and seeing if that fixes my problem... nope... same bootloop problem...
my thinking is... if I undo "samsung_unlock_n4-fix" and that would fix my bootloop. If thats true..... I guess my biggest question is: if the boot loader is unlocked, then why can't I flash TWRP like I was able to the first time??
I appologize, I will be unaviable for the next 5 or 6 days..... any help would be much appreciated!
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
UmbrellaTakedown said:
I followed Max Lee's guide on youtube for rooting/unlocking the bootloader I recommend downloading the files he has linked, just ensure that your phone is the SM-N910V the hardest part or more time consuming part is getting kingo root to get you that temporary root needed to unlock your bootloader/root phone. Kingo root is very unstable and your phone will freeze/restart many times, You definitely need a spare sd card, at least a 2GB from my experience and patience, set aside a few hours because your follow through is crucial. If all goes well you will be able to install TWRP. I hope this helps. Tip, if you decide to follow his method, the file titled 'samsung_unlock_n4-2' you need to rename it to say 'samsung_unlock_n4-fix' good luck!
Click to expand...
Click to collapse
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
TouchOdeath said:
I appreciate your post. However I don't think you quite understand whats going on.
https://galaxynote4root.com/cwmtwrp-recovery/
His site specifically states: "Verizon SM-N910V unless you have a developer’s edition phone as retail version come with locked bootloaders meaning you cannot install regular CWM or TWRP!!!"
It also shows that comment in the video. I definitely DO NOT have the developers edition.
In summary: I flashed the firmware that has the bootloader unlock vulnerability->Installed twrp->Installed CWM->Installed Firmware with bootloader vulnerability, which replaced everything I did. Now it seems like the bootloader is re-locked, and I can't boot into normal mode, which means I can't run kingo again. I can't flash TWRP, the only things I can do are: adb sideload, odin, boot any 5.1.1 in safe mode.
Click to expand...
Click to collapse
I did not have a developers edition either, I have retail, this method makes your phone into the developer edition. This method is designed for verizons note 4. So what i'm saying is, I followed his method using a retail note 4 branded verizon and this exploit makes it into a developers edition so you may install twrp and roms. You are able to odin flash stock firmware for marshmallow and then downgrade to 5.1 to run max's method.
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
TouchOdeath said:
Ok so.. I managed to get everything working... so I'm happy. Thank you UmbrellaTakedown for invoking thought and thank you for replying, your the only person who replied, so much appreciated!
1. Boot into safe mode
2. Install app by: adb install c:\kingoroot.apk
3. At this point, its installed but the launcher needs to be refreshed for the icon to show up. I don't know how to refresh the launcher without a reboot.. so...
4. Find the kingoroot package name: adb shell 'pm list packages -f'
5. In my case it said: package:/data/app/com.kingo.root-1/base.apk=com.kingo.root So your answer is: com.kingo.root
6. Now in order to launch kingo, you need to find the activity of the package: adb shell pm dump PACKAGE_NAME | grep -A 1 MAIN
7. Start the activity: adb shell am start -n com.kingo.root/com.kingoapp.root.MainActivity
From here I was able to temp root through kingo, and run samsung_unlock_n4-fix. This time I had to only run samsung_unlock_n4-fix once. After that, TWRP installed no problem (where before it would not).
Update:
I am now officially on Jasmine ROM marshmallow. I had to copy the jasmine folder to /data/media/0/TWRP/BACKUPS/xxxx/jasmine
xxxx= you get that from adb devices
Then simply do a restore, after restore, restore the partial firmware file (it has to be done in that order or else it won't work)
Click to expand...
Click to collapse
Just an FYI, you need to run the sasmung_unlock_n4 application twice. The first time, it will write your eMMC CID to the correct one, and the second time you execute, it will write the CID signature/blob to the bootloader - completing the unlock process. Glad to see you got it working.
Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be unlocked because I read in other forums that you only have to unlock it if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
It's an English forum
I hope i am right but translated from german to english using google translate.
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked without problems.
Now I have two questions:
1. Must the bootloader be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the floor and only give apps root rights. I also want to keep getting OTA updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" on End, as with my model number). Now to my question: Can I use it or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards
Shademaster639
Lol, just recognized that the forum is english. I didn't think about this as I wrote the entry. The translation @spawnlives gave fits my question. Sorry for my mistake!
EDIT: I've edited my entry now to english.
Shademaster639 said:
Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
Click to expand...
Click to collapse
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Shademaster639 said:
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Click to expand...
Click to collapse
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
spawnlives said:
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
Click to expand...
Click to collapse
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Shademaster639 said:
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Click to expand...
Click to collapse
Basically yes. Stock firmware will generally replace any modifications done to the phone.
spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
Thanks.
Appreciate the insight and the clarification.
Hopefully @Shademaster639 will pay attention to your post.
O/T: should say thanks also to the exploits made even though I don't have a ( US ) snapdragon variant on other devices.
elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
I have unlocked my bootloader now since I had to do it nevertheless. I couldn't use cf-auto-root since there was no modified firmware for my device (sm-a505fn) listed on firmware.mobi. I tried rooting my phone using the latest version of magisk (v20.x) now, got random bootloops though. So I flashed my device back to stock with the original samsung firmware.
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Shademaster639 said:
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Click to expand...
Click to collapse
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Some more info from here
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Click to expand...
Click to collapse
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo: https://www.youtube.com/watch?v=zqbu7jCmeMY
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Shademaster639 said:
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo:
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Click to expand...
Click to collapse
KG state - prenormal
and / or
RMM state - prenornal
Problems with modifying phone.
KG state - checking
RMM state - normal or disappeared
Allows modifying phone.
For want of better terminology they are separate keys to the same lock.
There are plenty of sites regarding this:
https://chimeratool.com/fr/docs/sam...onitoring-and-management-rmm-unlock-functions