This recovery cannot always be used to make nandroid backups, as the partition layout that is in the recovery is sometimes incorrect for some devices.
Intel Android Devices Root / Temp Recovery Session
- Thread starter social-design-concepts
- Start date
This recovery cannot always be used to make nandroid backups, as the partition layout that is in the recovery is sometimes incorrect for some devices.
mezacorleehone
Senior Member
Goodnight.
someone will know why I do not recognize internal memory and sd?
is 16 GB of internal memory
codename: Saltwell
intel atom z2520
ram:1979 mb
Model: Intel ECS TR10CS1
internal storage:11,42 gb
hardware:TR10CS1_8
android:4.2.2
someone will know why I do not recognize internal memory and sd?
is 16 GB of internal memory
codename: Saltwell
intel atom z2520
ram:1979 mb
Model: Intel ECS TR10CS1
internal storage:11,42 gb
hardware:TR10CS1_8
android:4.2.2
Attachments
Last edited:
mezacorleehone
Senior Member
Thank you very much
I would appreciate any response
since a large part of Latin America
we have the problems with this tablet
delivered by the government.
IntelAndroid-FBRL-05-16-2015-PTR
* ACCEPT
*5
* T4
it does not throw errors
but when entering the recovery does not mount the SD or the Internal
---- IntelAndroid-FBRL-07-24-2015 ---
this one throws errors
* ACCEPT
*5
* T4
neither does the sd mount me
I would appreciate any response
since a large part of Latin America
we have the problems with this tablet
delivered by the government.
IntelAndroid-FBRL-05-16-2015-PTR
* ACCEPT
*5
* T4
it does not throw errors
but when entering the recovery does not mount the SD or the Internal
---- IntelAndroid-FBRL-07-24-2015 ---
this one throws errors
* ACCEPT
*5
* T4
neither does the sd mount me
Attachments
Droidriven
Senior Member
Have you tried using the T3 option as the OP(first post) instructs, instead of T4 option?
Sent from my LGL84VL using Tapatalk
mezacorleehone
Senior Member
Hello, thanks for answering
T1
T2
T3
They are not an option.
T1 throws OEM error
T2 OEM erro
T3 installs the recovery but does not start it.
T4 installs it and starts it but without SD and internal memory
IntelAndroid-FBRL-07-24-2015
when installing
appears on the tablet screen
E: Failed to read
and does not include the partition
logs ext4 / dev / block / mmcblk0p7
IntelAndroid-FBRL-05-16-2015-PTR
Here I do not get any error of that type.
I get a error of recovery.fstab
but it does not mount the storages either
Droidriven
Senior Member
Seems as if the partitioning on your device might be incompatible with the recovery. You said T3 starts but doesn't load recovery and T4 boots but doesn't see your partitions correctly. You may have to modify the T3 or T4 recovery in the tool to work with your device. Or find someone else to do it.
Sent from my LGL84VL using Tapatalk
mezacorleehone
Senior Member
I appreciate your response
I do not understand how to modify the information that you indicate to me.
I'm not experienced.
at least on these issues.
I attached some images for you to see
If you could help me or a member of the forum could help me.
appreciate
and so be able to give solutions to many of my country and other places in South America
Attachments
I have a "dead" Asus ME181c. Display is black but backlight is shining. Cannot boot it into recovery with "Volume up and Power button". Tethered CWM Recovery shows UNKNOWN. I dont get a connection. Asus drivers should be installed. Can somebody give me some advise please how to get it back to life?
Droidriven
Senior Member
unfortunately no, I only get the backlight on the screen, but screen stays black.
I just tryied to root my z580c but unsuccessefully. I fallow all instructions, but i cant enter into temp cwm. Recovery loader showed many errors, as you can see on photo, and device stay in fastboot mode.
What can i do?
I have a Nextbook 8 that is hung up on the boot loader. I can not "make sure you have enabled developer options / adb debugging under settings on your device" because i can't get there from here.
Every time i try to run one of the zip packages, i get a signature error.
I can boot it to TWRP and set the ADB mode, but it can not execute any zipped files, surely due to signing issues...
Is there any way to get it into debugging mode without being able to boot to the OS?
P.S. I didn't break this... I'm trying to help a friend.
(but i could have easily been "one of those guys") LOL
Every time i try to run one of the zip packages, i get a signature error.
I can boot it to TWRP and set the ADB mode, but it can not execute any zipped files, surely due to signing issues...
Is there any way to get it into debugging mode without being able to boot to the OS?
P.S. I didn't break this... I'm trying to help a friend.
(but i could have easily been "one of those guys") LOL
Droidriven
Senior Member
You can boot into TWRP then use the built in terminal emulator or adb to enable USB debugging.I have a Nextbook 8 that is hung up on the boot loader. I can not "make sure you have enabled developer options / adb debugging under settings on your device" because i can't get there from here.
Every time i try to run one of the zip packages, i get a signature error.
I can boot it to TWRP and set the ADB mode, but it can not execute any zipped files, surely due to signing issues...
Is there any way to get it into debugging mode without being able to boot to the OS?
P.S. I didn't break this... I'm trying to help a friend.
Do a Google search for:
"Enable USB debugging with adb"
Sent from my LGL84VL using Tapatalk
Android 9 Slice PIE !
Can any one help me get to PIE! ? !
Android 9.
We need those updated firmware's that allow lower ram usage!
Please help. I am still on 4.4.2 have not rooted yet.
Least like to get highest version I can get if absolutely impossible to get PIE a go!
USA Eastern Time currently 7am (6:55am) [As of post]
Can any one help me get to PIE! ? !
Android 9.
We need those updated firmware's that allow lower ram usage!
Please help. I am still on 4.4.2 have not rooted yet.
Least like to get highest version I can get if absolutely impossible to get PIE a go!
USA Eastern Time currently 7am (6:55am) [As of post]
Last edited:
Droidriven
Senior Member
I doubt anyone will take the time to build P for a device that old. Your best bet is to try learning how to do it yourself.
Sent from my LGL84VL using Tapatalk
TBM 13
Senior Member
Worked very good in Bangho Aero J0101 (Foxconn International Holdings Limited AERO_J0101_J0101HC5AMC1XX)
I'm trying to unlock bootloader in that device.
I'm trying to unlock bootloader in that device.
Most Intel devices are hopeless to unlock the bootloader on, especially Clovertrail+, I've been trying for three years now.
TBM 13
Senior Member
Yeah, mine is clovertrail and hardware is redhookbay. I tried with almost everything and i can't unlock it.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
301Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
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-2833Supported 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 T39IntelAndroid-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.8Links 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
