Nook Tablet: Doesn't Boot, Hold Charge, Etc. - Barnes & Noble Nook Tablet

Background:
I'll admit, I've been messing around a bit too much with the software/hardware of my Nook Tablet without any real prior knowledge, so this came of little surprise when it eventually stopped working. Originally, I had Rooted my Nook Tablet to expand on its capabilities, but wasn't satisfied; therefore I attempted to run CyanogenMod 10.1 on the Nook Tablet, but I realized (a little too late) that the version of ClockWorkMod I was running was too old to handle Android 4.1/4.2 Jelly Bean, which got the Nook stuck in a bootloop. Additionally, in the process I'd messed up the partition tables and they are no longer intact at all. I then proceeded here, to the XDA Forums, to find a potential solution, and found one that pretty much worked all the way up until I was physically restoring the partitions; I had ADB into the Nook and used a few partition images. After restoring the most important ones I went around to fix the others lesser ones, but the terminal on Linux said I'd run out of space.
After that the Nook had been shutdown with out fully restoring the partitions (probably leaving them corrupt, for all I know) and this is the end result:
1.) Nook cannot boot to any sort of recovery or operating system.
2.) Nook will not recognize and boot to an SD card upon start-up.
3.) Nook doesn't hold charge even though battery is tested and working.
4.) When Nook boots up, there is a large "N" logo and nothing else happens.
So the boot sequence is like this:
1.) Press power button; gives battery low/charge for 15 minutes error.
1.) Plug-in and charge for 15 minutes.
2.) Nook powers on and boots to "N" logo.
3.) Cannot do anything before/after.
Is there any way I can remedy this? Preferably I would like to restore the Nook Tablet to full working condition and restore the operating system to a stock ROM.
Note: I have a Nook Tablet 16 GB.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to the Nook Tablet development section. There are tons of guides to unbricking your tab.
The Ubuntu total wipe and reflash method
Unbrick Nook Tablet on Windows Vista/7
I'm pretty sure there are many other methods, but those 2 are the best ones I found so far (with a lot of "thanks" feedback from users).
About the battery level: use any regular microusb charger for a cellphone. Let it charge overnight, then proceed to unbricking.

sagirfahmid3 said:
Go to the Nook Tablet development section. There are tons of guides to unbricking your tab.
The Ubuntu total wipe and reflash method
Unbrick Nook Tablet on Windows Vista/7
I'm pretty sure there are many other methods, but those 2 are the best ones I found so far (with a lot of "thanks" feedback from users).
About the battery level: use any regular microusb charger for a cellphone. Let it charge overnight, then proceed to unbricking.
Click to expand...
Click to collapse
I should've added the "Bro, Do You Even Read?" to this response too; I should allude to you the fact that I have tried several methods from the XDA Forums (as I mentioned previously), including the total wipe method on Ubuntu as well as Windows (my Macs are undergoing hardware/software upgrades right now, and they're probably too old to be any use for me anyway). Additionally, while the results/symptoms are similar to other cases I hear here and other places on the web, there seems to be some uniqieness about it, which leads me to believe that the device is more than "just bricked".
Tell you what, when I attempted to restore the partition tables initially, it got messed up leading to the device's demise. The internal EMMC as well as any sort of recovery and bootloader has been completely obliterated from existance. The device can no longer physically recognize the micro SD Card Slot, and half the time it won't even boot on command (I have to wait until it feels like doing so when charging).
Secondly, I have tried other USB cables and adapters and I've gotten the same results, I even left it at a B&N store to charge during a one week period and the same results occur; doesn't keep the charge. The battery was swapped with another device and was proven to be working as it charged in the other device just fine.

I think I should also mention that the Windows-restore Method that you linked me to mentioned the following:
"Update: If you have followed every steps from above instruction and still getting "please contact nook support" then you have "erased" factory partition table which means that now your device doesn't have any "build history" associated with it, like serial number, build info and so on. That means that factory ROM will not be able to run without getting that information from your device so your best choice is to call BN or go to BN and get a warranty or replacement service."
And as I said in the initial post, the partition tables are no longer intact, in fact, they no longer exist at all. And when I did bring it to Barnes & Noble, they were of no help whatsoever in my two local stores, so . . .

I guess you're SOL then...
(I always make sure to create a backup of the /rom partition before doing any major mods. That's where the serial number and wi-fi mac address are stored).
Try and see if this works http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/

Related

[Q] Mac OS wont recognize Phone SD just EXT

Ok im New to the whole Android thing , but i am excited to finally get on board with a Google phone. I like the iphone, i have no problems with it, its just the new carrier wont work with it. I have 2 macs, Macbook and MacPro (hackintosh) Im am very familiar with computer and how stuff works, I understand 70% of the commands i have to copy and paste from forums to make things work. Right now i am stuck (and im 100% sure its not due to the fact my Desktop isnt legit)
I got this phone used last week, fresh install with a certain rom (i dont know wich one, not sure how to tell, have no ideal how to get factory roms etc.) the phone is unlocked.
Before i plug in the usb to my phone, i enable debugging, then i select, USB mass storage.
WHen i connect i get the " Mac os X can't repair the disk "NO NAME"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then the External will mount, (so will the internal) here is what disk Util shows
It says the internal is 2.36 gb with 12.74 gb avail and only 980mb used, 0 number of files..
Now when i try to unmount the external, its fine, when i try to unmount the Internal, (NO NAME) all hell breaks loose, i wont let me, sometimes i get an error saying i cant unmount etc.. when i unplug it from the computer its still on my desktop, DiskUtil goes crazy and doesnt respond, then eventually any program that can see the drive will not respond (finder, activity Monitor)
anyone know a way around this? do i need to put a differnt install on it? its a t-mobile phone, should i just dl their newest update? how do i actually do that? their webpage? thanks for the help
j
I do not think Apple wants ppl to use Android..... Jealousy I guess, You can try a couple of things one would be Downloading this software from: Salling Media sync app for mac This usually works but not all the time and I do not know why.
This will work until you find a real fix from TMO, Samsung. It takes a few steps but works:
First open Terminal (applications - utilities - terminal), then type in "gpt show /dev/disk1" without the quotes. Make sure USB Debugging is turned on. Plug in the phone, it will be detected in Finder as a TMO CD, after a minute that will disappear, you can eject it to get there faster. Then mount the USB device, wait for the disk error message and select "Ignore" then unmount the card then remount it. Then in the Terminal hit Enter to run the "gpt show /dev/disk1 command". You may have to run the command more than once. It should recognize your card at that point. Then you can access the card as usual.
BTW, THIS IS WHY I HATE APPLE, they are excellent at making thing compatible for their products but, give little support to others......
yeah i tried that, but when i plug in the phone Network settings pop up no TMO CD
you think it could be because of the custom rom that was installed? I tried to find out wich one i had, but no luck..
it seems like there is somethign wrong with the 16gb partition... maybe a fresh install?
Yes when All else fails fresh install also you might find someone with a windows based computer to check it it amke sure the phone is not the problem
Yeah thats my next option.. VM wont work because OSX see's the phone 1st.. i cant just get win7 to take control without osx getting their hands on it..
now being familiar with the iphone. i would just find a stable version open itunes and select what version i want to install.. seeing how i bought my phone rooted and unlocked. and not knowing what ROM i have installed, do i just goto t-mobile's site and get the latest software from there?
connected fine on a windows machine.. this really sucks.

[Q] Help! Soft Brick/Possible Hard Brick

First off, I'll be brief, but I'm new on the site. I've been around looking at the forums here and there which helped me to previously root my Atrix.
I had intended to return this phone, but it's watermarked which sucks. Whatever, there's nothing I can do about it now. For fear of it not being returnable I decided to wipe the Atrix and unroot the phone. I first ran aRoot to unroot the phone. Everything worked to basic perfection unrooted. I deodexed back to 1.83 to get rid of GingerBlur, which it did. I did notice, however, that the phone would still boot into Tengar's CWM Recovery Mode when plugged into a wall charger while powered off. In a fit of absolute stupidity, I formatted everything that it is possible to format while in the CWM Recovery outside of my microSD card. Now when I reboot the phone it sticks on the "Dual-Core Technology" with Moto logo screen. No boot whatsoever.
After freaking out for a good hour or two I tried a couple of things I saw on this website because I can get into the general phone recovery (by holding down the volume button). All of them have been no-gos for me so far.
The recovery from a soft brick on the wiki gives me "Cold-booting Linux/ Reading ODM fuse: 1" when using Early USB Enumeration and sits on that indefinitely which takes out ADB. I can boot into Android Recovery mode, but, as has been noted on that topic, you can't load any update.zip files as the microSD card is not mounted. I also tried doing a wipe data/factory reset via Android Recovery but that's a no-go as well. On the bottom left it does say "E:Can't open /cache/recovery/command" in AR. I thought about flashing back to 1.83 or older using RSD-lite, but I get "Battery is too low to flash" every time when going into RSD mode.
Outside of these problems, my phone will turn on when plugged into a computer, but only to the same screen mentioned earlier and it takes nearly and hour after the charge has been (presumably) completed. The phone will not charge via USB wall charger - instead the phone turns on. I have no flashing red LED or any other warning messages nor can I turn the phone on without it being plugged into a USB cable.
When AR is run for factory reset:
.Performing BP clear...
.E: open mdm_ctrl ok
.E: bp status before bp power down 0
.E: (0,success -1, failed, 1, panick), return result: 0 after BP shutdown....
E: begin BP power up.....
E: reture value of bp start up:-1
E: bp status after bp power up 4
....E: from flash to normal mode
....E: open dev
E: engine init finished
E: Successfully wrote 13 bytes.
E: Transferred 13 byte(s) CMD opcode = 0x0012 to aux engine succeeded.
E: write finished
E: Attempted to read 12 bytes and read 12 bytes.
E: Successfully read 12 bytes.
BP clear complete successfully.
Formatting DATA:...
Formatting CACHE:...
Data wipe complete.
After which I let it reboot. It sits there at the logo, still, no matter how long I leave it plugged in.
As a side note, last I remember, my phone was set with USB debugging on and to be a Mass Storage Device.
Please, I'm desperate right now. This is going to be my only phone for the next two years, whether I like it or not, and I'd like to keep it (besides, I do quite like it).
Post deleted
Sent from my Motorola Olympus using XDA Premium App.
i did not understand quite well your situation but in a desperate time this is what i would do:
to bypass the low battery, you need a usb cable:
open like the picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
insert the red one between battery and its connector on the phone (the + on the battery will tell you the correct "slot" ) battery needs to be correctly inserted.
plug to the pc
the phone will think it's fully charged.
then plug a normal usb cable to pc and phone enter rds mode and let the process begin, full sbf (not service) advised
let it go
Well, as helpful as that was, the cut-a-USB-to-charge trick didn't quite work for me. Might anyone else be able to help me? My phone is as dead as a door nail atm.
same here...
Me too, have a very similar problem, but not because of flashing ( I think so ) ..
Chronology : have use phone regularly with Froyo, rooted, no unlocked bootloader yet, no micro SD card ever inserted, can access internet with small download speed.
The problem arise (as per I remember correctly),
first, I install Calc-P (sideload from androiddev dot orkitra dot com) , install then use it, no problem ..
second, update Android Assistant from market, install and use, no problem
third, download then install Smart Taskbar (com.smart.taskbar)
download went fine, but during install, it takes like forever to finish, AND it doesn't!
unfortunately, my battery on that time was dried off, and the-install-takes-forever just died.
after a full recharge, I turn on, and used the phone ok for a while, until I realize there are some app (from market) that I don't regularly use, so I decided to uninstall it.It also, TAKES FOREVER with nice black&white rollover progress bar.
I think, something went wrong, so, panickedly, I turn off the Atrix.
And now, just stuck on Rethink Possible bootscreen, no where else.
-tried android recovery : no go
-tried android boot (no bp) : no go
-tried fastboot : no go
Someone, please, how to solve this.
Problem solved by wiping all data and apply pie crust (from navalynt) onto those already crispied gingerbread ..

[Q] touchpad 16 gb only showing 12 gb of space?

I just reset my touchpad. (doctor + on device data wipe). My touchpad used to 14 gb before this now it shows 12gb. Any suggestions?
did you install touchdroid android, or modify the partitions in any way?
also, check your installed apps/preware veifry app space usage
I tried that chroid ipk and thats it thats why I doctered my device because I wouldent let me use uberkernel anymore.
curious...do you know how to use novaterm?
No idea man...
blerg...the big problem i have with webOS doctor is that it doesnt restore the partition table...it doesnt even touch it...so im thinking that either something modified your partition, or you can try to reinstall 3.0.2 again...
if you knew how to use novaterm, we could check the partition tables to see if theyre valid, but if you dont have the sdk/pdk set up, its not worth it to do it if you dont know how to use it
Is there a toutorial I can follow that can help redo my partitons?
i TOTALLY do not recommended doing that! As far as I know, that is the only surefire method to bricking your touchpad if you miss a single character on the command line.
Id say google it, but you might be better off taking the 2gb hit and wait for some partition guides to come available. Most of the advanced nova stuff is on webosinternals.com and the palm SDK site, so you cam start your research there.
Also ask some other 16gb users who can use nova to post the size/locations of their partitions, that way you have a reference point
Sent from my HTC Sensation Z710e using XDA App
Thanks man... ill try that do you think CM7 will rest the partitions.
UnderZone7 said:
Thanks man... ill try that do you think CM7 will rest the partitions.
Click to expand...
Click to collapse
highly, unlikely, if anything you will end up with LESS spaace on your webOS partition because CM will need to reallocate partition space for its own use
My Touchpad shows only 12,6 gb too, but it've been that way all along. Other strange thing was that i wasn't able to update from 3.0 to 3.0.2 by OTA, it just showed me "your device is up to date", had to use Doctor. Hope that all those things are just a software hickup, not a damn hardware malfunction.
Unrealwolf said:
My Touchpad shows only 12,6 gb too, but it've been that way all along. Other strange thing was that i wasn't able to update from 3.0 to 3.0.2 by OTA, it just showed me "your device is up to date", had to use Doctor. Hope that all those things are just a software hickup, not a damn hardware malfunction.
Click to expand...
Click to collapse
wow, that is strange... i hope it isnt a hardware defect either...unless webOS 3.x.x takes up 2gb
heres how you can check (make sure you have palm SDK, novaterm and a calculator handy )
-connect TP via usb straight to your pc (no usb hubs!)
-on the TP, either hit cancel or do nothing, do not enter usb mode! you dont need dev mode either.
-load up novaterm
-hit connect
-type "df -h" (without the quotes)
-add up the size totals, and see whatcha got!
if possible, please post results, im curious to see if its hardware or software
I have the same issue.. I will try it out once I get home later today
Solidus_n313 said:
-connect TP via usb straight to your pc (no usb hubs!)
-on the TP, either hit cancel or do nothing, do not enter usb mode! you dont need dev mode either.
-load up novaterm
-hit connect
-type "df -h" (without the quotes)
-add up the size totals, and see whatcha got!
if possible, please post results, im curious to see if its hardware or software
Click to expand...
Click to collapse
I've got some problems with novaterm - it shows an error (which could be ignored) after every keypress, it doesn't scroll proper, ant it doesn't allow me to copy/paste. I've made a screensot of the beginning of that long output thing, here
http://dl.dropbox.com/u/21304732/unt.png
BTW. i've found that it's quite common: here is the thread of a guy who has 12.6 gigs too http://forums.precentral.net/hp-touchpad/298469-where-my-16gb.html
I also had 12.6 GB free space when I received my TP. But I was able to update it to 3.0.2 via OTA without any problems. Though, the free space was still 12.6 GB after the update.
I have a 32gb only showing 23.5 gb available. It seems to lose 2gb each time I do webos doctor. Hopefully there's someway to reset its partitioning.
I'm only showing 12 Gb as well.
Here's what I show in Novaterm:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
theniel said:
I have a 32gb only showing 23.5 gb available. It seems to lose 2gb each time I do webos doctor. Hopefully there's someway to reset its partitioning.
Click to expand...
Click to collapse
I would hope that is not the case....can anyone verify this? Would make WebOS doctor a pretty crappy restore tool.

[Q] Soft Bricked Nexus 4

Hi there, first of all I need to say that I'm sorry if I started this topic in the wrong section, second of all sorry for my english. Hope that I will be undrestood.
On my Nexus 4, I was running CM 11 custom ROM, and I've heard about the brand new one named Lollipop 5.0 . I've found Mako build for that new ROM and tryed to flash it via Rom Manager (Play Store). It runned smoth without any issues even if it's just an alpha release. But one day I've checked my storage tab, seen there that almost half of entire memory it was full, and I didn't had than just a few low space requiered apps. I tough about it and I realised that Lollipop ROM was installed OVER CM 11, of course not the ROM by itself but even if it wiped all data before to install the Lollipop, all junk stuff from CM 11 remain there.
So i wanted to reinstall a fresh copy of that Lollypop by using Nexus Toolkit.
Things would have been fine if my computer suddenly restarted while processing the flashing ROM, right after it wiped everything or something like that. Bad luck, huh?
So now I've got a soft bricked Nexus 4, where bootloader apparently still works but without recovery wich now it's replaced by and android dead icon and over that big red triangle, and when pressing the correct combination of volume + power buttons should give me fastboot, instead of that I'm stuck on "Download Mode". One more thing I forgot to mention, If I'll boot up device and run straight without pressing nothing, it will pop out the Google loading screen and it will stuck there, doing nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read many threads about how to unbrick devices. Still got no answer because they refer at other soft brick posibilities, that includes pushing backups or what requires to simply flash them by fastboot or ADB, the problem here is that those posibilities will be great if I CAN get acces to my phone, what that means is I cannot run "USB debugging" to get my device being recognized by computer in this dead stage. Even my drivers are installed and "Download Mode" is active where should, as I read, grant me the acces to device even if it's not waked up completely. And second option to unbrick it leads me to the recovery mode (wich is dead) and restore from there a previous backup, and even if I had access to it, I DON'T have a backup.
So the big question for you guys about this annoying mishap: "Is there still a possibility to push files from computer to device, or I need to visit an authorized service?"
Thank you in advance. Peace.
Cosmin Petrisor said:
Hi there, first of all I need to say that I'm sorry if I started this topic in the wrong section, second of all sorry for my english. Hope that I will be undrestood.
On my Nexus 4, I was running CM 11 custom ROM, and I've heard about the brand new one named Lollipop 5.0 . I've found Mako build for that new ROM and tryed to flash it via Rom Manager (Play Store). It runned smoth without any issues even if it's just an alpha release. But one day I've checked my storage tab, seen there that almost half of entire memory it was full, and I didn't had than just a few low space requiered apps. I tough about it and I realised that Lollipop ROM was installed OVER CM 11, of course not the ROM by itself but even if it wiped all data before to install the Lollipop, all junk stuff from CM 11 remain there.
So i wanted to reinstall a fresh copy of that Lollypop by using Nexus Toolkit.
Things would have been fine if my computer suddenly restarted while processing the flashing ROM, right after it wiped everything or something like that. Bad luck, huh?
So now I've got a soft bricked Nexus 4, where bootloader apparently still works but without recovery wich now it's replaced by and android dead icon and over that big red triangle, and when pressing the correct combination of volume + power buttons should give me fastboot, instead of that I'm stuck on "Download Mode". One more thing I forgot to mention, If I'll boot up device and run straight without pressing nothing, it will pop out the Google loading screen and it will stuck there, doing nothing.
View attachment 2999210
I've read many threads about how to unbrick devices. Still got no answer because they refer at other soft brick posibilities, that includes pushing backups or what requires to simply flash them by fastboot or ADB, the problem here is that those posibilities will be great if I CAN get acces to my phone, what that means is I cannot run "USB debugging" to get my device being recognized by computer in this dead stage. Even my drivers are installed and "Download Mode" is active where should, as I read, grant me the acces to device even if it's not waked up completely. And second option to unbrick it leads me to the recovery mode (wich is dead) and restore from there a previous backup, and even if I had access to it, I DON'T have a backup.
So the big question for you guys about this annoying mishap: "Is there still a possibility to push files from computer to device, or I need to visit an authorized service?"
Thank you in advance. Peace.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

Unbrick Asus MemoPad FHD 10 LTE (ME302KL)

Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working

Categories

Resources