Intel Android Devices Root / Temp Recovery Session

Search This thread

Messers

New member
Jul 13, 2009
1
0
Thanks a lot!!

Kurio Motion (c14100) using CWM and Trigger 4.
Worked like a charm
 
Last edited:

acidmonkey

Member
Jan 21, 2011
9
2
Hello

I have Acer B1-750. And am trying to root this tablet. I have OS Windows 10 x64.

I cant change default ADB driver.
DEVICE STATUS: ADB-ONLINE
DEVICE INFORMATION: 44642664069 device


my hardware id USB\VID_0502&PID_367B&MI_01
i was try also to change in inf file but i cant install after i change it. So i was try to root with ADB driver that i have already installed but i getting that error on all T1.2.3.4 options. Error is "could not open /sys/devices/virtual/backlight"

anyone have some idea how can i change this ADB driver in windows 10. Think so that problem is in that driver? Or not?
 

Droidriven

Senior Member
Jan 27, 2014
15,404
9
5,349
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Hello

I have Acer B1-750. And am trying to root this tablet. I have OS Windows 10 x64.

I cant change default ADB driver.
DEVICE STATUS: ADB-ONLINE
DEVICE INFORMATION: 44642664069 device


my hardware id USB\VID_0502&PID_367B&MI_01
i was try also to change in inf file but i cant install after i change it. So i was try to root with ADB driver that i have already installed but i getting that error on all T1.2.3.4 options. Error is "could not open /sys/devices/virtual/backlight"

anyone have some idea how can i change this ADB driver in windows 10. Think so that problem is in that driver? Or not?
Do you have the device booted into fastboot mode when you connect the device while the recovery tool is open on PC? If you read the first post of this thread carefully, you'll see where it is supposed to say Device Status: fastboot online.

You might have to manually configure the device drivers in device manager to select the "android bootloader interface" driver.

Go to device manager, select your android device on the list then right click, select update driver, select browse my computer for driver software, select let me pick from a list of available drivers on my computer, select android bootloader interface. Then fastboot should connect correctly.

Sent from my LGL84VL using Tapatalk
 
  • Like
Reactions: Vortell

Bludwurst

Senior Member
Mar 26, 2016
541
477
Moto G
Redmi 9A
have anyone tried to install Magisk by using Tethered CWM?

You can't, to my knowledge, install Magisk in devices with locked bootloader (which is why you're using this tool, no?).

I tried and all I got was my tablet refusing to boot because something something modified software.
(Had to reflash the stock ROM).

Remember Magisk uses a modified boot.img

Sent from my BLU Grand M using XDA Labs
 
  • Like
Reactions: badbd09
It seems like my tablet hasn't locked bootloader (i rooted with Magisk without problems) but i have to use this tool because in fastboot (droidboot) i can't flash nothing (i use fastboot flash recovery) it just says error, and most of oem commands just doesn't exists.

---------- Post added at 18:55 ---------- Previous post was at 18:40 ----------

@social-design-concepts This is no longer updated?

How did you manage to do that?
 

Joanse

Senior Member
May 12, 2014
96
17
Can anyone help me please?

I was messing around with a z3735f intel tablet that had android 6, i used this method to root it and it went all okay....

but then my curiosity started craving me and i realized that if it had a bios setup i could install windows on it, so then i downloaded a version of windows and booted pressing f8 on the keyboard, when it loaded it said something like "flashing bootloader, we need to restart" and then the tablet never booted up again, when i plug it to my pc it never connects and doesnt even sounds when conected, the tablet is off completely and the only sign of "life" is that the processor chip heats up very much, nothing else...

I've read in some forums and youtube videos that it is possible to fix by re flashing the bios but i dont have the tools needed for it and also im not entirely sure if this is the fix for my problem.

can anyone guide me on how to fix my tablet please? thanks
 

Droidriven

Senior Member
Jan 27, 2014
15,404
9
5,349
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
Can anyone help me please?

I was messing around with a z3735f intel tablet that had android 6, i used this method to root it and it went all okay....

but then my curiosity started craving me and i realized that if it had a bios setup i could install windows on it, so then i downloaded a version of windows and booted pressing f8 on the keyboard, when it loaded it said something like "flashing bootloader, we need to restart" and then the tablet never booted up again, when i plug it to my pc it never connects and doesnt even sounds when conected, the tablet is off completely and the only sign of "life" is that the processor chip heats up very much, nothing else...

I've read in some forums and youtube videos that it is possible to fix by re flashing the bios but i dont have the tools needed for it and also im not entirely sure if this is the fix for my problem.

can anyone guide me on how to fix my tablet please? thanks
If you had read this thread carefully you would have understood that Windows can not be installed on your device.

Here is why....

This tool was created to be used to root Intel based devices that have a locked bootloader because custom recovery can not be flashed on devices that have locked bootloader. The only thing that can be flashed on devices that have a locked bootloader is the official stock firmware and official stock updates specifically made for the device in question.

You can't flash anything that is not stock when the device has a locked bootloader. That means you can't flash a custom recovery, can't flash any kind of custom ROMs and can't flash an alternative operating system such as Windows or Linux.

If these devices had bootloaders that are already unlocked, this tool would not be needed and would have never been created because if the bootloader were unlocked, a permanent TWRP could be flashed on these devices instead of having to use this tool to boot a temporary custom recovery session. This tool works on devices that have locked bootloader because booting a temporary recovery does not require actually flashing the recovery onto the device, instead, it merely boots a "live" session, similar to using a bootable USB drive on PC to boot a Linux live USB instead of installing linux on the PC.

Next time you want to modify a device, do more research, read more, look for what CAN and CANNOT be done on your specific device, don't just "assume" that you can flash whatever you want.

You might be able to flash the original stock firmware for the device to repair it, if you can find the correct firmware, but I'm willing to bet that it isn't available anywhere and never was or will be. These cheap tablets usually do not get any kind of support from the manufacturers.

If you had used the TWRP built into this tool to create a nandroid backup of your stock ROM before you attempted to install Windows, you might have been able to restore that backup to fix the device, but it's too late for that.

All of this is because you did not properly research information about your device or the process you attempted to use on the device. You did not verify whether you could actually do it before you tried it, you just assumed you could and now you are paying the price for your ignorance. Consider it a learning lesson.

ALWAYS, ALWAYS, ALWAYS check bootloader status before attempting to flash anything that is not it's own stock software on any kind of android device(regardless of what model it is) to verify if the bootloader is locked or unlocked. If it is locked, you can't flash it with anything that is not it's own stock software, attempting to do so always results in a bricked device. If it is unlocked, you can flash it without the bootloader causing a problem, but that does not guarantee that what you flash will work, it just guarantees that you won't brick the device due to a locked bootloader.

Sent from my SM-S767VL using Tapatalk
 
Last edited:

Wandeta

Member
Dec 25, 2011
49
5
İstanbul
How can I root Reeder A8 i Quad 2 GB ?

Android version : 5.1.1---İntel

I tried the things you said in the discussion but it didn't work
 
Last edited:

sharky1984

New member
Aug 24, 2019
4
0
Hello
I have a Toshiba Tablet AT7-C8

Follow the instructions, issuing the command T3 tablet restarts, while the computer displays "waiting for device", my question as mode manually fastbot on Toshiba AT7-C8 - because I think this is the problem?

Thank you for your help and sorry for English

i have the same issues like this guy. It seems like the fastboot mode is disabled, the script just reboots the tablet, and when i try the VolUp+Power it gets me to stock recovery. Anybody knows how to get into the fastboot on that tablet?
 

Droidriven

Senior Member
Jan 27, 2014
15,404
9
5,349
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
i have the same issues like this guy. It seems like the fastboot mode is disabled, the script just reboots the tablet, and when i try the VolUp+Power it gets me to stock recovery. Anybody knows how to get into the fastboot on that tablet?
Volume down+power or both volume up&volume down+power.

Or, use adb command

adb reboot bootloader

If you get a menu with fastboot as one of the options, select fastboot.

Sent from my SM-S767VL using Tapatalk
 

sharky1984

New member
Aug 24, 2019
4
0
Volume down+power or both volume up&volume down+power.

Or, use adb command

adb reboot bootloader

If you get a menu with fastboot as one of the options, select fastboot.

Sent from my SM-S767VL using Tapatalk
thank you for your fast reply ) that i even didn't hope )
So:
VolDown+ power - just powers on the tablet
VolUp+VolDown+power - enters the stock recovery
adb reboot bootloader - tried before, so as the script is also working with that command - just reboots the system
I get no menu with the options as you said, and as i also saw on other tablets :(
So i kinda lost my hope :(
I readed about some Thrive Toshiba tablets that they disabled the fastboot in the last updates. But they do have a application that after you install you can rollback the firmware to that version where the fastboot was working. But, that app is not doing any progress on my tablet. And then i've searched for any firmware donwgrades for my tablet - nothing there too. This tablet has just one option - upgrade the firmware through the service update application until the last one, and you don't have any way back after, which is pretty ****ty, cause without root it's just a piece of garbage with 4 GB of storage
 

Droidriven

Senior Member
Jan 27, 2014
15,404
9
5,349
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
thank you for your fast reply ) that i even didn't hope )

So:

VolDown+ power - just powers on the tablet

VolUp+VolDown+power - enters the stock recovery

adb reboot bootloader - tried before, so as the script is also working with that command - just reboots the system

I get no menu with the options as you said, and as i also saw on other tablets :(

So i kinda lost my hope :(

I readed about some Thrive Toshiba tablets that they disabled the fastboot in the last updates. But they do have a application that after you install you can rollback the firmware to that version where the fastboot was working. But, that app is not doing any progress on my tablet. And then i've searched for any firmware donwgrades for my tablet - nothing there too. This tablet has just one option - upgrade the firmware through the service update application until the last one, and you don't have any way back after, which is pretty ****ty, cause without root it's just a piece of garbage with 4 GB of storage
Your device might not even have fastboot mode.

Sent from my SM-S767VL using Tapatalk
 

Pran98

New member
Sep 15, 2019
1
0
Fastboot Tethered recovery

Device status: UNAUTHORIZED
My tablet isn't showing any prompt to allow the computer so how shd I get past this?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 300
    Intel Android Devices Root / Temp Recovery Session

    social-design-concepts said:
    Disclaimer:
    Before you proceed to the rooting instructions below, please read this disclaimer:
    XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.

    as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
    i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.

    if you root you should always consider your warranty voided

    Tethered Temporary CWM / TWRP Recovery Session :

    Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
    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. . .

    WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
    It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images


    Intel Fastboot Tethered Temporary Recovery Session Launcher download :
    Current Version : IntelAndroid-FBRL-07-24-2015.7z

    Generic Instructions for use better instructions coming later just wanted to get the thread up :

    notes :
    make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
    make sure you have enabled developer options / adb debugging under settings on your device . . .

    make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd

    1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
    2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue

    check that the tool is reporting as either :
    DEVICE STATUS: ADB-ONLINE
    DEVICE STATUS: FASTBOOT-ONLINE

    If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
    If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok

    3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :

    T1 oem startftm ( very few devices support this command , but its the original used so )
    devices supported : coming soon

    T2 oem backup_factory ( limited devices support this command )
    devices supported : coming soon

    T3 oem stop_partitioning ( should work on alot of kitkat builds )
    devices supported : coming soon

    T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
    devices supported : coming soon

    4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
    note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
    note : if you see unknown oem command the trigger isn't supported by your device.

    5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
    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
    7 : confirm the installation
    8 : after install completes reboot your device

    note :
    some devices have limited space under /system and the supersu app wont install
    if you don't see the supersu app on your device attempt to install it from the playstore
    more than likely the su binary installed correctly but there want enough room on the device for the app.

    This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery


    You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (

    APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE


    XDA:DevDB Information
    Intel Android FBRL, Tool/Utility for the Android General

    Contributors
    social-design-concepts

    Version Information
    Status: Stable

    Created 2015-07-28
    Last Updated 2015-07-28
    33
    Supported Devices List / Trigger

    Supported Devices List / Trigger

    Acer :
    B1-730 T2
    B1-730HD T2

    A1-830

    A1-840FHD T3
    A1-840 (HD) T3

    Asus :
    ME170C T2 & T3
    ME176C T2 & T3

    Dell :
    Venue 7 3730 / Venue 8 3830 All Triggers Should Work
    Venue 7 3740 / Venue 8 3840 T3
    Venue 7 3741 / T3

    Venue 8 7840 T3

    Iview :
    i700 T2 & T3

    Kurio :
    Xtreme 7 Only had a chance to test trigger T3

    Odys :
    intellitab 7

    Nabi:
    Dreamtab model IN08A trigger T3 reported working

    Prestigio :
    MultiPad Thunder 7.0i

    Tesla :
    L7 Tablet T3

    Tesco :
    Op3n Dott 8 T2 & T3

    Toshibia :
    Excite 7 T3
    9
    IntelAndroid-FBRL 05-16-2015 Public Trail Release

    i'm not ready to post a full update so i guess you can call this a public trial , there's a few things i wanna fix not related to the 7840 really just a couple things i wanna add for a couple of other things.

    IntelAndroid-FBRL-05-16-2015-PTR.7z

    one tester reported that on the Dell Venue 7840 that it wouldn't mount the internal sdcard , it's probably an issue with needing a recovery designed for lollipop , but this will still allow you to root.
    8
    Links to devices specific threads / forums

    Links to devices specific threads / forums

    If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .
    6
    The Concept / Source Code

    The Concept / Source Code