Database Users

How to know if your phone is rooted or not?

I was rooting my nexus one last night on a guide from theunlockr.com and got through every step except the last one where you have to install ''install-superboot-windows.bat'' when i clicked on it it showed a little blackbox with something in it for about half a second and nothing else showed up so i assumed it was finished. When i go into bootloader it says unlocked at the top and on the start up screen it shows a little unlocked sign at the bottom but i went into the market to download the torch application, the whole reason i rooted it and it told me that i was not rooted and it would not work.

You have root just don't have superuser permission. I say flash the cyanogen add-on if you don't to flash a rom that has su built in.

Reboot your phone. If you have a pic of a unlocked lock, then your phone has been unlocked, and you can flash the amon_ra recovery, then flash a custom rom with superuser permission.
Also, you can go to a terminal emulator and type in su.

david1171 said:
Reboot your phone. If you have a pic of a unlocked lock, then your phone has been unlocked, and you can flash the amon_ra recovery, then flash a custom rom with superuser permission.
Also, you can go to a terminal emulator and type in su.
Click to expand...
Click to collapse
Where can i get a terminal emulator?

Hi mate, I had the same problem... I think you have unlocked your bootloader but failed to root your phone.
Im pretty sure the bit when you ''install-superboot-windows.bat'' doesn't work sometimes.
I had to manually re-do that bit ...
---------------Manual Rooting---------------
open a command window in that folder by holding down your shift key and right clicking anywhere in the window. and selecting open command prompt here
type this command in your command prompt "fastboot-windows flash boot nexusone.superboot.1.1.img"
then enjoy your rooted phone.

viperman78 said:
Hi mate, I had the same problem... I think you have unlocked your bootloader but failed to root your phone.
Im pretty sure the bit when you ''install-superboot-windows.bat'' doesn't work sometimes.
I had to manually re-do that bit ...
---------------Manual Rooting---------------
open a command window in that folder by holding down your shift key and right clicking anywhere in the window. and selecting open command prompt here
type this command in your command prompt "fastboot-windows flash boot nexusone.superboot.1.1.img"
then enjoy your rooted phone.
Click to expand...
Click to collapse
Thanks Do i have to put the phone into bootloader or do anything else on the phone?

No... just follow the last bit of this.
http://www.android-devs.com/?p=100
For some reason the batch file didn't do its magic, so I had to do it manually... Pretty sure you have the same issue .
And really??... the whole reason you voided your warranty was for the torch app???? You are not installing Cyanogen mod or anything?

viperman78 said:
No... just follow the last bit of this.
http://www.android-devs.com/?p=100
For some reason the batch file didn't do its magic, so I had to do it manually... Pretty sure you have the same issue .
And really??... the whole reason you voided your warranty was for the torch app???? You are not installing Cyanogen mod or anything?
Click to expand...
Click to collapse
haha no but thats how i found out about rooting. Also you said just follow the last bit of the steps do you mean just do step 7, Sorry for all the questions im new to most of this and dont want to mess up my nexus.

Thanks, I got it to work but now wifi does not work

Install all the latest Cyanogen stuff and you should have no problems. Also you will have a lot more mem for apps!
Voiding your warranty just for a flashlight is a bit silly IMO.
GL

I installed the cyanogenmod 5.0 rom and everything was installed correctly and when i reset the phone it just shows the firework things coming together over and over again.

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate

Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.

I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.

jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?

xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?

try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.

jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!

xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.

g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?

xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.

I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.

It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

Unlock Problem: Permission Denied??

I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.

If I root the phone, will that work?
Also, what are some good programs to copy the EFS folder?
Sorry for all the questions.

I'm fairly certain you have to be rooted

I am rooted as of 10 mins ago.
I tried to unlock it and I still got the same thing.
It says Permission Denied
Anyone have any ideas?

Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.

molson24 said:
Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.
Click to expand...
Click to collapse
in Terminal?
type:
su
(and hit enter)
before the command that needs superuser permission.

Also you probably would be better off just pulling the whole efs folder.

molson24 said:
I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.
Click to expand...
Click to collapse
for permission denied try this:
open terminal emulator on your phone (download it from the market if you dont have it yet)
or you can type "adb shell" without quotations into the dos prompt and do it from there.
and type:
su
chmod 777 /efs/nv_data.bin
exit
exit
then in the dos prompt try:
adb pull /efs
or if you just want nv_data.bin:
adb pull /efs/nv_data.bin
if you need further help, this was written for the 19000 but it should help you anyways.
http://www.communityhosting.net/sgsunlock/i9000.html

You need to copy your nv_data.bin from your phone to your pc
You should see a folder made in the repair_nv_data folder like this Sauverarde_efs_apres_reparation
Move your nv_data.bin there along with nv_data.binvierge and repairation_nv_data.jar and Step2 and Step 4
Run Step 2 again and then Step 4 after its done creating the new nv_data.bin
I can't remember but I think you have to delete nv_data.md5 and a few others from your phone first

Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol

molson24 said:
Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol
Click to expand...
Click to collapse
lol yeah I can see that happening
I've accidently denied su permission a few times myself even when I do notice the pop up
well congrats!

Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?

molson24 said:
Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?
Click to expand...
Click to collapse
Unlocking should not break your downloads (At least I've never heard of it happening) but you'll be fine flashing any rom you like, without having to unlock again.
are you still on t-mobile just unlocked?
orare you on a different carrier now that your unlocked?
the main things to be careful of when flashing roms is:
be careful going from froyo (2.2 JK2/JK6) back to eclair (2.1 JFD/JI6) its a little tricky, but not too bad.
and be careful with lag fixes, if you use one always disable it before flashing. (I never found them very useful myself anyways)
going from JFD to JI6 and back should be fine though.
if you want a completly clean slate then you can use Odin and it still wont re-lock your phone.
you might even find that you like some of the roms out there better than the stock one
I know I did.

BootLoader Unlock (both ZE551ML and ZE550ML)

Congrats to all ( both ZE551ML and ZE550ML users), bootloader has been unlocked without connecting to ASUS servers.
2.19.40.20 is also unlockable
New update 2.19.40.20 can be unlocked as well and Asus did not patch the hole. Thanks to @oxydius7 for confirming this here
Bootloader of both ZE550ML and ZE550ML can be unlock if rom is on 2.19.40 or 2.19.40.20
Lets discuss, problems and unlocking related experience here.
How to unlock bootloader:
1. Update to 2.19.40.18 or 2.19.40.20
2. root it
3. make sure adb is insatlled and working
4. enter the following commands in cmd
adb shell (press enter)
su (press enter)
getprop ro.isn > /factory/asuskey ( press enter)
reboot bootloader ( press enter )
Phone will restart in bootloader and after updating itself phone will restart again and ASUS splash screen will be white ( locked bootloader has black screen, you will see difference by yourself)
5. download black splash screen for 551 from here
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
or for 550 from here
http://forum.xda-developers.com/attachment.php?attachmentid=3376376&d=1435127302
6. navigate to adb folder open cmd and type the following commands
adb reboot bootloader (press enter)
fastboot devices (press enter)
see if device is listed, write following
fastboot flash splashscreen splashscreen.img (press enter)
restart your phone and now black splash screen is back. Congrats your bootloader is now unlocked.
If you follow my steps there would not be any data loss from internal memory and sd card, but i will advice to take a backup in case if you are out of luck
ZE551ML OTA 2.19.40 OTA Download:
http://fota.asus.com/delta_package/...W_Z00A-20150612/WW_551_0529_0612_20150612.zip
you guys can side-load or flash in via recovery method
Thanks to @fuzzybuffalo for providing the link
Download ZE550ML 2.19.40.12 complete Rom:
Download Here
Changelogs
credit goes to @keepfishes for coming up with links on post
Download ZE550ML 2.19.40.12 OTA Rom:
Download Here
credit goes to @singhnsk for coming up with links on post
Tip:
if you have problems with adb try to install "Terminal Emulator" app and running the commands from there
su
getprop ro.isn > /factory/asuskey
reboot bootloader
Thanks to @hugoprh for providing the tip, thank to him on his post
white splash screen for 551
Download
credit goes to @fuzzybuffalo for providing the link, thank to him on his post
Twrp Flashable, Black and white splash screens for 551
If you want twrp flashable zips of both white and black splash screens of 551, please download them from here
I will not take any responsibility, its your device and your will to try this
All credits goes to @shakalaca for providing unlock
donate and say thanks to him, press thanks button if i helped

anyone tested this method already? is it safe and does the unlock method cause data / os wipe?

Nice. This is great new. Thanks to @shakalaca. Cant wait for @TheSSJ to get TWRP working.

cangcan said:
anyone tested this method already? is it safe and does the unlock method cause data / os wipe?
Click to expand...
Click to collapse
i tried it and no it will not wipe any data if you follow my steps

cangcan said:
anyone tested this method already? is it safe and does the unlock method cause data / os wipe?
Click to expand...
Click to collapse
Can confirm it worked flawlessly, took literally 15 sec to do.

Wow, cant wait for the development to begin... Cyanogenmod+4gb Ram+ 64gbStorage ...

ravian29 said:
5. download black splash screen from here
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Would it be possible to create a mirror for this file. maybe google drive? My ISP is blocking Mega. Thank you

saurabhrck said:
Would it be possible to create a mirror for this file. maybe google drive? My ISP is blocking Mega. Thank you
Click to expand...
Click to collapse
Here ya go, https://drive.google.com/file/d/0BzkVsWgLUMFIY1o3c19RNWdYR0E/view?usp=sharing

Great news. Looking forward to start Breaking this baby.

Is it possible to do this on 2.18? My phone just refuses to update to 2.19 no matter what I try.

Christopher876 said:
Is it possible to do this on 2.18? My phone just refuses to update to 2.19 no matter what I try.
Click to expand...
Click to collapse
I dont belive so, the needed files are part of the 2.19 update. I also had a problem with the update so I had to reset phone, then sideload a full copy of 2.18 and then sideload the 2.19 update and reroot phone.

Christopher876 said:
Is it possible to do this on 2.18? My phone just refuses to update to 2.19 no matter what I try.
Click to expand...
Click to collapse
I got bootloop 3 times.. then...a fresh install nonrooted 2.17 ..upgrade it to 2.18... upgrade that to 2.19... do not touch anything inbetween..

Triston182 said:
I dont belive so, the needed files are part of the 2.19 update. I also had a problem with the update so I had to reset phone, then sideload a full copy of 2.18 and then sideload 2.19 and reroot phone.
Click to expand...
Click to collapse
Alright, I will try this right now and see if it updates, thank you for responding. This is the only phone that I have been having problems consistently with. It is kind of making me feel like I should of went the extra money and buy a device from LG or Sony.

Christopher876 said:
Alright, I will try this right now and see if it updates, thank you for responding. This is the only phone that I have been having problems consistently with. It is kind of making me feel like I should of went the extra money and buy a device from LG or Sony.
Click to expand...
Click to collapse
same here i always bought samsung since s2, i can understand how this phone messes and waste a lot of timw with small things which can be done in seconds

I can reconfirm this process works with latest update. Thank you!!

Followed the instructions, works like a charm, nothing got wiped out.
:good::good:

Wow. The amount of work achieved by XDA members never ceases to amaze me!

Triston182 said:
Nice. This is great new. Thanks to @shakalaca. Cant wait for @TheSSJ to get TWRP working.
Click to expand...
Click to collapse
@Dees_Troy will have his own ZF2 soon

thank you very much to all of the developers who helped unlocking the bootloader!
just one question - what does unlocking the bootloader gives me? (sry for noob question)

SpaZzzzz said:
thank you very much to all of the developers who helped unlocking the bootloader!
just one question - what does unlocking the bootloader gives me? (sry for noob question)
Click to expand...
Click to collapse
can flash custom[dev made] roms,kernel which maybe increase or decrease performance,battery,added features,latest android version etc etc[like CM12..1]

[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.