Database Info

[Recovery] Rogue XM Touch Recovery v1.5.0-R1 (CWM-based v5.0.2.8) [2012-05-25]

Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101​
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010​
All I did slap together all their hard work to make it work on the TF101.​
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123​
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723​
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly​
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.​
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch​
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)​
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.​
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.

Thank you, looks nice. Doing a nand backup right now with it.

there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App

Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk

baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.

Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!

Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver

Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..

luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.

Worked for me. Way way way better color scheme and it booted quick! Thanks!

wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x

Just awesome!!! Thanks so much!

this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium

Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!

New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.

Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --

I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.

jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.

jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?

hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!

[Q] CWM recovery filenames

This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.

phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.

I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?

Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit

ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.

dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.

That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!

The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.

bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.

I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.

well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..

garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress

im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA

Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces

[Solved!] Difficulty updating to 1.63.531.2 without setting up from scratch

Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah

hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.

Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah

yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!

yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah

Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah

check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img

xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah

just try opening it with a plain windows explorer

xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah

hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2

Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.

KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.

Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah

No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.

does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!

well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient

On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.

Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah

It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah

[CWM Recovery][Root]Alcatel Onetouch 997D

ROOT:
We've been discussing about this for about a month, and I think it's time to sum it all up and open a new cleaner thread.
First, how do you root the Alcatel Onetouch 997D?
This phone is quite new (less than 2 months in the market) and is one of the few phones which can't be rooted by the script developed by Bin4ry or the other well-known methods, such as Unlockroot or SuperOneClick, but it is not unrootable.
In order to root this phone, you must first boot it into Factory mode, a special menu, present in all Mediatek based phones, which can be used to test the various parts of the phone. You get to this menu by turning the phone on while pressing the volume down batton and power button at the same time, until it appears.
Once in factory mode menu, you can connect the phone to a pc, which, if the appropiate adb drivers are installed, will detect it. At this point, the phone can be rooted, by the use of an app called MTK Droid tools. I've succesfully tested versions 2.2.8 and 2.2.9.
After MTK Droid Tools finds the phone, you just have to press the "root" button. The phone will be rebooted two times, and after the second reboot, MTK Droid Tools achieves a temporary root which enables it to install Superuser, su and busybox, so the root is permanent.
During this process, MTK Droid Tools asks whether you want to make a backup. You'd better answer no, since this process is very buggy and fails on this phone, so it's a complete waste of time.
When "Task is complete" message appears, you can reboot the phone, but it won't work right away. Due to a problem not yet identified, it's mandatory to wipe data from recovery for the phone to work. Some people have reported the loss of Google Play Store, and others have lost a lot of apps. Anyway, a wipe solves the problem and the phone remains rooted.
MTK Droid Tools 2.2.8 can be found here: http://www.4shared.com/zip/NyHaro3-/MTKdroidTools.html
CWM Recovery:
We have a 99% working CWMR. I compiled it myself with the help of the dsixda kitchen and the MT6577 CWMR porting plugin developed by Bruno Martins.
I say it's 99% working because backup doesn't work 100%. Alcatel phones have a non standard partition called "custpack", which contains a lot of apps bundled with the phone and whose deletion prevents OTA updates from working, so it's not something one would like to remove. My knowledge of Android is not enough to try to dig inside CWMR source code, to see if I can modify the backup process and make it recognize the custpack partition, so I left it as is. Instead, I decided to develop a shell script which can make CWMR-compatible backups, which can at least be restored from it.
Everything else is fully functional. It's version 6.0.1.2.
To flash it, you need to root the phone, using the method explained above, and flash the recovery image using Mobileuncle Tools utility, which can be freely downloaded from Google Play Store. It's very important to download the latest version from Google Play, since previous versions lying around, and the version MTK Droid Tools installs during the root process can't flash a recovery on MT6577 processors.
To flash the recovery with Mobileuncle tools, you have to place it on the root of the external sd card and open Mobileuncle tools. After granting root permissions, if you haven't done yet, you choose "change recovery" and choose the corresponding .img file. Once the process is done, the phone will automatically reboot into the new recovery. It may fail, which you'll notice because the phone boots into the stock recovery, and you may need to do it again. I've noticed that, at least in mine, it works best if I do it while the phone is unplugged from the computer.
As I said abpove, everything, except backup, works well. Restore works, if you have the correct backup (more on this later).
My CWMR can be downloaded from my Mediafire account: http://www.mediafire.com/?v7wfjr6v1t7b0z5
NANDROID BACKUP:
After noticing the backup process in CWMR can't backup the Alcatel exclusive custpack partition, I began trying to solve this. I guess the best way to do it should be modifying the source code of CWMR to adapt the backup process, but, since that exceedes my current knowledge level, I tried differemt approaches. I downloaded the app Online Nandroid backup from Google Play, and learnt that a nandroid backup can be easily done using a shell script, given you have a rooted phone and a way to execute shell scripts. The good news is that it's done, and I have achieved my goal, and now have a working shell script, which creates backups that can later be restored from CWMR.
This script creates 7 files, like the standard CWMR backup process does. The files are:
1) boot.img
2) recovery.img
3) system.ext4.tar
4) cache.ext4.tar
5) data.ext4.tar
6) .android_secure.vfat.tar
7) nandroid.md5
Files 1, 2, 4, 5 and 6 are exactly what you now get if you use my CWMR port and perform a backup. The difference lies in file 3.
In a backup created from our current CWMR, this are the contents of the tar archives:
system.ext4.tar: files under /system, and all its subdirectories
cache.ext4.tar: files under /cache, and all its subdirectories
data.ext4.tar: files under /data, and all its subdirectories
.android_secure.vfat.tar: files under /sdcard/.android_secure
In a backup created by my script, it's slightly different:
system.ext4.tar: files under /system, and all its subdirectories, and also files under /custpack, and all it's subdirectories
cache.ext4.tar: files under /cache, and all its subdirectories
data.ext4.tar: files under /data, and all its subdirectories
.android_secure.vfat.tar: files under /sdcard/.android_secure
On both backups, boot.img and recovery.img are images compatible with Mediatek Flash Tool or Mobileuncle Tools (in the case recovery.img), and nandroid.md5 contains the md5 sum of every file, so the restore process can validate the integrity of them, to prevent you from ever restoring a corrupt archive.
In order to use my script, you need an app which can execute them. My preference (and the only one I have fully tested the script with) is GScript, which can be freely downloaded from Google Play Store.
There's also a paid version, but the only difference between them is that the paid version is updated more often than the free one.
How to install the script:
1) Download and install GScript, free or paid. You can use the apk file provided by me inside the attached zip.
2) Download the attached zip file with the scipt, if you haven't done so to install GScript.
3) Put the script on the external sd card, under a folder called "gscript". Use lowercase characters for the name and never change the name, as this would result in GScript not working or finding your scripts. The resulting structure should be:
/sdcard/gscript
|
------------> bin
Inside /sdcard/gscript you have the script itself, called "Alcatel_OT_997D_nandroid.sh" and inside /sdcard/gscript/bin, you have the busybox
binary, used by the script. Even if you have busybox already installed, don't delete this binary, since it's the only one the script will use, and
the only one it's been fully tested with.
4) Open GScript.
{
"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"
}
5) On the GScript main window, you can see a pair of sample scripts already included. You need to touch the menu button and then on "Add script".
6) Browse for the .sh file on /sdcard/gscript, and tick "Needs SU?" if it's not already ticked, since this script needs a rooted phone.
7) Once the new script is in the list of installed scripts, you only need to touch its name to launch it. The first time you do it, GScript will ask for root permissions. Allow it.
Once you open the script, it will run automatically, and will end around 5-10 min. later, depending on how loaded your phone is. In order to be able to see every message shown by the script, it's better to raise the screen timeout, to at least 10 minutes. After execution, the output window will auto close, unless you cancel auto closing by touching anywhere on the screen except, of course, the close button.
The backups are stored under the /sdcard/clockworkmod directory (the script will create it if its not already there), under which it will create a new subdirectory, with the date and time of the backup, just in the same format CWMR uses.
During the execution of the script, you may see two error messages, which are not really errors, but warnings you can ignore. These errors are:
1) Errors creating directories at startup. If the script has already been used, or you have tried the backup inside CWMR, sdcard/clockworkmod/backup already exists. The script will tell you that, but it will keep working.
2) Removing leading "/" from member names: tar utility removes "/" from the input parameters, just that.
3) XXXXXXXX: socket ignored, where XXXXXXXX is the name of a file. Sockets are temporary files Unix apps use to communicate with other apps. Since they are temporary, tar just ignores them, so you can also ignore the error message.
On mi phone, after I close the results window, GScript force closes, but this doesn't affect the execution of the script. As I've read somewhere, it
looks like this is a problem common to a lot of users.
DISCLAIMER:
This script is offered AS IS, with no warranty. It has been successfully tested on my own phone, and the generated backup was then perfectly restored from recovery with no issues, but I can't say it won't fail on other people's phones.
It's the first version, fully functional, but with some room for improvement. As it is right now, it's not error free, since it doesn't check if you have enough space left on the sdcard, or if you don't have any apps moved to the sd card. In fact, I have not tested it in such a situation, and I don't know what would happen if you backup your phone with no apps moved. On the other hand, it doesn't bakcup sd-ext, so if anyone has a second partition on the sdcard, to use Link2SD o a2sd, that partition won't be backed up, although data for apps linked to the second partition will. Anyway, even if it fails, you don't have to worry, since it won't change anything inside the phone. If you later restore a backup made with this script, you are doing it AT YOUR OWN RISK. I will not accept any responsibility for damage or data loss caused by the use of this script or restoration or any backup created with it.
Don't forget this script needs a rooted phone, and that performing some things on rooted phones is risky. If the worst case, you will always be able to recover the phone using Alcatel One Touch Upgrade on your pc.
Any comments or improvements are welcome, but if you change / improve anything, don't forget to share it with the community, so everyone can take advantage of it.
IMPORTANT:
This script is only suitable for the Alcatel OT-997D, and probably other phones by the same brand, if they have the "custpack" partition, exclusive to Alcatel. It won't work, unless code regarding the custpack partition is modified, in other phones, and I will not give support to users complaining the script doesn't work on their non Alcatel phones, or their Alcatel phones without s custpack partition.
FINAL NOTE:
Ok, that's it. Now, I'm going to have a rest, maybe until Alcatel release the long waited Jelly Bean update.
EDIT:
I had forgotten the "thanks" section:
Thanks to:
@dsixda, for the great kitchen
Bruno Martins (@bgcngm) for his valueable advice and his scripts to unpack/repack recovery of any MT657x based device
@yuweng, who developed the great kitchen plugin to port CWMR to any MT657x based device. and also pointed me in the right directory when I was trying to root the phone
@ameer1234567890, author of the great onandroid script. I haven't used your code, but it taught me I had to unmount and remount the sdcard on a different location to be able to backup .android_secure

Reserved

Reserved too

Any chance of working on a custom rom? i would love to get the standard google theme instead of the alcatel icons
maybe i try to get this done, changing the icons is'nt that hard normally
btw i'm still looking to cleanup this phone, you know the partitions pretty wel, where is the location of all the stock apps like chrome etc, i would love to make the phone as close to googles standard as i can get it
edit: you can always pm me, i don't want to ruin this topic

Hey jman10 thank you very much for your awesome tutorial.
But i still have to ask, if the restore works 100%, because of lack of gps signals i made a cwm backup of my current stock-rom(4.0.4) and tried, if the newest update(4.0.4-01001) still has problems with gps signals. Well actually it didn't get any better, so i decided to go back to the old version with the help of my backup.
CWM said there were no errors while restoring, so also thought it. But i get a few bugs using the old version, the stock camera-app gets force closes, even after reboots or a data wipe. The stock e-mail app shows weird artefacts on the email subjects, a very large 'x'. It seems, like a lot of system files are missing or sth.
Can you help me?
Thanks!

kassipopassi said:
Hey jman10 thank you very much for your awesome tutorial.
But i still have to ask, if the restore works 100%, because of lack of gps signals i made a cwm backup of my current stock-rom(4.0.4) and tried, if the newest update(4.0.4-01001) still has problems with gps signals. Well actually it didn't get any better, so i decided to go back to the old version with the help of my backup.
CWM said there were no errors while restoring, so also thought it. But i get a few bugs using the old version, the stock camera-app gets force closes, even after reboots or a data wipe. The stock e-mail app shows weird artefacts on the email subjects, a very large 'x'. It seems, like a lot of system files are missing or sth.
Can you help me?
Thanks!
Click to expand...
Click to collapse
If you use my script to backup your rom, restore from CWMR will work 100%. So, your way to go is to start from scratch. Download Alcatel Onetouch Upgrade to a pc, connect the phone and get the latest full version rom on their servers (which sometimes is not the latest one available). Then, connect via wifi and get the latest OTA update. After that, you can root the phone, flash CWMR and make a working backup. From that moment, you'll be able to restore whenever you want and not risk anything.
By the way, which problems are you having with the gps? Mine is working like a charm, even indoors. Where are you from and what kind of tests have you done with it?

Hey thanks for your quick answer, actually i did the whole process that way:
-root stock firmware 4.0.4
-installed cwm per mobileuncle tools
-created image per script
-updated with the help of one touch manager to 4.0.4-01001
-tried gps, didnt work
-rooted
-installed cwm per mobileuncle tools
and then i wanted to return to point 1, but as soon as i restored the backup, my camera doesnt work and i get random fc's of several apps. i would like to return to stock 4.0.4, because since the new update the system is more laggy
do you know a way? do you have a *.img of the old version?
my gps is really weird, i would say it works at 10%. in my home city i couldnt make it work, then i tried it randomly in 2 other cities and it worked instantly, but then i try it again at the same spot, where it worked a couple of hours earlier and it doesnt work anymore its really weird.
thanks man!

kassipopassi said:
Hey thanks for your quick answer, actually i did the whole process that way:
-root stock firmware 4.0.4
-installed cwm per mobileuncle tools
-created image per script
-updated with the help of one touch manager to 4.0.4-01001
-tried gps, didnt work
-rooted
-installed cwm per mobileuncle tools
and then i wanted to return to point 1, but as soon as i restored the backup, my camera doesnt work and i get random fc's of several apps. i would like to return to stock 4.0.4, because since the new update the system is more laggy
do you know a way? do you have a *.img of the old version?
my gps is really weird, i would say it works at 10%. in my home city i couldnt make it work, then i tried it randomly in 2 other cities and it worked instantly, but then i try it again at the same spot, where it worked a couple of hours earlier and it doesnt work anymore its really weird.
thanks man!
Click to expand...
Click to collapse
Did you do a factory reset after rooting? It's really important to do so, and the phone doesn't work if you don't.

Hey mate,
sure i did, i have no problems with root at all. My problem is to restore my cwm backup i did with the old firmware, because i really want it back badly. Do you have a image file of the "roll out" stock firmware?
Thanks in advance!

Hi,
it seems like I am missing something.
I installed the MTK-Tools 2.2.8, connected the phone but the phone is not recognized. I see there is missing some MT65xx AndroidPhone-Driver. Where can I get one?
The installation of the OneTouchManager does not help. Any ideas?

kassipopassi said:
Hey mate,
sure i did, i have no problems with root at all. My problem is to restore my cwm backup i did with the old firmware, because i really want it back badly. Do you have a image file of the "roll out" stock firmware?
Thanks in advance!
Click to expand...
Click to collapse
The system image I have is vastly modified by me, so it might not be suitable for you. If you did the backup using my script, it should work right away. Can you tell me what files (names, sizes, etc.) you have in your backup?

Roland_SGN said:
I installed the MTK-Tools 2.2.8, connected the phone but the phone is not recognized. I see there is missing some MT65xx AndroidPhone-Driver. Where can I get one?
Click to expand...
Click to collapse
There is a driver directory inside mtk tools zip. Let windows take that driver manually.

we now have kernel (and more) sources online from alcatel:
http://sourceforge.net/projects/alcatel/files/OT_997D_20121228.tar.xz/download
I'm downloading them...

fear_factory84 said:
we now have kernel (and more) sources online from alcatel:
http://sourceforge.net/projects/alcatel/files/OT_997D_20121228.tar.xz/download
I'm downloading them...
Click to expand...
Click to collapse
Now we just need a CM10 rom, then we're on!
Sent from my Packard Bell [email protected] v20 using Tapatalk

MadMav88 said:
Now we just need a CM10 rom, then we're on!
Sent from my Packard Bell [email protected] v20 using Tapatalk
Click to expand...
Click to collapse
You need also to implement dual sim support on it.. it's a huge work!!!
For now we can aim to fix those annoying bugs on stock rom (if we can) and get a 100% working recovery.
My bugs on latest stock rom:
- bluetooth freezes when bt headset is disconnected by lack of signal
- compass doesn't give good values at all
- need for speed most wanted sound is borked and is not 100% smooth like on other mtk 6577 devices.
In addition I would like to have:
- smaller system bar on the bottom
- search button and menu button always visible on system bar
- extended power menu with the option to have "extended desktop" (system bar hidden by killing it, and then restarted when reenabled)
These can be made by editing framework with smali and friends.
Prerequisite is a fully deodexed rom (and that is easier) and a lot of spare time!

Any news?
Sent from my ALCATEL ONE TOUCH 997D using xda app-developers app

fear_factory84 said:
You need also to implement dual sim support on it.. it's a huge work!!!
For now we can aim to fix those annoying bugs on stock rom (if we can) and get a 100% working recovery.
My bugs on latest stock rom:
- bluetooth freezes when bt headset is disconnected by lack of signal
- compass doesn't give good values at all
- need for speed most wanted sound is borked and is not 100% smooth like on other mtk 6577 devices.
In addition I would like to have:
- smaller system bar on the bottom
- search button and menu button always visible on system bar
- extended power menu with the option to have "extended desktop" (system bar hidden by killing it, and then restarted when reenabled)
These can be made by editing framework with smali and friends.
Prerequisite is a fully deodexed rom (and that is easier) and a lot of spare time!
Click to expand...
Click to collapse
About bugs:
- When I'm calling someone that is listed as favourite for a specific sim, the system asks which number I want to use.. I know about the configuration, I settled the first sim as principal (every call) and the second sim just for some contact. So, why is still asking which number is able to use for them? Is it a bug?
- The digital compass doesn't work well, or better, it's not working at all! The North it's not properly indicated, it follows the gravity verse..
Addictions:
- The status bar can be toggled by power menu or maybe by a sequence (example: vol - vol -)
Etc.
Sent from my Packard Bell [email protected] v20 using Tapatalk

MadMav88 said:
About bugs:
- When I'm calling someone that is listed as favourite for a specific sim, the system asks which number I want to use.. I know about the configuration, I settled the first sim as principal (every call) and the second sim just for some contact. So, why is still asking which number is able to use for them? Is it a bug?
Click to expand...
Click to collapse
It's the same on mine.
I tried to set one contact associated to 1st sim and an other to the 2nd sim, and I set the 1st sim for all call.
When I want to call:
-if I phone one contact without associated's sim, call goes direct by the 1st Sim.
-If I phone one contact with the 1st sim associated, call goes direct by the 1st Sim.
-If I phone one contact with the 2nd sim associated, the sim choice windows appear but it's written "suggested" on the 2nd sim.
So the call don't start automatically.
and I set no principal sim for call (every time you need to choose), I have the sugestion on the associated's Sim.

Many people complained about this contact sim preference bug.. I never used this function, so I can't tell.
To toggle status bar, the better working solution I've found is the Hide bar app (search it on xda).
Yesterday I was fighting with my phone that looses signal on the secondary sim when on charge. It may be a bug with my sim/operator combination when sim1 has 3g enabled.
Sim1 Wind Italy, 3g enabled on it, Sim2 Tim Italy no 3g (obviously), when I attach charger or usb cable, I loose Tim signal.
Swapping usim card slots does nothing.
If I enable 3g on Tim Italy, and no-3g on Wind Italy, it works flawlessy. Same if I disable totally 3g.
Anyone with similar issues?
I collected radio logcats and sent them to Alcatel Italia. Probably they will not reply at all, but I have tried...
Please do the same for other bugs! Maybe they'll hear us..

Converning CWM Backup: What about making the backup with online nandroid backup using an adapted partition layout like for those devices here?
That would be restorable by your cwm, too?

[GUIDE] How to restore your Nextbook Ares 8 - NXA8QC116 to Stock (TWRP/Rooted)

After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.

PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
An absolutely great post! You need a special thanks because this ability to recover from catastrophe likely will encourage others to move forward with more daring mods. I feel much more secure in playing with a few ideas knowing you have the base Rom and recovery spelled out and that it actually worked (Yes, I knew how, but knowing it worked for sure is huge!)
Thanks,
Freddy999

Now if only some kind hearted dev would release a ROM....

Actually, after you root and decrypt it, and fix the cpu governor and such, and get rid of the google apps that you don't use, with the exception of the lollipop HW overlay flaw it is not a bad ROM to start with. I wiped most of the Google stuff and put in Nova launcher. Now the device is quite manageable and very fast without much further help. Here is a pretty good summary of the device for anyone who has the tools to build a ROM: http://specdevice.com/showspec.php?id=ee2d-39de-0033-c5870033c587 with the exception I can not find that the FM radio exists in the device although the hardware seems to say it is there..........

what do you mean cpu governor?

adamx said:
what do you mean cpu governor?
Click to expand...
Click to collapse
Playstore: No frills CPU control
set it ondemand, noop
You might want to get also CPU spy reloaded to see the effect/

The backup file expired (or something) on OneDrive. Would you mind re-upping it somewhere? Thanks!
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse

Yes the link to the backup is dead, can OP or anyone else upload another? I wiped the internal storage and now android has no home or back buttons so I cant get out of apps

Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY

stevemp said:
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
Click to expand...
Click to collapse
Thanks!

stevemp said:
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
Click to expand...
Click to collapse
Thanks Steve you're a true bro

THANK YOU!!!!!!!!!
I rooted and removed the encryption from my ARES 8 but then when messing with an (official) flashing tool I ended up formatting my system partition., So I had NO OS at all., But I did have TWRP., And now thanks to your post I have a living breathing working tablet again., By all your gods (or none at all if that's your thing) I Bless you! Thank you X Infinity! :good::good::good::good::good:
-Eric.
P.S. I got it to work from my SD card but I did have to make a backup with TWRP first, then pop the SD card into the PC delete all the files from the folder and copy your files into the folder that TWRP had created. Otherwise it didn't show up at all... Anyway Thanks again! :victory:
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse

It's says root only on Linux I have windows xp does anyone know how I can root this on this type of computer thank u

Here is a question, we bought one for the grandson.. How come when you open up the play store, and choose apps, it does not show any that came with the tablet itself, kind of like you see when you go to play store on a smartphone..

really need some help
ericzollman said:
I rooted and removed the encryption from my ARES 8 but then when messing with an (official) flashing tool I ended up formatting my system partition., So I had NO OS at all., But I did have TWRP., And now thanks to your post I have a living breathing working tablet again., By all your gods (or none at all if that's your thing) I Bless you! Thank you X Infinity! :good::good::good::good::good:
-Eric.
P.S. I got it to work from my SD card but I did have to make a backup with TWRP first, then pop the SD card into the PC delete all the files from the folder and copy your files into the folder that TWRP had created. Otherwise it didn't show up at all... Anyway Thanks again! :victory:
Click to expand...
Click to collapse
i am having the same basic problem, i flashed twrp and supersu not sure what i did wrong or if it rooted succesfuly, i do have twrp but wont boot past recovery. twrp says it cant mount data and i cant back up., and have no os. how can i fix this ?
im new to this whole thing so please give me step by step if you can and any links or downloads you can, please help :crying: this tablet is how i comunicate w my daughter... in colorado. i need it up and running

I partitioned my Ares 8 and now it is stuck awaiting fastboot command. Any ideas?

Can someone help me? Why does mine fail when restoring system?

My ares 8 is stuck in DNX mode and will not enter recovery, and is pretty hosed. I need a scatterfile and rom so I can flash it and use it for something besides a paperweight. Thanks 1000 times in advance!

Ahhh, after several hours of reading, I managed to get recovery back, but cannot seem to flash a rom successfully, and also my backup - says it was successful but when I reboot, it goes straight to DnX mode and I have to use a batch file to get back to recovery. But progress has been made and hopefully by today I will have it back up and running an OS

Hi, i have Nextbook Ares 8 after rooing i can't boot the device it has an error says "Your device is unable to start because the Android OS image has failed to verify" please help me to fix this problem.