Related
Ok, so I ultimately want to root this phone and install a custom ROM on it. However, it is not activated, and I cannot bypass the prompt to activate, I can only get to a dialer.
So, after reading the forums, it appears that the latest official FW is .621 and there's a root method for it, but it only works on .621. Obviously, root methods are version dependent. I figure I have to know the software version before continuing then.
Is there a code I can enter into the dialer to pull up software info? Or perhaps an adb command that doesn't require root? Anything at all I can do?
Or, do I even need software info? Can I simply proceed with some alternative root method?
Regards
Smith
EDIT: I ended up solving this through trial and error. I flashed the 2nd most recent sbf file and it produced an error in the bootloader, indicating that the device must've been on .621 so I sbf back to .621 and I'll proceed with that method.
EDIT 2: Ok, so that's fine and dandy and I was able to flash the sbf specified in the thread, but now zerg exploit won't run because I have no way of enabling adb :/ any ideas?
smithisize said:
Ok, so I ultimately want to root this phone and install a custom ROM on it. However, it is not activated, and I cannot bypass the prompt to activate, I can only get to a dialer.
So, after reading the forums, it appears that the latest official FW is .621 and there's a root method for it, but it only works on .621. Obviously, root methods are version dependent. I figure I have to know the software version before continuing then.
Is there a code I can enter into the dialer to pull up software info? Or perhaps an adb command that doesn't require root? Anything at all I can do?
Or, do I even need software info? Can I simply proceed with some alternative root method?
Regards
Smith
EDIT: I ended up solving this through trial and error. I flashed the 2nd most recent sbf file and it produced an error in the bootloader, indicating that the device must've been on .621 so I sbf back to .621 and I'll proceed with that method.
EDIT 2: Ok, so that's fine and dandy and I was able to flash the sbf specified in the thread, but now zerg exploit won't run because I have no way of enabling adb :/ any ideas?
Click to expand...
Click to collapse
http://www.droid-life.com/2010/06/10/tip-how-to-bypass-android-activation-screen-on-motorola-droid/ this shows how to by-pass the "activation", I just did it so it does in fact work for the Droid X M8810
dasfaust said:
http://www.droid-life.com/2010/06/10/tip-how-to-bypass-android-activation-screen-on-motorola-droid/ this shows how to by-pass the "activation", I just did it so it does in fact work for the Droid X M8810
Click to expand...
Click to collapse
You sir are incredible, thank you, I will try this when I get back to work tomorrow !
Sent from my SGH-I747 using xda app-developers app
Also, if you want to root, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1800047
Please post any questions you have in that thread
Sent from my Galaxy Nexus using Tapatalk 2
Going to check that thread now, got ADB working, just need to path it, and get all the other stuff going... Got this Droid X free and it has that pesky .621 on it.
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
I am having trouble using the motochopper method of rooting the phone. I followed all instructions correctly and have all up to date software installed. If anyone can tell me what i did wrong, please feel free to do so. This is what i got:
[*]
[*] Motochopper: Android root exploit (Windows version)
[*] v1.1
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well.
[*]
[*] Before continuing, ensure that USB debugging is enabled, that you
[*] have the latest USB drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
* server not running *
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2791 KB/s (1283460 bytes in 0.449s)
[*] Pushing root tools...
3011 KB/s (366952 bytes in 0.119s)
2746 KB/s (1867568 bytes in 0.664s)
2854 KB/s (1578585 bytes in 0.540s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .
So I'm wondering what base your phone is.
MDL or MF3 ?
If its MF3 than motochopper won't work.
Sent from my GT-I9505 using XDA Premium 4 mobile app
As stated above me IF you have mf3 then motochooper will NOT work. Either will Casual+Motochopper .
So now into the next question which firmware do you have?
MF3? Then look up SafeStrap.
MDL? Then try Casual+Motoxhopper from Adam Outlet.
Read all the stickies BEFORE trying to do ANYTHING ELSE to your phone so you do not have a paperweight.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
RockRatt said:
As stated above me IF you have mf3 then motochooper will NOT work. Either will Casual+Motochopper .
So now into the next question which firmware do you have?
MF3? Then look up SafeStrap.
MDL? Then try Casual+Motoxhopper from Adam Outlet.
Read all the stickies BEFORE trying to do ANYTHING ELSE to your phone so you do not have a paperweight.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
Now that we have the mj6 tar file you can get that paper weight back to life.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
If on MF3 and need root this should work.
rayburne said:
If on MF3 and need root this should work.
Click to expand...
Click to collapse
Yes the exFAT plus terminal commands method
sent from a I337 MF3 S4
I had y n3 rooted with kingo awhile back then I had to reimaged my phone with this file ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and now I can not get kingo to work. does anyone have any suggestions. thanks
in what way? how/ when does it fail.
kingo
Stryker1297 said:
in what way? how/ when does it fail.
Click to expand...
Click to collapse
the last thing I see before it fails is downloading requisite then it goes straight to fail notsupport
kingo
can anyone help with this. thanks
Mine failed the first time so had to run it twice. I would recommend enabling unknown sources and disabling verify apps so it can just do it's thing without any prompts.
Sent from my SM-N900V using Tapatalk
Whenever you wanna root via Kingo...make sure that the screen display time is set to 10 min...because while kingo is rooting the device we need to grant some permissions which pop-ups on the screen...
Also if Kingo fails for the first time run it again...2-3 times
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.