yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Droidriven:
It's a method that temporarily boots a recovery session without actually permanently flashing the recovery onto the device, then using that temp recovery to root the device. This is typically used on devices that have a locked bootloader or some other security based coding that prevents flashing custom software, these devices can only flash official stock softwares. Thus a bootable temporary recovery session such as this program/script is used because live booting instead of flashing is not an issue in regards to the locked bootloader or whatever coding that prevents actually flashing the recovery.

Once you gain root, root is permanent until removed, but the recovery session is temporary and this tool has to be used again the next time you want/need to boot into a custom recovery.

It explains this in the text in red letters in the first post of this thread almost the first words you see in this thread. You obviously haven't read any of it and decided to ask here instead of reading for yourself, that's laziness. Don't continue to expect help from this community if you're gonna be that lazy.

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Miscellaneous Android Development] CresentChaos:
Hello Program,

I did indeed read the red text but since I'm new to this, I didn't know what i refereed too/

As far as I understood it had something to do with device restart, however due your explanation, I now know that you will require to use the script/tool whenever you need to use another CWM / TWRP ??? (is that correct) .

Please Program, don't get hostile with young-lings ( even though it gets tiring with time ) as we are all here to learn not be judged.
[Miscellaneous Android Development] Droidriven:
The red lettering clearly states that it is for devices with locked bootloader and must be used every time you need a recovery session. How much clearer could it have been?

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Miscellaneous Android Development] CresentChaos:
Hello Program,

Apparently not clear enough for new users ( hence all the posts.. ) anyhow I don't see the point to drag this out as much as it has., specially with someone that clearly can't be too nice... (damn grid filled with issues.)

Thank you for your 1st answer, it was helpful + learned something :]
[Miscellaneous Android Development] yfonsecav:
Restore procedure

aicjofs:

I have the same problem with my IN08A. I downloaded the backup from androidfilehost but I need the restore procedure. Thanks in advance.
[Miscellaneous Android Development] Droidriven:
This is copied from the red lettering in the first post, seems pretty clear to me for anyone with the ability to understand the English language, and it's pretty much exactly what I told you, you understood what I told you so you should have understood it in the first post because I told you the same thing it says.

This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .

I'm not being mean, I'm telling you that you already had what you needed to know the answer, you just didn't pay attention, which is the point I was making when I said you were being lazy. If you had read it more than just once and broken it down in your head, you would have understood what it was saying. Unless you're an idiot, but you aren't an idiot are you? So why didn't you take the time to understand what it was saying? Why didn't you think about it for yourself? The only answer is you were being mentally lazy.

Look deep inside at yourself and then think about what I've said, then you'll understand.

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Miscellaneous Android Development] Lottelita:
So this means that you are able to root the device, say to get rid of bloatware, but you cannot upgrade to a new android version, right?
[Miscellaneous Android Development] Droidriven:
Yes, it allows you to root and modify anything already on the device or apply mods such as Xposed but you can't flash a custom ROM. There is one exception to this, the Intel devices that use this recovery session CAN flash a ROM if they have an unlocked bootloader, there are Intel devices that use this tool even though they don't have a locked bootloader, locked bootloader devices CANNOT flash a ROM.
[Miscellaneous Android Development] Lottelita:
OK. Thanks. I guess I got good use out of it but it's now going to be obsolesced because fewer and fewer apps support it.

Oh, well.

Thanks.
[Miscellaneous Android Development] martyfender:
I realize this is a somewhat old post but:

[MENTION=4790846]KUMARKUSUM[/MENTION] Have you tried the fastboot command:

fastboot flashing unlock

?

That is the command I have to use on my Nextbook Ares 8A, Intel Cherry Trail, Intel Atom x5-Z8350, Android 6.0.1, tablets.
[Miscellaneous Android Development] Kirek50:
My tablet is Trekstor Tolino Tab 8. Android 4.4.4. Root failed, and the reason is in the picture. Do you have an idea what to do next? I tried the option T3 and T4, each time the same effect.
[Miscellaneous Android Development] clyde54:
Hi, I am getting "DEVICE STATUS: UNKNOWN" when running the launcher.bat file from IntelAndroid-FBRL-07-24-2015.7z at the beginning of the instructions. What do you mean specifically by "check your driver installation under Windows Device Manager?" I know what Device Manager is but what driver(s) am I looking for? This tripped me up rooting another device, bricking it, so I would like to avoid that this time. ?
[Miscellaneous Android Development] Droidriven:
Just open device manager while the device is connected, if you don't see a "?" or a "!" beside any of the devices listed, then the driver is installed.

***Note***

There is a different driver for each mode the device is booted into. When you check device manager to verify the driver, make sure you are booted into the correct mode for the instructions in this thread, then you can be sure whether you have the right driver(s).
[Miscellaneous Android Development] clyde54:
I checked Device Manager and I don't see a "?" or a "!" beside any of the devices listed.

Could you please explain what you mean by booting into the correct mode for the instructions?

Thanks
[Miscellaneous Android Development] Droidriven:
Android devices have several modes that can be booted into. For most devices, these are the modes that are most common, each mode requires its own driver when connected to PC. There are other device drivers required for other functions of the device as well, such as: adb drivers when using adb or a driver for using the devices USB tethering ability, for example. Each function that interacts with PC requires a device driver to be installed on PC to allow that function.

1) System-(this mode is the mode you normally use the device in)

2) Bootloader or flashing mode(this mode goes by different names depending on the device, such as: fastboot mode, download mode, Hboot, Droidboot, etc... This is the mode that you must be booted into when flashing via PC tools. This is the mode you need to be booted into when using the instructions in the OP and this is the driver that you need to verify.

3) recovery mode- depending on whether stock or custom recovery, they serve different purposes, stock recovery is limited to only wiping the device, applying stock updates and sometimes limited adb functionality, custom recovery can do much more than stock recovery including backing up/restoring the device and flashing custom ROMs and other custom softwares.

4) Safe mode- this mode is the same as being booted into system normally but this mode only boots the pre-installed system apps, it does not boot the user installed apps. This is a good tool to find out if something that you installed is causing an issue because if the device functions correctly when in safe mode but doesn't when booted into system normally, then you know something that you installed is causing the issue.

There are other modes also but these are the modes typically used by most users.
[Miscellaneous Android Development] clyde54:
How do I boot into these different modes?
[Miscellaneous Android Development] Droidriven:
It can vary from device to device, but generally speaking, holding volume down+power boots to bootloader(flashing mode), volume up+power boots to recovery. Some devices have a bootloader menu screen when using volume down+power, then they select which mode to boot into from that menu. The method to boot into safe mode is different for each device.

Basically, if you want to know how to boot into all of these modes on a device, you need to do a Google search for how to do so on the specific model number that you have.
[Miscellaneous Android Development] clyde54:
Ok now I'm confused again. I extracted the IntelAndroid-FBRL-07-24-2015.7z file, installed the latest adb/fastboot drivers, enabled adb debugging on my tablet, and ran launcher.bat. The instructions say

check that the tool is reporting as either :

DEVICE STATUS: ADB-ONLINE

DEVICE STATUS: FASTBOOT-ONLINE

but instead I am getting a menu of Recovery Options. Nothing about Device Status. Where am I going wrong?
[Miscellaneous Android Development] Droidriven:
When you get the options, what is listed in the options? Are you sure its recovery that you're seeing? Or is it the bootloader menu with options to boot into different modes?

Do you have an option that says "bootloader" or "fastboot"
[Miscellaneous Android Development] m3mmo:
Yeaaah(drago mi je da si rijesio).I also felt like a little child when I rooted this little beast. :good:
[Miscellaneous Android Development] bodivas:
I have not changed anything, that's just an older version..
[Miscellaneous Android Development] jcespi2005:
Perhaps the fstab is needed for Teclast X98 to work... anyway, thanks for pointing to this ;)
[Miscellaneous Android Development] social-design-concepts:
I still have to dig into this devices fastboot.img to figure out why the generated recovery.fstab

isn't work on this device
[Miscellaneous Android Development] HorstiG:
It´s a verry nice beast :), verry fast with 2 GB RAM, I have now installed the app Link2SD (root) and have almost 4 GB of internal memory free.

Some stuff is my Tesla baby faster than my S5, and with GravityBox (xposed) I can adjust the brightness up to 10% down.
[Miscellaneous Android Development] lietkynes82:
I tried to run this cwm on my venue 8 3g. I cannot make a backup. Problem with access to some folders.
[Miscellaneous Android Development] m3mmo:
But you do not need xposed to dim screen more then default.Just install ScreenFilter app from playstore [emoji1]
[Miscellaneous Android Development] juaaslo:
Hello [MENTION=281521]jcespi2005[/MENTION],

I am sorry to bother you again, but you are also a Teclast owner, so I'd like to know what I am doing wrong....

I launch the bat file and choose T3 option correctly. Then CWM starts normally, and I can install the "UPDATE-SuperSU-v2.40.zip" file correctly, so I think I have correctly installed CWM. But when I try to go to recovery after that, I go to the previous Teclast version of recovery, no to this one. Is there any missing step? Or I just misunderstood everything and everytime I want to use CWM I have to run the bat file in windows?

Thank you all for all this great work.

BR
[Miscellaneous Android Development] vampirefo:
That is normal recovery doesn't install, to get into recovery again you need to repeat the process, each and everytime you want to use recovery.
[Miscellaneous Android Development] HorstiG:
I don´t need any Filter, I set the Brightness in GravityBox to 10% minimum. ;)
[Miscellaneous Android Development] fsrkewd:
tried to do this on my Dell Venue 8 7840

At first, i was having trouble installing driver for it, it finally worked after i manually direct the windows driver installer to the inf in the intel driver package. I followed the step and it went into droidboot, and stopped there. I clicked recovery, and it gives me a "no command" screen with a dead android on it. I tried turning it off and on, but it does nothing. I booted into droidboot again by press volume down and power button, and i was able to boot back into android when i choose the reboot option in droidboot.

Did i break anything? When i try to click the recovery option in droidboot, it gives me the no command screen everytime.

EDIT:

Got it to work, and rooted it. The problem for me is that it doesn't seem be able to install the driver automatically, so i have to manually install the driver through device manager to get it to work
[Miscellaneous Android Development] xxxx-g-xxxx:
3730 Bricked?

Hi Guys,

So i followed the instructions and ended up by not getting into CWM. Went to recovery, where i got "no command" after that i rebooted. Now when i try to turn it on, the Dell logo flashes and then a USB logo appears. When i connect it to the PC i get a "CloverviewPlus Device" .

How to i get it to boot again?

Thanks
[Miscellaneous Android Development] gnegne:
If you want to spend some time on analysis. I uploaded the fastboot image of the original manufacturer

rom to

droidboot - X98 Air 3G (C8J7)-Android4.4.4-V2.02.img - 12.49 MB

Let me know if I can help you somehow.

best,

gnegne
[Miscellaneous Android Development] social-design-concepts:
Press and hold power until it turns off and power on holding volume down and power should get you back to droidboot screen the select reboot. I suspect the fastboot driver didn't install correctly
[Miscellaneous Android Development] social-design-concepts:
I'm looking for a couple of tester so when I send it out I'll include you I've give that image a look
[Miscellaneous Android Development] HorstiG:
Tesla ttl7

Tesla TTL7 with root,

thanks again.
[Miscellaneous Android Development] bodivas:
social-design-concepts

sends me the correct link..
[Miscellaneous Android Development] social-design-concepts:
I'll send you a different testing one
[Miscellaneous Android Development] social-design-concepts:
not sure whats going on with the download links i think they are having syncing issues so ill just attach it here : View attachment 3116891
[Miscellaneous Android Development] m3mmo:
Few day ago I tried to do nandroid backup like I did it before,but now when I try to backup to external card it says that card is not mounted!?

All I can remember that is changed is that I made second ext2 partition on card so I can link apps to sd.I am using the latest launcher .Here is the pic with the error mentioned:
[Miscellaneous Android Development] clyde54:
Options are:

POWER OFF

RECOVERY MODE

RESTART BOOTLOADER

NORMAL BOOT
[Miscellaneous Android Development] Droidriven:
If you choose "restart bootloader", does it just bring you right back to that screen with the options?

If so, then it's probably in bootloader/fastboot mode when you see that menu. If it isn't being recognized by PC while in that mode then have you verified that you have USB debugging turned on in system settings on the device?
[Miscellaneous Android Development] clyde54:
Yes. Restart Bootloader brought me right back to the same Menu.

I have also found the following menu (Android system recovery):

reboot system now

apply update from external storage

wipe data/factory reset

fastboot mode

demo mode
[Miscellaneous Android Development] Droidriven:
When in android recovery, select the "fastboot mode" option, it should put you in fastboot mode. Then try connecting and see if you get the same errors.
[Miscellaneous Android Development] clyde54:
http://www.mediafire.com/folder/kwtl7q5vigl3z/XDA

The above link hopefully shows the 3 menus I am seeing on my LG G4. I have tried different options on the menus but still am not getting any status messages as shown on https://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096 when running the launcher. I always get menu 3. Where do I go from here? Thanks
[Miscellaneous Android Development] Droidriven:
The "menu 3" that you mention is the tool from this thread, from there you are supposed to select one of the listed options, each of those options boots a temporary recovery session, try all of those options and see if one of them successfully boots a temp recovery session, if they don't, they won't cause any harm because you aren't flashing the recovery onto the device, you are only live booting it, after you're done using it and you reboot, the recovery goes away and the tool is again required the next time you want to use a recovery session.

LG G4 has its own forum and its own rooting methods. Look in the G4 forum and you'll find what you need.
[Miscellaneous Android Development] clyde54:
I wrote LG G4 by mistake. I'm trying to root my tablet, Acer A3-A30.
[Miscellaneous Android Development] clyde54:
There is one menu that has RESTART BOOTLOADER as one of the options. Another option on this menu is RECOVERY MODE. In lower left of screen for both options FASTBOOT MODE is displayed in red; serial number, version numbers, etc are listed in green. Below this for both options is the message 'Could not open /sys/devices/virtual/backlight' is shown. Selecting RECOVERY MODE brings up this same menu again. Selecting RESTART BOOTLOADER brings up an Android System Recovery menu.

Relevant options on the Android System Recovery menu are 'fastboot mode' and 'apply update from external storage.' Selecting 'fastboot mode' brings up the first menu again.

The launcher tool shows DEVICE STATUS: UNKNOWN for all combinations of menu selections I have tried.

Hope that's clear :eek:

---------- Post added at 05:33 AM ---------- Previous post was at 05:20 AM ----------

There is one menu that has RESTART BOOTLOADER as one of the options. Another option on this menu is RECOVERY MODE. In lower left of screen for both options FASTBOOT MODE is displayed in red; serial number, version numbers, etc are listed in green. Below this for both options is the message 'Could not open /sys/devices/virtual/backlight' is shown. Selecting RECOVERY MODE brings up this same menu again. Selecting RESTART BOOTLOADER brings up an Android System Recovery menu.

Relevant options on the Android System Recovery menu are 'fastboot mode' and 'apply update from external storage.' Selecting 'fastboot mode' brings up the first menu again.

The launcher tool shows DEVICE STATUS: UNKNOWN for all combinations of menu selections I have tried.

Hope that's clear :eek:
[Miscellaneous Android Development] Droidriven:
The fastboot option should be putting you in fastboot mode.

When you connect the device, does it show anything at all in device manager?
[Miscellaneous Android Development] Ran4bud:
I downloaded fbrl file to my docs. Opened launcher but says not a valid 32 application. I also downloaded the tm800a5101cwm.rar file but im not sure what to do with that. And whats the temp recovery script for. How do i use it? Does launcher.bat use cmd or word or notebook. When i open it from rar it says view launcher.bat and its like i can type but it don’t let me type anything. I can use edit but what do i do there? Anyone have a video to make it easier? Its a nuvision tablet tm 800a510l. Stuck on boot no os to start. Im using windows 7 and downloaded all the files. I got adb to work on cmd and fastboot but I don’t know what to do. Been trying everything for 3 days. Please help i hot 2 of these tabs not working
[Miscellaneous Android Development] clyde54:
Under Other Devices/Android Phone there is a yellow triangle with an explanation mark in it. Under Properties it states "The drivers for this device are not installed (code 28)"
[Miscellaneous Android Development] Droidriven:
It helps if you quote my post when replying to me, that way I get a notification and can come check your reply. When you don't quote me reply then I don't know you replied unless I just happen to come check this thread.

I suspected that the device was seen in device manager just not being recognized.

As I asked earlier, have you installed the FULL USB drivers for your device? Or does it only have the drivers that auto install when you first connect the device?

Try installing the drivers, if you don't have a copy of the full USB drivers then do a Google search for:

"USB drivers for (your model number)"

If you already have this drivers installed, uninstall the drivers, restart PC, re-install the drivers then restart the PC.

Try different cables, try different USB ports on PC, try a different PC. You're probably missing something simple without realizing it.
[Miscellaneous Android Development] OverBim:
Hi. Thanks for the recovery. It works in Linux too if you unpack the ZIP and run the commands like here: https://blog.higgsboson.tk/2015/12/25/rooting-intel-based-tablets-on-linux-slash-mac-os-x/

I'll quote here:

So. Now how do I unlock my bootloader on my Medion Lifetab P8314 (Intel Baytrail Z3735F, running Android 5.0.2 x86)? Itried "fastboot oem unlock", but it didn't work... :/
[Miscellaneous Android Development] clyde54:
I have made some progress. I got the driver installed. Device was detected. Selected trigger T4, and files were copied to my device. I am hung up on part 6

"6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier

When I select install.zip I get "E:Can't mount /sdcard/"

I see that SR5-SuperSU-v2.82-SR5-20171001224502.zip is on the tablet under Internal Storage with 4GB available space.

Not sure where to go from here.
[Miscellaneous Android Development] Droidriven:
Have you tried the other options? T1? T2? T3?

Have you made sure that you're at root in terminal/shell?

---------- Post added at 08:04 PM ---------- Previous post was at 07:32 PM ----------

The bootloader doesn't need to be unlocked to use the tool in this thread because the recovery is not being flashed, it is only live booting temporarily until the next reboot, then the recovery is gone.

You will, however, need to unlock the bootloader in order to flash anything other than the stock firmware on the device.

There are other ways to install linux on android, similar to an emulator running the distro but not exactly emulation, more like linux running on top of android with android disabled.

Try this, a member I helped wrote this guide.

https://xdaforums.com/android/software/guide-install-linux-os-alongside-t3726844

He also got full terminal command and adb/fastboot functionality, the full distro with all features working also, you can install pretty much any linux package that your distro supports. Maybe he'll help you get configured also.
[Miscellaneous Android Development] clyde54:
T1-T3 all failed. I tried T4 again and now the process stopped with "E: failure while starting recovery." Now I am stuck at that point. I can't power down or re-boot. Also Device Manager no longer recognizes the device...

It also confuses me that there are 2 menus: Recovery Menu and Fastboot Tethered Recovery Launcher. I have been selecting cwm.zip on the first menu.

And what did you mean by being at root in terminal/shell?
[Miscellaneous Android Development] Droidriven:
It's been a while I used this tool on my tablet, I don't remember the whole process but you should be able to use adb to reboot the device then start over.
[Miscellaneous Android Development] clyde54:
Yes I was able to re-boot to the Fastboot menu. Any ideas on why there are 2 menus as I mentioned above? Also what you mean by being at root in terminal/shell?

The reason I used T4 earlier is the comment below from xdaforums.com/android/help/acer-a3-a30-t3044346
[Miscellaneous Android Development] Droidriven:
The "recovery menu" option probably boots to stock recovery/bootloader. The fastboot tethered recovery should be the temp recovery session.

If at any point you are using adb shell(there is a difference between adb and adb shell), you need to be at root by typing "su" then pressing enter. This gives access to the root partition via command prompt.

When using adb/fastboot(not adb shell) the root command is "sudo"