FORUMS
Remove All Ads from XDA

Intel Android Devices Root / Temp Recovery Session

2,392 posts
Thanks Meter: 1,811
 
Post Reply Email Thread
Intel Android Devices Root / Temp Recovery Session

Quote:
Originally Posted by social-design-concepts

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
The Following 271 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
 
 
16th December 2014, 04:42 PM |#2  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
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
The Following 31 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
16th December 2014, 04:42 PM |#3  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
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 .
The Following 8 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
16th December 2014, 04:43 PM |#4  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
The Concept / Source Code
The Concept / Source Code
The Following 5 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
16th December 2014, 04:43 PM |#5  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates
The Following 3 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
16th December 2014, 04:44 PM |#6  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
Generic / Tips for Unbricking
Generic / Tips for Unbricking
The Following 3 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
17th December 2014, 02:45 AM |#7  
GeeKerGurL's Avatar
Member
Flag Cancun MX currently
Thanks Meter: 10
 
More
Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.

Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
The Following User Says Thank You to GeeKerGurL For This Useful Post: [ View ] Gift GeeKerGurL Ad-Free
17th December 2014, 02:47 AM |#8  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
Quote:
Originally Posted by GeeKerGurL

Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.

Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!

We can remote around 1130pm est and I'll get you running v8 correct?

Sent from my XT907 using XDA Free mobile app
The Following 3 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
17th December 2014, 02:50 AM |#9  
GeeKerGurL's Avatar
Member
Flag Cancun MX currently
Thanks Meter: 10
 
More
Quote:
Originally Posted by social-design-concepts

We can remote around 1130pm est and I'll get you running v8 correct?

Sent from my XT907 using XDA Free mobile app

Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
17th December 2014, 02:53 AM |#10  
OP Senior Member
Flag Cincinnati
Thanks Meter: 1,811
 
Donate to Me
More
Quote:
Originally Posted by GeeKerGurL

Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?

1 hour 30 minutes

Sent from my XT907 using XDA Free mobile app
The Following 3 Users Say Thank You to social-design-concepts For This Useful Post: [ View ] Gift social-design-concepts Ad-Free
17th December 2014, 02:57 AM |#11  
GeeKerGurL's Avatar
Member
Flag Cancun MX currently
Thanks Meter: 10
 
More
Quote:
Originally Posted by social-design-concepts

1 hour 30 minutes

Sent from my XT907 using XDA Free mobile app

Okie dokie. Ill be here.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes