yashsingh1/xdaforums huggingface dataset:
[Dell Venue] tobago2013:
Today, I got this new System Alert showing that there's a new DELL System Update available...

[IMG="Dell OTA Update"]http://xdaforums.com/picture.php?albumid=12803&pictureid=51553[/IMG]

Since the 7840 has been wide open for Stagefright attacks, I decided to apply this update asap.

OTA download worked smoothly, the initiated reboot sequence does take a bit longer (as advertised), then the system update cycle starts, the Android Toolbox Droid appears - and then breaks down with the usual red excamation mark protruding from its metal body, accompanied by a nondescript "Error"-message....

Only thing I can do then is to do a hard power-off (10 seconds power button-method) and then start the thing up again....

Then the Dell/Intel bootup sequence begins and after a thorough startup period, I'm back at where I started from - no harm done to the system, but no update either.... and the Dell System icon again displays the "new update available"...

Was wondering if any of you had the same problem/experience? And if so, did you find a workaround?
[Dell Venue] sangsanh:
I had the same problem as you. I thought it was just me. Was rooted and the OTA didn't work. Then I unrooted, still same result.
[Dell Venue] thebreezer:
Mine downloads, seems to install, reboots and when back in Lollipop, the update is proposed again.
[Dell Venue] ascovit:
I just got my tablet off eBay and today I got the update message. 3 times it downloaded and nothing happened. A fourth download triggered by checking for system updates via About menu went smoothly (if you consider 30 mins for a 1.8gb download smooth) and it installed correctly. The android version is now 5.1 instead of 5.0.1.
[Dell Venue] thebreezer:
We are not talking about the 5.1 update.
[Dell Venue] ziemas:
Worked fine on my unrooted tablet, although it seems to have installed a bunch of rubbish such as Evernote, Camcard Free, Google Keyboard (with Pinny and Indic languages, huh?), etc, etc, etc.
[Dell Venue] toxic_garden:
if we could get the update.zip, it would most likely be possible to flash it via custom recovery. But after downloading, the file is moved from /sdcard/update.zip to somewhere else just before you can copy it to any other location. So if someone managed to keep the file, i'd be happy if it would be shared here.
[Dell Venue] jamebarron88:
I have it, will upload when I get home. The file is saved in data/data/dell ota update *or something similar under data/data.* I copied it to my sd before rebooting.
[Dell Venue] jamebarron88:
Here is the zip file. https://drive.google.com/file/d/0B8MfsJT1QP9NY0ZXblJyLWt0Wnc/view?usp=docslist_api Mine is only ~230mb and I have not attempted to flash it so don't blame me if it doesn't turn our like you hope.
[Dell Venue] ascovit:
Well it was 5.0.1 before and the Stagefright fix brought it to 5.1.
[Dell Venue] toxic_garden:
awesome, thanks. I'll try it out today in the evening and report back. Current plan is go install old 5.0 boot-img, launch tethered TWRP, install the fix and patch 5.1 boot-img back. It's about time to get permanent recovery for this shiny piece....
[Dell Venue] olvrick:
same for me

---------- Post added at 02:52 PM ---------- Previous post was at 02:09 PM ----------

Wont work, will give status 7 error, tried on TWRP and CWM
[Dell Venue] toxic_garden:
even when trying it from SD? Meh....

I'll google around if there's some way of getting the original recovery back. Since first root, it only boots back into bootloader when trying to access stock recovery. I guess it's in some way needed for this update.

I certainly hope Marshmallow arrives soon as the current situation is really a pain in the a$$
[Dell Venue] olvrick:
will be fun, if rooted devices wont be able to install MM6.0 update
[Dell Venue] toxic_garden:
so i gave it a try. Looks like the update checks the fingerprint of some build.prop string (most likely ro.build.fingerprint). I guess this could easily be changed, but chances are good that we mess up the whole system when being on 5.01 droidboot and applying a fix that's suited for 5.1. As i messed up my system anyways while experimenting with this whole stuff, i just started from scratch, which means putting the phone to factory state using the flash_DDO_BB.xml, dd'ing the system.img back to it's place and downloading the 5.1 update right now. After that, i'll try downloading and installing the stagefright-patch before rooting.
[Dell Venue] olvrick:
system.img provided here is already rooted
[Dell Venue] toxic_garden:
well at least i wasn't able to gain root before explicitly installing the SuperSU-Package via CWM.

Back to topic: i tried nearly everything yesterday, but after 4 hours of experiments, i rest my case. For me, there's no option on installing this update without having a proper working custom recovery on 5.1.
[Dell Venue] Illux:
Did anyone try going back to stock, yano like real stock, install the update via OTA and root as known?
[Dell Venue] toxic_garden:
we'd need an unrooted stock image for that. At least i don't know if there's one flying around already. Also, we'd need to create a 5.1 boot.img and droidboot.img after the stagefright patch.
[HTC Desire Eye] EmreAkz:
CyanogenMod is a free, community built distribution of Android 6.0.1 (Marshmellow) which greatly extends the capabilities of your phone.

Install instructions:

- reboot to recovery

- full wipe

- flash rom zip

- reboot

Rom:

Gapps : http://opengapps.org/

Notes:

This is using the unified HTCMSM8974 kernel based on work from yours truly and other CM contributors.

Kernel source: https://github.com/CyanogenMod/android_kernel_htc_msm8974/commits/cm-13.0

Device tree source: https://github.com/CyanogenMod/android_device_htc_eyeul/commits/cm-13.0

XDA￼evDB Information

CyanogenMod 13 - eye, ROM for the HTC Desire Eye

Contributors

uberlaggydarwin

Source Code: http://github.com/cyanogenmod

ROM OS Version: 6.0.1 Marshmellow

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Testing

Created

Last Updated

working cm 12.1

- make a full wipe

-let it boot wait few minutes (5mins)

-restart the phone

link : https://www.androidfilehost.com/?fid=24352994023709687

bugs:

-nfc

-no camera

special thx to [MENTION=2476734]luisitox22[/MENTION] he tested all my builds :)
[HTC Desire Eye] luisitox22:
Wait? what!? ohhhhhhhhhhhhhhhhh at long last!!!!!!!!

Awesome!!!!
[HTC Desire Eye] karo222:
Is it official or unofficial cyanogen Rom??
[HTC Desire Eye] Rouz.:
Unofficial, most likely.
[HTC Desire Eye] luisitox22:
Please post i would test with please and report :)
[HTC Desire Eye] EmreAkz:
It is a unofficial rom

I need time that evening i can post the Rom or tomorrow
[HTC Desire Eye] luisitox22:
[MENTION=7105308]EmreAkz[/MENTION] thank you very much for the support to our device! would gladly test!!
[HTC Desire Eye] EmreAkz:
Guys i have a Problem i get error messages when i try to brunch i can try to build a cm12.1 is that ok between that i work on the cm13 rom
[HTC Desire Eye] luisitox22:
Sure!!! any rom support is welcome and worth testing :)
[HTC Desire Eye] prmah:
I am not sure but brunch will work when CM 13 or 12.1 will be supported officially by cynogenmod. Instead of brunch you can use lunch and mka bacon combo.
[HTC Desire Eye] luisitox22:
what happened to this cool idea? is it dead? thanks?
[HTC Desire Eye] Rouz.:
Nope.

This thread should be locked until the dev has something to release.

Placeholders are not allowed on XDA.
[HTC Desire Eye] EmreAkz:
so i released the first build pls make a backup before you flash it and report me :)
[HTC Desire Eye] karo222:
Thanks, Nice work

I'll try it soon
[HTC Desire Eye] luisitox22:
Hey thanks! Will try un a little while. Thanks forma the effort!
[HTC Desire Eye] hbrajhbh1:
i flashed the ROM but hangup up on boot load ? tried to hard reset and soft reset nothing is workinghang up with htc logo only?

please any one help any alternative s? it is not going even recovery mode? help
[HTC Desire Eye] Rouz.:
Nevermind. Comment removed.
[HTC Desire Eye] Arun.Gunupudi:
Struck on boot......

Downloaded Eagerly..... ?
[HTC Desire Eye] Rouz.:
Too bad. Thanks for reporting.
[HTC Desire Eye] modaifallah:
Dead?
[HTC Desire Eye] prmah:
I tried to build CM 12.1 . Even CM 12.1 from uberlaggydawins device tree are getting stuck on bootloop. Still not able to get the problem.
[HTC Desire Eye] Rouz.:
You didn't do anything wrong. The source is broken.
[HTC Desire Eye] modaifallah:
Can you port Cyanogenmod MM from M8 source? We already have their kernel source code and I believe they already got working cm MM for their M8 devices.
[HTC Desire Eye] Rouz.:
During my testings, we had a new 5.1 build. Everything was working except the camera.

The camera is a real pain, and there is no solution to it as of now. If the maintainer finds a fix for the camera, a marshmallow build will come soon after that.
[HTC Desire Eye] prmah:
Maintainer already had camera fix but I m nt sure why isn't it released yet. He claimed fully working(with camera) CM for desire eye about a month ago .

Camera blob for desire eye and m9 are same. Which is fixed 2 months ago in CM MM for M9 and code is merged in Desire eye also.
[HTC Desire Eye] Rouz.:
He managed to fix it using confidential resources that he cannot share. He is trying to rewrite the code without copying anything from those sources, and (as of yesterday) it wasn't successful.

I don't know any more details because I quit the testing team yesterday.
[HTC Desire Eye] modaifallah:
Guys we already have working AOSP GPE MM can you just use latest Cyanogenmod source for MM and build it again?

---------- Post added at 02:06 PM ---------- Previous post was at 01:45 PM ----------

Here's link to latest M8 nightly

https://download.cyanogenmod.org/get/jenkins/142419/cm-13.0-20160103-NIGHTLY-m8.zip

Port it to our device using the GPE MM rom as base.

http://xdaforums.com/desire-eye/development/rom-google-play-edition-v1-0-pre-rooted-t3257680
[HTC Desire Eye] Rouz.:
I'm afraid it is not that straight forward. Although CM and GPE both look like stock Android, they are completely different underneath.

GPE has deep integration of HTC Framework, and aside from that, HTC doesn't publish the source code (unlike AOSP Android)

CM has to be compiled from source. So the files from GPE cannot be used.

Maybe some reverse engineering could help the maintainer, but that is just a hunch. I'm not sure if it is possible.
[HTC Desire Eye] modaifallah:
Thanks for the explanation. So what's the next step? Can we the community help you?
[HTC Desire Eye] luisitox22:
this is a very cool initiative! i hope i can support!
[HTC Desire Eye] modaifallah:
Man you already can! Reply me there in the thread or PM me the amount you will donate and I will add your name to the list.. :)
[HTC Desire Eye] luisitox22:
great work and thank you for developing. it was fun testing and i am sure this rom will be awesome in the future.
[HTC Desire Eye] agnostu:
hi all, someone knows if cyanogen 12.1 source for EYE are working?

OR

if i build cyanogen 12.1 can i get a booting rom?
[HTC Desire Eye] Rouz.:
I know cm13 is broken, but I am not sure about the cm12.1.

I guess we will find out once someone gives it a try
[HTC Desire Eye] EmreAkz:
The source for cm12.1 is probely working i mean
[HTC Desire Eye] Rouz.:
Can someone build it? The last build that I tried was booting, so it should boot.

The camera won't work, but a new booting build would be nice!
[HTC Desire Eye] luisitox22:
shame CM does not provide official support fr our device!
[HTC Desire Eye] EmreAkz:
I can do it but in a few weeks in this Moment i have a lot of projects
[HTC Desire Eye] Rouz.:
It's all up to device maintainer
[HTC Desire Eye] agnostu:
I've made a build from 12.1 source but it gets stuck in the bootlogo of cm, I've tried with old kernel and boot finished, i think that there are some trouble with kernel stuff
[HTC Desire Eye] Rouz.:
Do you mind sharing the booting build?
[HTC Desire Eye] luisitox22:
last build i helped test did the same thing. would boot up based on 12.1 boot low bot rate and camera was a no go. willing to help test anytime!
[HTC Desire Eye] Rouz.:
You were testing with Brinly?
[HTC Desire Eye] luisitox22:
I helped a bit EmreAkz but that was a few months ago. CM13 never booted and cm12.1 would ramdomly boot up but cam would not work. He was thinking about dropping support for the eye since it was very complicated to get cm on it it seems :(
[HTC Desire Eye] Rouz.:
That's unfortunate.
[HTC Desire Eye] Rouz.:
Edit: Please delete this post
[HTC Desire Eye] luisitox22:
Wait, we are not getting official cm support ever? dam shame.
[HTC Desire Eye] Rouz.:
I guess not
[HTC Desire Eye] agnostu:
HELLO MY FRIEND,

i've - hard - tried in the past few days to get boot CM 13, with the only results of getting into the CM logo.

I'm not a developer BUT with some scientific mind and right knowledge (-> something that can be learned wasting some time), I think we can get a working build. We can even add MAGIC.

There is a lot of work to but we have stock marshmallow rom (that make the whole things a bit easier).

Anyone who want to join to this crazy project? I'm not in a lost point, but I need some help.

In the next days i will setup repositories.
[HTC Desire Eye] luisitox22:
Count me in! Willing to help and can gladly test builds. Pm me.
[HTC Desire Eye] marsb455:
I can run tests also, message me
[HTC Desire Eye] rpwel:
Is this project dead?
[HTC Desire Eye] dpwguenther:
Hello all, ive tried to do some work on this, i can decompile the system.new.dat just fine but no matter what method i use to recompile it, it either doesnt at all or it recompiles into a 4.0GB system.img, what am i doing wrong??
[HTC Desire Eye] agiavedoni:
6.0.1 version has bugs?
[HTC Desire Eye] tommy1616:
Umm... Where is cm13, is me not-see? Sorry!
[Moto G Q&A, Help & Troubleshooting] hipsterdo0fus:
I was having some connectivity loss earlier, so I powered off, turned back on and on turning back on, I now get the initial splash screen and nothing further. Can boot into the boot menu and recovery. Tried wiping cache first, then factory reset. Neither option changed anything. Any suggestions?
[Moto G Q&A, Help & Troubleshooting] jayc137:
Were you using stock ROM?

Provide more information as to which ROM you were using.
[Moto G Q&A, Help & Troubleshooting] hipsterdo0fus:
I apologize, this is completely stock. I left it on overnight (plugged in) and apparently the battery wouldn't charge in this state as it was dead this morning. Plugged it in and charged for a bit and then tried turning it on and it is doing the same thing as before - hanging up at the initial splash screen.
[Moto G Q&A, Help & Troubleshooting] SoonerDude:
I am helping hipsterdoofus with his phone. I work in the same office.

The only thing I can do is get it into fastboot mode. I was able to get the drivers working in my PC.

When I run fastboot devices, it's showing the moto g.

The bootloader isn't unlocked. I tried to do a "fastboot boot recovery.img" to get it to temp boot into twrp, but it fails since the bootloader is locked.

Is it possible to unlock the bootloader from this state from the fastboot menu?

I assume we can't flash twrp from fastboot without the bootloader being unlocked.

I come from using a Nexus 5, so this device is quite a bit different than what I'm used to. Sorry if I'm asking stupid questions.
[Moto G Q&A, Help & Troubleshooting] SoonerDude:
Just wanted to do an update.

I was able to unlock the bootloader, then I downloaded the GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip file from a link I found on the forum.

I followed the steps for restoring stock firmware in this thread.

I did the section for flashing from the xml.zip file:

mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

If you get "(bootloader) Preflash validation failed" errors on the first two entries, you should be okay to ignore (something I read on another thread here).

After that, the phone rebooted. We weren't sure if it was ever going to finish booting up. It had the boot animation screen for quite some time before it finally loaded the OS.

So the good news is, the phone is booting up, and it's the GPE edition.

Bad news is, it's not detecting the SIM card.

If anyone has any ideas, I would love to hear them.
[Moto G Q&A, Help & Troubleshooting] satanas17:
Maybe trying to reflash corresponding radio firmware ?

http://xdaforums.com/showthread.php?t=2649763
[Fire Q&A, Help & Troubleshooting] AntDeek:
Do we have a change log or know any details?
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
Not yet.
[Fire Q&A, Help & Troubleshooting] bibikalka:
So far it's a lot of restrictions regarding customization (no TWRP boot, no downgrade, google services, etc)

Once the update file is captured, it'll be very straightforward to daisy chain the update on top of the existing one, and get root and all the goodies. Just have to be patient a bit.
[T-Mobile LG G4] Da harrow:
I am attempting to flash my old rooted img to my phone through ADB but it says my device is offline. Now I've been reading everywhere that you can just turn on and off usb debugging to solve the device being offline. Seeing as I can't access settings is there any way around this?
[T-Mobile Samsung Galaxy S 5] nathandgjoe:
I'm a rookie who seems to have deleted the calendar storage app on my T-Mobile Samsung Galaxy S5, and my calendar is no longer working. Every time I try to open it, it says "Calendar Storage disabled" because the app is no longer installed on my phone. I was reading elsewhere that someone else with a 4.4.2 S5 needs to upload their Calender Storage apk so I can reinstall it. Is this the correct solution, and if so, could someone please upload the apk for me! Thanks so much!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] darekz:
to disable update notification and how to delete OTA update files on non-rooted stock 4.4.4 Note 4?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] rile1564:
Non-rooted, not that I know of. I had 4.4.4, 5.0.2 and now 5.1.1.(N910T) This latest update was the best of all the three. Super fast, smooth and snappy. Plus my battery life is fantastic after a week. I'm full stock, never rooted. I highly recommend it. Just make sure to factory reset a few times. Yeah, it's a pain but completely worth it! I was thinking of switching to a V10 or NP6. Once I got the update I haven't looked back.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] rile1564:
Here's a better estimate of battery life on stock, Non-rooted!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ShrekOpher:
Yes. You can feeze the FOTA (firmware over the air) function on the phone. YOU DO NOT NEED ROOT.

Go check out the below thread. Very handy for not root users. It uses ADB to let you disable any system app. Just like the "freeze" option in titanium backup, only root is not required.

http://xdaforums.com/android/software/debloater-remove-carrier-bloat-t2998294/page124
[8125, K-JAM, P4300, MDA Vario ROM Development] soterisk:
look this app is perfect...

just fix the camera lens to make a macro mode (manual)hehe

enjoy...

http://www.penpowerinc.com/wcmobile.html

find this with the emule :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] Funny Sykes:
Hello,

My phone was working on 5.1.1 and then I rooted it with cf-autoroot. It was fine till then, later I flashed my phone with dr.ketan n5 port rom and then my phone had issues at the bootscreen saying seandroid is enforcing.

Later I realized my phone needed xsa firmware which I later flashed, since then the touch stopped working but s-pen works really fine. I am sure there was some problem with recovery/firmware I was using.

So as of now my phone is bricked :( nothing works. Even when I flash my phone with the stock rom from sammobile, it is stuck at the bootscreen. What do I do :(

I'm a noob and it has been a week my phone is bricked.:crying::crying::crying:
[Galaxy Note 4 Q&A, Help & Troubleshooting] GrippingSphere:
Odin flash with option Nand Erase All. After flashing official stock rom, remove and put back battery, then go to recovery and wipe data / factory reset.

This will erase everything on the internal SD card. Be sure to save first to external SD card any important files.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Funny Sykes:
Tried that, the phone booted and that was good, thanks to you. But one more problem that the touch doesn't work but s-pen works fine.

The touch does work, but the orientation is not good. It is like, I press button 3 and button 6 or 9 gets clicked. It is always one cm below where I touch. Can someone please help me with this issue?
[Galaxy Note 4 Q&A, Help & Troubleshooting] GrippingSphere:
Try *#2663# on the stock dialer and update the touch FW
[Galaxy Note 4 Q&A, Help & Troubleshooting] Funny Sykes:
It says tsk Internal update failed when I click on "Touch Key FW Update(Internal Storage)"

What did I do wrong ?:(
[Galaxy Note 4 Q&A, Help & Troubleshooting] GrippingSphere:
Try the upper button, TSP FW update (General)
[Galaxy Note 4 Q&A, Help & Troubleshooting] Funny Sykes:
Wow, Awesome brother. It totally worked. You saved my life like anything :) :D

Thanks a ton :D :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] GrippingSphere:
No problem bro. I'm just sharing what I learned here in XDA.
[General Questions and Answers] quocanha:
So i have installed Xposed Installer 3.0 alpha 4 for lollipop but somthing comes out

It wont work and say: "xposed framework is installed but not active.please check the logs for details

When i check the logs, my logs say:"could not read log:/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (no such file or directory)" .

Any sollution please ?
[General Questions and Answers] LastLeg:
I am having this same issue after moving to a CM13 based ROM for my OnePlus One. Did you find a solution?
[One (M9) Q&A, Help & Troubleshooting] StageProps:
Hey so here's my situation:

Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.

I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.

I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
[One (M9) Q&A, Help & Troubleshooting] jollywhitefoot:
I downloaded and flashed the 2.11.502.18 ruu from the HTC website with no problem. Ate you getting an error?

Edit: in my experience, if an ruu.exe starts to run and then never does (like you get the spinning wheel for a minute and then nothing) it's either a bad download or antivirus is blocking the file. But just to repeat...the exe on the HTC website works fine. I used it about three weeks ago.