How To Create Image Of Tablet To Restore

[jerryferreira]

Hi everyone,

I just recently had a problem with my Asus Memo Pad Smart 10 (ME301T). I set my SuperSU Pro to install as a system app and when it rebooted, my tablet was bricked at the logo screen. I was able to reinstall the firmware that I downloaded from Asus, and used a whole afternoon to root, remove bloatware, and set up all my apps.

My question is: how can I create something like that? What I want to do is take an "image" of how the tablet is right now and put it on my MicroSD card and have it so that if this happens again, I can take the card, enter recovery, and flash the tablet to a point where I have it the way I like it.

I am familiar with ADB, but when my tablet was bricked at the logo screen, I couldn't get access to it with ADB.

Jerry

 

[vampirefo.]

You need to look into a custom recovery.

Sent from my BLU STUDIO 5.0 C using Tapatalk

 

[jerryferreira]

So I take it there isn't a way to take a snapshot of my tablet and create a bootable image as if I were installing firmware?

Thanks for replying.
Jerry

 

[vampirefo.]

So I take it there isn't a way to take a snapshot of my tablet and create a bootable image as if I were installing firmware?

Thanks for replying.
Jerry

Not without custom recovery.

Sent from my BLU STUDIO 5.0 C using Tapatalk

 

[jerryferreira]

Thank you!

 

[jerryferreira]

The more I read about unlocking the bootloader, installing a custom recovery, etc. the more I'm confused.
I keep reading that if I unlock the bootloader, my data gets wiped out.
This is what I think I'm supposed to do:

1. Backup with Online Nandroid Backup
2. Unlock the bootloader
3. Install CWM Recovery
4. Install CWM Rom Manager
5. Restore the Online Nandroid Backup with CWM Rom Manager

After restoring the Nandroid Backup, will I still have the CWM Recovery?

Thanks.

Not without custom recovery.

Sent from my BLU STUDIO 5.0 C using Tapatalk

 

[jerryferreira]

Oh boy, here we go. Now I'm getting this message (see attached pic)

Many Asus owners were having this problem two years ago and it's still not fixed?