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.
Related
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.
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
I found a post about firmware for this tablet to flash back to stock.
http://mobile.gaodi.net/Firmware-668989-1-1.html
Maybe someone can do something with it.
I may not be able to get cyanogen completely running but i can get an initial device tree setup and a twrp recovery made. i just need a copy of the boot image.
Lrs121 said:
I may not be able to get cyanogen completely running but i can get an initial device tree setup and a twrp recovery made. i just need a copy of the boot image.
Click to expand...
Click to collapse
anything you can do would be great. how would i go bout pulling boot.img?
neckbonest said:
anything you can do would be great. how would i go bout pulling boot.img?
Click to expand...
Click to collapse
I cant download the firmware restore file in the op but that would be the best place to get it. if there is a way to extract the image from the restore file thats how you would get it, example is a tool called unruu for htc devices. other wise it has to be directly copied from the device. if youre lucky the file system includes a path like this
Code:
/dev/block/platform/*something*/by-name/
you can see that with a file explorer like root explorer. With in that path there should be a bunch of partitions listed by name. im not certain of the name of the one id need. it could be aboot or boot or something else.
to copy a partition for me to use, youll need adb shell or an android terminal emulator installed and root.
run terminal emulator or run adb shell
Code:
$ su
give shell root access
# dd if=/dev/block/platform/*something*/by-name/aboot of=/sdcard/aboot.img
or
# dd if=/dev/block/platform/*something*/by-name/boot of=/sdcard/boot.img
youll then have a boot.img or aboot.img on you internal sdcard. let me know if you can get those that way or by extracting it or if you can send me factory restore file and i can try to extract it myself.
I just wonder how well twrp or something will work because of verizons habit of having locked bootloaders.
Lrs121 said:
I cant download the firmware restore file in the op but that would be the best place to get it. if there is a way to extract the image from the restore file thats how you would get it, example is a tool called unruu for htc devices. other wise it has to be directly copied from the device. if youre lucky the file system includes a path like this
Code:
/dev/block/platform/*something*/by-name/
you can see that with a file explorer like root explorer. With in that path there should be a bunch of partitions listed by name. im not certain of the name of the one id need. it could be aboot or boot or something else.
to copy a partition for me to use, youll need adb shell or an android terminal emulator installed and root.
run terminal emulator or run adb shell
Code:
$ su
give shell root access
# dd if=/dev/block/platform/*something*/by-name/aboot of=/sdcard/aboot.img
or
# dd if=/dev/block/platform/*something*/by-name/boot of=/sdcard/boot.img
youll then have a boot.img or aboot.img on you internal sdcard. let me know if you can get those that way or by extracting it or if you can send me factory restore file and i can try to extract it myself.
I just wonder how well twrp or something will work because of verizons habit of having locked bootloaders.
Click to expand...
Click to collapse
verizon does love to lock bootloaders. not sure if this is locked or not.
i a not able to download the firmware ether. ive tried adb shell and terminal but get the following on both
tmp-mksh: give : not found
bootloader
it looks like the bootloader is locked, shocker right! it is verizon after all. not sure how locked down it is.
ive tried physical buttons, adb shell and terminal with no luck but this is me we are talking bout. maybe someone smarter can get in
neckbonest said:
it looks like the bootloader is locked, shocker right! it is verizon after all. not sure how locked down it is.
ive tried physical buttons, adb shell and terminal with no luck but this is me we are talking bout. maybe someone smarter can get in
Click to expand...
Click to collapse
I see the issue. the line "give adb root" was a comment not something to actually run.
commands excluding the line starting with give. and replace *something* with the proper path. for the htc m9 its
Code:
/dev/block/platform/f9824900.sdhci/by-name/
If it doesnt work i can at least get the device tree started.
I know enough stuff to keep me out of trouble with adb/flashing. And based on where I would need to start to try and pull the boot file, I'm lost haha. Anything else and I'd be happy to help with!
Sent from my VK815 using XDA Free mobile app
So my tablet today prompted me to update to 11A. But since it's rooted it didn't go thru. Does anyone know what we can do with that info? Like to keep root and update?
Came here looking for the same. There's a chance that even after update could root, possibly like g4, but no guarantees. And without ever having a recovery, the only possibility would be with flash fire, but still no guarantees. And we would need for someone to upload a system image to rip for that...
Has anyone found a recovery that works on the VK815 on 5.0.2?
I am wondering if anyone has found a way back to stock so that we can take the upgrade to 11A
Lrs121 said:
I see the issue. the line "give adb root" was a comment not something to actually run.
commands excluding the line starting with give. and replace *something* with the proper path. for the htc m9 its
Code:
/dev/block/platform/f9824900.sdhci/by-name/
If it doesnt work i can at least get the device tree started.
Click to expand...
Click to collapse
Do you still need a boot image? If so, let me know and I'll work on pulling it for you.
Totally jail breaking this device would be a plus for the world.
Jim
jowski said:
I see the issue. the line "give adb root" was a comment not something to actually run.
commands excluding the line starting with give. and replace *something* with the proper path. for the htc m9 its
Do you still need a boot image? If so, let me know and I'll work on pulling it for you.
Totally jail breaking this device would be a plus for the world.
Jim
Click to expand...
Click to collapse
I figured since its a Verizon tablet, the boot loader would be locked and I lack the knowledge and experience to bypass it. However I could still get a device tree started
Wouldn't 'dd' with root privileges be enough? It might not be script friendly but ... I've used CM with the stock boot loader before on other phones and the boot loader wasn't a show stopper.
Anyway, it you need an image from me; I'll work it in the schedule.
Jim
Katmeat said:
I am wondering if anyone has found a way back to stock so that we can take the upgrade to 11A
Click to expand...
Click to collapse
I'm assuming it's not safe to take this OTA, maybe we can use LGs flash tool if we could get our hands on the stock firmware?
Pipedreams said:
I'm assuming it's not safe to take this OTA, maybe we can use LGs flash tool if we could get our hands on the stock firmware?
Click to expand...
Click to collapse
I think everyone is being cautious knowing how Verizon likes to censor things. Yes, censor is the correct word. They are trying to tell VK815 owners what they can and cannot put on the VK815 owner's VK815.
I'd like to see a dedicated version of linux for the VK815. Later today I plan on emailing LG on that and a few other things.
Jim
jowski said:
Wouldn't 'dd' with root privileges be enough? It might not be script friendly but ... I've used CM with the stock boot loader before on other phones and the boot loader wasn't a show stopper.
Anyway, it you need an image from me; I'll work it in the schedule.
Jim
Click to expand...
Click to collapse
To obtain the image yes that's sufficient, its when you try to replace the recovery or rom is where the locked bootloader causes issues.
Katmeat said:
I am wondering if anyone has found a way back to stock so that we can take the upgrade to 11A
Click to expand...
Click to collapse
Does anyone had problems with this new update? All my apps always blink when I'm unsung it.
Lrs121 said:
To obtain the image yes that's sufficient, its when you try to replace the recovery or rom is where the locked bootloader causes issues.
Click to expand...
Click to collapse
I was thinking that with root privileges one could 'dd' over the boot loader with a new one.
Have you (or do you know anyone who has) been able to compile android-5.1.0-r1 with the LGVK815_Lollipop_Android.tar.gz added on? My attempts fail with a "make: *** No rule to make target `out/target/product/generic/obj/STATIC_LIBRARIES/libtune2fs_intermediates/export_includes', needed by `out/target/product/generic/obj/EXECUTABLES/updater_intermediates/import_includes'. Stop." I'd feel better if I could successfully compile the stock version.
Jim
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
calle124 said:
Does anyone had problems with this new update? All my apps always blink when I'm unsung it.
Click to expand...
Click to collapse
Did you allow the update with a rooted VK815? That would be good information for all to know.
Jim
UPDATE Thanks to @thjubeck for testing this, it seems that this userdebug kernel actually works on all devices running antirollback v0 and running Marshmallow! I only have the Sprint variant, so be careful!!! Enjoy root guys
A bit of a disclaimer is that this is root through adb. dm-verity is off and system is rw, so you can install apps as root, get a hotspot hack to work, and anything through a shell but I am having trouble installing SuperSU. Please try yourself though as I am probably doing something wrong! If there are any bugs you have found please post them, as this phone is my backup and not my daily driver.
So okay, here is the guide:
PLEASE MAKE SURE YOU HAVE A WAY TO GO BACK INCASE THINGS GO WRONG. DO NOT ATTEMPT TO ROOT THIS WITHOUT HAVING A KDZ/TOT FOR YOUR DEVICE THAT YOU KNOW YOU CAN FLASH BACK TO. I AM NOT RESPONSIBLE FOR THINGS GOING WRONG.
1. Download this zip
2. Install Terminal Emulator from the Play Store
(This is modified from the V20 bootloader unlock, HUGE thanks to all of those devs for sharing their dirtysanta code with me and allowing me to modify it!)
3. Copy all the files from inside the "dirtysanta-boot" and paste it into your active ADB directory
4. Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
(When you run The sh or Bat files there may be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.)
5. Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
6. Open Up Terminal Emulator on your phone
Type:
Code:
id
Check if context is "Untrusted_app". If it is then we're good to go!
7. Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
8. Watch the RUNMEFIRST dialog for when it tells you to run Step2 (we don't have a step 2)
9. Reboot the phone into recovery mode and wipe data again
BOOM! Now the you have a userdebug kernel running on a userdebug system Time to turn off dm-verity, otherwise you will have a red triangle on reboot (Your device is corrupt. It cannot be trusted and may not boot) and cannot edit /system.
1. Finish setting up the phone and enable USB Debugging in developer options (you should know how to do this)
2. Plug the phone into your computer, and run these commands
Code:
adb root
adb disable-verity
3. Reboot the phone
4. Run
Code:
adb root
adb shell
mount -o rw,remount,rw /system
Bam. Enjoy your FULL UNLIMITED root shell with system set to rw and dm-verity off!!! Just make sure to type "adb root" before "adb shell"
If you ever want to go back, just flash your stock TOT/KDZ with UPPERCUT and you'll be all good!
BUY ME A PIZZA FOR THE HARD WORK: BTC 197ct1uti4zutJu76bYAW51H8NZ6zXeoEV PayPal: [email protected]
THANKS:
@tungkick for the userdebug boot and helping me with the ZV4 TOTs
@autoprime for UPPERCUT
@me2151 @glitschi667 @EMSpilot @elliwigy for their AMAZING work on the V20 and sharing their code!
Thanks for the mention. Since you didnt say anything else i thought you bricked. Glad it works for you guys
I'm assuming this won't work if I'm on nougat, is that right?
fenguepay said:
I'm assuming this won't work if I'm on nougat, is that right?
Click to expand...
Click to collapse
Nougat is the latest update (ZV8 I think), this only works on ZV4.
Glad I stayed on ZV3 since July.
Happy this is out now. There was some sass going on in another thread but it seems there's still some civility among us. I'll check this out and report anything of note. I'm most interested in a viable hotspot mod, so if I can figure out how to modify the APN settings I'll be quite happy. Will donate as soon as I figure out how.
SilverZero said:
Nougat is the latest update (ZV8 I think), this only works on ZV4.
Glad I stayed on ZV3 since July.
Happy this is out now. There was some sass going on in another thread but it seems there's still some civility among us. I'll check this out and report anything of note. I'm most interested in a viable hotspot mod, so if I can figure out how to modify the APN settings I'll be quite happy. Will donate as soon as I figure out how.
Click to expand...
Click to collapse
Lucky you! Make sure you flash the stock ZV4 TOT before trying this
An unlimited Hotspot is definitely possible. I'm on mobile right now but I'll see what I can do when I get home.
Honestly Annoying said:
Lucky you! Make sure you flash the stock ZV4 TOT before trying this
An unlimited Hotspot is definitely possible. I'm on mobile right now but I'll see what I can do when I get home.
Click to expand...
Click to collapse
I'd be first in line to give this a whirl in the real world but I'm leaving in the morning for a week or so on the road. Maybe I'll be able to do some playing around at the hotel. Hotspot is the brass ring, adblock is a close second. I've survived this long, so hopefully a few days of testing and squashing bugs won't kill me. I do want to be of service to the community if possible. It will be interesting to see how these new developments affect the development of the various G5 variants.
My apologies if I insinuated that I'm at all peeved with anybody working on this device or just offering encouragement. I know there are some conflicting personalities in the mix right now, so I hope everybody benefits and sees the value in what you're potentially onto with this.
SilverZero said:
I'd be first in line to give this a whirl in the real world but I'm leaving in the morning for a week or so on the road. Maybe I'll be able to do some playing around at the hotel. Hotspot is the brass ring, adblock is a close second. I've survived this long, so hopefully a few days of testing and squashing bugs won't kill me. I do want to be of service to the community if possible. It will be interesting to see how these new developments affect the development of the various G5 variants.
My apologies if I insinuated that I'm at all peeved with anybody working on this device or just offering encouragement. I know there are some conflicting personalities in the mix right now, so I hope everybody benefits and sees the value in what you're potentially onto with this.
Click to expand...
Click to collapse
I will absolutely be in touch with you for an adblock and hotspot hack, PM me your Skype
I think I found a way to get the hotspot hack, waiting for a tester...
I'm on z5, can I still follow this guide on the dot and flash z4?
btw, gratz and great job on your achievement!
bigid said:
I'm on z5, can I still follow this guide on the dot and flash z4?
btw, gratz and great job on your achievement!
Click to expand...
Click to collapse
Thank you!
Unfortunately ZV5 has antirollback enabled, so you can't downgrade to ZV4. If you really want to try it you can attempt to flash the ZV4 userdebug boot without the userdebug system (just follow the guide past the TOT steps) but I believe it will bootloop. I have not personally tried this so I have no way of saying for sure, but it'll probably bootloop.
Honestly your name does you justice! Thanks for your hard work
So bummed that I updated...
Sent from my LGLS992 using XDA-Developers mobile app
Honestly Annoying said:
Thank you!
Unfortunately ZV5 has antirollback enabled, so you can't downgrade to ZV4. If you really want to try it you can attempt to flash the ZV4 userdebug boot without the userdebug system (just follow the guide past the TOT steps) but I believe it will bootloop. I have not personally tried this so I have no way of saying for sure, but it'll probably bootloop.
Click to expand...
Click to collapse
so should i just update to nougat now?
EDIT: No items in the Google Drive folder? Am I missing something?
I'm definitely hoping to spend some time testing this out, but it's bad timing that I just got the family out on vacation. Hopefully I'll spend some time tonight or tomorrow, and quite likely after the 25th I'll have some time.
Meanwhile, I've got to figure out a solution to getting ADB working on my MacBook. It's EFI locked so I can't install the full SDK, and my windows VM isn't working either. Since I'm pretty sure I need a windows environment that will be my first hurdle. I wish I could sit down right now and just try it out for the community's benefit, but hopefully we'll get there soon.
Man I feel like buying a G5 just to try this on nougat! Does this also unlock the boot loader or allow twrp to be flashed?
chippinganimal said:
Man I feel like buying a G5 just to try this on nougat! Does this also unlock the boot loader or allow twrp to be flashed?
Click to expand...
Click to collapse
It only works if you still have version ZV4 or lower, so forget about nougat. At best you'll be rooted on ZV4 forever with a wonky system.
It will not unlock the bootloader since it's just a user-debug upgrade for tinkerers, but nonetheless useful to some.
Wait. Where did you get the userdebug build for G5?
Plug your device into the computer and verify ADB is working
Could this be a means for (or a step closer to) getting full root, or is that basically off the table?
Sent from my LGLS992 using XDA-Developers mobile app
Error: Error Code = 0x2000 when trying to flash.
I've used the search function and found nothing for this phone. I've used Google and found nothing about rooting this exact model.
I'm looking for the technique to root this phone and I'm finding nothing. Has anybody rooted and flashed a Custom ROM/custom recovery on this device and how did you do it?
I just got this phone as well, and I have been looking and also have found nothing for this exact variant. I have tried the usual one-click methods to no avail. Is there any development in the works? If you need a test dummy, let me know. I have several other phones to use as spares, so I am not afraid of a soft brick.
Rooting ZTE Blade a7 Prime
I too can be a test dummy to root this phone. Since Visible is such a hands off company you really need your phone to be rooted to do things for yourself. Currently for some reason my ZTE BLADE A7 Prime can’t send or receive calls and their techs are telling me 3 to 5 business days... counting yesterday and today that’s a week! Ridiculous! The APN settings look off compared to my wife’s phone but you can’t edit the settings.
ZTE Blade prime A7 Visible
I've been having the exact same problem with making and receiving calls also with losing service(for the service prob. Found great n easy solution- till find permanent one-**go to airplane mode in settings turn it on for 30secs to a minute then turn airplane mode back off TAKES SIGNAL FROM 0-4 BARS EVERYTIME AND I CAN GET/MAKE CALLS INSTANTLY ETC AGAIN ?)
Data saver seems to work for resetting connection as well. I too would be interested in rooting. I kinda like the phone, but it does have its issues.
First glance at unlocking bootloader
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Has anybody tried this?
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
I don't own this phone (yet), so I can't give it a shot myself.
I'm not very familiar with mediatek processors in general, but that looks rather promising with some restrictions... If I have time over the weekend, I'll give that a whirl and report back whether it works or bricks my device
seems lke ts gonna be a long process before were able to fiddle with roms but im atleast glad this is close to stock android.
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
Ditto here too. Couldn't get it working at first. Turned out I miss read the instructions and put all files in the init.d folder instead od the two files in the bin folder. Then your tip on using the 32bit binary got it working. Thanks.
Anybody figured out a way to change build.prop to make it stick after reboot? I am trying to enable APN editing by modifying /system/build.prop, but whenever I reboot I lose the changes.
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
wunderdrug said:
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
Click to expand...
Click to collapse
Looks like we can not add an APN even with root then? It's a bummer.
sasuke33 said:
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Click to expand...
Click to collapse
They removed the fastboot command to unlock the bootloader. I found it out by comparing the similar ZTE Blade 10 and Blade 10 Prime. The Blade 10 non-prime has the unlock command and it works whereas the prime version has the command removed but funnily enough the lock command is still there but is useless. I then looked at the bootloader for the a7 prime and same thing the unlock command is removed from the bootloader. So there isn't much hope for it unless a bypass can be found.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
+1 to another confirmation that the above works. Root is available, but there are limitations. I cannot install many of the modules from magisk, but this is still a great start. Thanks for the links :good:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
ultrasoul said:
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
Click to expand...
Click to collapse
I was also able to add and APN by just clicking on the "+" icon on the top-right corner of the APN configuration screen. When I inserted by MINT SIM Card (T-Mobile MVNO) there were not default populated APNs, but was able to get everything to work after adding an APN -- even after rebooting.
Big Tip: After entering the APN data and before leaving the data entry screen, make sure that you save the APN or it will not be persisted. Click on the "three dots" menu on the top-right corner and hit the Save menu item.
---------- Post added at 05:49 AM ---------- Previous post was at 05:39 AM ----------
AmazerG said:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
Click to expand...
Click to collapse
After studying the process a bit, I've come to conclude that this isn't really permanent root. All this does is the equivalent of running a script to gain temporary root after after reboot. This is done very late in the boot process, if you can even call it a part of the boot process since it's really just a user-space application auto-starting.
The modules are probably trying to be instantiated well before the root is made available through the pseudo "init.d" scripts.
It's still nice to have root access using this technique, but its usability is pretty limited. For example, I can't even get AFWall+ to start up, even if I configure it with a startup delay (hoping that it kicks in after temporary root).
So what are the odds we can make this a permanent root using a firehose file and QPST/QFIL? Similar to the Visible R2 phone?