Related
It should be noted that this is the current script, however, i am working on a cross platform java program that will do all of this for you
[NARS] is the Nook Automated Rooting System FOR MAC and LINUX
This program has been a WIP for myself for about a month, and I developed it so that people whom wanted to work with the adb development, and “bricking” of devices could quickly restore their devices to root. This program can also be used for a new user to, backup their programs, restore their programs, Root, Unroot, and Full restore.
Initializing ADB:
Download any app, and attempt to install it.
You can use this app if you need.
[*]Click on the Package Installer, and then a prompt will pop up asking if you want change the settings to allow 3rd party apps.
*DO NOT ENABLE 3RD PARTY IF YOU WISH TO ACCESS ADB*
I am working on a way to have it enabled by default.
[*]In the settings page you should see *2* USB Debugging modes.
*NOTE: if you disable automount, Debugging will maintain through unplugs
[*]Press them both and accept the prompt.
[*]PLUG IN YOUR DEVICE.
Note* You should see the Android Development icon on the bottom of the screen.
ADB will now be able to see your device. How ever you will need to restart the server before it sees it.
As it stands right now this scrip has 4 functions, and a video will be made for it tomorrow.
USE THIS SCRIPT AT YOUR OWN RISK!!!!!!!!
Using the script:
Download Start up script (Inside NARS):[/I][/B][/CENTER]
Check to see what operating system is running for which adb to used
[*] Inject the product id into the adb_usb.ini file.
[*] Start the adb server and look for devices.
[*] Verify that chosen devices is actually a Nook
[*] Load Menu
Current abilities:
Rooting with zergRush and installation of the su Binary
Installing busybox
Installing Gapps
Unroot
Factory reset
OTA block
Upcomming abilites:
Semi-automated install and config of keyboards
Installing launchers
Installing HomeCatcher
Custom Unbloating
Backup and custom recovery
Download:
[URL]https://github.com/loglud/NARS/zipball/master
Git-Hub
https://github.com/loglud/NARS
Changelog:
1/9/12:
Added ota blockage
New busybox
Bug cleanup
Nice! Will try later on today on my friend's Nook.
Sent from my X500 using XDA App
Windows
Any suggestion for us windows users which are outside of this curve?
verosity said:
Any suggestion for us windows users which are outside of this curve?
Click to expand...
Click to collapse
Use the windows script in this section, it does literally the same thing.
Ubuntu 11.10 not showing my nt
Are there any tricks to getting an Ubuntu 11.10 system to show the nook tablet in the list of attached devices? On my laptop the list is empty. The laptop does see the nook, both the on-board flash and the SD memory. But NARS.sh doesn't find it.
New Nook Tablet, first time plugged into the Ubuntu laptop.
jbs
SandlinJohn said:
Are there any tricks to getting an Ubuntu 11.10 system to show the nook tablet in the list of attached devices? On my laptop the list is empty. The laptop does see the nook, both the on-board flash and the SD memory. But NARS.sh doesn't find it.
New Nook Tablet, first time plugged into the Ubuntu laptop.
jbs
Click to expand...
Click to collapse
do me a favor and go into the NARS directory and type
Code:
./adblinux devices
and tell me what the output is.
also make sure you have adb debuging setup. To do this read the post in http://forum.xda-developers.com/showpost.php?p=19653967&postcount=3 Enableing adb Connection (eab1) part 4 through 8
I lost track of when I'd had the debug settings enabled. Between all my windows boxes, which all loaded a generic driver before I could use the custom drivers, and getting the linux box set for android development, I lost track of the last setting on the nook - I forgot to "measure twice and cut once" - I didn't go back to make sure debug was still enabled.
The reminder about the debug was the key.
Thanks.
Did not work on a mac running Lion. My nook is never detected. Clear, detailed instructions that are self-contained in the first post would be appreciated.
Not sure if any prep work is needed or if your script really should be this easy.
Thanks
UPDATE: YOU MUST COMPLETE THE FOLLOWING STEPS BEFORE BEGINNING NARS.
Cut and pasted from another t-r-i-c-k's thread at http://forum.xda-developers.com/showthread.php?t=1358051.
You must complete the following step before using NARS:
Code:
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
[url]http://goo.gl/vTNpJ[/url]
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
Now follow the instructions in post #1 of this thread.
After you have run that script, reboot your nook tablet (you can turn it off all the way by pressing and holding for a few seconds the power button. Then turn the nook tablet back on).
You need to make sure that you install golauncherex, which I forgot to do. Just find the .apk that you downloaded (go_launcher_ex_v2.66.apk in your notifications center on the nook) and then make sure to install it. This will give you a new homescreen with all of your regular apps.
Loglud said:
...
Upcomming abilites:
Autoinstall and config of keyboards
Installing launchers
Installing HomeCatcher
[*]Unbloating
Click to expand...
Click to collapse
Any chance of custom unbloating? Such as, if you want to keep some of the bloat? Like the games?
Hey all. Hopefully you have all gotten a chance to check this out. I would like if you guys could tell me what launchers, browsers, keyboars, etc. you guys use so i can put them into the code.
just some suggestions thanks.
launchers
go launcher
zeam
adw
hcl
ics launcher
keyboards
hacker keyboard
swift tablet and standard
extra app
amazon app store
es file exploxer
mx player
mx player arm 7 codec
swipe pad
I am not sure what is possible these are things I use and feel are solid for the tablet.
Loglud said:
Hey all. Hopefully you have all gotten a chance to check this out. I would like if you guys could tell me what launchers, browsers, keyboars, etc. you guys use so i can put them into the code.
Click to expand...
Click to collapse
Thumb Keyboard 4!!!
Block OTA?
Does NARS block OTA like Indirect's script under Windows?
great script, fails on option7 install additional apk's
would turning this into a full linux distro with say puppylinux for modding/tweaking and development for NC be useful?
Loglud: I've rehosted these files on XDA.
http://devftp.xda-developers.com/files/AdamOutler/NookTablet/Market-8009011.apk
and
http://devftp.xda-developers.com/files/AdamOutler/NookTablet/NARS.tar.gz
I just put in some changes on my domain so;
APK:http://nook1.adamoutler.com
tar.gz:http://nook2.adamoutler.com
This should make it substantially easier for us who are restoring frequently.. now to try this sucker out.
All of the lines like this:
Code:
read -p "Press any key to exit..."
should be
Code:
read -n1 -p "Press any key to exit..."
So that it takes a single key press instead of "Enter"
Also, here's some more stuff to add http://forum.xda-developers.com/showthread.php?t=1424811
Scripts are already written, you just need to modify them for ADB.
Thanks adam the script has been updated
Nice job devs. This nook is open like a brothel on payday!
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Hello.
I am sending this pm regarding the translation for flashing the Fujitsu f-05d sold by Docomo in Japan. I cannot reply in the development section due to my low post count.
My phone is an f-05d. I do not have a t-01d but, according to the original rooting guide for the f-05d, the users are reporting success in rooting the t-01d as well.
I will not really translate for you. Rather, I will explain what I did to root my f-05d.
Here is a rough summary of the steps I followed:
For starters, you need to make sure that adb recognizes your phone when connected to the PC via USB. This means that you need to install the Android SDK and the USB driver for your t-01d by Fujitsu.
I had trouble getting adb to recognize my phone, as Window$ insisted in recognizing it as an USB drive. What I did, among other things, was:
In the phone settings, go to Applications > Development and check USB Debigging and Stay awake.
Install the Google USB Driver package, in the extras section of the Android SDK Manager.
With the phone connected to the PC, go to Window$ device manager > Universal Serial Bus Controllers and uninstall (use the delete key from your the keyboard) every mass storage device that appeared when my phone was connected. Disconnect and reconnect the usb cable.
Only until I did this final step was my phone recognized and listed as Android Phone > Android Composite ADB Interface in the device manager. If your device is not recognized, you just cannot continue. Look for help about this, or else you cannot move on with this method of rooting.
Confirm that your phone is recognized as Android Phone > Android Composite ADB Interface in the Window$ device manager. Do not continue until it is.
From the Android SDK manager, install the package android sdk platform-tools.
You need download F05Droot.zip from the original blog page your linked before. I will not link to the file directly, but you should have no problem finding it. Extract the files within into the program directory \Android\android-sdk\platform-tools (this is my path).
You need to download a replacement for the file lsm_disabler.ko that is inside the F05Droot.zip. Get it from here and extract it an replace the one inside the platform-tools directory.
By the way, this platform-tools directory is the one that has the adb executable file. Just a heads up.
You need to download su. I cannot tell you where to get it. I just do not know where I got mine from, but was easy so go for it When you have it, extract it and put it in the platform-tools directory.
Confirm that the platform-tools directory includes these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
su
lsm_disabler.ko
f05dsu.bat
There will be more, but these are the ones needed for this to work.
Now, get ready to root. Connect your phone to the PC.
Go to your phone settings > setting my body > step/activity counter app > pedometer use and confirm it is checked on.
In the platform-tools directory, look for f05dsu.bat and run it. A DOS window will open. This is the funny part. Unless you are doing this from a Japanese version of Window$, or from a Window$ with Japanese locale active, you will see a lot of strange symbols instead of Japanese characters... which would be the same for almost anyone anyway Regardless, you will see a prompt to Press any key to continue . . .. At this point, you do not need to do anything on your phone, other than visually checking that the check mark on the pedometer is set.
On the DOS window press any key, your will see more garbage and another prompt to press any key. This is the important part. See if you can find among all those symbols this pattern: OFF/ON. If you do see it, it means we are on track.
Now that you were able to see the OFF/ON, go to your phone and uncheck the pedometer (OFF) and check it again (ON).
In the DOS window, press any key. Your phone will reboot. The message in the DOS window says that you must wait for the phone to boot up and for Window$ to recognize your usb connection to the phone.
When/if your phone is recognized by Window$, go to the DOS window and press any key.
Again, press any key and your phone will reboot.
The DOS window has a message indicating that you must now install superuser and busybox. When your phone reboots, go to the android market and install from there when you have the time.
You can now close the DOS window because, unless there was any error, you are now rooted, my friend
From the market, install a terminal, or an app that includes a terminal. I use Rom Toolbox because it has a terminal and scripts to mount the /system as rw.
Open whatever terminal you chose and, at the $ prompt type su
If new prompt is #, type soff
You will need to run these commands every time before trying to mount /system as rw.
That is all. I hope you can root your phone.
Just a petition, post this message in the forums, as it may help others who have similar difficulties. It sure could have helped me if someone had done before me.
Have a nice one and please forgive my English.
Click to expand...
Click to collapse
update 15/4
On 13/4 finally i got my phone rooted
I have to run f05droot.bat instead of f05dsu.bat
After I have run the f05dsu.bat, for the steps, no error popout.
then I open the terminal type su, it reply me "permission denied".
I know it is not successful, after several run, the situation still the same.
after that have checked the contents of f05droot.bat and f05dsu.bat.
They are very similar but the f05droot.bat will push the superuser and busybox into the device at the same time.
(so I added those files in the directory \Android\android-sdk\platform-tools )
Therefore, i tried that and its works finally.
I feel really exciting at that moment.
I hope this post can help they T-01d user to root the phone.
personally I really like this phone ^~^
the su file is also important
Anyone try it? Does it work?
I have got the source code from its web
But I dont know how to use that and lead me to root the machine
ttp://spf.fmworld.net/oss/t-01d/data/download.html
Can you post a review of this device?
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Click to expand...
Click to collapse
If you have time, can you please post a mini review of the device? I wanted to buy one too and I'm quite excited reading your review!
Thanks and more power!
Here is the mini review
Screen color is perfect except black and accurate. Speed is good in comparing with SGS2. Battery life is similar to SGS2. Form factor is better than SGS2. Camera is outstanding, thanks to the 1.3MP camera. Waterproofing design is what I like. The bad is upgrading is only possible in Japan. Digital TV is useless. Sound level is a bit low.
personally i like this phone very much especially the outlook.
my personal review is the following:
1. same as above the screen is perfect
2. the camera is also excellent
3. while you have a phone call, it change mode automatically depends on the environment
4. if i switch off all the data things, this phone can stand more than one day
(so i wont blame the battery, because I think we use too many network related stuffs)
5. i have to admit that the firmware is not quite stable (fortunately the phone can be upgrade to 4.0 after july)
for the rooting process, it seems like someone has success:
(i think that is temp root)
search "T-01D 軟解, tofu-keitai" in google (that is chinese unfortunately)
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Click to expand...
Click to collapse
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
hi HaoyuWen,
i have followed the steps, when i type su in the terminal simulator, it comes out segmentation fault su, do you have any idea.
I use titanium backup to check and it said my t-01d is not rooted.
for the pedometer on/off things, do i need to press the home key and go back to the pedometer to do the switch?
Thank you very much in advance
HaoyuWen said:
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
Click to expand...
Click to collapse
So both F-05D and T-01D can use this ?
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
finally i got my phone rooted
you have to run f05droot.bat instead of f05dsu.bat
the su file is also important
redcarrot said:
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
Click to expand...
Click to collapse
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
wth_is_life said:
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
Click to expand...
Click to collapse
I think I brick my T-01D. Don' know why, I do exactly the same what I have been told here... Now It ends up infinite boot loop
Anybody help me please?
Hey there everyone, sadly this guide isn't working for me. Everything in the guide goes smoothly and I do exactly what is listed but after my phone reboots the final time I still have no root access. I run f05droot.bat instead of f05dsu.bat like the user said but to no avail, I even ran f05dsu.bat and still nothing.
Anyone else have trouble? Maybe it is because I am on a certain FW? I am on 2.3.5
Baseband Version C_L1_M23
Kernel version: 2.6.35.7 [email protected] #1
and Build number is V43R41C
Just wondering as I really want root to disable all of these RAM-hogging default applications.
Bump? Anyone?
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
kinchung said:
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
Aw Thanks for the notice, of course it's my firmware. Any idea about ICS? It was supposed to come out in July but yeah..
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
kinchung said:
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
I see, I read about the T-01D (among many others) getting updated from articles like this: http://forums.hardwarezone.com.sg/e.../docomo-update-ics-4-0-18-models-3662812.html
I'm sure the T-01D would perform pretty awesome and maybe pre-installed software would not be as big a deal as it is now. Maybe since your SH-01D is getting updated, T-01D isn't far behind. The only thing I have to see is if I can update out of Japan.
I don't have sh-01d but galaxy tab 10.1 sc-01d instead. My t-01d also upgraded to V43R41C last month during visiting Japan. Upgrade of t-01d may not be possible outside Japan as Software Update cannot be executed without docomo sim and network.
Sent from my SC-01D using Tapatalk 2
Fluid Navigation Gesture
Installation
The app has a built-in option to hide the software navigation keys (if necessary) but it requires either root or a pc is required to grant a system permission.
Instructions:
1-Enable Developer Mode in the Android settings.
2- Enable USB Debugging
3- Install Adb (links bellow)
4- Run the following adb command to grant the
Permission:
Windows: adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE SETTINGS
macOS: Jadb shell pm grant com.fb.fluid android.permission.WRITE_SECURE_SETTINGS
You can restore the navigation keys using the app or by run this
adb command:
Windows: adb shell wm overscan O,0,0,0
macOS: /adb shell wm overscan 0,0,0,0
Actions:
Back
Home
Recent apps
Toggle split screen
Open notifications
Open power dialog
Open quick settings
Launch Google search overlay
Open keyboard selector
Voice Search
Launch assistant
Launch app
Launch shortcut
Download:
https://play.google.com/store/apps/details?id=com.fb.fluid
Hey guys
So I am a beta tester and I made a review of the app with detailed instructions in my channel so for anyone interested to see and understand it
youtu.be/y1X3wQnEMBc
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
stevenlientje said:
I get an error when running the command: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
Click to expand...
Click to collapse
The correct one is android.permission.WRITE_SECURE_SETTINGS
Regurding the fluid app
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
wasp45 said:
Hi its perfectly working on my note 9 as i want to remove the app please help me to remove the app the installation was done with the pc guide lines so any one who has the idea of how to remove the app from a note 9 as i did rwmove but the side still is thier
Click to expand...
Click to collapse
Read the guide. It tell how you can do it.
Have you tried to reboot device after removing it?
Force kill app not work! Pro version
What happens? @@Deadpool96
Sent from my [device_name] using XDA-Developers Legacy app
Unable to restore navigation keys on Yureka Black
I am using Yureka Black device and tried enabling fluid navigation. That worked well. But now i just want to restore my navigation keys but unable to do so. I tried from the app and from the ADB as well (adb shell wm overscan 0,0,0,0) but nothing works. Please help. I have tried rebooting and all
Twrp
Any devs can make a flashble zip for granting cammand through twrp? I iz noob.
does not work on Android 10, quits immediately (Google Pixel 3)
Recent apps
Hi, a little help here.
i have a oneplus 7 (not pro), and i installed FNG in august, and i absolutely loved it
but, since this week's update (i think on sep 21), the gesture for "previous app" changed its behavior. instead of showing the 3 previous app (one swipe changed to the latest, a second one to the one before, a third the one before, and then returning to show the previous app). it was super useful because i drive a cab and could change between 4 apps with ease while driving without little distraction, and also because recent apps has to rotate because it does not support landscape mode anymore (DON'T GET ME STARTED ON THAT, but any help on that would be also very useful).
now, it only shows the last app, and when on android auto it's common that it shows that, which only block the screen and is completely useless.
so, i'm willing to send a lot of good vibrations to whoever can help me with that (that's a once in a lifetime offer, guys). thanks for any help you can offer with this
I have an error running this command : error: device '(null)' not found
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
MikePlays_ said:
Hi, I had an error message whilst trying to hide naviagion bar using computer (win10). Error -> device unauthorized (I have screenshot of it, but I can't send link here. - (I have USB debbuging on)
Click to expand...
Click to collapse
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
Mmm, sounds more like an ADB problem, rather than an FNG one.
Hi, MikePlays_
I've had this problem myself occasionally when running ADB, not specifically with FNG, but with other apps requiring an ADB command line to be run.
Usually, when you run ADB for the first time, both your PC and your Android device displays a dialog box to confirm USB debugging authorisation. I'm a little hazy on the precise details of this dialog box, because it's been quite a while since I used ADB.
Anyhow, if this doesn't happen or you get an error message, then you can try to revoke USB debugging authorisations, and begin again, with the FNG ADB command line. Sometimes a reboot of both your PC and your Android device may be required after revocation.
You should find the revoke authorisation option in your Android devices Developer Options settings. See my screenshot below, taken from my Android 9 Moto G6.
I can't say for certain if this will work for you, but when I've had weird ADB authorisation problems in the past, this has usually fixed the problem.
Good luck & I hope this helps
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
MikePlays_ said:
Well, thanks for fast reply, I don't know how to properly use ADB, is there any tuturial for that? I can't see any dialog box on computer, so something is wrong.
Click to expand...
Click to collapse
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
As per my previous post, try revoking your USB debugging authorisations, and then reboot both your PC and your Android device. If all goes well, the dialog box should then appear when you run the ADB command. If I remember correctly, it's similar in function to pairing two Bluetooth devices together, with a unique code, and which you then have to confirm.
As for tutorials, try this to begin with...
https://www.xda-developers.com/quickly-install-adb
In the meantime, I'll get my laptop out, and see if I can grab a screenshot of the dialog box you should expect to see. Give me an hour or so
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
MikePlays_ said:
well, now I tried it again, when I was trying to allow USB debbuging, it gave me error -> screenshot at the bottom. But thank you very much for that quick response, I did not expect that
Click to expand...
Click to collapse
That's great news. Hope you get FNG working, with a disabled stock Nav Bar.
It's a terrific app, and one I couldn't imagine without, on my phone and tablet.
Rgrds,
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
OK, I was mistaken. No dialog box appears on the PC, but one does appear on your Android device, and it looks like the screenshot below...
Rgrds,
Ged.
Click to expand...
Click to collapse
Problem I have with it is even smaller pop up over that, it writes when I want to press "ok", it writes "an app is obscuring a permission request. Settings can't verify your response." It is visible on screenshot too, but it has low quality.
Hello all,
Mirroring through miracast works fine now! I managed to fix the issue I faced with trying to mirror the phone with miracast.
The phone I bought from China came with apparently some manually altered rom. It didn't have much of the bloatware of the Nubia stock firmware. Also, it did not come with the "screen projection" app of Nubia. This app seems to be integrated into the phone. I couldn't find any .apk of it online. I tried a bunch of different apps, none worked. Also, factory resets, did not reinstall that app either.
The solution was simple. I used TWRP to wipe the phone and install the latest (v2.23) rom from the official nubia website: http://ui.nubia.cn/rom/detail/56
After installing it, the app was there and worked instantly.
At the moment now I have some issues with TWRP. I will fix it and see if the build.prop presisted through all of this, I doubt it.
If it did, and any changes are still required, I will update the post.
Kind regards,
Rup7ur3
---- initial post ----
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). Currently when I try mirror with the use of wi-fi direct, it doesn't show the miracast dongle I use (anycast).
I've not any experience in this and am trying to google for solutions. Online I have found some answers, but it's not yet working.
Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
ro.hdmi.enable=true
ro.hdmi.mirror.enable=true
persist.adb.notify=0
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=0
Click to expand...
Click to collapse
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
Miracast is available on Android devices with Android 4.2 Jelly Bean
Click to expand...
Click to collapse
and
no more supported by Android since 6.0
Click to expand...
Click to collapse
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
#property to enable VDS WFD solution
persist.hwc.enable_vds=1
# Add by ztemt for ZWfd begin
#property to set wfd output resolution is 1080P(0) / 720P(1) / 960*540(2) / 800*480(3)
persist.sys.wfd.zte_resolution=0
#property to show wfd sink false(0) / true(1)
persist.sys.wfd.zsink_support=1
#property this is device support wfd 1080p output support(true) not support(false)
persist.sys.wfd.1080p_support=false
# Add by ztemt for ZWfd end
Click to expand...
Click to collapse
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
rup7ur3 said:
Dear folks,
I'm trying to fix miracast on the Nubia Z18 (NX606J). I've not any experience in this and am trying to google for solutions.
I have found some answers, but it's not yet working. Hopefully I'm on the right path, but if anyone can help, it's greatly appreciated.
Why
The reason I want to use miracast, is to stream content to a portable display without the use of internet (so by cable or with WIDI). I don't think this phone supports hdmi/display port. If someone manages to get mirroring to work over cable, please let me know. As for WIDI, I think miracast is the only option? So, my bets are on this horse and I'm trying to make it run. Also, I'm new to this forum. If I post this at the wrong place, please forgive me. I created this thread for this specific model, because the manufacturer, Nubia, creates it's own (quite elaborate) UI on top of stock android. I suspect this could be part of the issue.
Summary so far
What I tried so far, is to install the custom recovery image of TWRP on my smartphone and adb + drivers on my windows 10 pc. Next I used the "mount" option in TWRP to enable adjustments of system files. The file I changed is the /system/build.prop file. I pulled the file using adb commands. Then changed the file on my pc and pushed it back to the phone. I will describe it in detail below. Yet, the sad thing is: it does not work. On another, older, model of the Nubia Z line, the Z9 mini, it did work.
Details
I installed drivers & adb/fastboot and twrp.
TWRP: https://forum.xda-developers.com/nubia-z18/development/recovery-twrp-nubia-z18nx606j-t3882098
Drivers & adb/fastboot: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934 (in chrome download didnt start for me, had to use firefox)
Once the above were installed, I connected my phone with the pc. I put phone settings in developer options to enable usb debugging. I got a notification to let my pc debug the phone, and accepted. Next I enabled "wireless display certification", "OEM unlocking" and set usb configuration to "MTP" instead of charging.
The adb on my pc was installed on my C:\adb\ folder. In the folder hold shift & right click, select open powershell or adb. I checked if my phone was connected using "adb devices". It listed my phone. So I went on and put it in fastboot mode (hold power + decrease volume). I checked if adb recognized fastboot with "fastboot devices". It listed my phone. Then next I unlocked the phone and installed TWRP with the help of this guide, from step 2 onwards: https://bbs.app.nubia.cn/forum.php?mod=viewthread&tid=1412934
Once TWRP installed. I created a backup of the phone through there. Then I selected the tab "mount" and enabled the system folder. Back to adb, I ran the command "adb devices" to see if my phone was listed, it was. Then I ran the command "adb pull /system/build.prop" that copied the build.prop file to my c:\adb folder. I made a reserve copy of the file and adjusted it with notepad++. These are the lines I added or enabled:
Then I pushed it back with the adb command: "adb push build.prop /system/build.prop". Rebooted the phone, tested the mirroring option, no luck. The phone runs on android 8.1.0, has the nubia V6.0 UI and the build number is NX606J_CNCommonV2.23. Any app whatsoever with a miracast option, will redirect to the system miracast settings. The following screen will appear: https://imgur.com/a/Otf1YO0
The Struggle
I read online several forums where they claimed that setting these was helping other phones to enable miracast. For the Z18 it did not work. I tried this with the Nubia Z9 mini. Miracast did not work on there before, now it does. The build.prop seems to persist fine now. For some reason, the first few attempts (attempt 1 & 2) wiped TWRP and the adjustments on the build.prop. Third time it kept working. TWRP however, still is wiped after a few reboots, but the build.prop file remains intact with the changes I made.
The Nubia Z9 mini has a few stock apps: "screen projection", "screen projection services" and "projection sink". It loads the screen projection app and allows to chose from project/receive and works flawlessly after the build.prop changes. The Z9 mini runs on android 5.1.1 and as Nubia UI V4.0 with build number: NX511J_INCommon_V4.0.4.
I read online that:
and
Yet, I've seen people make it work, by adjusting the build.prop, for later versions also. Not seen one working with android 8.0 or 8.1. Is it impossible for some reason / a hardware thing? If it's a software issue, surely it can be overcome?
I found that the build.prop in the Z9 mini contained the following lines:
I believe it's coupled to those apps I mentioned screen projection apps which are on the z9 mini. It had no effect adding these on the Z18. Now I'm attempting to find those apps and install them on Z18. Or looking for ways to downgrade the Z18 to android 5x. Ideally I do not want to downgrade the android. Any help, advice or questions are greatly appreciated.
Click to expand...
Click to collapse
Never try downgrading this phone. It's a nightmare because it's using AVB2.0 which was introduced with Android 8 I think. So getting that to work would be extremely difficult. What I'm not sure about is if nubia is doing anything different from other vendors as, judging by the source code, it looks the same as Sony for example (actually that's no wonder since they got 70% of their code from Sony).
What's difficult about this is that they define custom, vendor and device specific values as you can see with the Z9 build.prop. I'm not that well versed in Android actually and mostly just learning all this stuff by experimenting right now, but I would say your best bet would be some tool that scans a system for possible values in build.prop. However I'm unsure if such a tool exists unfortunately..
Sorry I can't be of more help as of now. I think Lineage is supporting Miracast though? So once I got that to work, it might be an option for you
Nubia z18 support screen cast without internet.
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
jagdishgeb said:
I use with EZcast 2.4g/5g without any internet and wifi hotspot.
I buy from Aliexpress " EZCAST 1080P TV Stick Dongle 5G Wifi Support HDMI DLNA Miracast Airplay DLNA Stick For IOS Android Windows Smartphone"
Click to expand...
Click to collapse
Thank you for the response, great to hear that it is possible! Did it work immediately?
Also, if you don't mind me asking. Could you maybe check if there are any default screen projection / sink apps pre-installed on your z18?
Mine came without any. I will try reinstall stock to see if that helps. All apps I use go to this screen: https://imgur.com/a/Otf1YO0
Online I read there are supposed to be options to enable wireless display in there. However, I think Nubia disabled it in their UI.
The method is derived from This post and does not require root access hence doesn't void Warranty or trips Knox:-
This is a Noob-friendly and Safe Method. The wireless debugging section might be new to people though.
This method is demonstrated in this youtube video as well and all the download links are given in the video description
Primary tools and methods used are:-
ADB Tools
FrpUnclock
SamsungDriver
Disabled Driver signature
Wireless debugging
Step:-1 [Preparing the device and using FRP remover]
First of all, reset the device (hard reset before removing any existing account )
Wipe Data and cache partition and reboot to system.
Select language and go to next
Accept conditions and proceed to wifi selection.
Login to your wifi and press back instead of going forward
Now you should get the language selection screen.
Connect your device to PC and launch FRP Tool.
For this tool to work properly in Windows 10, you must disable Driver Signature Enforcement.
Now in SamsunFRP tap on disable Driver Signature,
[Before proceeding ensure that the wifi connection on the phone is working]
Click on BypassFRP (It may ask to install the driver but you should install the driver given in below)
vlcsnap-2021-12-27-23h49m37s183.png
Once the application does its job you will see a pop-up on the tablet named Easy Firmware.
vlcsnap-2021-12-27-23h50m42s631.png
Step:-2 [Downloading QuickShortcut to ignore Knox]
Click on View and it will launch youtube then Chrome.
In chrome don't signup yet and in the search tab search for "vnrom"
select first link stating BYPASS GOOGLE ACCOUNT 2021 - vNORM.net
On the opened page scroll and download "QuickShortCutMaker.apk"
Allow installation from chrome and launch the application.
[Disconnect from your WIFI]
In the application search box search for "Setup"
Expand the Android Setup and select the last section (Just above the other "Android Setup" with Clock Logo)
vlcsnap-2021-12-27-23h52m16s102.png
Select Try
vlcsnap-2021-12-27-23h53m14s399.png
It will show Preparing for Setup... (let it take its time)
It will soon display the screen. Now lock the device and use the notification drawer to access settings
Knox might try to peep in but keep using the notification drawer to access settings.
Under the settings use developer mode (re-enable if not visible)
Step 3:- Using Wireless Debugging to disable knox permanently
Ensure pc and device on same network and disable any internet connection.
Ensure there is only LAN but no internet access as here Knox will attempt to regain control.
GO to Developer Options and select Wireless Debugging.
Now in your PC navigate to ADB/Platform Tools and launch CMD or Powershell by pressing Shift and right-click Open PowerShell here.
If using CMD type command as adb pair.
else in PowerShell type command as ".\adb pair".
Check this tutorial to connect the device to adb wirelssly.
Once you are connected to the device
enter
.\adb shell
pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms
exit
vlcsnap-2021-12-27-23h55m09s659.png
Now enjoy your Bloatfree tablet.
You can change wallpaper add your own account and do everything as there will be no restrictions or Privacy invasion.
Note:- Updating or Resetting the device will roll back all the changes and you will have to repeat the procedure again
Thank you
Great. Love that people are now helping and sharing these tricks.
Great to see , will gain more popularity now .
have u tried root checker app does it shows no root ? if app shows grant permission dialog box then its rooted
AddictedA1 said:
have u tried root checker app does it shows no root ? if app shows grant permission dialog box then its rooted
Click to expand...
Click to collapse
Here check the edited post. I have attached screenshot for root checker and Samsung info as well
starkprime74 said:
The method is derived from This post and does not require root access hence doesn't void Warranty or trips Knox:-
This is a Noob-friendly and Safe Method. The wireless debugging section might be new to people though.
This method is demonstrated in this youtube video as well
Primary tools and methods used are:-
ADB Tools
FrpUnclock
SamsungDriver
Disabled Driver signature
Wireless debugging
Step:-1 [Preparing the device and using FRP remover]
First of all, reset the device (hard reset before removing any existing account )
Wipe Data and cache partition and reboot to system.
Select language and go to next
Accept conditions and proceed to wifi selection.
Login to your wifi and press back instead of going forward
Now you should get the language selection screen.
Connect your device to PC and launch FRP Tool.
For this tool to work properly in Windows 10, you must disable Driver Signature Enforcement.
Now in SamsunFRP tap on disable Driver Signature,
[Before proceeding ensure that the wifi connection on the phone is working]
Click on BypassFRP (It may ask to install the driver but you should install the driver given in below)
View attachment 5493067
Once the application does its job you will see a pop-up on the tablet named Easy Firmware.
View attachment 5493069
Step:-2 [Downloading QuickShortcut to ignore Knox]
Click on View and it will launch youtube then Chrome.
In chrome don't signup yet and in the search tab search for "vnrom"
select first link stating BYPASS GOOGLE ACCOUNT 2021 - vNORM.net
On the opened page scroll and download "QuickShortCutMaker.apk"
Allow installation from chrome and launch the application.
[Disconnect from your WIFI]
In the application search box search for "Setup"
Expand the Android Setup and select the last section (Just above the other "Android Setup" with Clock Logo)
View attachment 5493071
Select Try
View attachment 5493073
It will show Preparing for Setup... (let it take its time)
It will soon display the screen. Now lock the device and use the notification drawer to access settings
Knox might try to peep in but keep using the notification drawer to access settings.
Under the settings use developer mode (re-enable if not visible)
Step 3:- Using Wireless Debugging to disable knox permanently
Ensure pc and device on same network and disable any internet connection.
Ensure there is only LAN but no internet access as here Knox will attempt to regain control.
GO to Developer Options and select Wireless Debugging.
Now in your PC navigate to ADB/Platform Tools and launch CMD or Powershell by pressing Shift and right-click Open PowerShell here.
If using CMD type command as adb pair.
else in PowerShell type command as ".\adb pair".
Check this tutorial to connect the device to adb wirelssly.
Once you are connected to the device
enter
.\adb shell
pm disable-user --user 0 com.sec.enterprise.knox.cloudmdm.smdms
exit
View attachment 5493079
Now enjoy your Bloatfree tablet.
You can change wallpaper add your own account and do everything as there will be no restrictions or Privacy invasion.
Note:- Updating or Resetting the device will roll back all the changes and you will have to repeat the procedure again
Thank you
Edit 1:-
Here's the attached screenshot of the root checker and Samsung info app.
They both state no root and Knox hasn't been tripped as well
View attachment 5493339View attachment 5493341
Click to expand...
Click to collapse
Dude if anyone haven't connected the tab to the internet from the time of purchase, then more simple way is there. Don't connect the tab to the wifi instead skip in the startup setup, get to the homescreen of tab, then open settings & activate developer's option. from their activate usb debugging and use the same command as mentioned in adb cmd. and then you are free to connect with internet and use tab without knox getting into action. but you have to deactivate auto update from developers and system upate menu in settings. Soon i will put a youtube video for that!!! Njoy
KillerSX said:
Dude if anyone haven't connected the tab to the internet from the time of purchase, then more simple way is there. Don't connect the tab to the wifi instead skip in the startup setup, get to the homescreen of tab, then open settings & activate developer's option. from their activate usb debugging and use the same command as mentioned in adb cmd. and then you are free to connect with internet and use tab without knox getting into action. but you have to deactivate auto update from developers and system upate menu in settings. Soon i will put a youtube video for that!!! Njoy
Click to expand...
Click to collapse
Yup this should work as well. But for full compatibility, i have shown the entire step right from the first screen
starkprime74 said:
Yup this should work as well. But for full compatibility, i have shown the entire step right from the first screen
Click to expand...
Click to collapse
yes its very helpful & i thank u for that. with that guide of you and @AddictedA1 , i was able to break my first tab, now i'm just xploring other ways! this method is same as yours, but since device was opened for the first time and it havent enrolled not once with knox, we can enter home tab screen easily, so we can bypass the initial steps and go to the cmd step directly. it's the same output in end!
KillerSX said:
Dude if anyone haven't connected the tab to the internet from the time of purchase, then more simple way is there. Don't connect the tab to the wifi instead skip in the startup setup, get to the homescreen of tab, then open settings & activate developer's option. from their activate usb debugging and use the same command as mentioned in adb cmd. and then you are free to connect with internet and use tab without knox getting into action. but you have to deactivate auto update from developers and system upate menu in settings. Soon i will put a youtube video for that!!! Njoy
Click to expand...
Click to collapse
yeah my frnd did that but u have to be fast,knox fires up quick blocks every access as it is the device admin
AddictedA1 said:
yeah my frnd did that but u have to be fast,knox fires up quick blocks every access as it is the device admin
Click to expand...
Click to collapse
bro you dont have to connect to iinternet initially from the start when you just unbox the tablet for first time and open it. it works only for those tabs. soon i will attach a video guide for that.
KillerSX said:
bro you dont have to connect to iinternet initially from the start when you just unbox the tablet for first time and open it. it works only for those tabs. soon i will attach a video guide for that.
Click to expand...
Click to collapse
yeh i know somebody tried that , its different from stock rom
Is it is possible to format the device which has knox?
lol997 said:
Is it is possible to format the device which has knox?
Click to expand...
Click to collapse
what u mean format , goto recovery mode do wipe factory reset .cleans all data but not pre installed apps nor knox
lol997 said:
Is it is possible to format the device which has knox?
Click to expand...
Click to collapse
Yes but formatting/resetting won't remove knox
why down ?
AddictedA1 said:
why down ?
Click to expand...
Click to collapse
had to due to some concern. Will restore soon
Claims that disconnecting internet at 50 percent in setup will result in able to change wallpaper?
Can someone confirm this or should I do all the way without disrupting internet. As harder setting the device is also sending information regarding number of resets.
Abish4i said:
Claims that disconnecting internet at 50 percent in setup will result in able to change wallpaper?
Can someone confirm this or should I do all the way without disrupting internet. As harder setting the device is also sending information regarding number of resets.
Click to expand...
Click to collapse
Can't confirm it since didn't have a chance to try that
But do you just want to remove the wallpaper and let the monitoring and stuff be as is?
Yes, I'm not sure I'll be restriction privacy access as we have a ID tag already to the device.
Though when ppl think they can somehow restrict privacy without using FBE on FDE rom that's highly unlikely.
Installation from Chrome does not work for me. Has this been patched? Because other FRP Removals had similar methods where you download a app in Chrome but none of them work cause of this.