Database Info

[Q] Recover from failed root attempt thru TWRP?

I tried following this guide to root my HTC One XL, but flashing CWM didn't work. It all seemed to succeed in the Command Prompt, but the phone never rebooted and going into Recovery resulted in the message 'This build is for development purposes only. Do not distribute outside or HTC without HTC's written permission. Failure to comply may lead to legal action.'
I tried several different versions of CWM (5.8.2.7, 5.8.3.1, 5.8.4.0, and an interim build from Modaco), with the same result, before trying this. That completely broke my phone, and all I could get into was the 'development purposes' screen or fastboot. The actual phone was gone.
After stumbling upon the EndeavorU/Evita distinction - my phone is an Evita - I found this and flashed that TWRP recovery. Success!
However, there's no sign of the SuperSU zip. I definitely put it on my phone following the first rooting guide, but either TWRP can't find it or it was lost when I completely screwed my phone up.
Is there any way to get from where I am now to a functioning phone, through TWRP? Searching for 'TWRP tutorial' just results in page after page of 'how to install TWRP', which is the one bit I've actually managed to do successfully so far.
I currently have no phone whatsoever, so things are kinda desperate at this point.

[Completed] HTC Vivid won't boot, possibly after build.prop change

Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.

Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.

jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.

Thread closed.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

HTC One M8 Verizon Bricked - How I fixed it

I had bricked my HTC One M8 while trying to root it and had a very difficult time restoring the OS. After trying numerous things to fix the phone I had almost went out and bought a new phone. Lucky for me the deposit was more than what I could afford for which reason I decided to continue searching for a way to restore the phone online. I've created this thread in an effort to help someone who is in the same position as I had been.
I learned that RUU files were available at HTC's website for all carriers except for Verizon. HTC's website advises that your phone can be restored via Verizon Repair which is accessible within HTC Sync Manager. This didn't work for me. I'd hit the repair button and received a message that there are no downloads available.
The easiest solution is to follow this link: droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu
There are two methods 1) involves the use of a RUU file. This method is a little more difficult. The problem I had with this method is that I'd copy the file to my phone using windows and then reboot into TWRP and the file wouldn't be visible. This is also more difficult because you have to flash your phone with an image for TWRP. I eventually figured this method out. I had to learn how to use the sideload command within TWRP. You also have to learn the fasboot command. The easy way to restore your phone is to use the FUU file as this only requires that you reboot into fastboot mode by pushing the power button while holding the volume button down after which you then click on fastboot. You should see a notification that says fastboot USB at which time you can run double click the FUU file. If the FUU program doesn't recognize your phone you may have to download and install adb and fastboot drivers.
After I restored my phone using the FUU utility I later learned of a number of other methods that would have worked as well. All the methods however require that you have TWRP installed and that you know how to use the adb Sideload dos command. There are many tutorials explaining how to use this command. If your phone is bricked and you can't get into the OS then you'll have to use the DOS command to flash the TWRP image file. There are a number of sites that have ROMS for the HTC M8. When you sideload the file the ROMS automatically self install.

HTCM8Kaber said:
I had bricked my HTC One M8 while trying to root it and had a very difficult time restoring the OS. After trying numerous things to fix the phone I had almost went out and bought a new phone. Lucky for me the deposit was more than what I could afford for which reason I decided to continue searching for a way to restore the phone online. I've created this thread in an effort to help someone who is in the same position as I had been.
I learned that RUU files were available at HTC's website for all carriers except for Verizon. HTC's website advises that your phone can be restored via Verizon Repair which is accessible within HTC Sync Manager. This didn't work for me. I'd hit the repair button and received a message that there are no downloads available.
The easiest solution is to follow this link: droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu
There are two methods 1) involves the use of a RUU file. This method is a little more difficult. The problem I had with this method is that I'd copy the file to my phone using windows and then reboot into TWRP and the file wouldn't be visible. This is also more difficult because you have to flash your phone with an image for TWRP. I eventually figured this method out. I had to learn how to use the sideload command within TWRP. You also have to learn the fasboot command. The easy way to restore your phone is to use the FUU file as this only requires that you reboot into fastboot mode by pushing the power button while holding the volume button down after which you then click on fastboot. You should see a notification that says fastboot USB at which time you can run double click the FUU file. If the FUU program doesn't recognize your phone you may have to download and install adb and fastboot drivers.
After I restored my phone using the FUU utility I later learned of a number of other methods that would have worked as well. All the methods however require that you have TWRP installed and that you know how to use the adb Sideload dos command. There are many tutorials explaining how to use this command. If your phone is bricked and you can't get into the OS then you'll have to use the DOS command to flash the TWRP image file. There are a number of sites that have ROMS for the HTC M8. When you sideload the file the ROMS automatically self install.
Click to expand...
Click to collapse
No offense here, as I'm glad your device is up and running, however the title needs to be fixed.
You weren't "bricked". You were in a simple bootloop of the OS...
You simply flashed an RUU and put the phone back to stock, basically. Next step would have been to set to S-ON and then you're back to 100% stock.
You could have flashed TWRP, put a ROM on the device and flashed that.
If your device never got wiped, and you had a nandroid on it, you coulda installed TWRP and restored your nandroid.
Point is, a brick is when your device will not boot up. It won't turn on, it will not show a charging light when plugged in, the thing is well.. a brick.
You had a simple boot loop, and the differences are a working device and a paperweight.
The tutorial you gave is not even anything about a brick, but "Restore VZW M8 to Stock Android 5.0.1 Lollipop" I'm sure there are already other threads like this, but you were prob looking for a "brick fix" thread, so it's important to understand the differences so that this can help someone else in the future, because this doesn't fix a brick, and someone coming across this may think you just saved them from a paperweight, and that isn't what's going on.
But again, glad you are back up and running.

HTCM8Kaber said:
I had bricked my HTC One M8 while trying to root it and had a very difficult time restoring the OS. After trying numerous things to fix the phone I had almost went out and bought a new phone. Lucky for me the deposit was more than what I could afford for which reason I decided to continue searching for a way to restore the phone online. I've created this thread in an effort to help someone who is in the same position as I had been.
I learned that RUU files were available at HTC's website for all carriers except for Verizon. HTC's website advises that your phone can be restored via Verizon Repair which is accessible within HTC Sync Manager. This didn't work for me. I'd hit the repair button and received a message that there are no downloads available.
The easiest solution is to follow this link: droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu
There are two methods 1) involves the use of a RUU file. This method is a little more difficult. The problem I had with this method is that I'd copy the file to my phone using windows and then reboot into TWRP and the file wouldn't be visible. This is also more difficult because you have to flash your phone with an image for TWRP. I eventually figured this method out. I had to learn how to use the sideload command within TWRP. You also have to learn the fasboot command. The easy way to restore your phone is to use the FUU file as this only requires that you reboot into fastboot mode by pushing the power button while holding the volume button down after which you then click on fastboot. You should see a notification that says fastboot USB at which time you can run double click the FUU file. If the FUU program doesn't recognize your phone you may have to download and install adb and fastboot drivers.
After I restored my phone using the FUU utility I later learned of a number of other methods that would have worked as well. All the methods however require that you have TWRP installed and that you know how to use the adb Sideload dos command. There are many tutorials explaining how to use this command. If your phone is bricked and you can't get into the OS then you'll have to use the DOS command to flash the TWRP image file. There are a number of sites that have ROMS for the HTC M8. When you sideload the file the ROMS automatically self install.
Click to expand...
Click to collapse
Have you not read a single one of my threads?
Seriously?
You went to a third party click bait site to read a how to on work I have posted here many many times (and actively support) and you then come back here to post about this new novel approach? That guy only reposted my stuff to make money. His screen shot clearly shows he needed to re-run the RUU as his /data partition failed to update. Giving any credence to idiots like this is both dangerous and stupid.
This takes things to a whole new level.
Sent from my HTC6545LVW using Tapatalk

Getting root on the BNTV460 is a pain....

Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.

Articul8Madness said:
Just picked this up for the significant other's bday. Bootloader unlocked it with the instructions from @ipdev, and can report that method works. Can't get root.
Does anyone have this device and have achieved root? I'm a bit perplexed, even flashing a patched boot img isn't getting Magisk on there the way that it should.
Thanks!
Important to Note that the 460 has the exact same EVERYTHING as the 450, including build #s. They just gave it double the internal space is the only difference I've seen.
UPDATE: Just bricked the lil' guy. Since the device is encrypted with every system file having a -sign behind it, I went and frolicked around trying to get Magisk on there via ADB. The only way to do that was to patch the boot-sign .img and since I got the new Magisk, I let it patch, flashed, and now voila, nothing but a bootloop. Off to DM Verity my way out of it lol.
Click to expand...
Click to collapse
If it is close enough to 450, and you can get into fastboot, you can try and boot the linked boot.img
fastboot boot m19_ST16C7BNv205.img
Same modifications I had to use to get the first boot image I found to work with BNTV450.
avb, mtk type and signature removed.
Also patched with Magisk 19 (canary release)
For good measure.
https://drive.google.com/open?id=1LgtB2JKCKwLJ64mUlij5Cb_cJrBi8Av1
PS.
Tested above modified v2.0.5 boot.img on BNTV450 running v1.0.2, so it should work on BN v1.0.2 and up.
Good Luck.
Cheers.
PPS.
Just ordered one. (Should show up in 2-3 days.)

Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.

Articul8Madness said:
Hey @ipdev make sure you get the insurance for 2 years. Shouldn't be more than 6-8 bucks. You're going to need it.
I went ahead and tried all the versions that you posted on your OP for flashing; only one was successful - the rest softbricked on the flash. When I went back and flashed the 460 stock on it, it was a different stock and never did run back right - kept getting the blinking red border ring and unfortunately lost the serial #, flash, and every possible entry on the "About Nook" tab - essentially glitching it out. Since I''d only had it for 12 hours, I took it back and swapped it out for a fresh one
So the issues I'm seeing so far are:
1. It's encrypted and says as such - this is what is causing the probs later in flashing and you can't deactivate it from what I see so far without a custom recovery.
2. Patching the boo img via MagiskManager will softbrick it, and I tried with both 18 & 19 inase there were issues with one over another.
3. The device will try to auto update ASAP OTA so make sure you don't connect it to the internet before you disable that function.
4. There is no "official firmware" you can download - B&N will only let you direct download the firmware through notifications. Granted, if you want the only one I was able to find I can post it (it says its Oreo 8.1.0 but it looks different than what comes on the device and its running a crappy Android Go)
5. Its easy to unlock the bootloader per your instructions but after you get the Orange State it takes an awful long time for basic boot (which is more of a personal irritant than a problem, lol)
6. If you patch and flash the boot img with Magisk, you will completely lose the screen. Keep in mind though, if you plug it into the computer you will keep hearing the connect/disconnect chimes. It will keep doing that and neither adb or fastboot will function (even though you can fastboot devices command and it will show a Daemon output).
7. Booting into recovery becomes harder and harder from adb and fastboot once you unlock the bootloader - pressing volume rocker and power does not do it at all.
I'll try your new files and see what happens...I think the guy got a hell of a lot of potential and needs a nice streamlined rom or at the very least root to get the bloat off so its faster. But I think it says something on its crippled nature when the guys at B&N say it ain't worth it in the long run - apparently they aren't as great as even the nook HD line.
Click to expand...
Click to collapse
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304

turtleletortue said:
If you just need a temporary root, I put up this guide a few minutes ago since there was no definite resource about rooting this device. https://forum.xda-developers.com/nook-7/how-to/how-to-temporary-root-bntv460-t3963304
Click to expand...
Click to collapse
I appreciate it, but I've since taken it back. Tell you what though, maybe I'll pick up a used one on ebay and try it