yashsingh1/xdaforums huggingface dataset:
[Dell Venue] cowpen:
Just my luck... I rooted my new 7840 last night, but ran out of time to install xposed. Then the update downloaded this morning and I got a prompt to reboot. :( So I postponed the reboot, and ran a system / app data backup.

Not sure how I should proceed at this point? Should I just reboot and lose root until a new method is worked out, or do I have a better option. Would appreciate some guidance. Thanks!
[Dell Venue] vampirefo:
Too late at this point, might as well reboot.
[Dell Venue] ChristianJay:
Bought my mother one for her birthday, man its nicer than my Nexus 9.
[Dell Venue] cowpen:
<sigh> that's kinda what I figured. Oh well... will be watching for some new kung fu from social-design-concepts.
[Dell Venue] soban881:
Hey all, I usually lurk and ride the coat tails of whoever succeeds first, but I couldn't stand to be without root after the update and gave it a shot.

Sorry to report that after an uneventful unlock (checked the debugging option then "fastboot oem unlock"), the Tethered recovery fails to do it's thing (tried T3 and T4 options). The unlocked bootloader is also very annoying; it asks for a power button confirmation every time you boot...

Output from social-design-concepts' 05-16-2015 tethered recovery tool (T4):
[Dell Venue] vampirefo:
Unlocking bootloader isn't going to allow tethered recovery to work, that exploit is done, your droidboot is locked. Now if you were able to use older droidboot you would be OK.

However with unlocked bootloader, you could just flash permanent custom recovery, and then flash root zip through it.
[Dell Venue] soban881:
Aha, didn't catch that - thanks
[Dell Venue] social-design-concepts:
Well the device is unlockable at least. A permanent recovery would be the best option. I'm now curious if this fastboot supports the loading of your own key so you could then relock after flashing.
[Dell Venue] Chyrio:
For those that got the Ota and don't want it yet... Freezing the Dell Update app after (accidentally) hitting the update option in the notification shade will not stop the update. If you freeze the download app it will stop it though!! I think I'm going to wait a bit for this one. Root is very much a need for me.
[Dell Venue] xBIGREDDx:
Looks like Google has changed the Verified Boot spec again, so that button press should go away with the M update, assuming we get it.
[Dell Venue] vampirefo:
Yes that looks very annoying,

[MENTION=2865125]soban881[/MENTION] will it lock back and stop asking for confirmation on each boot.
[Dell Venue] social-design-concepts:
Yep thanks to the California kill switch! Its annoying if your the one that comprises your phone but great if you didn't and say that at least you know your devices was messed with.

I'm unclear on the if an unsigned image will boot after oem lock you might have to install your own keys first minnow board might have some notes I can't recall if you have to flash your own key for lock or just verified boot.
[Dell Venue] vampirefo:
That appears to be a great deal of work and research, I don't have a tablet with 5.1, so I don't plan on looking into it.

If my tablet gets 5.1, or I buy a tablet with 5.1, then things will change, rooting 5.1 seems like it's going to be one on one, no one exploit to cover different devices.
[Dell Venue] soban881:
So far it's asked each boot - I haven't poked around enough to figure out if the confirmation can be stopped. Others may know better; I haven't touched a nexus device in some time so it's all new to me. I haven't re-locked the tablet.

I'd be happy to flash a permanent recovery, but didn't want to use the one from the tethered recovery tool as it appears to be kit kat specific. If someone can point me in the direction of a compatible recovery along with a copy of the stock 5.1 recovery image (or a way to pull it from my device) I'm game to be a guinea pig.
[Dell Venue] syryanyang:
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?
[Dell Venue] xBIGREDDx:
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 [MENTION=4821597]social-design-concepts[/MENTION] 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.)

Flash zip here.

Phone Flash Tool Lite here.

social-design-concepts tether with vampirefo recovery here.

AdAway, mostly.
[Dell Venue] simjo4565:
Thank you !! ...
[Dell Venue] Johnson_145:
Confirmed. I've just tested your method and got root successfully. No further problems yet. Thank you very much!
[Dell Venue] social-design-concepts:
Well now that you can create a backup of the recovery.img you could back it up and make a twrp permanent recovery.img using the tethered assets.
[Dell Venue] vampirefo:
No custom recovery exist for your device, 5.1 was just released, you should work on getting your device to relock and get out of the annoying request on each boot.
[Dell Venue] Johnson_145:
xposed not working

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?
[Dell Venue] anggusss:
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.
[Dell Venue] Lucky Thirteen:
Thanks Bigredd, this has worked flawlessly! :good:
[Dell Venue] Johnson_145:
Thanks! Although it took several hours it's finally working now under Android 5.0.

For everybody else who messed up his/her phone while trying to install xposed on 5.1: The most annoying problem was that nearly every flash action made with the Intel Phone Flash Tool Lite could not be finished anymore. After spending hours to find a solution I finally did: retry it. I changed nothing. Just repeated exactly the same procedure for many times. Can't tell why and when it worked, but probably you need to be lucky and start flashing exactly in the correct moment of boot loop. After successfully reseting the droidboot I needed to reset the rest like described here. I'll stay on 5.0 until anybody has found a way to get xposed work.
[Dell Venue] TonyBigs:
Worked just fine.

5.1 rooted and AdAway installed. Ahhhhh......
[Dell Venue] simjo4565:
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 ...
[Dell Venue] xBIGREDDx:
Mine shows four files:

adj

cost

debug_level

minfree
[Dell Venue] simjo4565:
Could you please post the files or a zip ...

---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------

Bigredd, if my update is corrupt, what do you suggest ??

---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------

Bigredd, If my 5.1 update is corrupt, what do you suggest ??
[Dell Venue] simjo4565:
Eureka !! - rolled back droidboot - flashed 5.1 update.zip from ext SD - flashed current droidboot, then firmware - files appeared - buginess left tablet - I think my original issue occurred when I flashed new droidboot, then firmware in succession without rebooting in-between ...
[Dell Venue] thedreamix:
Sorry for the noob question but can you write step by step how to use Phone Flash Tool ?

I had to shutdown the Dell Tablet before flash ?

Thanks
[Dell Venue] wonglynn2004:
Kudos!

One more question, what I should do if I'm on rooted 5.0 now? Should I directly flash update.zip and flash 2nd and 3rd zip in your files?

Or should I first upgrade to stock 5.1&losing root, and follow all your steps?

Thanks
[Dell Venue] simjo4565:
Install the 5.1 OTA update (losing root) - flash zip 1 - use SDC/vampirefo tethered recovery to regain root - flash zip 2 - then flash zip 3 - done ... Reboot after each flash ;) ...
[Dell Venue] social-design-concepts:
you would need to be using the files for the Dell Venue 7040 not the 7840 that's a good way to own a brick . . . I'm at work at the momment but maybe someone can help you adapt the process with the proper files for the Dell Venue 7040
[Dell Venue] AxMaster007:
Tried substituting the eaglepeak files for the blackburn files by simply renaming them, no dice. guess more work needs to be done on the phoneflash zip.
[Dell Venue] xBIGREDDx:
If you are still wondering, I'd suggest upgrading to stock 5.1 first, then do all the steps.
[Dell Venue] wonglynn2004:
I think I made a mistake and now the device is bricked. I updated to 5.1 from 5.0.2 successfully. And flash your 1st file. And tried to use tethered CWM to root, but accidentally choose "wipe cache" after root. At that time the device freezed. I hold the power button to reboot the device and it cannot boot into the system, stuck at "Intel inside" logo. I tried to use phone flash tool to flash the firmware and droidboot (zip file no.1) but doesn't work, I tried use tethered CWM again but without luck.

What should I do now to unbrick the device?

Thank you.
[Dell Venue] notbadday:
Hi all, does anyone have worldwide stock rom 5.1 for this device. Mine is Chinese version :(
[Dell Venue] RockChalk:
I need help flashing this using the procedure. I'm running Windows 10 64bit. Flashing keeps getting stuck at 33 percent. This is what I'm doing:

1. Installed Intel Flash Tool and Intel Android USB drivers

2. Powered off tablet

3. Loaded 1-502_droidboot_and_firmware with Intel Phone Flashing Tool

4. Connected tablet to PC with OEM cable and pressed volume up and power button

5. Clicked Start to Flash.

Flashing begins, gets to 33 percent and says: Rebooting in Provisioning OS in top portion of window. It sits there for about 2 minutes and then fails. This is what the tools says:

In the bottom portion where output is

08/13/15 14:48:38.769 INFO : [Port 4/1] Command `"xfstkFlashTool.exe" "C:\Users\rockc\Downloads\Dell7840\venue_7840_droidboots\dnx_fwr_blackburn_qs_rd_opensource.bin" "C:\Users\rockc\Downloads\Dell7840\venue_7840_droidboots\ifwi_blackburn_qs_rd_opensource.bin" "" "C:\Users\rockc\Downloads\Dell7840\venue_7840_droidboots\droidboot_dnx.img" "0x80000c27" "none" "none"` succeed

08/13/15 14:48:38.769 INFO : [Port 4/1] Running `Wait for device with status pos on port 4/1` command

08/13/15 14:51:38.769 ERROR : [Port 4/1] Command `Wait for device with status pos on port 4/1` failed

08/13/15 14:51:38.769 ERROR : [Port 4/1] Flash failed (Command type: Device enumeration)

What am I missing?
[Dell Venue] xBIGREDDx:
Does the tablet screen show you in the bootloader? It looks like your computer isn't detecting fastboot. I wonder if there's a conflict with the Intel drivers and Windows 10? Do you have the latest Intel drivers?
[Dell Venue] RockChalk:
Those drivers are installed as well. Intel phone flashing tool says connected when I do volume up+ power. Everything looks good before I begin. It just gets stuck at 33 percent and then stalls.
[Dell Venue] RockChalk:
Sorry, I missed that question earlier.

How do I confirm it is in bootloader mode or computer has detected fastboot?

These are the steps I'm doing:

I power off the tablet and then load firmware through tool. Connect tablet to PC. I hit power button and volume up. Intel tool detects the tablet and says connected. It starts flashing, gets to 33 percent, and times out.

The screen on the tablet is black the entire time except around the 16 percent mark where a USB logo shows up on the tablet for about a sec and then goes back to dark. Then failure notice appears in the tool.
[Dell Venue] xBIGREDDx:
Hmm, after the USB logo, it should transfer the bootloader (a.k.a. droidboot) over and then boot to it; you'd see a screen with an Android robot on it and it would have some information (Product Name, IFWI version, Serial Number, etc.) on it. Do you have any non-Windows 10 systems you could try this from? I don't know why that would be an issue but this is pretty odd behavior that I don't think I've seen before.
[Dell Venue] RockChalk:
I have one Windows 8.1 machine not upgraded to Windows 10. When I repeat the same procedure it fails immediately. I checked device manager and saw that a warning was next to a Morefield device. I uninstalled Android USB drivers and reinstalled in compatibility mode. I think that solved the problem because the warning was no longer there. But when I attempt to flash again, it fails immediately. Still researching....

---------- Post added at 01:16 PM ---------- Previous post was at 12:26 PM ----------

Some success...a little. Removed everything from Windows 8.1 machine and installed again. I get to same 33 percent and see a bootloader which shows Normal Boot and it sits there. Its still fails though.

---------- Post added at 01:23 PM ---------- Previous post was at 01:16 PM ----------

Also, the last dialogue on the screen says, Fastboot CMD waiting...
[Dell Venue] thedreamix:
Are you see this first post http://xdaforums.com/dell-venue/general/how-to-root-lollipop-dell-venue-8-7000-t3160552 ?

It helps me for usb driver.
[Dell Venue] RockChalk:
I'm starting to wonder if there is something wrong with my tablet? I tried the method thedreamix mentioned and the launcher script does not detect the device. Tried on Windows 8.1 and 10 with same results. Reinstalled drivers on both PCs using compatibility mode. Don't know what to do next.
[Dell Venue] thedreamix:
Do you follow this step when you have "fasboot cmd waiting" ?
[Dell Venue] RockChalk:
I did that step this morning and it worked! I clearly missed that step somewhere down the line. That got things moving and I was able to complete all steps! Thank you everyone.
[Dell Venue] cgf:
Thanks for this. I was able to recover from a boot loop using your instructions.
[Dell Venue] dant3ch:
Can encryption be disabled on 5.1 update?

My 7840 downloaded the 5.1 ota. The ota applies mandatory encryption. Is there a way to disable encryption or roll back to 4.4.4? I was able to root and install custom recovery. Thanks
[Dell Venue] odub303:
Tethered recovery or permanent? If permanent, where did you find it?
[Dell Venue] dant3ch:
I used these instructions http://xdaforums.com/showpost.php?p=62013578&postcount=43
[Dell Venue] thedreamix:
You have 5.1.1 ?

I have only 5.1.
[Dell Venue] dant3ch:
No, I only have 5.1. It was a typing error.
[Dell Venue] odub303:
Were your able to find a custom recovery to flash after you rooted using those instructions?
[Dell Venue] dant3ch:
No, just tethered recovery.

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

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?
[Dell Venue] xBIGREDDx:
There is a selection box on the left side labeled "Flash file" (example image) and it should have 3 different options with the zip from my post. It defaults to item 1.
[Dell Venue] Chyrio:
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?
[Dell Venue] thedreamix:
I use this https://play.google.com/store/apps/details?id=nextapp.sdfix

to grant write permission to sd card (root require).
[Dell Venue] jjmai:
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
[Dell Venue] xBIGREDDx:
Probably use the most recent, though I haven't tested it.
[Dell Venue] Johnson_145:
Does anybody have the knowledge to do so? Or does anybody already have made some progress on this?
[Dell Venue] ecsjr:
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.
[Dell Venue] ecsjr:
Any chance you can build the flashable zip for the 7040 using the files for the 7040 on dells opensource ftp?
[Dell Venue] r_nation:
I need the zip as well for venue 7000. I have several posts, can't even get a response
[Dell Venue] r_nation:
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
[Dell Venue] r_nation:
Nevermind lol, that firmware on dells open source isn't 5.1
[Dell Venue] taranfx:
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?
[Dell Venue] el_venga:
i get same problem as post above with 5.1.1 unlocked bootloader.

EDIT: solved the timeout fails when i found this thread http://xdaforums.com/dell-venue/general/root-howto-dell-venue-8-7840-t3282532.

i did same process posted here. i still have to restore the 510 droidboot and firmware.
[Dell Venue] GroovyGeek:
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?
[Dell Venue] arthur7480:
Hi xBIGREDDx，

Could you help to share this OTA file again? The original download link has been removed.

Thanks!

Arthur
[Dell Venue] arthur7480:
Hi，

I tried to flash several times and failed, do you have any other suggestions?
[Moto X Q&A] andsherlock:
Hey Guys

I have a rooted moto x on android 4.4.4 and recently motorola released the android 5.1 OTA update for my device.

So i was just wondering if i should upgrade or not, or if there are any known problems because my friend with a nexus 5 upgraded to lolipop quickly and it was a disaster.

Any help is appreciated.

Thanks
[Moto X Q&A] hugh a:
other than loosing a few contacts ours which includes xt1060's and xt1058's went pretty smooth, some with unlocked BL and some with not
[Moto X Q&A] Bhargav4591:
Pros and cons of lolipop (IMHO)

Pros:

1) New moto voice (you can set your own launch phrase)

2) Marginal lag reduction

Cons:

1) Mobile standby battery consumption is off the charts in all lollipop builds (No solution in sight yet)

2) Wave to wake on active display is disabled , can't get it to work without tasker (yes it was available in 4.4.4, although not advertised)

3) Internal space consumption is higher due to ART implementation

4) If you're an Xposed fan, the builds for Xposed right now are in the Alpha build stage .

5) Can't revert to 4.4.4 stock without chance of permanent bricking

Hope it helps
[Moto X Q&A] Katly:
Hello. I actually searching for help with my phone and found this forum. I have the older moto x xt1058 (factory just the way it comes) it updated 4 days ago and I have already ordered a new phone diff brand. The phone is a complete different thing now.

Some of the issues include Bluetooth and wifi won't work if both on at same time, wifi connection is random, lots of lag time, turned off then back on a few times, drains battery like Super crazy crazy, and then I didn't like the changes in the way things look...like text messaging changed size and font, the keyboards changed ect.

Hopefully my phone is a fluke and other folks do much better.

Good luck to you and have a great day
[LG Watch Urbane] PaulQ602:
FYI.... As of this moment, the official OEM charging cradle for the Urbane is back in stock on Google. $19.99 plus tax, free shipping.

I had been waiting for this.
[Galaxy S 5 Q&A, Help & Troubleshooting] ADMkirito@gmail.com:
If anyone able to help me, please help !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

When I installed the Rom "XtreStoLite 2.2 5.0.2" that came with the anti-theft option even without the Samsung account começou.Mas after seeing it could not clear the anti-theft function because there was no way to enter the samsumg account the way anti-theft blocked my bloatloader and dowload.

I installed the rom stock lolipop alert by Odin 3.0.7. Now my phone this continues with anti-theft and so can not clear the function and I can not access my account now samsumg now for Unmark, someone help me.

...

probably happened to others who have installed the rom '' XtreStoLite 2.2 5.0.2 ''

To understand better see the video ======== """I stole my own mobile phone? """ search on youtube does not cost anything, I could not post the link because I am newbie

youtu.be/4Pjx6VsCPbc

Please help me !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
[Galaxy S 5 Q&A, Help & Troubleshooting] dork997:
okay first of all....calm down.......Here is what you need to do. Flash Stock Kitkat firmware from sammobile From there you can disable reactivation lock in security.

I repeat YOU CAN ONLY DO THIS ON STOCK KITKAT ............. FIRST DOWNGRADE TO KITKAT DISABLE IT and then you may update to lollipop if you want. Hope it helps.
[Galaxy S 5 Q&A, Help & Troubleshooting] ADMkirito@gmail.com:
okay I will try here, please stands by, I'll answer then worked thank you
[Galaxy S 5 Q&A, Help & Troubleshooting] dork997:
did it work?
[Moto G Q&A, Help & Troubleshooting] lost101:
Sounds like possible Bootloader corruption. I would try again with the unbrick tool. Best ask in the thread. Avoid trying to update Bootloader (motoboot.img) - Lollipop is not supported.

Here is the exact 4.4.2 Firmware Image:

http://www.filefactory.com/file/793...9_7_release-keys-cid12-AmericaMovil_AR.tar.gz
[Moto G Q&A, Help & Troubleshooting] epexy:
Thanks for the reply.

Ok, I'll head over to the unbrick thread again. The thing is my phone doesn't seem to be hard-bricked, because it boots to bootlader and it's not recognized by the PC as "qhsusb_bulk" in Device Manager.

That's why I tried to "brick" it using the tool on that thread, but it didnt get bricked at all :\
[Moto G Q&A, Help & Troubleshooting] lost101:
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.