Related
Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!
My phone had a constant wakelock and it was draining my battery.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ with the name 'startsysupservice'.
Edit the script and put the following line in the file:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
NOTE: The correct way is for your ROM maintainer to update the sources with the new patch. Unfortunately, many ROMs are no longer maintained (especially for older devices) so this way is a good way to get around this issue for these ROMs. I originally created this for CarbonRom on my P769. I then switched to CyanogenMod 11 by dhiru1602 and this workaround still worked. It should work on other devices as well.
frostinide said:
My phone had a constant wakelock. After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/#/c/91021/
The fix I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime. I have P769 with CarbonRom.
Click to expand...
Click to collapse
Interesting info Frost..
and the script is a good idea. By the time I have Oneplus O2 OS all patched up, it will look worse than Frankenstein and I'll never remember all of the operations.
Frost,
Would you detail the differences between "Only the receivers should be disabled, the service should remain enabled"?
Thanks.
JeffDC said:
Would you detail the differences between "Only the receivers should be disabled, the service should remain enabled"?
Click to expand...
Click to collapse
I got that information from the CyanogenMod link I posted. You can see the patch there and see exactly what lines were changed for this fix.
I suggest you read the Android development documentation if you want to know how it all works.
I also found this link, but I can't vouch for its correctness as I don't have enough knowledge of how Android works: http://stackoverflow.com/questions/14548927/android-broadcast-receiver-vs-service
This is a major problem affecting all CM based custom ROMS. The problem is Carbon is not doing anything about it. If you go on their website, there is no new nightly for Galaxy S3 D2LTE - It has been the same ROM since 2014. When you boot the phone, it disables SystemUpdateService. So the phone never sleeps. Waiting for Carbon to Fix this issue.
So here's the real question...
WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
ocd_amp said:
The problem is Carbon is not doing anything about it.
Click to expand...
Click to collapse
If you go to their website, they say they basically stopped working on KitKat except for certain fixes, and are concentrating on Lollipop.
https://carbonrom.org/on-to-sweeter-things/
You can check on their website for more info or if you want to try and contact them. Although I would say it's not really worth it.
I would just use the workaround that I posted (or any other workaround out there). It's not the cleanest solution, but it gets the job done.
ocd_amp said:
WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
Click to expand...
Click to collapse
Check the link I put to the CyanogenMod fix. It has the patch showing the exact line changes and the files that have changed.
update!
Please check this thread.
[MOD] [v7.0.99] Google Play Services with System Update Wake Lock Fix
http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082
frostinide said:
My phone had a constant wakelock and it was draining my battery. I am using CarbonRom on my P769.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime.
Click to expand...
Click to collapse
Thanks a lot buddy.
From a battery drain of anywhere between 20-45% / hour, went straight to 0.3% / hour since the last 4 hours now ( was sleeping myself, but nonetheless the lower end aka 20% drain used to take place when I was sleeping.
Your fix has restored my battery life ( atleast in this short time I do feel that has happened)
Thanks again.
Hi there,
i got rid of the googleupdateservice wakelock by the above hack.
But now i have the fingerprintscannerwakelock keeping my device awake.
Any suggestions for that??
This is the only method I've found to work on my phone to automate the process upon boot. Thanks!!! I've tried about 10 different other ways, from init.d scripts to autoruns to appOps to modified play service apks to you name it.
frostinide said:
My phone had a constant wakelock and it was draining my battery. I am using CarbonRom on my P769.
After doing more research I found that it is because of a recent update to Google Play Services. The Cyanogenmod fix is here:
http://review.cyanogenmod.org/91021
The workaround I used was to enable the service at startup. Only the receivers should be disabled, the service should remain enabled. See the above link for details.
Here is a workaround I use:
Install Script Manager (SManager) from Play Store. https://play.google.com/store/apps/details?id=os.tools.scriptmanager.
Enable Browse as root in SManager (Advanced > Configuration).
From SManager, create a script in /data/local/ called 'startsysupservice' with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
Mark the following options: Su, Boot, Bg.
Change the radio button from 'Is script' to 'Is executable'. This may not be required for CarbonRom but was when I tested this on CyanogenMod. If you don't select this, the CPU may be constantly doing something so it will actually be worse than before (this selection may have something to do with what shell is used to execute this).
Hit Save. Reboot the phone.
Whenever the phone boots up, it will start the service which should stop the wakelock. It may take a few minutes before the script is run, but eventually the service will start. You can use the 'Disable Service' app to check that it worked.
It would be nice if the Cyanogenmod fix in the link above could be merged into CarbonRom and other ROMs for future releases, but I wanted to share this workaround in the meantime.
Click to expand...
Click to collapse
I don't get what you mean by "with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
How do I do that part? All I get is an option to set the name of the script
noob to android said:
But now i have the fingerprintscannerwakelock keeping my device awake.
Any suggestions for that??
Click to expand...
Click to collapse
Sorry, no idea on that one. You should probably create a new post for that.
wasiq224 said:
I don't get what you mean by "with the single line:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
How do I do that part? All I get is an option to set the name of the script
Click to expand...
Click to collapse
Put in 'startsysupservice' as the name of the script. Then edit the script (there is an edit button at the top) and put the following line in there:
su -c "pm enable com.google.android.gms/.update.SystemUpdateService"
After it's saved, edit it again to make sure the contents did actually save. If it doesn't work, you may need to save on your sdcard first and then copy it over manually with a root explorer.
It works but you have to say that this file must have changed permissions.
Thanks a lot.
Dru79 said:
It works but you have to say that this file must have changed permissions.
Thanks a lot.
Click to expand...
Click to collapse
Which are the new permissions for the file?
Hei there!
I just encountered some suspicious behavior on my phone, and I suspect some kind of malware / rootkit.
Background Information
After I accidentally deleted some pictures, I've installed EaseUS MobiSaver to try to recover those.
The scan for deleted files found some of my lost pictures, but also quite some more!
Turns out there are dozens of pictures, respectively screenshots of very random screens like, setting up my clock, browser pages, browsing files, watching YT or VLC, opened apps and so on.
I've attached some of those below.
At first I thought those images are just some kind of framebuffer leftovers or something like that. But then I found that "rootSU.png" image which is baffeling.
Kaspersky, Sophos and Malewarebytes do not find any hints of a infection.
As for my phone / environment
Pocophone F1
PixelExperience 10.0
NoGravityKernel 1.4
Magisk 20.4
So for now my phone is offline, and I would like to investigate what's going on there.
Is there any way to scan the system from external over adb or something?
.
The mentioned rootSU.png picture obviously is a screenshot, made by whomsoever. Yes, an innocent-looking image - sent either via the internet or text - could open your Android phone up to hacking.
Can it be you've run XIAOMI ROOT tool?
BTW, with regards to ADB: If your device is rooted, then install Termux: Termux is a free and open code app that simulates the command shell used in Linux. By doing so, you can introduce all the usual commands and work comfortably from your Android device - you don't need ADB.
jwoegerbauer said:
The mentioned rootSU.png picture obviously is a screenshot, made by whomsoever. Yes, an innocent-looking image - sent either via the internet or text - could open your Android phone up to hacking.
Can it be you've run XIAOMI ROOT tool?
BTW, with regards to ADB: If your device is rooted, then install Termux: Termux is a free and open code app that simulates the command shell used in Linux. By doing so, you can introduce all the usual commands and work comfortably from your Android device - you don't need ADB.
Click to expand...
Click to collapse
Thank you for answer.
No, did not use any XIAOMI Root-tool. Rooting was done via Magisk.
But termux could give me some insight. :good:
Well, despite those suspicious files, I was not able to identify any odd behaving processes.
I guess it's time to wipe and reinstall.
Hi folks, I had a Firestick 4k Fire OS 6.2.7.1 with Wolf Launcher and all was bliss. The OS got updated to 6.2.7.3 and that broke the Home button. I tried all I could find from scouring the XDA forums but nothing worked for me (accessibility apps, adb commands...) The Home key, as well as reboot, always return to the Amazon stock UI. I really miss the Home button returning to the Wolf launcher, as well as long-press of the Home button to get to Network settings because I often switch between my VPN router and normal router. Anyway, I got totally pissed at all the failed attempts and took a chance on rooting the Firestick 4K with Fire OS 6.2.7.3 to see what I could do. I hadn't seen anyone else mention that it could be done on 6.2.7.3, but I can indeed confirm that I was able to do it without issue following the very good 3 part video beginning with this->one (thank you Paul Jones), which begins by showing you how to dismantle the FS4K in order to short it and proceed with the unlocking of the device. It really was not that difficult. Now I have a rooted device with TWRP and Magisk installed and with many possibilities for customization.
I did delete the Amazon home screen (optional in video #3) and when I hit the Home button, it simply went to a blank screen. As I now have root access, with ES File Explorer I was then able to edit the keylayout file for the Amazon remote (/system/usr/keylayout/Vendor_0171_Product_0413.kl) to remap the HOME key to act as a BACK key and that solved that problem, but caused another. If the device went to sleep, I had to reboot the stick because the stock long-press Home button to get to Apps no longer worked. The fix to that was simply to disable sleep mode with ADB (settings put secure sleep_timeout 0). So now, I'm basically to where I was with 6.2.7.1 and the Wolf launcher booting up with the help of FTVLaunchX but now with root access. There's no more Amazon home screen or Amazon app store to get to, however I can still install Amazon apps via the Amazon website to my device. I can also install from a myriad of other sources like Aptoide TV, Downloader...
I still miss being able to long-press the Home button with the Wolf launcher in order to get to Network settings. I've tried all kinds of key mapping apps but none seem to work on Firestick 4K with OS 6.2.7.3. Does anyone know of a key mapping program that actually works with Firestick 4K OS 6.2.7.3? I run Button Mapper no problem on another Android TV OS device but Button Mapper installed on the FS4K does not recognize any key input from the FS4k remote. Its accessibility settings are setup properly but still no joy. Does anyone have Button Mapper working on a FS4k? If so, was there anything special required to get it working? Or, does anyone know where to map events based on key presses defined in the keylayout file?
Alternatively, does anyone know how to create a shortcut on the Wolf Launcher desktop that will allow me to map to the Network settings page? I think you can create shortcuts via ES File Explorer, but I don't know where the Network settings executable is. I know I can just get there with a few clicks via the new Fire TV settings icon, but that's no fun. It would be so much cooler to be able to create shortcuts to specific settings pages or whatever...
I also thought about some kind of wifi widget but the Wolf launcher doesn't allow widgets. ATV Launcher 1.5 does allow widgets but not sure if that works on FS4K.
Sorry for the long post but I'm eager to learn and would appreciate any help or suggestions.
You can try my root Settings replacement.
NewSettingsRoot.apk
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Boot twrp.
adb shell mount -o rw /system
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Vendor_0171_Product_0413.kl from 6.2.7.1 attached.
0815hoffi said:
You can try my root Settings replacement.
NewSettingsRoot.apk
https://forum.xda-developers.com/showpost.php?p=82368799&postcount=1
Boot twrp.
adb shell mount -o rw /system
adb push NewSettingsRoot.apk /sdcard/NewSettingsRoot.apk
adb shell "mkdir /system/priv-app/NewSettingsRoot/"
adb shell "chmod 0775 /system/priv-app/NewSettingsRoot/"
adb shell "chown root:root /system/priv-app/NewSettingsRoot/"
adb shell "cp /sdcard/NewSettingsRoot.apk /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell "chmod 644 /system/priv-app/NewSettingsRoot/NewSettingsRoot.apk"
adb shell reboot
Vendor_0171_Product_0413.kl from 6.2.7.1 attached.
Click to expand...
Click to collapse
Hi 0815hoffi, I have already done that as part of removing the Amazon Home screen. What I am trying to get at is how to achieve long-press Home to get directly to wifi settings, like the Wolf launcher did before it was broken. You can't put in key values in the .kl file to do events. It only contains a value for each key on the remote. Events are coded somewhere else, do you know where that is? Unfortunately, I can't get any button mappers to work on firestick. The other alternative is to find a way to create shortcuts on the main Wolf desktop to get right to the Network settings screen. Is there a way to do that?
In the new settings, where it says to factory reset, do you know if that keeps root and simply wipes the OS clean or does it really factory reset and remove root? Also, what about checking for updates, will that remove root as well? Just curious...
Thanks
NewSettings only launcher the Parts of the original Amazon Settings.
Only Magisk can be Lost, but TWRP is still there.
So if it lost, reflash magisk.zip
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
#!/bin/sh
su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
https://www.google.com/url?sa=t&sou...BMAB6BAgNEAI&usg=AOvVaw1uM2ngLobEuN8uCqybAqNt
Can create shortcuts.
Needs busybox
https://forum.xda-developers.com/attachment.php?attachmentid=5023241&d=1590005330
Thanks, I will give that a try when I get a chance.
0815hoffi said:
NewSettings only launcher the Parts of the original Amazon Settings.
Only Magisk can be Lost, but TWRP is still there.
So if it lost, reflash magisk.zip
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
#!/bin/sh
su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
https://www.google.com/url?sa=t&sou...BMAB6BAgNEAI&usg=AOvVaw1uM2ngLobEuN8uCqybAqNt
Can create shortcuts.
Needs busybox
https://forum.xda-developers.com/attachment.php?attachmentid=5023241&d=1590005330
Click to expand...
Click to collapse
Hi 0815hoffi, the "su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity" command works perfectly in remote adb and opens up the Network settings screen just like I want, but I can't get any shortcut on Wolf desktop to work. I don't know much about programming apk but I tried the "hello world" beginner apk tutorial and was able to save that to my FS4K Wolf desktop. All I really want is the "hello world" apk, but instead of opening a screen with "hello world", on click I would like it to run your script and open the Network settings screen. I don't have enough expertise to be able to program that one line command into an apk. Any help would be appreciated. Thanks again for all your help.
seems like a mess I think i'll stay on 6.2.7.1 as i run magisk and xposed without any issues.
kick60 said:
Hi 0815hoffi, the "su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity" command works perfectly in remote adb and opens up the Network settings screen just like I want, but I can't get any shortcut on Wolf desktop to work. I don't know much about programming apk but I tried the "hello world" beginner apk tutorial and was able to save that to my FS4K Wolf desktop. All I really want is the "hello world" apk, but instead of opening a screen with "hello world", on click I would like it to run your script and open the Network settings screen. I don't have enough expertise to be able to program that one line command into an apk. Any help would be appreciated. Thanks again for all your help.
Click to expand...
Click to collapse
Here a Link to a older Version off my Settings.apk and also the SourceCode as Zip.
This Settings.apk makes many Shortcuts on your Launcher.
Shortcuts you dont need must be hidden in Launcher.
https://forum.xda-developers.com/showpost.php?p=82289861&postcount=1
Maybe that is what you want.
0815hoffi said:
Here a Link to a older Version off my Settings.apk and also the SourceCode as Zip.
This Settings.apk makes many Shortcuts on your Launcher.
Shortcuts you dont need must be hidden in Launcher.
https://forum.xda-developers.com/showpost.php?p=82289861&postcount=1
Maybe that is what you want.
Click to expand...
Click to collapse
Hi again 0815hoffi, I installed the settings.apk and even though I get all the icons on the desktop, they all open the same FireTV Settings page with all options e.g. Sleep, Display & Sound, Network... and the focus is always on the Sleep option. I do want all the icons, but I actually want them to open the correct settings page. For example, when I click on the Wifi icon, I want it to open the Network tab of the FireTV Settings automatically (like running su -c am start -a com.amazon.device.settings.action.ADD_NETWORK -n com.amazon.tv.settings.v2/.tv.network.NetworkActivity) and not see the FireTV Settings page at all. Mayby this has something to do with having previously installed the most recent NewSettingsRoot.apk that just has the one icon and just opens the FireTV Settings page. I manually deleted the NewSettingsRoot directory from /system/priv-data and uninstalled the settings.apk, re-booted and re-installed the settings.apk and still all icons open the same FireTV Settings page.
Is there something else I need to do. I'm so close to what I want to accomplish. Thanks again.
You must allow root access.
Try to delete Wolf Launcher Data and Cache .
0815hoffi said:
You must allow root access.
Try to delete Wolf Launcher Data and Cache .
Click to expand...
Click to collapse
Still no luck and have allowed root access and cleared Wolf Launcher Data and Cache. Each settings icon still boots the same FireTV settings page.
Not sure what to try next. I will try to find a way of putting my network.sh script file on the Wolf desktop somehow and try to find a way to launch it.
Thanks for your help.
SH Script Runner
Can create shortcuts for sh Scripts.
0815hoffi said:
SH Script Runner
Can create shortcuts for sh Scripts.
Click to expand...
Click to collapse
Yes you had mentioned that in an earlier post and I downloaded it but couldn't get it to work properly. I will try it again. If I still have issues, I will let you know. Thanks
kick60 said:
Yes you had mentioned that in an earlier post and I downloaded it but couldn't get it to work properly. I will try it again. If I still have issues, I will let you know. Thanks
Click to expand...
Click to collapse
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
0815hoffi said:
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
Click to expand...
Click to collapse
Sure, that would be fantastic. Thanks
0815hoffi said:
I can customize my settings for you.
But i am currently in Holliday.
So i can do it in around 10 days if you can wait.
Click to expand...
Click to collapse
Hi again 0815hoffi, hope you are enjoying your holiday. You no longer need to customize that app for me. The curious in me couldn't wait and so I downloaded Android Studio to see what I could do and I finally have a working app that makes a shortcut on my screen that launches the shell command to bring up Network settings. I don't know much about Android apk coding (although I do have programming experience) and likely broke a few Android programming "rules" but I did manage to make it do exactly what I wanted, and that is to have an icon on my desktop that directly launches Network settings. This app also could easily be modified to create a shortcut on the desktop and run any shell command.
I've successfully run this apk on my rooted Firestick 4K with the Wolf launcher desktop and it is only designed to run the Amazon Firestick 4K specific com.amazon.device.settings.action command that you sent me. After installation, you will have to grant root access.
I've attached the apk and zipped source code. Feel free to provide any feedback and thanks for all your help.
kick60 said:
Hi again 0815hoffi, hope you are enjoying your holiday. You no longer need to customize that app for me. The curious in me couldn't wait and so I downloaded Android Studio to see what I could do and I finally have a working app that makes a shortcut on my screen that launches the shell command to bring up Network settings. I don't know much about Android apk coding (although I do have programming experience) and likely broke a few Android programming "rules" but I did manage to make it do exactly what I wanted, and that is to have an icon on my desktop that directly launches Network settings. This app also could easily be modified to create a shortcut on the desktop and run any shell command.
I've successfully run this apk on my rooted Firestick 4K with the Wolf launcher desktop and it is only designed to run the Amazon Firestick 4K specific com.amazon.device.settings.action command that you sent me. After installation, you will have to grant root access.
I've attached the apk and zipped source code. Feel free to provide any feedback and thanks for all your help.
Click to expand...
Click to collapse
?
My code is not perfect either.
It has to work, nothing else matters.
?
kick60 said:
Hi folks, I had a Firestick 4k Fire OS 6.2.7.1 with Wolf Launcher and all was bliss. The OS got updated to 6.2.7.3 and that broke the Home button. I tried all I could find from scouring the XDA forums but nothing worked for me (accessibility apps, adb commands...) The Home key, as well as reboot, always return to the Amazon stock UI. I really miss the Home button returning to the Wolf launcher, as well as long-press of the Home button to get to Network settings because I often switch between my VPN router and normal router. Anyway, I got totally pissed at all the failed attempts and took a chance on rooting the Firestick 4K with Fire OS 6.2.7.3 to see what I could do. I hadn't seen anyone else mention that it could be done on 6.2.7.3, but I can indeed confirm that I was able to do it without issue following the very good 3 part video beginning with this->one (thank you Paul Jones), which begins by showing you how to dismantle the FS4K in order to short it and proceed with the unlocking of the device. It really was not that difficult. Now I have a rooted device with TWRP and Magisk installed and with many possibilities for customization.
I did delete the Amazon home screen (optional in video #3) and when I hit the Home button, it simply went to a blank screen. As I now have root access, with ES File Explorer I was then able to edit the keylayout file for the Amazon remote (/system/usr/keylayout/Vendor_0171_Product_0413.kl) to remap the HOME key to act as a BACK key and that solved that problem, but caused another. If the device went to sleep, I had to reboot the stick because the stock long-press Home button to get to Apps no longer worked. The fix to that was simply to disable sleep mode with ADB (settings put secure sleep_timeout 0). So now, I'm basically to where I was with 6.2.7.1 and the Wolf launcher booting up with the help of FTVLaunchX but now with root access. There's no more Amazon home screen or Amazon app store to get to, however I can still install Amazon apps via the Amazon website to my device. I can also install from a myriad of other sources like Aptoide TV, Downloader...
I still miss being able to long-press the Home button with the Wolf launcher in order to get to Network settings. I've tried all kinds of key mapping apps but none seem to work on Firestick 4K with OS 6.2.7.3. Does anyone know of a key mapping program that actually works with Firestick 4K OS 6.2.7.3? I run Button Mapper no problem on another Android TV OS device but Button Mapper installed on the FS4K does not recognize any key input from the FS4k remote. Its accessibility settings are setup properly but still no joy. Does anyone have Button Mapper working on a FS4k? If so, was there anything special required to get it working? Or, does anyone know where to map events based on key presses defined in the keylayout file?
Alternatively, does anyone know how to create a shortcut on the Wolf Launcher desktop that will allow me to map to the Network settings page? I think you can create shortcuts via ES File Explorer, but I don't know where the Network settings executable is. I know I can just get there with a few clicks via the new Fire TV settings icon, but that's no fun. It would be so much cooler to be able to create shortcuts to specific settings pages or whatever...
I also thought about some kind of wifi widget but the Wolf launcher doesn't allow widgets. ATV Launcher 1.5 does allow widgets but not sure if that works on FS4K.
Sorry for the long post but I'm eager to learn and would appreciate any help or suggestions.
Click to expand...
Click to collapse
I have successfully followed your lead and rooted my 4K 6.2.7.3! I have root, magisk and twrp working.
How do i replace the launcher and make Wolf Launcher default?!
yurividal said:
I have successfully followed your lead and rooted my 4K 6.2.7.3! I have root, magisk and twrp working.
How do i replace the launcher and make Wolf Launcher default?!
Click to expand...
Click to collapse
It's all in the "Unlock and Root a Firestick 4K - Part 3" by Paul Jones. I connect using the iso like the Part 2 video as that worked flawlessly. At about the 45 second mark of the video, it tells you where to download the files and how to go about it.
If one's primary focus is getting a custom launcher working with the Home button (e.g. with FTVLaunchX), would I be able to flash rbox's pre-rooted 6.2.7.1 image via TWRP on top of stock 6.2.7.3 after unlocking with kamakiri?
I'm asking because I'm one of the unlucky people who forgot to block updates and had my unrooted stick update to 6.2.7.3.
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.