Database Info

[GUIDE] How to get CWM back after flashed the ICS OTA

It seems that many guys don't know what to do after flashing official ICS OTA and finding no CWM.
The OTA contains its stock recovery,and ever more,there is a script (/etc/install-recovery.sh) checking and rewriting the recovery on every normal boot.
So to get CWM back and revert to gingerbread, we can use fastboot.
Requirement:
Working SDK with fastboot, adb is optional.
1) Poweroff your phone
2) Boot into bootloader(fastboot) by pressing vol down and power
3) Plug the cable in and open your terminal.
4) Download CWM img from the following URL.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
5) In your terminal type the following command.
fastboot flash recovery <Path of the recovery you downloaded in 4)>
Things should goes like this:
D:\android-sdk-windows\tools>fastboot.exe flash recovery recovery-clockwork-5.0.
1.0-crespo.img
sending 'recovery' (4116 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.558s]
finished. total time: 1.078s
6) DO NOT REBOOT! Boot into recovery DIRECTLY!!!
7) Now CWM is back,and the evil official OTA can't stop you from reverting to gingerbread now.
8) Optional : If you really like the ICS OTA even it can't be rooted yet, CWM is still very important,right? So you need to delete some evil scipt.
In CWM ,you can use adb to delete the script which checks and rewrites recovery every normal boot.
You can mount /system in CWM ,and use the following command to delete it.
adb shell
rm /system/etc/install-recovery.sh
PS: Sorry for my poor English.

Thanks - just what i was looking for.
Is there a way of getting root back? i have super user on my phone but for some reason it wont root

I've tried it this way.
But in bootloader, fastboot can't find the device.
Any advice?
When my rom is booted it's listed at adb devices

I just flashed the ics stock rom. I tried several guides but it's not ****ing working, how the hell can a total noob get back cwm, so that i can flash back to my old rom?
Would be amazing if anybody can tell me! especially in german, since that would be the easiest way!

Stothex said:
I just flashed the ics stock rom. I tried several guides but it's not ****ing working, how the hell can a total noob get back cwm, so that i can flash back to my old rom?
Would be amazing if anybody can tell me! especially in german, since that would be the easiest way!
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
Just unpack it , conected your device at the PC and click run.bat.....
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)

Did work for me. Those new driver Files made it.
Didn't need to delete install-recovery.sh ... it's somehow allready gone.

Soft Brick

So I managed to successfully soft brick my one xl with rogers after I tried the Debranding method explained by JSLEnterprises, while we wait for a CWM recovery that might help me I need some help getting my phone working. So far fastboot is useless (on a mac) when I try to fastboot update to JSLEnterprises's rogers ruu.zip I get all this
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '??K?WY-??/?>?*{??
??#/????mGFb?-=?f?qxg??|*??)???y?ftm???>?66?-#???????$???:̇+_??????????Z?~???>??fe?o?/?`?O?B??A??xa_?&???+{]?W???G
??Άֽ???0??)
??
?K???ڷ[?v-i
XrOW??7 ?l????ր?z??9'?'??R??y???-?:?????W|???>??
??????? ?_?)?VC?--???B?o???<Xa??Z8 ????_x??vo????????ԟ6p???
c{~?~??j???Js?a???0????????`??
??>?[.씄C쿨덻
?',`?~??o??ѱ3?x??P?6v?
?:???!?X?,"K???S??=x?\??M
;sO#L~?Eh?p????/??f?²}?آ?u?!??
I have also tried extracting the system.img boot_signed.img and recovery (just for kicks) and tried flashing those individually. The system.img just wouldn't flash,
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
boot and recovery send and write just fine.
I tried extracting the contents of my zip with the only program I could find that could open said zip, (all others would say it was invalid) and then rezipped it, when I try to flash that I get it telling me that no boot.img was found, thats fair cuz its named boot_signed, I open the zip, rename all the *_signed.img to just *.img and it goes fine with the exeptions that no .sig files are there and system.img is too large.
Whenever I go to my recovery and try to factory reset, I get errors at first about how it cant mount /data/data/recovery/log, but the factory reset gives me
Formatting /data
cant't mount /data
and then cant' mount all sorts of locations in the /cache
then formatting /cache
wipe complete
trying to apply and update from either internal, external or cache seems to fail and make my phone reboot
I have also tried the windows at&t ruu, every one out there the 1.52, 1.68 even 1.44 but no luck. I did JSLEnterprises trick of replacing rom.zip with the rogers.zip but I get error 155 and my phone gets stuck at a black screen with chrome htc letters until i reboot it. Is there anything else you guys could suggest that would help since I contacted the fellow who is working on a CWM port and he informed me that mounting the "sdcard" wont be possible right away.
Somebody help!

[CWM Touch][TWRP] Root + Recovery for Tilapia

Shinj1EVA reported that koush's web builder is now producing boo table CWM Touch images. I have built one and added it to the download page. I have not updated the regular CWM to 6.0.2.3 since there are no commits that affect how it works since I last built 6.0.2.1
12/20- All recoveries are functionally up to date as of this day.
I have seen most of the guides recommend flashing the 'grouper' recovery image. Don't do this. This is why your OTAs and update.zips are failing with 'Status 7'. Those zips have an assert check that ensures you are flashing your zips to the correct device. This is failing if you have a recovery image that was made for a different device.
Those assert checks are there for your protection and you should not get in the practice of working around them. Using grouper recovery.imgs is ill-advised and conceivably dangerous. The two devices differ in more respects than a simple assert check, including having different recovery.fstab files, which are used to make and configure recovery.
I have ported TWRP and compiled a CWM-based (Touch and non-touch) recovery image, made from CM10.1 tilapia source. You will need fastboot, at minimum, to write this recovery. To root, you will need the CWM-flashable zip of SuperSU by chainfire..
Instructions
Boot into the bootloader (2 choices)
Turn the device on while pressing volume down; or
Code:
adb reboot bootloader
Unlock your bootloader
THIS WILL WIPE ALL OF YOUR DATA! No way around it...
Code:
fastboot oem unlock
With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
Mount system in the 'mounts' menu
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
To Root (With /system still mounted):
Code:
adb push CWM-SuperSU-v0.98.zip /sdcard/
Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
Reboot System
Congratulations, you now have the proper tilapia custom recovery and can flash roms and OTAs. Anytime you get a 'status 7' from now on, you know that rom was not made for your device. CWM will have instructions that gives you the option of preserving custom recovery and maintaining root.
If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
If you want to keep tilapia recovery but have a grouper rom you want to try, you will have to change the updater-script of that rom. It takes two seconds. Look at the third post for instructions.
Downloads
Recovery (just pick one)
CWM Recovery (Touch/Non-Touch) (6.0.2.1)
TWRP 2.3.2.1
Root (Get the CWM flashable zip)
SuperSU
ClockworkMod is the work of the estimable koush and TWRP is from the good men of Team Win.

a mirror please?

How to use grouper roms w/tilapia recovery
Use an archive manager like 7zip and open your rom without unzipping.
Open META-INF/com/google/android/updater-script
Look for the line (usually the first) that says something like this:
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper");
[*]
Change 'grouper' to 'tilapia'
Save and flash!
Hopefully soon, devs will make two versions of their roms, although that may not happen until we finish porting the GSM stack. A solution for the meantime would be to edit the above assert to (off the top of my head):
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper") || (getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia")
For anything meant to service both devices. The devs should not be expecting users to run another device's recovery in my opinion, even if it is working. Because, as we know, it breaks other things, like OTAs and other update.zips.
My expectation would be that they will begin to build separate roms, as that is best practice and doesn't make use use the grouper fstab stuff. Not the most efficient use of bandwidth, I concede...
Ather said:
a mirror please?
Click to expand...
Click to collapse
Sure. Is techerrata/Goo a non-working option for some people? I use it for a project that is has mostly international users and haven't had any complaints. What/where would be helpful to you?
Update: Since I am here...I will post CWM Touch eventually. CWM Touch still has closed source elements, so the only way I know of to compile it is to use koush's web builder. But the result of that build is not booting. I ported Touch by hand, but it is too buggy to release, something needs to be modified in the recovery.fstab, I guess.

Mirror:
http://core.routed.com/nexus7/

If this is installed, will I be barred from installing grouper roms? I currently have multirom running, with stock as the main rom and PA as the alternate. PA doesn't get 3G but it works fine. Other grouper roms still work too, just no 3G. This is holding me over until they get the "tilapia" roms up. I just installed the OTA manually through fastboot.

Xentar712 said:
If this is installed, will I be barred from installing grouper roms? I currently have multirom running, with stock as the main rom and PA as the alternate. PA doesn't get 3G but it works fine. Other grouper roms still work too, just no 3G. This is holding me over until they get the "tilapia" roms up. I just installed the OTA manually through fastboot.
Click to expand...
Click to collapse
You will have to hack the grouper roms to change their assert to read tilapia rather than grouper (assuming they have them, and it is REALLY easy to do either way, easier than flashing an OTA in fastboot easy). I tend to be of the opinion that it is better to have a hack like that when you know you are doing something dangerous as opposed to the reverse.
Not that it is all that dangerous with the Nexus devices. But if you are flashing a rom from a different device onto your tablet, I think that you should have to indicate you are aware you are doing it.
The best thing would be for roms that are able to work on both devices should have updater-scripts that reflect that. You shouldn't be required to run recovery not for your device. But personal choice, as always.
Edit: As indicated on the OP, grouper and tilapia have different layouts. Look at the recovery.fstab, tilapia has this line:
Code:
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
That file is used in making and configuring recovery...the rom makers will have to be able to work with tilapia recovery if they ever hope to have the GSM stack work, I would guess.

mateorod said:
You will have to hack the grouper roms to change their assert to read tilapia rather than grouper (REALLY easy, easier than flashing an OTA in fastboot easy). I tend to be of the opinion that it is better to have a hack like that when you know you are doing something dangerous as opposed to the reverse.
Not that it is all that dangerous with the Nexus devices. But if you are flashing a rom from a different device onto your tablet, I think that you should have to indicate you are aware you are doing it.
The best thing would be for roms that are able to work on both devices should have updater-scripts that reflect that. You shouldn't be required to run recovery not for your device. But personal choice, as always.
Click to expand...
Click to collapse
Cool, I'll give it a go once you get TWRP up and running. Maybe Tassadar, over in the MultiROM forum, can tweak it for MultiRom as well. I'm really liking MultiRom - IMHO it's less risky when toying with unknowns. It's probably more risky in reality though, and I'm just crazy

I've flashed this recovery to get 4.2.1 on my Nexus 7 3G, but it seems that I can't go into recovery mode anymore. The screen shows me picture of an android lying down with its front open.
The only way I'm able to go into recovery is to reflash, or do a
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
This works for that 1 boot, after which I get the same issue.

superc0w said:
I've flashed this recovery to get 4.2.1 on my Nexus 7 3G, but it seems that I can't go into recovery mode anymore. The screen shows me picture of an android lying down with its front open.
The only way I'm able to go into recovery is to reflash, or do a
Code:
fastboot boot recovery recovery-CWM-tilapia-regular.img
This works for that 1 boot, after which I get the same issue.
Click to expand...
Click to collapse
Okay. After I flashed the OTA, CWM asked me if I wanted to make it permanent, but maybe that by itself us not enough. I had already done the following step.
flash recovery and boot into it. Mount system, and then:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
CWM asked me if i wanted to prevent the updates from flashing stock recovery and if I wanted to secure the root (su binary). But maybe that doesn't work right out of the box.

mateorod said:
Okay. After I flashed the OTA, CWM asked me if I wanted to make it permanent, but maybe that by itself us not enough. I had already done the following step.
flash recovery and boot into it. Mount system, and then:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
CWM asked me if i wanted to prevent the updates from flashing stock recovery and if I wanted to secure the root (su binary). But maybe that doesn't work right out of the box.
Click to expand...
Click to collapse
Yup, I renamed recovery-from-boot.p to recovery-from-boot.p.bak using ES File Explorer and it's all good now. I'm now able to use CWM. However, CWM always asks me if I want to prevent updates from flashing stock recovery and I always chose no (since it warns that this is irreversible).
Strange though. I assumed that even if CWM doesn't stick without renaming recovery-from-boot.p, the N7 3G would flash stock recovery and it would still be functional.

installed last night, works great..frankly i prefer the non-touch, dunnow why but its much better...i tried to rename the files, but there werent any files in the /system , flashed the CWM package, took a nandroid..all works great

Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.

gwisch said:
Somehow this still does not seem to work for me:
After I reflashed the tilapia recovery (CWM 6.0.1.9), I executed the nakasig file and get:
Code:
Finding update package...
Opening update package...
Installing update...
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk". "212e537985a59a7d40ff8b450a3de597ade4251c". "521503fb2a63dc6d80c4a1ecf72770c3745c4178")
E:Error in /sdcard/0/65880f45b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That error message has absolutely nothing to do with the recovery image.
This special talapia version of CWM isn't some magic pill that will make every other problem go away. It's simply designed to accurately reflect the hardware for the tablet you own (talapia vs grouper) so you don't run into as many problems down the road installing OTA updates and custom ROMs that check.
However, you still need to meet ALL the other requirements of the updates. So if you made changes to your /system files, kernel (not in this case, but in general), build.prop, etc., the OTA update will still abort and explain why.
Did you even read the error message?
Verifying current system...assert failed: apply_patch_check("/system/framework/framework-res.apk".
It's pretty clear that you modified the framework file. You will need to revert that back to stock and flash the OTA again afterwards. Any other tweaks/modifications/freezes/removals/etc. of system apps will most likely result in the same thing.

TWRP is up...
I compiled a TWRP image for tilapia as well.
This actually took a little doing...my intention here was to simply compile some images, but since tilapia is only Android 4.2, and we don't have CM10.1 (officially), I actually endied up having to port TWRP whole cloth. This is compiled from TWRP source code, with a few tweaks.
There are a couple things about the port I would like to eventually tweak, I had to copy the sbin folder over by hand, and due to the intertwined nature of grouper/tilapia, settings derived from common files in the source code are named grouper still, (i.e. ueventd.grouper.rc instead of ueventd.tilapia.rc) but that is quibble stuff and may end up staying that way regardless, since many of the tilapia make files are merely pointers to the grouper files. It certainly doesn't hurt anything.
The TWRP image has been confirmed working with the OTAs.
I thought long and hard about possibly modifying these recovery images to allow users to flash grouper roms as well. I know it is unlikely that everything will be made available in two versions, even though it should be.
Any thoughts on this? It is a demonstrably better idea than having people use the grouper images, but I still think the developers/modders should be the ones handling this problem. People are going to NEED this recovery image once the nightlies of AOKP/CM10.1 and whatever start coming down, but I know that grouper zips will still be tempting to many.

Under the instructions in the first post, it says:
OR: If you just want to boot into custom recovery instead of overwriting the stock or grouper recovery(playing fast and loose- keeping grouper recovery on-device for grouper roms, at least until devs add tilapia asserts to their updater-scripts), use
fastboot boot recovery recovery-CWM-tilapia-regular.img
Click to expand...
Click to collapse
So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?
When I try to do this, it doesn't work, and I just get this:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'
I also tried to follow the main instructions and it fails on step 2 with:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s
I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?

manekineko said:
Under the instructions in the first post, it says:
So without flashing anything, I should be able to just point fastboot towards the clockworkmod file on my computer and it should reboot into clockworkmod right?
When I try to do this, it doesn't work, and I just get this:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery D:\Downloads\recovery-CWM-tilapia-regular.img
cannot load 'recovery'
I also tried to follow the main instructions and it fails on step 2 with:
Code:
C:\Program Files\Droid Explorer\SDK\tools>fastboot flash recovery D:\Downloads\recovery-CWM-tilapia-regular.img
sending 'recovery' (6568 KB)... FAILED (remote: Bootloader is locked.) finished. total time: 0.021s
I looked at other threads and found out that normally flashing a custom recovery requires issuing a fastboot oem unlock command that wipes all data. Am I missing anything or is this actually required before either of these?
Click to expand...
Click to collapse
Yep. My bad.
I originally just posted the images as an alternative to the recoveries for the regular Nexus 7 (non-3g) images people were using. I later realized that some new people would come by so I threw rooting instructions as well. I didn't go back far enough, sorry. I will fix it now.
What you need to do is easy though, just like you mentioned you need to unlock your bootloader. So once you boot into the bootloader,
Code:
fastboot oem unlock
This will wipe all of your data, and there is no way around this, sorry. It is a security measure of some sort. There will be a screen where you acknowledge this and then the bootloader will unlock. You can then follow the rest of the instructions. Sorry for the confusion.
Update: Fixed and streamlined OP. Glad you got me to do this, I think it is better now.

In the rooting instructions, this line wasn't working for me, as /sdcard/ was for some reason a directory containing 3 folders (0, odb, legacy), where 0 had the normal contents of /sdcard/:
adb push CWM-SuperSU-v0.98.zip /sdcard/
Click to expand...
Click to collapse
Instead, I had to do:
adb push CWM-SuperSU-v0.98.zip /sdcard/0/
After that change, I was able to flash the zip and root successfully.

Hi OP,
I followed your instructions and managed to root my nexus 7 3G running stock Android 4.2.1. Thanks.
However there are some extra "incidents" which is not captured in your instructions and somehow it happen on my side, so I just detailed down what happen in case it can be of help to others:
Below is the full OP's original instruction and some extra "incidents" during rooting
Instructions
1. Boot into the bootloader (2 choices)
Turn the device on while pressing volume down; or
Code:
Code:
adb reboot bootloader
2. Unlock your bootloader
THIS WILL WIPE ALL OF YOUR DATA! No way around it...
Code:
Code:
fastboot oem unlock
My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to
2a. Reboot into bootloader
Code:
adb reboot bootloader
3. With your Nexus 7 3G in the bootloader and connected to your computer through the usb cable:
replace recovery-CWM-tilapia-regular with the name of the recovery image you chose to download.
Code:
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
4. To make CWM your permanent recovery: (this can, despite the warnings, be undone. Do it.)
Boot into recovery mode by pressing 'vol up' and when the menu says 'recovery mode' press the power button.
Mount system in the 'mounts' menu
Code:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
5. To Root (With /system still mounted):
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.
Code:
Code:
adb push CWM-SuperSU-v0.98.zip /data/media/
Flash the SuperSU zip in recovery ('Install' menu with TWRP or 'choose zip from sdcard' in CWM)
Code:
Reboot System
5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.

COLOR="Red"]My Nexus rebooted after this step and all the ADB drivers on my Windows 7 pc is gone. With my Nexus 7 still connected and booted up, when I do "adb device", I cannot see my device. I open the Device Manager and notice that the "ADB Composite Interface" driver is gone!
I got to re-install all my drivers for my Nexus 7 manually. I downloaded WugFresh Toolkit and follow the first step to re-install all the drivers. (I just wana try manual rooting, that's why I didn't use WugFresh Toolkit)
After making sure my device can be listed after "adb device", I proceed to
Click to expand...
Click to collapse
I can't speak as to how Windows works exactly, but I can tell you that fastboot code does nothing to the 'host' PC. Not saying it didn't happen, but it wasn't fast boot.
There is no error when pushing the zip file to /sdcard/ but the file just didn't appear. The windows command prompt also indicate that the push was successful. I notice that the my /sdcard/ directory is softlink to /data/media/, so I push to /data/media/ instead and it works! The zip file now appear in /sdcard/. I am not sure why is this so.
Click to expand...
Click to collapse
The person above you reported that they had to push to /sdcard/0. I checked my original instructions and they work for me. I haven't decided what to put yet. They have been playing around with the standard nomenclature for emulated storage, but I have yet to see anything that explains the varied experiences. I haven't looked yet really, either
5a. CWM will give a warning message stating overwriting of flash recovery. I cannot recall what is that exact message. But you will be presented with a llist of options with one "Yes" and all "No". I choose "Yes" to retain CWM as my recovery.
Click to expand...
Click to collapse
I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.
Thanks for your feedback.

I originally told people to follow the CWM directions on having permanent recovery. But some user experience taught me that some people are going to skip this step due to confusion over the warnings. So I decided to put in the manual method.
Click to expand...
Click to collapse
Hi,
In fact I am also confused about the warning. Not sure does choosing "Yes" means retain CWM or not. So I just choose "Yes" and saw that CWM is still the recovery after reboot.
So do you mean after this step:
Code:
adb shell
mv system/recovery-from-boot.p system/recovery-from-boot.bak
exit
It does not matter whether I choose "Yes" or "No" in the final phase, and I will still have CWM as my recovery?

Root DL701Q, CWM recovery, Firmware, and Discussion.

This thread is about DL701Q tablet.
Specs uploaded here.
http://www.specdevice.com/showspec.php?id=bcad-973e-0033-c5870033c587
http://www.bestbuy.com/site/digiland-7-8gb-black/8610212.p?id=1219354106671
This is a cheap quad core tablet that includes bluetooth and GPS, Specs http://specdevice.com/showspec.php?id=a1a0-8080-0033-c5870033c587
The tablet's one short cumming is Ram (512 MB), The tablet works well despite the amount of Ram, it uses swap partition to help balance out the lack of Ram.
CWM Recovery now backs up and restores, use caution as with anything you use, you could damage your tablet.
micro sdcard required to use this recovery.
Code:
Do not use format commands at anytime.
format /data
format /cache
format /system
to install
adb reboot bootloader
fastboot flash recovery DL701Q_dual_boot_recovery.img
fastboot reboot
after tablet reboots
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
backup
to restore almost same process
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
restore
CWM Recovery
download
https://www.androidfilehost.com/?fid=95916177934541508
To root this tablet, use the CWM recovery, I ported to flash SuperSU
download
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Firmware
download
http://www.panduoduo.net/r/9960566
http://www.mediafire.com/download/0au4z5j9leao9ft/mid713l-lp-lvds-20141226.rar
https://mega.co.nz/#!18wVWTRR!sa1ua8cWoczNT6cTdqzBgaqXRyYoyNPzVah_NaZzNcc
If you choose to flash firmware not needed if your tablet is working fine.
I would recommend flashing only system, then flash gapps. This firmware is older than what comes with DL701Q tablets, plus it doesn't include gapps or wifi update. This version can't be updated, so make sure to backup your system before flashing this system.
If DL701Q tablet gets wifi updates you need stock system to get them, so keep a copy of your stock system handy.
Gapps I used pa_gapps-modular-micro-4.4.2-20140608-signed.zip
https://www.androidfilehost.com/?fid=23501681358543824
Below are some pics of battery life and GPS, GPS test taken inside my house, too much snow to go outside. I haven't tried offline maps yet, I have navfree installed on tablet, will test when roads are clear.
Good battery life also.
to flash recovery
enable usb debugging setup adb and fastboot
adb reboot bootloader
or from power off
press power and volume up at same time, when you come to a selection screen use volume up to select fastboot volume down to boot into fastboot.
fastboot flash recovery /path/to/recovery
credits
Carliv
Chainfire
TKruzze

Tested GPS, via navfree usa works great, If you are going to try navfree usa, use older version, the latest version doesn't work very well, lot of bugs, very slow.
I am going to give MapFactor a try today, very lite navigation app.

Added new recovery to OP.
UBIFS filesystems are not as easy to use as ext4,use caution with this type of tablet, I have uploaded a cwm version that backs up and restores, You use this recovery at your own risk.
For the recovery to work correctly the process must be preformed correctly, below is the process that works.
I am sure the question why unmount cache and later remount cache, this is needed cause cache mounts wrong partition during initial start up. I could force cache to mount correct partition, but this is a dual recovery, so it would be counter productive to do that.
Anyway it only takes a few seconds to unmount cache, then mount system, data and cache in that exact order to get recovery to see partitions correctly. DO NOT USE FORMAT COMMAND PERIOD.
EG
format /data
format /cache
format /system
When restoring backup, recovery will wipe partitions, not format them, wipe is all that's needed
micro sdcard required to use this recovery.
Code:
Do not use format commands at anytime.
format /data
format /cache
format /system
to install
adb reboot bootloader
fastboot flash recovery DL701Q_dual_boot_recovery.img
fastboot reboot
after tablet reboots
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
backup
to restore almost same process
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
restore

On other thread you were working on flashable rom via cwm recovery, how is that going?

tomtom1265 said:
On other thread you were working on flashable rom via cwm recovery, how is that going?
Click to expand...
Click to collapse
Yes, I have two flashable roms, one is made from my tablet dl701q system, other one is made from mid713l system.
They both work well, both roms are ubifs systems, both are rooted and allow adb remount.
Sent from my Venue 8 3830 using Tapatalk

Uploaded specs see OP.
Sent from my DL701Q using Tapatalk

Will this recovery work with other mt8127 tablets? Got a nextbook 7 and I'm interested in making/flashing a custom recovery as safely as possible (I've already exchanged it twice, trying to avoid a third trip) any help would be appreciated

corruption said:
Will this recovery work with other mt8127 tablets? Got a nextbook 7 and I'm interested in making/flashing a custom recovery as safely as possible (I've already exchanged it twice, trying to avoid a third trip) any help would be appreciated
Click to expand...
Click to collapse
I have no ideal, I made this recovery for this tablet, if your tablet is ubifs and partitions and kernel are the same recovery should work, if not it won't.
sent from my kingSing T1 via taptalk

There are two versions of DL701Q tablet.
1. ro.sf.hwrotation=90
2. ro.sf.hwrotation=0
Version 1 has full software on Digiland website.
http://www.digi-land.net/Photo_Show.asp?InfoId=487&ClassId=56&Topid=53
If you have version one you should be able to use software as is, if you have version 2, like I do you will need to edit build.prop else touch screen will be wrong, plus screen will be upside down.
You can flash full software if you want, I only flash system.
this is my method to flash system, once you have downloaded the software unpack it, need to have custom recovery, boot tablet into custom recovery.
Code:
adb reboot recovery
unmount cache
mount system
mount data
mount cache
rm -rf /system/*
rm -rf /data/*
rm -rf /cache/*
adb reboot bootloader
fastboot flash system system.img
power off tablet, or press reset button in back
hold power up + volume up to get into boot selection
choose recovery then tab volume down.
when recovery fully loads.
unmount cache
mount system
mount data
mount cache
adb pull /system/build.prop
change ro.sf.hwrotation=90 to ro.sf.hwrotation=0
adb push build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
reboot
You should now be able to use the software, somethings may be a little off camera and so on but non the less software is usable.
Don't like software use recovery to restore your back up.

vampirefo said:
There are two versions of DL701Q tablet.
1. ro.sf.hwrotation=90
2. ro.sf.hwrotation=0
Version 1 has full software on Digiland website.
http://www.digi-land.net/Photo_Show.asp?InfoId=487&ClassId=56&Topid=53
If you have version one you should be able to use software as is, if you have version 2, like I do you will need to edit build.prop else touch screen will be wrong, plus screen will be upside down.
You can flash full software if you want, I only flash system.
this is my method to flash system, once you have downloaded the software unpack it, need to have custom recovery, boot tablet into custom recovery.
Code:
adb reboot recovery
unmount cache
mount system
mount data
mount cache
rm -rf /system/*
rm -rf /data/*
rm -rf /cache/*
adb reboot bootloader
fastboot flash system system.img
power off tablet, or press reset button in back
hold power up + volume up to get into boot selection
choose recovery then tab volume down.
when recovery fully loads.
unmount cache
mount system
mount data
mount cache
adb pull /system/build.prop
change ro.sf.hwrotation=90 to ro.sf.hwrotation=0
adb push build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
reboot
You should now be able to use the software, somethings may be a little off camera and so on but non the less software is usable.
Don't like software use recovery to restore your back up.
Click to expand...
Click to collapse
Digiland has made the update files,etc available on their website http://www.digi-land.net/upload/DL701Qupdate_software.rar
There are no instructions on the site. Maybe someone can help a noob reflash/update with these files? I have a rooted device, but can't do the wireless update because it says system was damaged and update is disabled. I would like to update and re-root.

SYN1ST3R said:
Digiland has made the update files,etc available on their website http://www.digi-land.net/upload/DL701Qupdate_software.rar
There are no instructions on the site. Maybe someone can help a noob reflash/update with these files? I have a rooted device, but can't do the wireless update because it says system was damaged and update is disabled. I would like to update and re-root.
Click to expand...
Click to collapse
If you can't follow the instructions included with the update, Then you need to contact Digiland.
This thread isn't about teaching newbies to install updates. You can start your own thread, How to install updates for Digiland tablets if you want.
sent from my kingSing T1 via taptalk

vampirefo said:
If you can't follow the instructions included with the update, Then you need to contact Digiland.
This thread isn't about teaching newbies to install updates. You can start your own thread, How to install updates for Digiland tablets if you want.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
A bit hard to follow instructions that DON'T exist

vampirefo said:
fastboot flash recovery DL701Q_dual_boot_recovery.img
Click to expand...
Click to collapse
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s

freakified said:
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
Click to expand...
Click to collapse
No ideal why it doesn't work for you, you could try the splashtool.
Sent from my Venue 8 3830 using Tapatalk

freakified said:
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
Click to expand...
Click to collapse
I'm having a similar issue. Tried this way and the TWRP guide. Ever attempt says successful but ends up frozen on the normal boot splash screen when trying to manually or adb into recovery.

Could be your device is different, you made need to use your own kernel.
Unpack your boot.img, then unpack my recovery and swap out kernels then repack and flash.
Sent from my BLU STUDIO 5.0 C using Tapatalk

Hello. Just bought 2 of these tablets from Best Buy today. It would seem I have all the correct drivers installed, both adb and fastboot see my device but even though I have the custom recovery .img on both my micro sd card and the tablets internal storage when i type the command "fastboot flash recovery DL701Q_dual_boot_recovery.img" I get back the error "error: cannot load 'DL701Q_dual_boot_recovery.img'. What am I doing wrong? Where does the file have to be for fastboot to find it?
EDIT: Nevermind. Been awhile since I've tinkered with flashing a tablet. For others that might not know the file to be flashed needs to be in the same folder as the fastboot.exe.

Okay installing the custom recovery went great but I've tried numerous times to install the root zip file from recovery and haven't gotten root even after about 5 tries. I think I read somewhere that this method was somehow blocked in newer firmware. Perhaps I have that firmware. Kernel version on my "About Tablet" says "3.4.67 [email protected] #1 Fri Apr 3 15:55:00 CST 2015" and "Build number is " ALPS.KK1.MP10.V1.45" if that means anything to anyone.
Tried some iRoot crap which is probably exactly what it is and didn't end up with anything but a bunch of chinese bloatware on my tablet, which I promptly deleted, but no root.
Would flashing one of the older firmware definitely get me root?

InfernoShark said:
Okay installing the custom recovery went great but I've tried numerous times to install the root zip file from recovery and haven't gotten root even after about 5 tries. I think I read somewhere that this method was somehow blocked in newer firmware. Perhaps I have that firmware. Kernel version on my "About Tablet" says "3.4.67 [email protected] #1 Fri Apr 3 15:55:00 CST 2015" and "Build number is " ALPS.KK1.MP10.V1.45" if that means anything to anyone.
Tried some iRoot crap which is probably exactly what it is and didn't end up with anything but a bunch of chinese bloatware on my tablet, which I promptly deleted, but no root.
Would flashing one of the older firmware definitely get me root?
Click to expand...
Click to collapse
You have to follow OP exactly, what is happening is you are just trying to flash a zip without doing the mounts and umounts in OP.
Unmount cache
Mount system
Mount data
Mount cache
Now flash root zip.
Sent from my NXA8QC116 using Tapatalk

vampirefo said:
You have to follow OP exactly, what is happening is you are just trying to flash a zip without doing the mounts and umounts in OP.
Unmount cache
Mount system
Mount data
Mount cache
Now flash root zip.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
I love you man! LOL! Root is a go, verified by Root Checker! :good:

Unable to flash TWRP, lost recovery and OS...

I can't flash or boot TWRP. I get the following error.
What can I do? without losing data?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp.img"
downloading 'boot.img'...
OKAY [ 0.784s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.835s
Help.

Hey! I've run over the similar issues while trying to port ubuntu touch.
try switching slots by using 'fastboot --set-active=a' reboot. If it worked, go to TWRP (don't change slots or wipe storage) and dirty flash stock 9, then change slot and flash stock 9 again.
If it didn't work:
Grab https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665, unzip it, then unzip images.zip
and open visible .bat file (flash all or something similar in name).
You can copy all fastboot flash * commands and execute them in your terminal.
NOTE: it uses \r instead of \n because the script was written on windows, so executing in by 'bash flashall.bat' will cause errors.
This has worked for me, I was able to boot into TWRP and continue porting
(I've tested this on op6t)

mrcyjanek said:
Hey! I've run over the similar issues while trying to port ubuntu touch.
try switching slots by using 'fastboot --set-active=a' reboot. If it worked, go to TWRP (don't change slots or wipe storage) and dirty flash stock 9, then change slot and flash stock 9 again.
If it didn't work:
Grab https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665, unzip it, then unzip images.zip
and open visible .bat file (flash all or something similar in name).
You can copy all fastboot flash * commands and execute them in your terminal.
NOTE: it uses \r instead of \n because the script was written on windows, so executing in by 'bash flashall.bat' will cause errors.
This has worked for me, I was able to boot into TWRP and continue porting
(I've tested this on op6t)
Click to expand...
Click to collapse
Switching slots helped me. I can get into TWRP after a botched Magisk 22 update. Thanks.
What do you mean "dirty flash stock 9?" And, does that mean all my data will be erased?