Database Users

r800at (Locked Bootloader) root

Afternoon all,
As much as I hate to ruin the business of the fellows who have the ability to unlock the bootloader for you, I wanted to let the community know that I have discovered an exploit which, when run with the phone in USB connect, allowed the phone to be rooted... in about 30 seconds.
I do not take credit for the exploit, however I have hosted it.
goo.gl/Nc1iC
TO USE:
•Extract to the Desktop of your PC.
•Enable USB Debugging on the Phone (Settings►Application►Developement►USB Debugging)
•Connect your phone via USB.
•(Make sure you have Java installed on the PC)
•Click runme.bat.​
As in all things, I do not take credit for anything you choose to do to your system. But as an AT&T customer, I was heartbroken that I couldn't get the bloatware off of MY system without paying someone to unlock my bootloader.
Please be careful with your phone! And happy gaming!
​

Not that I am knocking this way of rooting but we had root before this without having to unlock the bootloader. I used zergrush before by itself and through flashtool to get root. Haven't unlocked my bootloader.
Sent from my R800a using Tapatalk

twilightphe0nix said:
Afternoon all,
As much as I hate to ruin the business of the fellows who have the ability to unlock the bootloader for you, I wanted to let the community know that I have discovered an exploit which, when run with the phone in USB connect, allowed the phone to be rooted... in about 30 seconds.
I do not take credit for the exploit, however I have hosted it.
goo.gl/Nc1iC
TO USE:
•Extract to the Desktop of your PC.
•Enable USB Debugging on the Phone (Settings►Application►Developement►USB Debugging)
•Connect your phone via USB.
•(Make sure you have Java installed on the PC)
•Click runme.bat.​
As in all things, I do not take credit for anything you choose to do to your system. But as an AT&T customer, I was heartbroken that I couldn't get the bloatware off of MY system without paying someone to unlock my bootloader.
Please be careful with your phone! And happy gaming!
​
Click to expand...
Click to collapse
Rooting doesn't cost squat. And you don't need to unlock the bootloader to remove bloatware. You only need to do that to run custom kernels.
Sent from my R800x using XDA

twilightphe0nix said:
Afternoon all,
As much as I hate to ruin the business of the fellows who have the ability to unlock the bootloader for you, I wanted to let the community know that I have discovered an exploit which, when run with the phone in USB connect, allowed the phone to be rooted... in about 30 seconds.
I do not take credit for the exploit, however I have hosted it.
goo.gl/Nc1iC
TO USE:
•Extract to the Desktop of your PC.
•Enable USB Debugging on the Phone (Settings►Application►Developement►USB Debugging)
•Connect your phone via USB.
•(Make sure you have Java installed on the PC)
•Click runme.bat.​
As in all things, I do not take credit for anything you choose to do to your system. But as an AT&T customer, I was heartbroken that I couldn't get the bloatware off of MY system without paying someone to unlock my bootloader.
Please be careful with your phone! And happy gaming!
​
Click to expand...
Click to collapse
I would not trust this guy.
If you want root on your R800at, I would HIGHLY suggest using the SuperOneClick Root Method, or zergRush method.
Sent from R800x

Zergrush with superoneclick couldnt be easier. Anyone examined the fikes he 'graciously' shared?
Sent from my R800a using XDA

Wow, repost ftw. This is Doom's script that he posted over in the zergRush root thread. Moreover, it's 1.0, and I'm pretty sure the thread has atleast 3.0 directly from Doom.
@OP - Just change your post to say that you've reposted DoomLoRD's script (congrats, buddy, you posted a 5 month old file) (or erase OP, and say "I'm sorry I'm such a tool, I should learn to read and search before I repost files." )
Sent from my R800x using Tapatalk

Motochopper

I tried rooting with motochopper. Installed the drivers, ran the run.bat, got the following:
press enter to root phone
press any key to continue
(pressed enter)
waiting for device
daemon not running, starting
daemon started successfully
device found
pushing exploit
4463 KB/s <1283460 bytes in .0.200s>
4496 KB/s <1867568 bytes in 0.405s>
4940 KB/s <1578585 bytes in 0.312s>
pkg: /data/local/tmp/Superuser.apk
Success
Rooting phone
this may take a few minutes
Failure
Cleaning up
Exploit complete. Press enter to reboot and exit.
Press any key to continue
(pressed enter)
superuser is installed on the phone, but the phone's not rooted. Tried this on 2 separate computers running Win7 Home 64bit.
Does anyone have any ideas?

Why don't you use QBKings how to root video. Its very simple to.do.
Sent from my SPH-L720 using Tapatalk 2

UnlikelyKiller said:
I tried rooting with motochopper. Installed the drivers, ran the run.bat, got the following:
press enter to root phone
press any key to continue
(pressed enter)
waiting for device
daemon not running, starting
daemon started successfully
device found
pushing exploit
4463 KB/s <1283460 bytes in .0.200s>
4496 KB/s <1867568 bytes in 0.405s>
4940 KB/s <1578585 bytes in 0.312s>
pkg: /data/local/tmp/Superuser.apk
Success
Rooting phone
this may take a few minutes
Failure
Cleaning up
Exploit complete. Press enter to reboot and exit.
Press any key to continue
(pressed enter)
superuser is installed on the phone, but the phone's not rooted. Tried this on 2 separate computers running Win7 Home 64bit.
Does anyone have any ideas?
Click to expand...
Click to collapse
Are you on MDC or MDL firmware/software? You can check this by going to Settings/More/About Device and look at your baseband and software. If the last 3 letters are MDC, motochopper will work for root but if it reads MDL, go here....http://forum.xda-developers.com/showthread.php?t=2277480

Chain fire's CFAutoroot is the way to go. I wouldn't even bother with Motochopper.
Sent from my SPH-L720 using Tapatalk 2

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Foulwx said:
Chain fire's CFAutoroot is the way to go. I wouldn't even bother with Motochopper.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
1+

travisw0204 said:
Are you on MDC or MDL firmware/software? You can check this by going to Settings/More/About Device and look at your baseband and software. If the last 3 letters are MDC, motochopper will work for root but if it reads MDL, go here....http://forum.xda-developers.com/showthread.php?t=2277480
Click to expand...
Click to collapse
It is MDL, I will follow the thread you suggested, thank you.

UnlikelyKiller said:
It is MDL, I will follow the thread you suggested, thank you.
Click to expand...
Click to collapse
No problem. Good luck

[Q] root Canadian i337m with Mac Help!

Has anybody else come across this while rooting their Canadian i337m while using motochopper on a Mac?
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
After rebooting the superuser icon appears but it is not rooted. I've searched a while and have not found a solution. Anybody else solved this, or have an alternative method to root using a Mac?

Rooting phone
cory.l.83 said:
Has anybody else come across this while rooting their Canadian i337m while using motochopper on a Mac?
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
After rebooting the superuser icon appears but it is not rooted. I've searched a while and have not found a solution. Anybody else solved this, or have an alternative method to root using a Mac?
Click to expand...
Click to collapse
Hi,
Look at this link. It should help you.
http://forum.xda-developers.com/showthread.php?t=2314494

[Q] Rooting my Nexus 7 with Wugfesh Toolkit

Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?

TheRicolaa10 said:
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
Click to expand...
Click to collapse
Did you go through all the driver steps? Even after the correct drivers were installed, I had to put mine into bootloader mode manually, then root.

I already tried that, with no succes.

I also had to uncheck MTP and install the drivers while in the webcam mode. Then my device would show up in the toolkit as ADB connected but status would be red. At that point is when I put it into bootloader manually. Running Windows XP, btw.

Krulm said:
and install the drivers while in the webcam mode. .
Click to expand...
Click to collapse
I will try to uncheck MTP. But what do you mean by ''In webcam mode''?

Mine gives two options (4.2.1). Media Device(MTP) or Camera(PTP), whereas I am forced to select one or the other. In PTP mode it shows up as a Webcam when connected to Win XP.

I did the rooting process. Bit it looks like it's failed. When I start up SuperSU it said: "No SU binary found".
Can I do this rooting process again?

It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4

iresq said:
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
I did it 2 times, I had no errors when I did the rooting process. I don't know where it goes wrong actually.
Is it possible to delete SuperSU?

iresq said:
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
Download http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Use Wugs toolkit to flash to device. Worked for me.

TheRicolaa10 said:
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
Click to expand...
Click to collapse
Hey, just turn off mpt connection, turn on USB debugging and ptp connection and viola. Might have to delete any former files from nexus 7 on computer first though. Then just use cmd or command line to confirm adb, type adb devices on the command line and hopefully it should identify your device (it doesn't have to be your actual device name, it can be with random numbers.) Those steps worked for me so it should work for you to, rooting it then takes 10 minutes if I can remember.
Sent from my Nexus 7 using XDA Premium HD app

I did this last night and I had to put mine into ptp. Then adb would recognize it. After I got unlocked before I could root I had to re delete everything and then it recognized it.
Hope that helps.
Sent from my Nexus 7 using xda app-developers app

[HOWTO] Converting your Retail Note 4 to a Developer Edition Note 4

This guide will walk you through the process of converting your Retail Note 4 to a Developer Edition Note 4. This means you have an unlocked boot loader and you are free to do what you wish with your device.
Requirements:
Retail Note 4 (Verizon)
Computer (PC, Linux or Window)
USB Cable
Samsung USB Drivers (If you are on Windows)
SD Card (Recommend a small one that you do not mind storing away for later)
ADB (Android Debug Bridge)
Root (Either Temp or Perm, that will not be explained here)
Samsung Unlock file (Creators Thread)
Steps:
- Verify you have an ADB connection to your device and you have root.
Connect your phone and launch ADB in either command prompt or terminal (Depending on your OS).
Type the following command to view the currently connected devices:
Code:
adb devices
You should see a list of devices. If not, verify USB Debug Mode is enabled on your phone.
-Copying the unlock file to your phone
After you have downloaded the file from ryanbg's thread (samsung_unlock_n4-2) we need to copy it to the device. You will want to make sure your current directory is the directory that the file you downloaded is in.
Time to push the file to the phone, run the below command:
Code:
adb push samsung_unlock_n4-2 /data/local/tmp/
-Connect to your phone
Type the following command:
Code:
adb shell
You are now in in a shell through ADB on your phone.
Elevate your permissions by entering:
Code:
su
You may get a confirmation on your phone for requesting root access. Be sure to grant ADB permission.
-Change Directory
Go to the directory we copied our files to
Code:
cd /data/local/tmp/
-CHMOD and CHOWN the unlock file
This allows us to actually execute the file. Execute the below commands
Code:
chmod 777 samsung_unlock_n4-2
Code:
chown root.root samsung_unlock_n4-2
-Time to execute
Running the below command will generate a warning and a requirement to enter yes or no. Read the warning carefully before continuing:
Code:
./samsung_unlock_n4-2
At this point you will see a few thing similar to this:
Code:
[+] CID at boot time is/was: 1501xxxxxxxxxxxxxxxxxxxxxxxxx
[+] device not yet dev CID, now changing to dev CID
[+] programming new CID 150100523231384d4100657e54fc1200
[+] success! powering off device, power back on and verify CID
[+] then run this binary again to finish the process
As binary states, your phone CID is changing is going to reboot.
Before turning your phone back on, be sure the SD card you are okay with formatting is inserted into the phone.
Once your phone comes back online, launch terminal, ADB shell, obtain root access, and change directories. Now launch the unlock binary again:
Code:
./samsung_unlock_n4-2
You will see the same warning and you will need to enter yes or no again. Once you enter yes, you should see something like this.
Code:
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Keep the SD card in a safe place. If for some reason you ever break your phone, you can possibly use the loaders on this card to fix it.
Power your phone up in download mode (VOL-DOWN + HOME + POWER). Your phone should now show Developer mode. If this is not the case, you either did something wrong or your phone is not a Verizon Note 4

i can say it is really appreciated that we have this ability but this blunt "we wont tell you how to at least temp root it" thing is kind of messed up because a lot of people have no idea where to go to find the right temp root for this phone. We have always needed root yet now we have unlocked bootloader which again is appreciated, but a little help with the latter would be nice.

KingVekxin said:
i can say it is really appreciated that we have this ability but this blunt "we wont tell you how to at least temp root it" thing is kind of messed up because a lot of people have no idea where to go to find the right temp root for this phone. We have always needed root yet now we have unlocked bootloader which again is appreciated, but a little help with the latter would be nice.
Click to expand...
Click to collapse
To be honest if a person cannot find KingRoot, they should not be using this method. This mindset is shared by a lot of people on XDA. This is not a simple click and go type unlock, it requires someone to get down and dirty to get things done.

chriskader said:
To be honest if a person cannot find KingRoot, they should not be using this method. This mindset is shared by a lot of people on XDA. This is not a simple click and go type unlock, it requires someone to get down and dirty to get things done.
Click to expand...
Click to collapse
Trust me it wouldnt be the first down and dirty with rooting for me lol. But i have found it and will see if it goes alright and then i will try to link others to it to make it a little easier, at least with that part

can someone who has not done this, download and install brick bug app from Play store and post of screen shot of it running. I wanna check if Note 4 come with a emmc other than Samsung.

Well I did everything as stared and now it's stuck in a bootloop.
I wiped everything also. It does say mode developer though.
Couldn't get some help guys?

I can already hear the laughter
I have successfully completed these steps. However, I want to know is there any difference between this and an actual developer edition at this point?

I'm really kind of in trouble here. It only boots up in download mode and in recovery. It says mode developer but it just bootloop. Kies won't connect to it.
Is it possible to Odin back?
Thank you.

edjahman said:
I'm really kind of in trouble here. It only boots up in download mode and in recovery. It says mode developer but it just bootloop. Kies won't connect to it.
Is it possible to Odin back?
Thank you.
Click to expand...
Click to collapse
remove battery and sd card. Then insert battery and reboot.

KingVekxin said:
i can say it is really appreciated that we have this ability but this blunt "we wont tell you how to at least temp root it" thing is kind of messed up because a lot of people have no idea where to go to find the right temp root for this phone. We have always needed root yet now we have unlocked bootloader which again is appreciated, but a little help with the latter would be nice.
Click to expand...
Click to collapse
To be fair, I don't even own this device. The exploit happened to apply to the Note 4 and we decided to make it compatible for you guys. That's why I can't really help you with it. Make sense?
edjahman said:
I'm really kind of in trouble here. It only boots up in download mode and in recovery. It says mode developer but it just bootloop. Kies won't connect to it.
Is it possible to Odin back?
Thank you.
Click to expand...
Click to collapse
Try pulling your battery and removing your SD card. Then try to wipe cache in recovery. Typically, you would unlock your bootloader if you wanted to flash custom ROMs/kernels. If that doesn't work, feel free to PM me and I'll help you as best I can.

Phew. Ty guys. Somehow I overlooked that lol.
It's fine now. I really appreciate it.
Edjahman
---------- Post added at 04:04 PM ---------- Previous post was at 03:59 PM ----------
So I assume we treat this like a Dev edition Note 4 then as long as it says developer mode in recovery?
I'd hate to ODIN TWRP or CF Autoroot and brick it for real.
Thanks

Just ODIN TWRP and flash supersu in twrp.

I'm unclear about the directory part. If someone could clarify that would be great

Will this work on the latest Verizon OTA? LMY47X.N910VVRU2BPA1 (Android 5.1.1)
I'm currently on BOG5 - Safe Upgrade with the BOAF Bootloaders (hsbadr). Should I flash back to 4.4.4 and allow all of the OTA updates or is there a point to where this won't work?
Suggestion to OP: Update Step 1 on the Requirements to include which Android version we need to be on for this to work. I "assume" 4.4.4, because I've heard that KingRoot only works on 4.4.4. Please confirm this. Thank you.
EDIT: Also, Step 5 of the Requirements section, I assume you meant MicroSD card, not SD Card.

BotRob said:
I'm unclear about the directory part. If someone could clarify that would be great
Click to expand...
Click to collapse
You would just copy and paste the commands into the ADB shell window.

sixtythreechevy said:
You would just copy and paste the commands into the ADB shell window.
Click to expand...
Click to collapse
K thank you very much for clarifying

Wait so do you need root to do this? If that is the case is there any way I could do anything with the note 4 on the latest firmware?

After typing Yes to confirm the warning message all I get is:
[-] this is for <some> Samsung devices only
[-] it will kill other devices

I keep getting this ::
------------------------------------------------------ 2nd attempt
(Yes/No)
[+] CID at boot time is/was: 15
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[-] you MUST have a 1GB or greater sd card inserted
[-] 4GB or greater is recommended
[-] do NOT patch this out of code!
[-] fail
10|[email protected]:/data/local/tmp #
------------------------------------------------------
Fails I got this the first time... I loaded fully back in then tried again and got this. not in dev mode.
----------------------------- FIRST TIME -----------------
(Yes/No)
[+] CID at boot time is/was: 15
[+] device not yet dev CID, now changing to dev CID
[+] programming new CID 15
[+] success! powering off device, power back on and verify CID
[+] then run this binary again to finish the process
------------------------------------
Thanks

JimChagares said:
After typing Yes to confirm the warning message all I get is:
[-] this is for <some> Samsung devices only
[-] it will kill other devices
Click to expand...
Click to collapse
download brickbug app from Playstore and check emmc cid, if it starts with 15 only then can you use this process. If it starts with 15 it would be better to wait and see what comes up tomorrow.