Related
Here I share some instructions I found on how to root the Atrix 4G after installing the new update
After updating your Motorola Atrix 4G to software version 4.5.141 you will lose root access. For those of you want to root your Motorola Atrix 4G after updating to build 4.5.141 this is how you do it.
Keep in mind that when typing in the commands during the rooting process you will leave out the quotes.
Instructions to root Atrix 4G running Gingerbread on 4.5.141:
Download and Extract Fastboot Files (I was unable to post the Link, but you can go to "android-advice" website to find it)
Connect your phone to the computer via USB
Put your phone in fastboot mode (restart phone holding volume down button)
Open a command prompt and navigate to C:/moto-fastboot-win32
type “moto-fastboot.exe flash preinstall preinstall.img” press enter
Press “Vol Up” to initiate fastboot protocol
type “moto-fastboot.exe reboot” press enter
Your phone should reboot, wait for it to come back up
type “adb shell” press enter (to restart the shell)
type “/preinstall/dosu” press enter
If step 10 fails type “/preinstall/su” instead and hit enter
type “/bin/mount -o remount,rw /system” press enter
type “cp /preinstall/su /system/bin/” press enter
type “chmod 6755 /system/bin/su” press enter
type “PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk” press enter
Reboot your phone
NM.............//10 chars
The Article this was copied from is: Root the Motorola Atrix 4G Running 4.5.141
All of the downloads and original article can be found there.
Does anyone try this method
I dont know if is safe and i read several ways to root the atrix and dont also know who method should I choose
Thanks
If you know what you are doing then it's safe.
It also depends on what GB Build you are on. AFAIK, this is the only root method for 4.5.141
ErnestoD said:
Does anyone try this method
I dont know if is safe and i read several ways to root the atrix and dont also know who method should I choose
Thanks
Click to expand...
Click to collapse
live4nyy said:
If you know what you are doing then it's safe.
It also depends on what GB Build you are on. AFAIK, this is the only root method for 4.5.141
Click to expand...
Click to collapse
My Atrix have Android Version 2.3.6 Compilation 4.5.141
I´ve just bougth it second hand and I understand it is sim unlock (couse Im using carrier named Ancel from Uruguay South America.
I also know that this atrix use to had root cause I can see all phones directory (but now I cant change permissions)
I dont know what would happen with carried unlock if I succed with this
Can U help me
From what I have read before, a SIM Unlock would not be affected.
You should be able to root and flash ROMs and all that.
ErnestoD said:
My Atrix have Android Version 2.3.6 Compilation 4.5.141
I´ve just bougth it second hand and I understand it is sim unlock (couse Im using carrier named Ancel from Uruguay South America.
I also know that this atrix use to had root cause I can see all phones directory (but now I cant change permissions)
I dont know what would happen with carried unlock if I succed with this
Can U help me
Click to expand...
Click to collapse
live4nyy said:
From what I have read before, a SIM Unlock would not be affected.
You should be able to root and flash ROMs and all that.
Click to expand...
Click to collapse
Thanks man. Anyway I will read and read more before attemting to do this
Thanks for your support
PilsenerX said:
Here I share some instructions I found on how to root the Atrix 4G after installing the new update
After updating your Motorola Atrix 4G to software version 4.5.141 you will lose root access. For those of you want to root your Motorola Atrix 4G after updating to build 4.5.141 this is how you do it.
Keep in mind that when typing in the commands during the rooting process you will leave out the quotes.
Instructions to root Atrix 4G running Gingerbread on 4.5.141:
Download and Extract Fastboot Files (I was unable to post the Link, but you can go to "android-advice" website to find it)
Connect your phone to the computer via USB
Put your phone in fastboot mode (restart phone holding volume down button)
Open a command prompt and navigate to C:/moto-fastboot-win32
type “moto-fastboot.exe flash preinstall preinstall.img” press enter
Press “Vol Up” to initiate fastboot protocol
type “moto-fastboot.exe reboot” press enter
Your phone should reboot, wait for it to come back up
type “adb shell” press enter (to restart the shell)
type “/preinstall/dosu” press enter
If step 10 fails type “/preinstall/su” instead and hit enter
type “/bin/mount -o remount,rw /system” press enter
type “cp /preinstall/su /system/bin/” press enter
type “chmod 6755 /system/bin/su” press enter
type “PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk” press enter
Reboot your phone
Click to expand...
Click to collapse
I like these kinds of step-by-step instruction lists, and I had seen these on the android-advice site. Others have said that the 6th step (Press “Vol Up” to initiate fastboot protocol) should be done before the 4th step (Open a command prompt and navigate to C:/moto-fastboot-win32). As a relative "noob" at this myself, I wanted to seek the advice of experts on this forum to see if they concur that this corrected order is important.
Thanks.
will this format/erase something __¡¡??
Thanks
Better was to save Root before update
androidxpert.com/2012/02/keep-root-after-ota-update-with-voodoo-ota-rootkeeper/
It worked great for me... wifi tether still works also...
thanks, but i can't do it
alexuong said:
thanks, but i can't do it
Click to expand...
Click to collapse
What´s your problem dude.
Stuck
I had root before update. I will for sure check Forum next time before update. I updated without doing anything, everything worked, but I lost root. I hard reset device. SUPERUSER still on device.
Followed each step, up to:
$ /preinstall/dosu
/preinstall/dosu
/preinstall/dosu: not found
$ /preinstall/su
/preinstall/su
/preinstall/su: not found
$ /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
/bin/mount: not found
Click to expand...
Click to collapse
How do I get root back on 4.5.141
Thanks for your help
Mofiki said:
The Article this was copied from is: Root the Motorola Atrix 4G Running 4.5.141
All of the downloads and original article can be found there.
Click to expand...
Click to collapse
Thanks! This worked
Diablo_692 said:
I like these kinds of step-by-step instruction lists, and I had seen these on the android-advice site. Others have said that the 6th step (Press “Vol Up” to initiate fastboot protocol) should be done before the 4th step (Open a command prompt and navigate to C:/moto-fastboot-win32). As a relative "noob" at this myself, I wanted to seek the advice of experts on this forum to see if they concur that this corrected order is important.
Thanks.
Click to expand...
Click to collapse
I tried the steps just as they are printed and had no issues.
I will just advise you to read and read, look for videos, etc. before trying something you don´t feel you fully understand. Is important you identify exactly what device you have and SW versions, so you are sure you are following the correct instructions for you.
Hope this helps!
Stuck
First time rooting on my first phone
I got stuck where it said "type adb shell" the phone booted completely and then i panicked and pulled the battery and so far i have not been able to re do this to any point every time I get to where it says “moto-fastboot.exe flash preinstall preinstall.img” it takes forever and nothing happens (i waited about 20 min)
Oh also the bootloader is Unlocked
Thanks in advance
andanao2 said:
First time rooting on my first phone
I got stuck where it said "type adb shell" the phone booted completely and then i panicked and pulled the battery and so far i have not been able to re do this to any point every time I get to where it says “moto-fastboot.exe flash preinstall preinstall.img” it takes forever and nothing happens (i waited about 20 min)
Oh also the bootloader is Unlocked
Thanks in advance
Click to expand...
Click to collapse
ADB shell is a command
WOW.... it worked great.
Thank you....
After letting AT&T update my ATRIX 4G from 4.5.91 to 4.5.141 several weeks ago... I lost root.
I found the instructions here on how to root 4.5.141.... and tried several times to root my ATRIX again.
Finally... today I got it. It is now rooted. And I then installed the Voodoo OTA RootKeeper to ensure that I don't lose root again. RootKeeper is a nice free app that even allows for very simple to use temporary unrooting and re-rooting.
Thank you... Thank You.... THANK YOU.
hello...help please...
after ''/preinstall/dasu''.....
''bash: groups: command not found
[email protected]:/#''
any idea?
tks
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
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
stu5797 said:
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
Click to expand...
Click to collapse
Suggestions:
Make sure you have USB debugging enabled. Shut down and do a battery pull and re-try.
I haven't tried Kingo with the new update, but the battery pull seemed to help on MJ7 and I have seen where others successfully used Kingo after the update.
I did have USB debug enabled. Kingo goes through the whole process then says root failed
It worked. Forgot to turn off anti virus on computer
stu5797 said:
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
Click to expand...
Click to collapse
already answered
az_biker said:
already answered
Click to expand...
Click to collapse
so is kingo safe???
jrocc24 said:
so is kingo safe???
Click to expand...
Click to collapse
If you are ALREADY on MJE, root with Kingo, then install safestrap
If you are still on MI9 or MJ7, boot into odin and install MJ7 tar, accept MJE OTA, root with Kingo, install SS, profit.
With the exception of the above info, check out my SIG and see the detailed step by step!
but i mean with that whole stealing IMEI and all that... just a worry and not a reality?
jrocc24 said:
but i mean with that whole stealing IMEI and all that... just a worry and not a reality?
Click to expand...
Click to collapse
After gaining root with Kingo, there are steps in my SIG instructions how to install Chainfire's SuperSU which overwrites Kingo's superuser. Also, once rooted, I would uninstall Kingo app from pc, run quick anti-virus scan... I know dozens of users who have done this with ZERO issues, including myself.
As with ANYTHING when rooting your phone, it is YOUR call and your responsibility to change, add or remove anything related to your phone. But I can tell you, I have not heard of ONE verifiable incident of erroneous data collection or anything similar related to the use of Kingo.
Follow my steps, and enjoy! Don't forget to hit THANKS if this helped you and pass the word to others who would benefit from the step by step...
thanks man!! i hit thanks twice ill keep it in mind when i need it for tethering once they totally block it... once again thank you
Kingo is SAFE.
You also need to set your screen timeout to be 10 minutes and swipe to unlock your device to get to your home screen and leave it there while it installs.
You don't need to remove any PIN's or passwords you have, just get into the phone because Kingo will ask you to install a few programs on your device to get it to root.
RypeDub said:
Kingo is SAFE.
.
Click to expand...
Click to collapse
I don't think ANYBODY can state that 100% although it does seem relatively low risk at this point.
jmorton10 said:
I don't think ANYBODY can state that 100% although it does seem relatively low risk at this point.
Click to expand...
Click to collapse
Technically nobody can say ANY program that uses an exploit is 100% safe. Uninstall kingo from pc immediately (anti virus scan) install Chainfire's superSU immediately after root (overwrites kingo superuser)...
Notorious 3
got my new Note 3 today, i let it install the newest MJE update right away. Followed the directions with latest Kingo 1.1.5, it just sits there and says it can't connect over and over and does this little flashing between the orange and red icon on the Kingo client. Running on Windows XP, going to try again on a different pc with Windows 7 this evening. Yes USB debugging enabled and screen timeout set to max (10 minutes). Tried two different cables too. Tried different USB ports, tried rebooting phone and pc.
neyenlives said:
got my new Note 3 today, i let it install the newest MJE update right away. Followed the directions with latest Kingo 1.1.5, it just sits there and says it can't connect over and over and does this little flashing between the orange and red icon on the Kingo client. Running on Windows XP, going to try again on a different pc with Windows 7 this evening. Yes USB debugging enabled and screen timeout set to max (10 minutes). Tried two different cables too. Tried different USB ports, tried rebooting phone and pc.
Click to expand...
Click to collapse
Turn off you anti virus
Can't, I'm on a work pc right now. Will try later on my laptop at home.
Sent from my SM-N900V using Tapatalk
neyenlives said:
Can't, I'm on a work pc right now. Will try later on my laptop at home.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Make sure display timeout
is over 10 min, disable pc anti-virus. Retry even if kingo fails..took me 3 attempts
Check link in my sig for step by step
Notorious 3
It was the anti-virus I guess, worked fine first time at home on my laptop after disabling MSE real time protection.
Sent from my SM-N900V using Tapatalk
Glad you're up and running
Notorious 3
Just to confirm a few things:
Was running MJ7 rooted w/ Beans build 4
installed stock MJ7 tar through Odin
rebooted
Took MJE OTA
rebooted
rooted via Kingo
installed Chainfire's SuperSU
Installed Safestrap
restored MJ7 rom (Beans Build 4)
NOT a single issue after re-rooting with Kingo
MJE running MJ7 Rom
VERIFIED KNOX 0x0 and 0x0
I've recently updated to V10E. I used to have a rooted device with towelroot.
After upgrade (done via LG PC suite), I lost the root.
I tried to root using PurpleDrake, all screen instructions and actions go fine, but the device is not rooted.
Is there a way to root V10E version at all ?
PurpleDrake - Lite is the only method of rooting this firmware at the moment, and it does work.
If you are having issues then either its your pc, or you not following the instructions that is the problem.
Lennyuk said:
PurpleDrake - Lite is the only method of rooting this firmware at the moment, and it does work.
If you are having issues then either its your pc, or you not following the instructions that is the problem.
Click to expand...
Click to collapse
What PC has to do here?
What kind of instructions are you talking about?
It's a simple ".bat" file that only requires to press Enter twice, that's about it.
Adb does see my phone, USB debugging is on and etc.
Temproot and Permaroot are being applied fine, no errors or anything. But it just doesn't work.
I can print a screen shot if you want.
By doesn't work what are you referring to? If the .bat file says its applying the files fine then it means it transferred the required files to your phone without error, there is then no reason for it not to be present when you reboot?
How do you know it didn't work?
jodvova said:
I've recently updated to V10E. I used to have a rooted device with towelroot.
After upgrade (done via LG PC suite), I lost the root.
I tried to root using PurpleDrake, all screen instructions and actions go fine, but the device is not rooted.
Is there a way to root V10E version at all ?
Click to expand...
Click to collapse
I updated my D855 rooted with towelroot last night via the OTA update and retained root, apart from having to turn xposed back on. The reports of inconsistent results I'm hearing are really odd. Mine's a 16gb model on ee, what's yours?
Sent from my LG G3
Lennyuk said:
By doesn't work what are you referring to? If the .bat file says its applying the files fine then it means it transferred the required files to your phone without error, there is then no reason for it not to be present when you reboot?
How do you know it didn't work?
Click to expand...
Click to collapse
The phone remains unrooted.
I can't install SuperSU nor edit build.prop
Rootchecker says no...
I'm on 32gb model from HKG.
jodvova said:
The phone remains unrooted.
I can't install SuperSU nor edit build.prop
Rootchecker says no...
I'm on 32gb model from HKG.
Click to expand...
Click to collapse
You can't install SuperSU, or when you open super su it fails to find the binary?
I even tried to run your guide to restore the phone (http://forum.xda-developers.com/lg-g3/general/guide-unroot-ota-using-lg-pc-suite-pc-t2802286) and then apply purpledrake but the phone remains unrooted.
Lennyuk said:
You can't install SuperSU, or when you open super su it fails to find the binary?
Click to expand...
Click to collapse
I click install in the play store, it downloads it, says installing... But then aborts with Incompatible update message.
jodvova said:
I click install in the play store, it downloads it, says installing... But then aborts with Incompatible update message.
Click to expand...
Click to collapse
that sounds like a separate issue. You do not need to be rooted to install the app from the Play Store, it just won't do anything if you install it without having root. The fact its not letting you install it is linked to some other issue, are you sure you don't have any other SU apps already installed, if you do remove them all first (including SuperSU if you have that installed) and then reboot before trying to download it again.
Lennyuk said:
that sounds like a separate issue. You do not need to be rooted to install the app from the Play Store, it just won't do anything if you install it without having root. The fact its not letting you install it is linked to some other issue, are you sure you don't have any other SU apps already installed, if you do remove them all first (including SuperSU if you have that installed) and then reboot before trying to download it again.
Click to expand...
Click to collapse
So originally, when I was on v10b and rooted with towelroot I had super su installed.
After that the phone told me there is OTA available which I immediately tried to install.
Since I also had dpi changed, OTA update failed. With that I lost the root, supersu disappeared from applications.
I then upgraded to v10e via LG PC suite. And now trying to root using PurpleDrake.
Super SU shows as not installed in Play Store. Titanium Backup doesn't see such apk installed.
I dont have any other "su" applications installed.
Any suggestions on how to fix it ?
jodvova said:
So originally, when I was on v10b and rooted with towelroot I had super su installed.
After that the phone told me there is OTA available which I immediately tried to install.
Since I also had dpi changed, OTA update failed. With that I lost the root, supersu disappeared from applications.
I then upgraded to v10e via LG PC suite. And now trying to root using PurpleDrake.
Super SU shows as not installed in Play Store. Titanium Backup doesn't see such apk installed.
I dont have any other "su" applications installed.
Any suggestions on how to fix it ?
Click to expand...
Click to collapse
Try to go to menu > settings > apps and see if you can see the SU app there.
Failing that your best option might be to factory reset and then root.
Lennyuk said:
Try to go to menu > settings > apps and see if you can see the SU app there.
Failing that your best option might be to factory reset and then root.
Click to expand...
Click to collapse
It's not there.
Also, as I said before rootchecker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) says the phone is not rooted.
I assume it doesn't use supersu to check whether it's rooted.
That's the output from console.
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D855 ] on [ GLOBAL ] running SW version [ V10e ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
Waiting for device... Found device!
Applying permaroot...
Waiting for system to settle...
Checking if it worked...
Permaroot worked, all done here. Moving on...
All done! Your phone has been successfully rooted.
After you press enter, your phone will be rebooted back to a rooted system.
Please be careful with what you change.
Press [enter] to continue...
Click to expand...
Click to collapse
jodvova said:
It's not there.
Also, as I said before rootchecker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) says the phone is not rooted.
I assume it doesn't use supersu to check whether it's rooted.
Click to expand...
Click to collapse
never used it before, but I would have thought that it would request SU permissions which would require an SU app.
Did a factory reset and root works now.
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.