Related
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.
JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!
jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...
pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.
Hello, everyone. Thanks in advance for any help provided.
Recently, I purchased this phone from Amazon, and I like it a great deal, except for one thing -- the wireless hotspot does not turn on. When I try to activate it, I get the following message, after it checks subscription status:
"Account not set up for tethering
To enable, go to att.com/mywireless or dial 611"
Here is the issue though -- I have the service through Tracfone's BYOP program, and they do not support the feature, even though they do not mind you using it if it happens to work. So, they will not enable it. Further, AT&T cannot help, as the service is through Tracfone and they do not have access to their customer's account information.
I have looked around this excellent forum, and I have found that this issue can be fixed by using ADB shell to enter this command:
settings put global tether_dun_required 0
as well as adding this line to the build.prop file in the /system folder:
net.tethering.noprovisioning=true
I was excited by this, and attempted to do it through ES File Explorer using root explorer -- and then told the option doesn't work on this device. The reason, of course, was because the phone is not rooted, so I figure, if I can root my phone, then I can edit the file, reboot the phone, and enable the hotspot. So, I continued researching.
I learned in the last day or two I learned that you cannot unlock the bootloader on this phone, something to do with Amazon's agreement with Motorola as a way to keep people from removing the advertisements. So, I cannot go that route.
I downloaded KingRoot (version 4.9.6) and attempted to root with it... and it failed, multiple times.
So, I was hoping someone might have a suggestion of what step or steps to take next. Any help would be greatly appreciated.
Hotspot works
On my 32gig Amazon G4 the hotspot works without rooting and no additional software. I've got FoxFi loaded, but it has never been used on this phone, and was not running.
Rincrast said:
Hello, everyone. Thanks in advance for any help provided.
Recently, I purchased this phone from Amazon, and I like it a great deal, except for one thing -- the wireless hotspot does not turn on. When I try to activate it, I get the following message, after it checks subscription status:
"Account not set up for tethering
To enable, go to att.com/mywireless or dial 611"
Here is the issue though -- I have the service through Tracfone's BYOP program, and they do not support the feature, even though they do not mind you using it if it happens to work. So, they will not enable it. Further, AT&T cannot help, as the service is through Tracfone and they do not have access to their customer's account information.
I have looked around this excellent forum, and I have found that this issue can be fixed by using ADB shell to enter this command:
settings put global tether_dun_required 0
as well as adding this line to the build.prop file in the /system folder:
net.tethering.noprovisioning=true
I was excited by this, and attempted to do it through ES File Explorer using root explorer -- and then told the option doesn't work on this device. The reason, of course, was because the phone is not rooted, so I figure, if I can root my phone, then I can edit the file, reboot the phone, and enable the hotspot. So, I continued researching.
I learned in the last day or two I learned that you cannot unlock the bootloader on this phone, something to do with Amazon's agreement with Motorola as a way to keep people from removing the advertisements. So, I cannot go that route.
I downloaded KingRoot (version 4.9.6) and attempted to root with it... and it failed, multiple times.
So, I was hoping someone might have a suggestion of what step or steps to take next. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I would avoid Kingroot as that won't get you rooted. Tethering is iffy at best depending on your carrier. Some will suspend your service if they catch you tethering which they can easily do. Tracfone used to be pretty quick about suspending service for anyone tethering so good luck on getting it to work.
You can use adb mode if you turn on USB debugging in developer settings. Settings > about phone > tap build number a lot of times to enable it.
Then it'll be in settings. And you can use system-wide adb for Windows to make it easier to use ADB.
Or, you can try an app called EasyTether to tether.
ADB and EasyTether
AidenSurvival said:
You can use adb mode if you turn on USB debugging in developer settings. Settings > about phone > tap build number a lot of times to enable it.
Then it'll be in settings. And you can use system-wide adb for Windows to make it easier to use ADB.
Or, you can try an app called EasyTether to tether.
Click to expand...
Click to collapse
I know the ADB commands to try; I listed one of them in the OP. However, it didn't help in my situation.
EasyTether doesn't have a wireless network tether option, and I have tried other apps too -- such as Pda+ -- that will not enable the wireless tether.
What I need is a way to edit the build.prop file, but it appears that I cannot do it without rooting.
Someone mentioned there might be an issue with Tracfone not permitting it. I conferred with Tracfone, and, though they do not support the feature, they do not mind if you can get it to work.
Flashxxposed framework and iinstall x tether
hooks024 said:
Flashxxposed framework and iinstall x tether
Click to expand...
Click to collapse
That requires rooting and OP said he couldn't root.
Wondering if there is any way to get rid of the At&t block on the hotspot feature without rooting. Whenever I try to use it it fails on the authentication process which I believe it´s mostly because the feature is blocked by att&t. I am NOT on att&t network, I´m overseas, I have unlocked the sim just fine. I have no problem with rooting, actually would love to be able to root, but my phone, just before I bought it, got the april security patch which from searching the web up the wazoo, I´ve concluded it cannnot be rooted as of now. I use the hotspot quite often so this is making me consider just selling the v20 and getting something else.
Thanks
emv1031 said:
Wondering if there is any way to get rid of the At&t block on the hotspot feature without rooting. Whenever I try to use it it fails on the authentication process which I believe it´s mostly because the feature is blocked by att&t. I am NOT on att&t network, I´m overseas, I have unlocked the sim just fine. I have no problem with rooting, actually would love to be able to root, but my phone, just before I bought it, got the april security patch which from searching the web up the wazoo, I´ve concluded it cannnot be rooted as of now. I use the hotspot quite often so this is making me consider just selling the v20 and getting something else.
Thanks
Click to expand...
Click to collapse
Where did you here that?
Fadedrobin said:
Where did you here that?
Click to expand...
Click to collapse
where did I hear about the security patch = no root or about the no root=hotspot won´t work?
emv1031 said:
where did I hear about the security patch = no root or about the no root=hotspot won´t work?
Click to expand...
Click to collapse
security patch = no root
Fadedrobin said:
security patch = no root
Click to expand...
Click to collapse
https://forum.xda-developers.com/v2...bootloader-t3519410/post72461784#post72461784
Check post #2597 by Jaistah... I´ve seen the same info in other places, that´s just the one I have more handy.
Fadedrobin said:
security patch = no root
Click to expand...
Click to collapse
https://forum.xda-developers.com/v2...bootloader-t3519410/post72245488#post72245488
Post #2488 is another one.... I found out when I tried following the steps to root my H910 and process was not working.. it´s because of that security patch
emv1031 said:
https://forum.xda-developers.com/v2...bootloader-t3519410/post72461784#post72461784
Check post #2597 by Jaistah... I´ve seen the same info in other places, that´s just the one I have more handy.
Click to expand...
Click to collapse
You could flash a prerooted ROM without rooting your current rom.
Fadedrobin said:
You could flash a prerooted ROM without rooting your current rom.
Click to expand...
Click to collapse
I´d need to see a guide or tutorial on how to do it... The problem with the security patch comes at the initial steps of the process, before even being able to unlock bootloader, flash twrp, etc... until now I have not found a solution to it and everyone points to the security patch. Weird that no one so far suggested just flashing a pre-rooted rom, if it´s really that easy to accomplish root that way.
Try DirtyElf
Lg v20 h910 hotspot fixed
Hotspot on LG V20 H910 GOT FIXED
Dear LG V20 H910 Users,
Did you purchased unlock LG V20 AT & T only to feel frustrated that you own a smartphone but its function doesn't seem to be smart –hotspot is on but it doesn't work, meaning it won't share any wifi to other devices. Are you experiencing this right now? If yes, in fact, you're not alone like Michael Jackson's song. Guess what? I felt that I shouldn't have purchased the phone, at first.
After testing it for countless times, I figured it out.
Now, I am going to share a simple trick, which is a temporary result only. I said "a temporary result" because you need to repeat the process if your restart your phone. However, if you don't restart your phone, you can use your phone as a wifi provider all the time.
IT DOESN'T REQUIRE ROOT PERMISSION AT ALL.
PREREQUISITES
1) Computer
2) USB Connector Type C
3) LG V20 H910 (maybe work on other LG V20, but never tested)
PROCEDURES
Step 1: Turn on Developer Option and select USB Debug
Step 2: Download "terminal emulator.apk" and "setting database editor.apk".
Then install them.
Note:
a) setting database editor.apk is free and used to enable hotspot on LG V20 H910.
b) terminal emulator.apk is used to enable wifi share on LG V20 H910.
Step 3: Run "setting database editor" on your phone and change the value of "tether_entitlement_check_state" [5 changed to 0 (zero) or -1(minus one)]
Step 4: Install ADB driver and LG Universal driver
Step 5: Connect your LG V20 H910 to the computer with USB connector type C
Step 6: You must run Terminal Emulator simultaneously on your phone while it is still connected to the computer.
Run command prompt and type "adb shell" in order to make your computer communicate with your phone. Then hit "ENTER"
Step 7: Type" settings put global_dun_required 0" on the Prompt Command.
Step 8: Enjoy using your hotspot. This process doesn’t require ROOT permission at all.
I am not an expert in Android. So if you need more technical assistant, ask the real experts.
cheansayon said:
Hotspot on LG V20 H910 GOT FIXED
Dear LG V20 H910 Users,
Did you purchased unlock LG V20 AT & T only to feel frustrated that you own a smartphone but its function doesn't seem to be smart –hotspot is on but it doesn't work, meaning it won't share any wifi to other devices. Are you experiencing this right now? If yes, in fact, you're not alone like Michael Jackson's song. Guess what? I felt that I shouldn't have purchased the phone, at first.
After testing it for countless times, I figured it out.
Now, I am going to share a simple trick, which is a temporary result only. I said "a temporary result" because you need to repeat the process if your restart your phone. However, if you don't restart your phone, you can use your phone as a wifi provider all the time.
IT DOESN'T REQUIRE ROOT PERMISSION AT ALL.
PREREQUISITES
1) Computer
2) USB Connector Type C
3) LG V20 H910 (maybe work on other LG V20, but never tested)
PROCEDURES
Step 1: Turn on Developer Option and select USB Debug
Step 2: Download "terminal emulator.apk" and "setting database editor.apk".
Then install them.
Note:
a) setting database editor.apk is free and used to enable hotspot on LG V20 H910.
b) terminal emulator.apk is used to enable wifi share on LG V20 H910.
Step 3: Run "setting database editor" on your phone and change the value of "tether_entitlement_check_state" [5 changed to 0 (zero) or -1(minus one)]
Step 4: Install ADB driver and LG Universal driver
Step 5: Connect your LG V20 H910 to the computer with USB connector type C
Step 6: You must run Terminal Emulator simultaneously on your phone while it is still connected to the computer.
Run command prompt and type "adb shell" in order to make your computer communicate with your phone. Then hit "ENTER"
Step 7: Type" settings put global_dun_required 0" on the Prompt Command.
Step 8: Enjoy using your hotspot. This process doesn’t require ROOT permission at all.
I am not an expert in Android. So if you need more technical assistant, ask the real experts.
Click to expand...
Click to collapse
Will a usb type a to type c cable work too?
cheansayon said:
Hotspot on LG V20 H910 GOT FIXED
Dear LG V20 H910 Users,
Did you purchased unlock LG V20 AT & T only to feel frustrated that you own a smartphone but its function doesn't seem to be smart –hotspot is on but it doesn't work, meaning it won't share any wifi to other devices. Are you experiencing this right now? If yes, in fact, you're not alone like Michael Jackson's song. Guess what? I felt that I shouldn't have purchased the phone, at first.
After testing it for countless times, I figured it out.
Now, I am going to share a simple trick, which is a temporary result only. I said "a temporary result" because you need to repeat the process if your restart your phone. However, if you don't restart your phone, you can use your phone as a wifi provider all the time.
IT DOESN'T REQUIRE ROOT PERMISSION AT ALL.
PREREQUISITES
1) Computer
2) USB Connector Type C
3) LG V20 H910 (maybe work on other LG V20, but never tested)
PROCEDURES
Step 1: Turn on Developer Option and select USB Debug
Step 2: Download "terminal emulator.apk" and "setting database editor.apk".
Then install them.
Note:
a) setting database editor.apk is free and used to enable hotspot on LG V20 H910.
b) terminal emulator.apk is used to enable wifi share on LG V20 H910.
Step 3: Run "setting database editor" on your phone and change the value of "tether_entitlement_check_state" [5 changed to 0 (zero) or -1(minus one)]
Step 4: Install ADB driver and LG Universal driver
Step 5: Connect your LG V20 H910 to the computer with USB connector type C
Step 6: You must run Terminal Emulator simultaneously on your phone while it is still connected to the computer.
Run command prompt and type "adb shell" in order to make your computer communicate with your phone. Then hit "ENTER"
Step 7: Type" settings put global_dun_required 0" on the Prompt Command.
Step 8: Enjoy using your hotspot. This process doesn’t require ROOT permission at all.
I am not an expert in Android. So if you need more technical assistant, ask the real experts.
Click to expand...
Click to collapse
Registered to say that... this WORKED! I bought a V20 from eBay and am using in Canada. Now the tethering works THANK YOU. However, I needed to change:
settings put global_dun_required 0
to
settings put global tether_dun_required 0
For me anyway.
Awesome, thanks again.
A Simple Solution - NO ROOT REQUIRED
emv1031 said:
Wondering if there is any way to get rid of the At&t block on the hotspot feature without rooting. Whenever I try to use it it fails on the authentication process which I believe it´s mostly because the feature is blocked by att&t. I am NOT on att&t network, I´m overseas, I have unlocked the sim just fine. I have no problem with rooting, actually would love to be able to root, but my phone, just before I bought it, got the april security patch which from searching the web up the wazoo, I´ve concluded it cannnot be rooted as of now. I use the hotspot quite often so this is making me consider just selling the v20 and getting something else.
Thanks
Click to expand...
Click to collapse
Go to Play Store and find "Settings Database Editor" by 4A (app id=by4a.setedit22).
The icon for the app (both on Play Store and in Android) is a blue "Settings" gear on a red field.
Install and run.
Navigate down in System Table, and find "tether_entitlement_check_state".
Edit Value from "5" to "0".
DONE
Takes 30 seconds
All of these other steps are not necessary.
cheansayon said:
Step 7: Type" settings put global_dun_required 0" on the Prompt Command.
Click to expand...
Click to collapse
Great solution, thanks! Only one correction for Step 7: the correct script is: "settings put global tether_dun_required 0"
hannor said:
Great solution, thanks! Only one correction for Step 7: the correct script is: "settings put global tether_dun_required 0"
Click to expand...
Click to collapse
Does this route tethering through the main phone data line? Or is it routed through as Hotspot data? I ask because Hotspot data is typically throttled and data capped. Data for the handset it's typically not throttled or data capped.
Thanks.
Who knows....
kaluna00 said:
Does this route tethering through the main phone data line? Or is it routed through as Hotspot data? I ask because Hotspot data is typically throttled and data capped. Data for the handset it's typically not throttled or data capped.
Thanks.
Click to expand...
Click to collapse
Honestly, it could go either way.
This bypasses the handset seeking approval from the mother-ship to allow you to tether. So, usage is probably un-monitored, and therefor un-metered.
However, I received a nasty-gram (by way of SMS) from my provider reminding me that hotspotting data from my handset was an extended service and cost extra to do so.
I received this message once... in 3+ years of hotspotting at least once a week.
My best guess is that it is not metered, and thereby considered handset data (by your criteria).
But, I'm not sure how to even test possible answers.
Having Hotspot Data on your plan would probably invalidate the question...
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone
This is amazing! Will try it here in about an hour and report back
Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app
djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all
Hope it works
Sent from my Pixel 2 XL using Tapatalk
PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.
Didn't work for me. Any tips to try?
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol
collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.
Tried on my P2XL device and no luck..
nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.
tried this plus added recommendation and no luck. Verizon Pixel, 8.1
Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice and install it. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
First thing you need to do is ensure your player is unlocked. When in the fastboot screen it should show the lock state. If it's locked, you need to run this command twice from your computer: "fastboot oem unlock"
Okay, now you're ready to go, you need to extract the factory firmware and use adb to flash it. Extract the main firmware file. Inside is another large zip file with the broken out recovery and system images. Extract that file also.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the flashed bootloader: fastboot reboot-bootloader (If it doesn't reboot in the bootloader, unplug and use the hold button and plug in to get back to the bootloader screen)
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
TWRP Might ask if you want to keep system Read Only. Push the button that says Keep Read Only.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v17.3.zip (Or whatever version of Magisk you happened to download)
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe/factory reset of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip This will disallow updates to be applied.
Remount the system partition as readwrite
cd /
mount -o rw,remount /system
Disable otacerts.zip
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
exit
exit
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sdcard/disupdate.sh
You should then use adb shell again and move the script into place
adb shell
su (accept request on screen if it asks to become root)
mv /sdcard/disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots. If there is no directory /sbin/.core/img/.core/service.d then Magisk isn't likely properly installed. You might need to reboot or something to get it to load.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Thank you! My player started random reboots then lost wifi on android 8. This worked great and she seems to be running properly again.
The final step fails for me. I run adb push to move the script and it looks like it does it, no error message but the file doesn't copy. Not a big deal, I can watch netflix again.
---------- Post added at 12:32 PM ---------- Previous post was at 11:47 AM ----------
I worked around it. What I did was push the file to a location I had permission to write to on the nexus.
Then I copied the file using a root powered file manager, Solid Explorer in this case, to /sbin/.core/img/.core/service.d/
Hopefully this helps others to keep their nexus player alive. 7.1.2 runs very nice.
Update: After running great for the past week my nexus player how just sits at the black google screen.
You lost me at the "USB OTG adapter"
I wonder if your problem with Ver. 8 (which is Oreo?) has to do with unplugging or losing power to the device? - After I lost power for just a second (blink) the unit partially bricked and finding your post got me to a different page that showed how to sideload (via ADB) the ver. 8 OTA onto the device.
That worked OK until the unit lost power again (I unplugged it to move it). The problem returned and since I don't have the mouse adapter, I just tried to sideload a ver. 7.1.2 OTA but that refused to load with an error message that I didn't grok but probably meant that it was incompatible with stuff that Ver. 8 had on the filesystem.
So I restored again the latest Ver. 8 ota.zip and for now (until the next power off) it is working.
-----
Seems like they have a problem serious enough thought that another update will have to happen.
-----
Thanks!
snowzach said:
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
Once you are in fastboot mode, you need to extract the factory firmware and use the minimal adb to flash it.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the old bootloader: fastboot reboot-bootloader
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v16.7.zip
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip
This will disallow updates to be applied
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
You may also need to use adb shell again and run:
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Click to expand...
Click to collapse
First off great starting point to get nougat back on nexus player but a few points...
a) I had to do "mount -o rw,remount /system" after SU to get write on /system
b) The method you outlined for running script on boot didn't work for me and i ended up having to use https://play.google.com/store/apps/details?id=com.k2.bootshellprokey with the script you provided
Other than those two points worked great and staying on 7.1.2
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
texasjmzmd said:
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
Click to expand...
Click to collapse
I answered these questions. However I get an error of failed to copy when I adb push the sh file.
Had to do this 4 times to get it to stick. The second to the last step preventing the update is what was difficult. It kept upgrading to Android 8. I couldn't get the script part to work. So far so good this has worked for me. Kibmcz's "a)" suggestion allowed me to stop the automatic upgrade. So far it's sticking and working really well. I did this to prevent the black screen of death that everyone's getting with Android 8.0 upgrade.
Got the OTG adapter - questions & comments
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
A couple of days later, the 4 balls animation returned. Brought up Restore, TWRP and attempted to revert to a backup made with it but it would not restore it. So... Flashed boot and Flashed system and it came back to life for another couple of days. TWRP doesn't load anymore though so the un-altered system without the script still doesn't want to load Oreo as there is a copy of Oreo still there that didn't pass verification.
Still busted every couple of days though.
ggregor said:
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
Click to expand...
Click to collapse
I couldn't get the script to work either.
Did this August 21st. Still working today [Sept 2].
For those of you still having trouble, it seems like you are having an issue with installing Magisk. When you have Magisk installed, it actually creates linked directories in the system partition. You aren't making changes to system. I am going to update the original post to push the script and then move it to a directory that Magisk manages. That hopefully fixes everyone else.
Thanks for posting and updating your instructions. I used my own workaround for keeping my 3 Nexus Players alive and locked on Nougat 7.12...
Do you have a theory on how to make the LED light work again on those NPs that have gone dark and unresponsive to the OTG connection from a laptop or PC?
Instead of rooting or using Magisk, just use TWRP and its file manager to rename the ota certs file. You can also use it to put in the script if you want, or use it to remove gms and gsf to stop GPS from updating which actually is more the problem - people on lineage 15.1 are still bricking.
Did this August 21st. Still working today [Sept 20].
Mine is dead now.... No light on powerup, quickboot screen or any other sign of life. Forced to move on to a non-branded Android box. Boot loop even started after using LineageOS 15.1 (which required starting with 8.0 Oreo)
thanks for the guide, I did this and it worked great. Used the script as well and all 3 of my players are still working 2+ weeks after doing this.
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Triumph said:
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Click to expand...
Click to collapse
Which specific streaming apps are you referring to and what do the error msgs say?
growsonwalls said:
Which specific streaming apps are you referring to and what do the error msgs say?
Click to expand...
Click to collapse
They are HGTV, Travel Channel, Cooking Network, and ABC.
When I open them up they show a "Live Channel" option, and I enter in my online information for the channel (That has always worked in the past, and works on my Nvidia Shield device that isn't rooted.)
If I choose the Live Channel quick enough it tries to play then times out and says "There was an error playing this content."
If I open the app, and stay at the main screen for a minute or so, the Live Channel option disappears from the header, and I don't see it again, until I reboot the player.
I can play previous show episodes, just not the live stuff.
Triumph said:
They are HGTV, Travel Channel, Cooking Network, and ABC.
I can play previous show episodes, just not the live stuff.
Click to expand...
Click to collapse
In order to recreate this, I am still missing vital information.
Is this happening inside of Kodi or did you download these 4 apps (channels) through the Google Play Store?
In Kodi, I've never seen a "Live Channel" option for these channels, just several old episodes listed.
As for the 4 channels from the Play Store, they each have a stream live option where you sign in to your tv provider. My tv provider isn't on that 'sign in' list so can't watch it live.
If in Kodi, were they installed from the Kodi repo or did you install a 'build' that came with them already installed?
Or is there a different streaming app that is hosting these apps?