Database Users

[Q] PLEASE help me! Droid X wont boot into recovery

Hello, im SO desperate...
I rooted my Droid X a while ago, and just decided to flash a custom ROM yesterday.
I tried ApeX; worked great. Buy it reminded me of my rooted CM'd G1, so i wanted something else. I decided to try a bunch of ROMs so i could make an educated desition.
Needless to say Bootstrapper worked great.
I tried Fission, then, DarkSlide; GummyJar, Liberty 1.5 & finally, Tranquility.
I must say, the latter one is a bit too buggy for me.. For one thing, lock screen.. doesnt shoe the lock button, so you kinda just have to trust it'll unlock when you swipe your finger, and in most cases, it does... But it aint what i was looking for.
Ive decided i liked Liberty, for its easy to use GUI for customization.
Heres where the problem starts...
My device will boot into Tranquility just fine, but if i try to run recovery thru bootstrapper... uh-uh. Nothing happens, I guet stuck in the Tranquility boot screen (tranquility replaced the default M screen, as well as the animation boot, just like liberty)....
I tried using clockworkmod rom manager and i got the EXACT same results.
I tried formatting my sd card; nuttin... i read somewhere, someone said that "charging the battery to a full 100% worked for him"... it doesnt make any sense, but ive tried it.
I dont know what to do... i mean, my phone works fine, but i dont wanna get stuck with TRANQUILITY!
ive also tried unrooting and rerooting... uninstalling and reinstalling both bootstrapper and clockwork...
If i shut down and boot with the home+power pressed buttons, the phone WILL enter its recovery mode, ive already tried a "factory reset", and all i get is... THE SAME THING! Itll reset my Tranquility as if it were the first time i flashed it.
How can i flash another rom?
I read something about an SPL, but ive no idea what that is nor what to do with it.
Id appreciate your help...
Paul Suquet

First of all it is an SBF, and will get to that in a second, first try booting while holding just the volume down button with the power button. If that does not work, you may want to SBF. This is a process that erases all the data and system files and takes you back to how the phone was when it came out of the box, or 100% stock. After doing this you could root again and then install liberty. If you want a guide on how to SBF, then just Google it. There are many guides available

There is a thread here called getting into clockwork mod the hard way. You could try it before doing an sbf.
Sent from my DROIDX using XDA App

try turning ur phone off, plug it into ur charger let it do the charging animation and then turn it on, it should boot into recovery

Ok people, [SOLVED]
Good news people, i successfully recovered via Verizon's SPL.
Allow me to recap; i own a Mexican Droid X, known as Motoroi X. I rooted via one click root, and installed Fission ROM. Then i wanted to try ApeX, after that, i tried GummyJar, then Liberty, then DarkSlide, and finally Tranquility. I don't know if i did something wrong, of if this is a problem Tranquility has, but after Tranquility, bootstrapper woudn't boot to recovery... so, i wasnt able to switch roms. Tranquility booted just fine, but if i tried to boot to recovery (be it via Bootstrapper, or via ClockworkROM), i got stuck in the "tranquiliy boot screen" (not even making it into boot animation), so , i had to take the battery off, and boot regularly... Trouble is, I didnt lile Tranquilty (all my respect for all dva's but, Liberty 1.5 was my choice, and it is at the moment). I liked the easy customization it has. One of my friends decided on ApeX (he liked the idea of having a bit of Blur).
SO, what troubled me was:
(1) My phone aint from verizon. I live in Mexico City, and my carrier is called IUSACELL... my phone actually had a totally different version on it when i first got it. Ill give out the version it had from factory, to trigger search results towards this page; hence help the multiple people in mexico city who bought their Droid X device via this carrier... my Sistem Version was:
Version.3.0.15.MB810.Iusacell.en.MX​
Ive attached a screenshot of what my "About Phone" looked like from stock.
Cant attach anything, due to being quite new to the forum, sorry about that.
So anyway, I, and one of my best friends (with the same phone and carrier... allow me to say, that in mexico, this phone is not commercially known as a DROID X, its called Motoroi X, buy as you can see by the version MB810, it is the exact same hardware you verizon users know).
Let me say that, my phone was able to keep all my carrier config (that is, PRL, VPNs and such). So, to all other Iusacell Motoroi X users; ROOT YOUR PHONE; AND RUN ANY ROM YOU LIKE!
(2) I heard so much about SPL, but no one could tell me what the heck that was... SO here it is, plain english; its just like doing a firmware update; or, like updating your bios... Let me call it "hardware formatting"... Just a way to get your phone TOTALLY back to stock... Now, this SPL i found, was for Verizons stock, (which had a lot more crap than Iusacell did...), but hell, it saved my @$$. Youll need an Ubuntu Live CD (i use Ubuntu as my daily OS, so... no need to do that), the SPL per se, your phone, and a micro usb cable (no, not a mini USB, we all know motorola did a trick on us and used this micro USB instead of the common mini usb... i suppose they saved some space).
Here are the complete instructions: (remember this will flash your phone, so, be sure to backup at least all the contents of your SD, and; even if there is a slight chance, remember that any of this thing COULD potentially brick your phone, i'm willing to help all i can; anyone out there, but dont hold me responsible, this worked GREAT for me, and it MIGHT not work for you).
Please note that most of these instructions are not authored by myself, i just made a few adjustments to thm and i wanted to make them publicly available to those out there who are in the same ordeal i was:
1: Download the Ubuntu image. It's an .iso file - this means it can be burned onto a cd/dvd. Do so.
2: Once the burn is complete, reboot your computer, set your bios to boot from cd/dvd if you have to.
3: Ubuntu's Menu will appear, select "Try" to boot into the OS without altering your current setup.
4: Download the .sbf_flash utility and the proper .sbf file (note that a file that starts with a period, means to linux, that it is a hidden file. The sbf_flash I got, dont remember where i got it from but it weighs exactly 24KBs. And the .sbf file i found is called "VRZ_MB810=_2.3.34_1FF_01.sbf" weighting 445,393KBs. Dont you dare change the name of these; as Linux doesn't recognise spaces as a character, so, if you changed all the underscores to spaces, Linux' console would not be able to "see" it. If you can't find it, post a reply in this forum, ill see the way of getting it to you.
5: Flash the image onto your phone:
Turn on hard recovery mode; turn phone off; press (and keep pressing): CAMERA + VOLUME DOWN + POWER. Until it comes on. You may have to release all three, and press again power (usually the screen is "blocked").
Now youre in hard recovery mode, and the phone will recognize the computer via USB; so... CONNECT YOUR PHONE VIA USB, duh!
Place the .sbf file to a directory (e.g. Documents)
Place the sbf_flash file into the same directory
Open up a terminal window
Change to the directory that the files are in. [cd] is the command you use; so if in Documents, type [cd Documents].
Ubuntu is caps sensitive, so you need to type the capital "D". If you type "ls" (the equivalent of typing "dir" on Windows Command, or DOS) it lists all the files in the current directory you're in, so type [ls], if you see the files, you're golden.
Type [chmod +x sbf_flash] (ignore brackets) – this command makes sbf_flash an executable. If you've been rooting your phone with ADB Tools you've seen this command before.
Type [sudo ./sbf_flash [name of sbf file, starts with 'VRZ_']] (once again ignore the brackets) – this command runs the sbf_flash file. 'sudo' is the linux-y way of 'running as administrator' in Windows.
It will prompt you for your password - enter it (if your in a Live CD; password is most likely "admin", with no quotes)
Your Ubuntu machine will hard format your phone. Youre probably used to seeing your phone itself perform the installation of a ROM, this is similar. But it aint your phone directly doing it; its Ubuntu... Glorious, faithful ubuntu.
Your phone will reboot, and youll be in a Verizon Stock Rom. You WONT be in the version i described before (but that version was lost since your first Rom...) Iusacell Mexico will work flawlessly... youll still have your telephone line working, and your data plan (if applies). All you have to do now, is run bootstrapper again (this time itll work), your phone is most likely still rooted. If its not, run one click root again; and run your favorite Rom.
Ive tried all roms and decided to keep Liberty 1.5, only downside ive found is; a) camera works, but stock software seems a bit buggy, and b) NO HDMI port. My friend kept ApeX, there IS an HDMI port on ApeX, but as far as I know, youll need to install Stock (Blurry) gallery.
It is a shame HDMI can only be used for picture and video taken from the phone, viewing... I trust sooner or later, there'll be a rom (or a paid app...) able to exploit the HDMI capabilities of the Droid X.
Forum admin: is it ok to publicly plug my twitter account for spanish speaking X users to follow me if they wish to? (Sorry for asking, violated one forums code before, dont want to do it again)

suquet.paul said:
Good news people, i successfully recovered via Verizon's SPL.
Click to expand...
Click to collapse
There, i got the screenshot attached.

Great to hear its working

[Q] [DEFYMB525] Help my old "friend" please :)

Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent

The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).

cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!

Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.

robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!

Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!

Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)

Wiped Phone, OS is gone and phone is unrecognized

Hello everyone,
I have wiped everything using the TWR recovery boot option in a really poor attempt to unroot my phone since it was behaving strangely.
Now it look like my OS is gone and the phone cannot be recognized anymore by my PCs even if I install the appropriate drivers manually.
Since it is no longer possible for me to attempt to flash the phone with a stock firmware using odin, I have attempted transfering the file on the phone using the sd card and installing it through the TWR recovery menu however it does not seem to be a possible option.
Does anyone have any advice to propose to restore the phone with a working OS?
It should still be able to load a recovery file from TWR, I am just unsure where I could get these since they differ from ROMs available everywhere else, I can also make change directly to the device drive using the file explorer so worst case scenario, I suppose it could be possible to copy past all the content of an image over there via the sd card.
Thanks

what happens when you put it into download mode and connect it to a computer? can you even get to odin mode? there is a way to ADB an OS onto it , but its pretty particular and usually not necessary.

youdoofus said:
what happens when you put it into download mode and connect it to a computer? can you even get to odin mode? there is a way to ADB an OS onto it , but its pretty particular and usually not necessary.
Click to expand...
Click to collapse
The download mode seems functionnal on the phone, however the phone is not recognized by any PC which render it useless. My guess is that some files or driver on the phone side got deleted and it is no longer sending the right information to the machines it connects to.
Loading ADB into the OS seems like a neat idea, I didnt know it was possible. I am just unsure if flashing from within the phone is functionnal, my guess is that it probably work, but it is perhaps just a little riskier than doing it from an external device.
Thanks, I will try that, if you have any further advice, let me know
Edit : Oh I just realized you said to ADB an OS into it, yeah I don't thinks its possible, since nothing recognize the phone.

Have you uninstalled and reinstalled the drivers on your computer? Tried a few different computers? And, more likely to be successful, a few different cables?

youdoofus said:
Have you uninstalled and reinstalled the drivers on your computer? Tried a few different computers? And, more likely to be successful, a few different cables?
Click to expand...
Click to collapse
Yes, it also worked perfectly fine a minute before everything get wiped. I am pretty confident the only way to get it back working would be to copy the files into the phone manually, I am just unsure what files I should copy to the root since I have never seen how it usually look.

That's weird because I don't know of a way to wipe stuff in such a way to remove the capability of Odin connecting to a computer

youdoofus said:
That's weird because I don't know of a way to wipe stuff in such a way to remove the capability of Odin connecting to a computer
Click to expand...
Click to collapse
Hmmm I went on cyaogenMod and installed it on my device using the sdcard. Unsure why the stock OS wouldn't work, but at least now the phone is functional.
The phone is still not recognized but it seems like it is slightly better, it now displays as Unknown USB Device (Device Descriptor Request Failed). Which is better than getting disconnected right away from the computer. Now it probably just is a matter of fixing the drivers or the phone further since I have messed around a lot since everything stopped working.
Alright thanks a lot, it didnt occur to me that I probably could install other roms. Im still unsure whether or not I should stick with it but thats the least of my worries right now

garett_ said:
Hmmm I went on cyaogenMod and installed it on my device using the sdcard. Unsure why the stock OS wouldn't work, but at least now the phone is functional.
The phone is still not recognized but it seems like it is slightly better, it now displays as Unknown USB Device (Device Descriptor Request Failed). Which is better than getting disconnected right away from the computer. Now it probably just is a matter of fixing the drivers or the phone further since I have messed around a lot since everything stopped working.
Alright thanks a lot, it didnt occur to me that I probably could install other roms. Im still unsure whether or not I should stick with it but thats the least of my worries right now
Click to expand...
Click to collapse
have you tried a different version of odin? or at least a new download of it? does your computer recognize it when its booted up?

Restore BNTV460 Stock Firmware help

I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.

hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?

turtleletortue said:
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
Click to expand...
Click to collapse
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.

hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
I've been experimenting with my own since I bricked mine as well, and I was able to bring mine to full functionality. Here are a few things I learned. The scatter file in the firmware on the internet is messed up. They made the scatter file incorrectly, so as a result, whenever you flash the device with it you have to completely flash it. Their firmware has also been tampered with and probably doesn't have a serial number in it. So, I bet you wiped all of your partitions, including ones that potentially had the serial number. I dunno how to fix it, maybe see if you can get a new one from B&N for no extra cost. Unless you have a full sp flash tool backup of the device before you bricked it, I'm unsure of what to do for you. I was able to help myself because I only messed up system.img, which I took a backup of before modifying it, and I used the wwr_mtk + sp flash tool guide to make a proper scatter file so I could flash my system.img using download in sp flash tool. (Also sorry that it's been a few months since I've responded, I just thought up how I could fix my own device last night and successfully did it). Also, here is my scatter file.

hassanhassan said:
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
Click to expand...
Click to collapse
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this. NOTE: This rom is only for the Oreo version of this device, BNTV460, so for anybody with the BNTV450/Marshmallow device, your device likely will get messed up by this.

turtleletortue said:
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this.
Click to expand...
Click to collapse
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.

xKroniK13x said:
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
Click to expand...
Click to collapse
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.

turtleletortue said:
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
Click to expand...
Click to collapse
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...

xKroniK13x said:
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
Click to expand...
Click to collapse
Yeah, your device may be completely bricked. The Nook Tablet 7's are confusing due to the two of them being only slightly different, but different enough for disaster to happen.

how to enable Exfat for sd cards on Walmart Onn Tablet (10.1 inch w/ keyboard)?

Hi,
This is my first time trying to root a tablet but managed to unlock the bootloader and install magisk + Edxposed, but was unable to find a module that enabled exfat for the sd card.
Currently it only reads Fat32 formatted cards but I would like to load a 10gb file on there that the device can read.
Any ideas how to go about this? will flashing a custom kernel/ rom help me with this?
All help is appreciated.
Thanks in advance!

rachelld said:
Hi,
This is my first time trying to root a tablet but managed to unlock the bootloader and install magisk + Edxposed, but was unable to find a module that enabled exfat for the sd card.
Currently it only reads Fat32 formatted cards but I would like to load a 10gb file on there that the device can read.
Any ideas how to go about this? will flashing a custom kernel/ rom help me with this?
All help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
I believe you'd need something like vold-posix, along with a version of magisk modified to inject it
But vold-posix is for Android 8.1, although I believe there is a modified 9 build for Pixels.
I'm not even sure if anyone has gotten any custom roms working on any of these yet, but if they have, might be your only option.

Thanks!
As of now I think I bricked it....
I messed around and accidentally erased the system partition, tried to fix it by flashing the image posted here (https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227) and now the screen won't turn on, no recovery mode, no adb..... the device is still detected through the SP flash tools though.
I think the image I used wasn't complete - can anyone upload a complete working image (including a scatter file) I don't care if it's stock or custom, just need something working on the device.
Thanks all!

rachelld said:
Thanks!
As of now I think I bricked it....
I messed around and accidentally erased the system partition, tried to fix it by flashing the image posted here (https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227) and now the screen won't turn on, no recovery mode, no adb..... the device is still detected through the SP flash tools though.
I think the image I used wasn't complete - can anyone upload a complete working image (including a scatter file) I don't care if it's stock or custom, just need something working on the device.
Thanks all!
Click to expand...
Click to collapse
Uploading my WWR backup right now. Kinda slow internet at work so I'll post the link tomorrow morning. Probably around 10am EST. It also has the scatter.
Edit: https://www.dropbox.com/s/pmgbaik485pa9st/ONN%2010KB%20Tablet%20ONA19TB007.zip?dl=0

razredge said:
Uploading my WWR backup right now. Kinda slow internet at work so I'll post the link tomorrow morning. Probably around 10am EST. It also has the scatter.
Click to expand...
Click to collapse
Thanks so much! Will try flashing this when I get home later today

rachelld said:
Thanks so much! Will try flashing this when I get home later today
Click to expand...
Click to collapse
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.

rachelld said:
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
Click to expand...
Click to collapse
Is it still detected by the computer? That's really all you need to flash the ROM. I would be careful not to overwrite or format the unit-specific data on the emmc, like nvram, proinfo, persist, etc. I hope those did not get corrupted on your device.

rachelld said:
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
Click to expand...
Click to collapse
Is your computer still detecting it? What specific errors is SFFT giving you? Did you follow the guide HERE?

Appreciate all the help here! I did follow that guide but I believe I messed up when I deleted the internal storage so the flashing did not work...
Either way I have another one to play with as these were super cheap on black friday - does anyone have any ideas for my original question?
I don't mind flashing a custom rom if anyone knows of one that works with this device.

@rachelld, I don't understand what you mean by "deleted the internal storage" (I don't think you can delete the emmc chip ), but these tablets are basically unbrickable as long as you have a backup or at least the device-specific areas remain in the ROM. There is also no secure boot to speak of.

@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button

@rachelld, what about connecting it to the wall charger?

diplomatic said:
@rachelld, what about connecting it to the wall charger?
Click to expand...
Click to collapse
Nothing doing, no sign of life. Tested the charger with another device to make sure it's working

rachelld said:
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
Click to expand...
Click to collapse
Well no, if you did erase the emmc, then the stock Rom backups shared will not have enough data for you to fully restore from.
And it is not know what partitions can be shared between devices. For example. Secro has device specific data on it. Nvram , also.
So if you have multiple devices. Follow the wwr readback process and fully read back all the partitions from one that works. And flash it back to the bricked one.

rachelld said:
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
Click to expand...
Click to collapse
That's the factory mode, the clear eMMC option should just be another factory reset option.