[Q&A] [Root/Guide] How to Root/Install TWRP Touch Recovery for Digiland DL701Q 7&quo
Q&A for [Root/Guide] How to Root/Install TWRP Touch Recovery for Digiland DL701Q 7" Tablet
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Root/Guide] How to Root/Install TWRP Touch Recovery for Digiland DL701Q 7" Tablet. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My TWRP installation is getting aborted
I get an error message that says "Aborting, an error has been detected, cannot repack recovery..."
Device is updated and rooted; booted up normally. Tried to run in fastboot mode but the computer does not detect it. In the device manager, the device appears as "Android Composite ADB Interface". Please can you help.
aybhagwat said:
I get an error message that says "Aborting, an error has been detected, cannot repack recovery..."
Device is updated and rooted; booted up normally. Tried to run in fastboot mode but the computer does not detect it. In the device manager, the device appears as "Android Composite ADB Interface". Please can you help.
Click to expand...
Click to collapse
Please remove and re install your device drivers on your PC, delete the txt file and folders from the TWRP file, (not the executable). Reboot your tablet normally, connect to the PC and run the program automatically, you should get an install, but the orientation will be incorrect. Simply reboot your tablet again and reconnect, this time run the TWRP program following the steps for manual mode.
Been trying to install TWRP and keep getting a not compatible device error. When connecting the tablet, HTC Dream drivers get installed, I have removed drivers, forced installed android ADB drivers rebooted pc and tablet still nothing.
Any thoughts?
IamNWar said:
Been trying to install TWRP and keep getting a not compatible device error. When connecting the tablet, HTC Dream drivers get installed, I have removed drivers, forced installed android ADB drivers rebooted pc and tablet still nothing.
Any thoughts?
Click to expand...
Click to collapse
For the DL701Q Tablet, please confirm that you have downloaded the TWRP installer that is compatible with MTK devices with UBIFS system,
Protocol 9 said:
For the DL701Q Tablet, please confirm that you have downloaded the TWRP installer that is compatible with MTK devices with UBIFS system,
Click to expand...
Click to collapse
Using the 2.8.2.0 file listed in the how to page linked above.
Also that is the odd thing, It is saying the tablet is not a MTK device but when I pull up the hardware specs it is MediaTek MTK8127
Not sure why the installer isn't detecting your tablet correctly. Are you using the ubifs version. I will send you the zip file of the one I used.
Sent from my DL701Q using Tapatalk
I am using the 2.8.2.0 twrp software on windows 8. I have root by using iroot and have chain fire's supersu working. I can't get the computer to see the tablet using the twrp software. The device manager shows the tablet as dl701q. Any clarification on what drivers I am supposed to use would be great.
slushbilly said:
I am using the 2.8.2.0 twrp software on windows 8. I have root by using iroot and have chain fire's supersu working. I can't get the computer to see the tablet using the twrp software. The device manager shows the tablet as dl701q. Any clarification on what drivers I am supposed to use would be great.
Click to expand...
Click to collapse
You will need normal and recovery drivers for sure. To get recovery driver, power off tablet, hold volume button closest to power button; press and hold power button simultaneously. Should get you to bootloader to select recovery and connect to pc. I should say though that I am running windows 7 not 8.
Sent from my Nexus One using Tapatalk
what version of easy magic twrp is supposed to work with the dl701q? Thanks.
2.8.2 for UBIFS system.
Related
I need some serious help... I think I bricked my Nextbook Premium 7. I compiled a custom ROM and forgot to included a launcher. Didn't realize it until after I flashed it. My tablet is stuck in a bootloop and only way to shut it down is with the reset [pin hole] button. Power button does nothing except start it up. I have already tried to put the stock update.img on an external SD hoping it would boot from there, but it did not. I am not sure what to do next, I have looked all over google and xda. Please help!
Thank you in advance!
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
techno-update said:
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
Click to expand...
Click to collapse
There ins't a custom recovery installed, this device flashes by detecting an update.img and askes to install it. It doesn't get past what would be considered the kernel screen. This tablet doesn't work like a standard android phone. There are no hard buttons except the power button, so attempting to get into any recovery is not possible. It also doen't boot enough to add any files to it.
Sounds like your screwed. Sorry.....
Please hit the thank you button if i helped!
check out this link
http://forum.xda-developers.com/showthread.php?t=1410862&page=9
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Help !!
Please help, got the tablet yesterday NEXT7P12 YF091211085 by flashing the official site was a brick, the tablet will not turn on, the computer does not see it.
screen moved after installing rom
Hi, i don't know if I'm on the right place but if anyone can help me, please I haw the Nextbook 7 premium and have instaled costum rom on it, but after rebooting my screen position has moved from right to left 2 cm and from up to down 1 cm , so my screen is moved I don't know why I have try to install 3 other rom and factory firmware but the screen is still moved or should I say cut. Any ideas? please I have try to google it but no luck...
I no longer have my np7 but I did try just about every ROM for it. Never have I had or seen an issue like this, and in truth I can't think of what the issue may be.
There are different np7 variants and some don't play nice with custom ROMs (built sept 2012 and older lose WiFi) so you might have a model that can only use one software due to hardware/firmware change.
There never was much development for the np7 here, I think finlessbob and others are still working on it at freaktab.com maybe see if they can help
Sent from my Nexus 4 using xda premium
d33dvb said:
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Click to expand...
Click to collapse
Your link not working? Send alternative link please!
Q&A for [ROOT] Rooting Method for Alcatel Pop C2 4032A
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Rooting Method for Alcatel Pop C2 4032A. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
kirito9 said:
This is a guide on rooting the Alcatel Pop C2 4032A using 2 methods.
Disclaimer: Your warranty is now void. You do this in your own risk. I do not take any responsibility to your device.
How to Root using the Framaroot method:
Enable unknown sources from settings to allow installation of third party apps.
Download latest framaroot.apk version from here .
Install framaroot and click on the Barahir root exploit.
Reboot device and enjoy root .
How to Root using the recovery method
Requirements
SP flash tools
Mtk VCOM drivers (preloader drivers)
ADB driver
USB Cable
Mtk6572 Scatter
Recovery of your choice
SuperSu zip
Android phone of course
Working brain
Download the SP flash tools and Mtk VCOM drivers and extract them to desktop.
Install the Mtk VCOM drivers.
Download the scatter file and place also on the desktop.
Download the SuperSu.zip and place it on the sdcard or internal storage.
Download the recovery of your choice and place it on your desktop
Open the folder with SP flash tools and run flash_tool as administrator
Select the scatter file by clicking on scatter loading
Check the recovery check box and click on location and select the recovery of your choice.
Turn off your phone.
Connect the usb cable to the computer but don't connect the phone as yet.
Click on the download button on the SP flash tool and then connect your phone to the computer.
Wait for it to flash and then reboot into recovery using adb commands once the phone has booted up.
Once the phone is in recovery select install zip from sdcard and locate the SuperSU.zip.
Reboot and there you go root access
To Enable USB Debugging.
1. Go to settings and about phone
2. Tap the build number 7 times to enable development mode.
3. Go back and then go in development mode.
4. Enable USB debugging.
Click to expand...
Click to collapse
Hello there thanks for this guide, is there any chance that this will damage my phone. Noob here
yes there is a possibility of this damaging your phone but read the disclaimer and follow instructions and you will never go wrong
Sent from my 4032A using XDA Free mobile app
Hi,
I got my Nexus 9 around launch date and used Wugs toolkit to unlock bootloader, root and install teamwin recovery.
I kept gettting OTA updates for 5.0.2 but they wouldn't install. After months of ignoring I thought I'd update.
It wouldn't update so I tried to use Wugs toolkit to 'Flash stock + unroot to latest version'.
This failed saying something about no fastboot device, although the device went to the white screen and seemed to be displaying hboot/fastboot as options...
I got frustrated and used TWRP to wipe everything, including the OS!
I'm used to Samsung so expected an Odin type program to flash over my mess... I can't seem to do anything now.
HELP! (Please!)
A reason I don't like tool kits. If they don't work as expected you have no idea what to do next. Follow the long method of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
jotan said:
Appreciate the reply but I can't enable anything within the device as there is no OS installed...
I have used vol down and power to select fastboot.... Is this "Boot your device into the bootloader" in your guide?
All I get is waiting for device in the cmd window
thanks
Click to expand...
Click to collapse
Vol down and power does bring you into the bootloader. Do you have usb drivers setup? Go into device manager on your pc with the device connected. Do you have an icon with a yellow exclamation mark? If so right click on it and go to where you can choose a driver from a list on your computer. Choose Android adb composite interface.
Sent from my Nexus 9 using XDA Free mobile app
Sorry about the late reply, been on my honeymoon! For some reason it just wouldn't work on my PC, so I used my laptop and all was well.
Thanks.
Thread closed!
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
amaramar2000 said:
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
Click to expand...
Click to collapse
Please don't cross-post; found this exact text in three different threads. My earlier response here. Others have basically said the same thing. You're done.
Hi there,
Can't find solution for my problem.
I have installed twrp. Then tried to click unlock.bat and tablet get in fastboot mode. From where i can't recover tablet.
While fastboot i see there is no driver in device manager as shown in attachment.
I can get in twrp with power + volume up.
But can't do something else.
What is solution to recover from this situation?
arshileus said:
Hi there,
Can't find solution for my problem.
I have installed twrp. Then tried to click unlock.bat and tablet get in fastboot mode. From where i can't recover tablet.
While fastboot i see there is no driver in device manager as shown in attachment.
I can get in twrp with power + volume up.
But can't do something else.
What is solution to recover from this situation?
Click to expand...
Click to collapse
- on Windows machine install Motorola Device Manager from here; you do NOT need to launch the device manager once installed
- from TWRP boot into fastboot via Reboot -> Bootloader; the word 'Fastboot' should be displayed on HDX
- on Windows change device driver to "Mot Composite"; the word 'Ready' should appear on the HDX
- turn off tablet (long press power button) then reboot to TWRP
- attempt to run unlock.bat
Davey126 said:
- on Windows machine install Motorola Device Manager from here; you do NOT need to launch the device manager once installed
- from TWRP boot into fastboot via Reboot -> Bootloader; the word 'Fastboot' should be displayed on HDX
- on Windows change device driver to "Mot Composite"; the word 'Ready' should appear on the HDX
- turn off tablet (long press power button) then reboot to TWRP
- attempt to run unlock.bat
Click to expand...
Click to collapse
I have tried these steps but no luck with Mot Composite. I just get an error that it FAILED.
I have TWRP Recovery 3.1 installed and I attempted to manually unlock the boot loader but that didn't work out. I want to try the 1-Click which I just got but heres the problem. When I turn on the kindle it goes directly to Kindle Fire [fastboot]. or if I hold down Power and Vol+ I can get to TWRP. What should I do? My ultimate goal is to unlock bootloader. Thank you for any assistance!
tekiro7 said:
I have tried these steps but no luck with Mot Composite. I just get an error that it FAILED.
I have TWRP Recovery 3.1 installed and I attempted to manually unlock the boot loader but that didn't work out. I want to try the 1-Click which I just got but heres the problem. When I turn on the kindle it goes directly to Kindle Fire [fastboot]. or if I hold down Power and Vol+ I can get to TWRP. What should I do? My ultimate goal is to unlock bootloader. Thank you for any assistance!
Click to expand...
Click to collapse
You're pretty much screwed without a ROM or tethered connection. If you can get adb working in TWRP then there's some hope. That should be your focus.
Davey126 said:
You're pretty much screwed without a ROM or tethered connection. If you can get adb working in TWRP then there's some hope. That should be your focus.
Click to expand...
Click to collapse
I downloaded the stock 4.5.5 ROM from another post. After that I booted into TWRP and opened the sideload ADB option. Then I plugged in the kindle and ran the write code to load it. Success! . I have it working again! I will try draxies One-Click-program next. Thanks!