• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

7840 just got update?

Search This thread

dant3ch

Member
May 27, 2014
14
4
Were your able to find a custom recovery to flash after you rooted using those instructions?

Sent from my LG-VS985 using Tapatalk

No, just tethered recovery.

---------- Post added at 09:25 PM ---------- Previous post was at 09:19 PM ----------

Rooted. Just had to install the old droidboot, which also requires installing the old developer firmware if you haven't done the OEM Unlock. I've created a Flash zip to load into Phone Flash Tool Lite which has 3 parts. Flash file 1 flashes the old developer firmware and droidboot. After this completes, run the T4 tethered recovery from @social-design-concepts package and root like normal. At this point get yourself booted into Android and make sure you're rooted etc. Then (optional but highly recommended), you can run Flash files 2 and 3 (in order!) to put back the new droidboot and new firmware. This will make sure you don't have any compatibility issues with video codecs or hardware interfaces or future OTAs or anything. Then, if you want, do the standard Nexus-style OEM Unlock, which will wipe data but leave you with the option of flashing a custom recovery once somebody develops one.

(Standard disclaimer that I take no responsibility for your use of these files, use at your own risk, etc.)



AdAway, mostly.

BIGREDD, I used your instructions and they worked but I'm confused about the second part of your instructions. What are Files 2 and 3 you refer too?
 
Last edited:
  • Like
Reactions: odub303

Chyrio

Senior Member
Jun 9, 2010
377
51
Is everyone else getting this thing where you can't copy in between the sd card and local storage? It always asks me to grant permission but when I do it does nothing? It this because of the encryption?

Sent from my Venue 8 7840 using Tapatalk
 

jjmai

Senior Member
Sep 10, 2008
89
4
Rooted. Just had to install the old droidboot, which also requires installing the old developer firmware if you haven't done the OEM Unlock. I've created a Flash zip to load into Phone Flash Tool Lite which has 3 parts. Flash file 1 flashes the old developer firmware and droidboot. After this completes, run the T4 tethered recovery from @social-design-concepts package and root like normal. At this point get yourself booted into Android and make sure you're rooted etc. Then (optional but highly recommended), you can run Flash files 2 and 3 (in order!) to put back the new droidboot and new firmware. This will make sure you don't have any compatibility issues with video codecs or hardware interfaces or future OTAs or anything. Then, if you want, do the standard Nexus-style OEM Unlock, which will wipe data but leave you with the option of flashing a custom recovery once somebody develops one.

(Standard disclaimer that I take no responsibility for your use of these files, use at your own risk, etc.)



AdAway, mostly.

Does it matter if we use social-design-concepts's IntelAndroid-FBRL-05-16-2015-PTR.7z from the link above.
Or can we use his latest IntelAndroid-FBRL-07-24-2015.7z
 

ecsjr

Senior Member
Aug 17, 2007
51
3
Greetings, I've sorted through about 5 threads and not sure I've found what I am looking for... Does anyone have a "How-to" thread on rooting the Venue 10 7040? I noticed on the Dell opensource site they have a Eaglespeak blankphone zip listed for the Venue 10 7040? Also intel has the MDK 1-year evaluation of system studio... I sort of lost gathering all this info I am finding... What is what? I want root to be able to enable NTFS, exFAT, or ext4 support on the MicroSD port? Is this possible? Please help.
 

ecsjr

Senior Member
Aug 17, 2007
51
3
Rooted. Just had to install the old droidboot, which also requires installing the old developer firmware if you haven't done the OEM Unlock. I've created a Flash zip to load into Phone Flash Tool Lite which has 3 parts. Flash file 1 flashes the old developer firmware and droidboot. After this completes, run the T4 tethered recovery from @social-design-concepts package and root like normal. At this point get yourself booted into Android and make sure you're rooted etc. Then (optional but highly recommended), you can run Flash files 2 and 3 (in order!) to put back the new droidboot and new firmware. This will make sure you don't have any compatibility issues with video codecs or hardware interfaces or future OTAs or anything. Then, if you want, do the standard Nexus-style OEM Unlock, which will wipe data but leave you with the option of flashing a custom recovery once somebody develops one.

(Standard disclaimer that I take no responsibility for your use of these files, use at your own risk, etc.)



AdAway, mostly.

Any chance you can build the flashable zip for the 7040 using the files for the 7040 on dells opensource ftp?
 

taranfx

Senior Member
May 23, 2010
352
248
Mountain view, CA
geeknizer.com
Rooted. Just had to install the old droidboot, which also requires installing the old developer firmware if you haven't done the OEM Unlock. I've created a Flash zip to load into Phone Flash Tool Lite which has 3 parts. Flash file 1 flashes the old developer firmware and droidboot. After this completes, run the T4 tethered recovery from @social-design-concepts package and root like normal. At this point get yourself booted into Android and make sure you're rooted etc. Then (optional but highly recommended), you can run Flash files 2 and 3 (in order!) to put back the new droidboot and new firmware. This will make sure you don't have any compatibility issues with video codecs or hardware interfaces or future OTAs or anything. Then, if you want, do the standard Nexus-style OEM Unlock, which will wipe data but leave you with the option of flashing a custom recovery once somebody develops one.

(Standard disclaimer that I take no responsibility for your use of these files, use at your own risk, etc.)



AdAway, mostly.
I'm on 5.1.1 (latest)
I don't use windows. I'm trying to replicate this on mac:
> fastboot oem unlock
-- OEM unlocked ---
> fastboot oem stop_partitioning
> fastboot flash /tmp/recovery.zip FB_RecoveryLauncher/twrp_hdpi_portrait.zip
FAILED <remote: not allowed to flash this partition>

I understand that you want us to flash old bootlader first. How do I flash that?
> fastboot flash recovery droidboot_502.img? or 510.img?

OEM in unlocked do I've to flash older bootloader, firmware?
How do I flash new bootloader back once I'm done

---------- Post added at 07:07 AM ---------- Previous post was at 06:40 AM ----------

Updated to 5.1 - flashed old droidboot/firmware - rerooted - flashed new droidboot/firmware - all seemed well - went to install Autokiller memory app, which forceclosed - did some investigating - noticed there are no files under sys/module/lowmemorykiller/parameters - believe there should be several files here - i.e. adj, minfree, etc. - could someone verify the that they have these file ?? - fear that I may have had a hiccup during the update ...

Sent from my Venue 8 7840 using Tapatalk

How to flash the old droidboot?
 
Last edited:

drewski1969

Member
Apr 16, 2011
17
0
So I just got a Dell Venue 8 7840 and have been trying all day to get this to work. I am on Android 5.1 and when I try using the flashing tool I get errors and flash failed.
Anyone know what is wrong here ?

03/20/16 11:15:06.616 INFO : Intel(R) Platform Flash Tool Lite V 5.4.2.0 x86 (build on Wednesday February 03rd 2016, 14:44:25 UTC)
03/20/16 11:15:06.616 INFO : Using xFSTK Downloader version: 1.8.1
03/20/16 11:15:07.427 INFO : Using DFU Downloader version: 0.8.3-msvc
03/20/16 11:15:07.428 INFO : Using DnX Firmware Downloader version: 1.0.0.0 (API: 3.0.0.1066)
03/20/16 11:15:08.404 INFO : Using Intel Command Line FlashTool v.2.53 (Download Library v.5.21,0.0 )
03/20/16 11:15:08.665 INFO : Using Android Debug Bridge version 1.0.35
Revision 047597b3fc34-android
03/20/16 11:15:08.665 INFO : OS version detected: Windows 7 (x64)
03/20/16 11:15:08.667 INFO : SSL supported: No
03/20/16 11:15:14.297 INFO : Disk space available on drive C:/ : 7.86 GB
03/20/16 11:15:15.145 INFO : Adb and fastboot binaries OK
03/20/16 11:15:15.480 INFO : Platform Flash Tool Lite initialized successfully
03/20/16 11:15:29.998 INFO : Unzipping archive "C:/Users/Drew/Downloads/venue_7840_droidboots.zip"
03/20/16 11:15:31.724 INFO : Archive "C:/Users/Drew/Downloads/venue_7840_droidboots.zip" unzipped
03/20/16 11:15:31.749 WARNING: Bootloader DnX file not specified in flash configuration ("os_dnx" key)
03/20/16 11:15:31.751 INFO : Ready to flash!
03/20/16 11:15:31.754 INFO : Flash file C:\Users\Drew\Downloads\venue_7840_droidboots\1-502_droidboot_and_firmware.xml [Default] loaded
03/20/16 11:15:43.620 INFO : [Port -1] Starting flash ...
03/20/16 11:15:43.620 INFO : [Port -1] Running `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\xfstkFlashTool.exe" "-1" "C:\Users\Drew\Downloads\venue_7840_droidboots\dnx_fwr_blackburn_qs_rd_opensource.bin" "C:\Users\Drew\Downloads\venue_7840_droidboots\ifwi_blackburn_qs_rd_opensource.bin" "" "C:\Users\Drew\Downloads\venue_7840_droidboots\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` command
03/20/16 11:15:44.532 INFO : [Port -1] Disabling xFSTK Misc DnX
03/20/16 11:15:44.532 INFO : [Port -1] Disabling xFSTK wipe out ifwi option
03/20/16 11:15:44.532 INFO : [Port -1] Using xFSTK Solo interface (new API)
03/20/16 11:15:44.532 INFO : [Port -1] xFSTK Soft Fuse not set
03/20/16 11:15:44.532 INFO : [Port -1] XFSTK Downloader API 1.8.1
03/20/16 11:15:44.532 INFO : [Port -1] Copyright (c) 2015 Intel Corporation
03/20/16 11:15:44.532 INFO : [Port -1] fwdnx -- C:\Users\Drew\Downloads\venue_7840_droidboots\dnx_fwr_blackburn_qs_rd_opensource.bin
03/20/16 11:15:44.532 INFO : [Port -1] fwimage -- C:\Users\Drew\Downloads\venue_7840_droidboots\ifwi_blackburn_qs_rd_opensource.bin
03/20/16 11:15:44.532 INFO : [Port -1] osdnx --
03/20/16 11:15:44.532 INFO : [Port -1] osimage -- C:\Users\Drew\Downloads\venue_7840_droidboots\droidboot_dnx.img
03/20/16 11:15:44.532 INFO : [Port -1] gpflags -- 0x80000c27
03/20/16 11:15:44.533 INFO : [Port -1] softfuse --
03/20/16 11:15:44.533 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #0
03/20/16 11:15:45.663 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #1
03/20/16 11:15:46.793 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #2
03/20/16 11:15:47.923 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #3
03/20/16 11:15:48.553 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #4
03/20/16 11:15:49.683 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #5
03/20/16 11:15:50.813 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #6
03/20/16 11:15:51.943 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #7
03/20/16 11:15:52.573 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #8
03/20/16 11:15:53.703 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #9
03/20/16 11:15:54.833 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #10
03/20/16 11:15:55.964 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #11
03/20/16 11:15:56.594 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #12
03/20/16 11:15:57.724 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #13
03/20/16 11:15:58.854 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #14
03/20/16 11:15:59.984 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #15
03/20/16 11:16:00.614 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #16
03/20/16 11:16:01.744 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #17
03/20/16 11:16:02.874 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #18
03/20/16 11:16:03.504 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #19
03/20/16 11:16:04.634 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #20
03/20/16 11:16:05.764 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #21
03/20/16 11:16:06.894 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #22
03/20/16 11:16:07.524 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #23
03/20/16 11:16:08.654 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #24
03/20/16 11:16:09.784 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #25
03/20/16 11:16:10.914 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #26
03/20/16 11:16:11.544 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #27
03/20/16 11:16:12.674 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #28
03/20/16 11:16:13.805 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #29
03/20/16 11:16:14.935 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #30
03/20/16 11:16:15.565 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #31
03/20/16 11:16:16.695 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #32
03/20/16 11:16:17.825 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #33
03/20/16 11:16:18.955 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #34
03/20/16 11:16:19.585 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #35
03/20/16 11:16:20.715 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #36
03/20/16 11:16:21.845 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #37
03/20/16 11:16:22.975 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #38
03/20/16 11:16:23.605 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #39
03/20/16 11:16:24.735 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #40
03/20/16 11:16:24.735 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Timeout
03/20/16 11:16:25.509 INFO : [Port -1] XFSTK-STATUS--Detecting Intel Device - Attempt #41
03/20/16 11:16:25.509 INFO : [Port -1] XFSTK-STATUS--Aborting download process.
03/20/16 11:16:25.509 INFO : [Port -1] xfstkFlashTool exited with error code 13 Unknown error!
03/20/16 11:16:25.512 ERROR : [Port -1] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\xfstkFlashTool.exe" "-1" "C:\Users\Drew\Downloads\venue_7840_droidboots\dnx_fwr_blackburn_qs_rd_opensource.bin" "C:\Users\Drew\Downloads\venue_7840_droidboots\ifwi_blackburn_qs_rd_opensource.bin" "" "C:\Users\Drew\Downloads\venue_7840_droidboots\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed
03/20/16 11:16:25.512 ERROR : [Port -1] Flash failed (Command type: Ifwi)

---------- Post added at 11:49 AM ---------- Previous post was at 11:39 AM ----------

I just got a Venue 7840 and am only on 5.1. Mine says there is no updates when I check. How did you get to 5.1.1 ? Also whenever I try fastboot oem unlock i just get an error message:
<bootloader> checking unlock authorization
<bootloader> unlock command is protected
<bootloader> Go To Android OS to remove the protection.
FAILED <remote: Unlock not permitted>

I'm on 5.1.1 (latest)
I don't use windows. I'm trying to replicate this on mac:
> fastboot oem unlock
-- OEM unlocked ---
> fastboot oem stop_partitioning
> fastboot flash /tmp/recovery.zip FB_RecoveryLauncher/twrp_hdpi_portrait.zip
FAILED <remote: not allowed to flash this partition>

I understand that you want us to flash old bootlader first. How do I flash that?
> fastboot flash recovery droidboot_502.img? or 510.img?

OEM in unlocked do I've to flash older bootloader, firmware?
How do I flash new bootloader back once I'm done

---------- Post added at 07:07 AM ---------- Previous post was at 06:40 AM ----------



How to flash the old droidboot?
 

GroovyGeek

Senior Member
Oct 11, 2010
912
189
Google Pixel 6 Pro
Google Pixel 6
The described process does not work on my Venue 8 7480, every time I attempt to run the flash tool it complains that the device cannot be rebooted and I need to do so manually. Flashing the first part was possible because there are 30+ re-attempts. However, I cannot flash the second part since the flash tool immediately barfs. Suggestions?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Rooted. Just had to install the old droidboot, which also requires installing the old developer firmware if you haven't done the OEM Unlock. I've created a Flash zip to load into Phone Flash Tool Lite which has 3 parts. Flash file 1 flashes the old developer firmware and droidboot. After this completes, run the T4 tethered recovery from @social-design-concepts package and root like normal. At this point get yourself booted into Android and make sure you're rooted etc. Then (optional but highly recommended), you can run Flash files 2 and 3 (in order!) to put back the new droidboot and new firmware. This will make sure you don't have any compatibility issues with video codecs or hardware interfaces or future OTAs or anything. Then, if you want, do the standard Nexus-style OEM Unlock, which will wipe data but leave you with the option of flashing a custom recovery once somebody develops one.

    (Standard disclaimer that I take no responsibility for your use of these files, use at your own risk, etc.)


    Updated successful but haven't noticed any difference thus far.
    Out of curiosity, what do you guys do with root access since there is no custom ROMs available?
    AdAway, mostly.
    2
    Do you follow this step when you have "fasboot cmd waiting" ?

    2
    I tried to install the latest (unofficial) version v67 of xposed, but it's not working. Instead I ended up in a boot loop which will only show the intel logo. I have already posted it in the related thread.

    Does anybody have a 5.0 rom I can use to reset my tablet?

    I assume you can just go back to the 5.0 system img that xBIGREDDx posted here and using that to follow my steps here.

    It relies on you having access to a recovery, from what I'm reading you'll probably have to flash the older droidboot if you want to use the tethered one.
    2
    Look at this users output :

    http://forum.xda-developers.com/showthread.php?p=61983870

    I read it wrong man i really need to get glasses

    Did the ota include any full kernel images that could be repacked for custom recovery?

    Thanks, based on those shots I apparently had a messed up droidboot. I reflashed it using the dev tools, now I have "Device State - locked" and if I run 'fastboot oem unlock' it asks me if I want to unlock, but it's Google/Nexus style so I will have to data wipe before it lets me unlock. Looks like we won't have to wait for unlocked "developer" firmware anymore. Once I back up some stuff I'll run the unlock and then try the tethered recovery. I think at this point if we could get a flashable recovery that would work fine too.

    The OTA includes a full boot.img, if that's what you're asking.