Database Users

[Q] Genuinely Bricked??

I have looked high and low for a similar thread (detailing my specific problem) so I apologize if it exists and I was unable to locate it. I attempted to flash the PRIMEE ROM on my Acer with all apparently going well until the end. Messages were displayed saying that data, cache, etc. could not mount or something to that effect. I foolishly rebooted only to find that the Iconia will only display "Unrecoverable Bootloader Error (0x000000004)"
That's it. It is completely unresponsive to any other attempts to factory reset. Power/volume does nothing. I have looked extensively for some solution to this problem (attempted Reset button, moving lock screen slider/power-volume combination). You name it, I've tried it. It was briefly recognized by my PC when connected via USB but the AXP drivers were not found and did not install. I'm really flummoxed here.
Again, apologies if this is a duplicate thread but it seems fairly unique in that I cannot get any response at all. I fear that I've really done it this time. Any help would be greatly appreciated.

You DID install the custom clockworkmod app from the dev section, right? Not the one from the market...

Clockwork.....
No, unfortunately I did not. Didn't even realize there was a difference. I did install the Acer Recovery App as well, but otherwise, I think I'm pretty well screwed....

Well mate,now thats a huge problem you got there. If you would've screwed the /system partition np, /data partition,also np.....But uhh,bootloader error...i got the feeling your flashing has screwed up the internal Kernel of the Device,which is connected to the Bootloader,and without a Bootloader...well as its name says,you cant boot anything. Its like a Bios to a normal Computer,if you screw up the Bios,basically you can throw your Motherboard away...and sadly,the tablet comes all together,also i dont think Acer's Warranty will do anything about it aswell since you flashed an unofficial ROM/Kernel.
Your only solution is to send it to Acer,and see if your lucky enough and they fix it for free,if not ...well pay or get another one.
Goodluck with your problem mate.
Respect.

Yeah - kinda figured as much. Very disappointed that I lost it but I suppose I can make one last ditch effort to get it to Acer and see if they'll replace it but I'm skeptical at this point. Oh well - first time for everything. Lesson learned. Thanks for the help all the same.

First, congratulations. You managed to get the unrecoverable bootloader error
--> PM me with your UID, I may help you.

..............Edited..............

You should talk with sc2k I was in the same position you're in with the Unrecoverable Bootloader Error. Sent sc2k the UID for my A500 and he was able get my A500 back up and running again.

first of all, make sure you have a sd-card.
second. dl a stock rom to your PC 1.10.42 for instance, extract with decrypter and put the update.zip on the sd-card using a card reader or maybe your phone.
the put the sd-card back on your ICONIA.
after do the following:
hit VOLUME + (volume up) and power, until it vibrates, keep you finger on volume + and toggle the screen toggle switch.
it will then say formating data and formating cache, and the will start to flash the update.zip
once finished you should be ok.

Hi,
i have the same probplem, can anyone help me?

i have installed a custom firmware from thor and enabled the 3g option, my a500 will only vibrate after reboot with the error "Unrecoverable Bootloader Error (0x000000004)"
i cant read out the UID or anything else ... can anyone help me???

APX Mode runs but i cant recover with nvflash ...

[Q] Is my tablet beyond hope?

For the last two weeks, I've tried pretty much everything I can think of to get my TPT booted again. Symptoms of its current illness include:
Lots of error messages when booting into CWM recovery ("E:Can't mount /sdcard" for example)
If I attempt to boot normally, I get stuck on the Lenovo logo screen.
Randomly I'll boot into CWM recovery and get its logo on the screen, and a line of text, but no menus.
Other times I'll attempt to boot into CWM recovery, and just get a blank screen
So last night I used nvflash to put a new CWM recovery into partition 6: after which I was able to boot into CWM with no errors. (Yay) However, when I tried to reinstall CynogenMod (whose zip file was sitting on my external sd card), it hung during the installation. I rebooted anyway; this time it got as far as the CyanogenMod spinning logo and hung there. I went to bed, and seven hours later it was still spinning away.
Then I rebooted into CWM (without errors) and managed to install CM ROM this time also with no errors. However, again I can't boot. I get as far as the Lenovo logo, and if I boot into CWM recovery I have all the mount errors again.
Along the way I've erased the cache; done a factory reset, etc.
So: nvflash, new CWM recovery (but still errors), reinstalled CM ROM, but can't boot into it.
Any suggestions? Has this machine packed it in - is its hardware faulty in some way? Or is there something I could try which I haven't already?
Thanks folks - I think I've reached the limits of my fixing ability, and would be very gratefiul of some advice.
Thanks again,
Al

In CWM check to see if your /System folder is mounted with read-write privileges or only with read-only. If the former, then your bootloader may have locked itself. Also, what is your device model? If you have a have a US device then it cannot be unlocked as it has been encrypted by Lenovo...
Sent from my ThinkPad Tablet using Tapatalk

Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.

amca1960 said:
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
Click to expand...
Click to collapse
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...

eKeith said:
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
Click to expand...
Click to collapse
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.

amca1960 said:
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
Click to expand...
Click to collapse
No offense intended but you are somewhat peculiar as you are familiar with NVFlash, can determine which partitions to flash with the correct images but you don't have a record of, or can't find your device's model number? Check on your SD Card port flap (or your invoice). Then check out this page for details.
However if you decide to replace the motherboard then search eBay for "thinkpad tablet motherboard" and choose either of the 1838 or 1839 options. Any will fit and work but you probably won't get your (non-US) choice of replacement motherboard so will probably just have to get what's available.
See here for some basic dis-assembly instructions. Then just take you time and the rest will be obvious. Good luck!

Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?

amca1960 said:
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
Click to expand...
Click to collapse
No problem at all.
"I'm in the same boat": I replaced my motherboard with another US version about 6 weeks ago, rooted, installed CWM recovery and steady so far... "with fingers crossed"...
Let us know how it goes...

I really F-d it up

To start, I'm using the Verizon VS980.
While trying to get a custom recovery working on the latest OTA version, VS98026A, everything I tried seemed to fail. I used twrp manager to install the latest twrp into my recovery, but at the step where it reboots into recovery I got sent to fastboot instead. No problem, just try again right? Same problem. I did a little digging and it seems the 26A update locked down the bootloader tight, can't even get loki working, but flashing the 12B aboot was supposed to be a workaround. So I flash the 12B aboot through fastboot. Oops. I must have missed a step SOMEWHERE, even though I'm fairly experienced and careful, because now it won't boot.
At this point I'm thinking I'll just bite the bullet and restore it. Nope. Recovery mode is dead now, as is fastboot. I try to connect download mode, and it appears to work (download mode shows on the phone) but the computer doesn't recognize the phone even exists.
I'm a week away from my next paycheck to find a phone to pull the guts out of, and I have a full TWRP backup of all partitions, including EFS. What are my options, if any? Help... please?
(I also read - too late - that freegee is supposed to automatically downgrade bootloader)

No one has any ideas on fixing it?
I'll settle for ideas that will make it impossible to tell if it's rooted, like make it so it won't turn on or at least remove that ugly warranty-breaking "rooted" flag on the recovery warning. I'll just take it in for warranty claim after.

Anyone have any ideas? Maybe wiring the USB to short it out?
I seriously just need to break it, and soon because my employer can't contact me.
As a revelation that may fix/break the phone, I got the computer to recognize the phone. It came up as a bunch of unformatted drives, and one that was readable that contained an "image" folder.

since your computer can detect it now, why dont u try flash kdz using LGFlashtool ?

zekurosu said:
since your computer can detect it now, why dont u try flash kdz using LGFlashtool ?
Click to expand...
Click to collapse
Thanks for the suggestion, but it wouldn't work. It was detecting it as qhusb_bulk, not download mode.
I followed the steps here, http://forum.xda-developers.com/showthread.php?t=2582142, and partway through dd'ing the aboot my phone shut off. I guess the battery died. Now it won't turn on again AT ALL. Just what I wanted, kind of. At least now I can replace it under warranty.

Caught in a Boot Loop, no escape from reality

I guess I got a little too adventurous by trying to format my SD card to have two partitions, and now …
I'm in a really fast boot loop; adb can't seem to interrupt it, and I can't seem to invoke recovery mode properly.
It says "[FACTORY] : detect recovery mode !" … and goes back to rebooting, or if the battery is low enough, it shuts off.
I ran the battery down to no avail.
So, uh, what's next?

Looks like you're in the same boat as I am! I too have a Nook that appears to be bootlooped; it seems like I overwrote the recovery and boot partitions. I've heard rumors of some sort of tool called "SP Flash Tool" or similar, that works before the device has even fully turned on; I might take a look at it if I get time someday. Or maybe you'd like to give it a try?

saagarjha said:
Looks like you're in the same boat as I am! I too have a Nook that appears to be bootlooped; it seems like I overwrote the recovery and boot partitions. I've heard rumors of some sort of tool called "SP Flash Tool" or similar, that works before the device has even fully turned on; I might take a look at it if I get time someday. Or maybe you'd like to give it a try?
Click to expand...
Click to collapse
SP Flash Tool didn't work for me, because I couldn't create a scatter file. I got it replaced by B&N as a hardware failure, and then I tried to make a scatter file with the new Nook. No dice. Which is unfortunate, because I accidentally deleted some of the stock software. So… I'm trying for a second warranty replacement. :-/

Batshua said:
SP Flash Tool didn't work for me, because I couldn't create a scatter file. I got it replaced by B&N as a hardware failure, and then I tried to make a scatter file with the new Nook. No dice./
Click to expand...
Click to collapse
Sorry for my ignorance, but would you mind adding a bit more detail here so I can follow along (I've never used SP Flash Tool)? So you have a copy of SP Flash Tool that works for this device, i.e. recognizes it and everything, and it asked you for a scatter to flash the recovery? Why did creating a scatter file fail?
Also, regarding getting a replacement: did you just send your Nook back to Barnes and Noble and they sent you a new one under warranty, or was there something else wrong with it?

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.