yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] tofumaster:
I was updating my Mom's Nexus 4 to 4.4 (with the intention of bringing it to the current version to address various security issues -- like stagefright), but it appears to have "soft-bricked" as some people are calling it.

- locked bootloader

- not rooted.

- stock firmware

It goes into a "bootloop"? Where the Google logo displays forever (at least 30 minutes) w/o doing anything.

Normally I'd have spent more time doing this (e.g. backing it up, etc). But due to various personal mishaps in the past year, my tech environment is incomplete and a mess. I've never had problems w/ OTA updates so I foolishly went ahead w/o an adb backup -- which would have at least given me most files (even if I have to redo the entire setup). Also, due to poor timing, I was in a rush to get this done so she'd have a week or so before her trip to get used to the small changes (yes, she freaks out over small changes like the camera UI being different). So, whenever you're doing 2 things at once, you never pay attention to one thing fully. And this is also what happened to the OTA update -- so if there were ANY error messages or anything during the update, I did not notice. =(

Unfortunately I also don't have the device in front of me (things like work get in the way of personal masochism -- aka playing with tech).

Anyhow... I'm not exactly certain if it was going to 4.4. When I downloaded the OTA images for the Nexus 4 for 4.4 and tried to flash using the flash-all tool, it complained that the bootloader was not the right one. When I pulled down 4.3 and tried to flash, it did not complain about that bootloader version. So perhaps it didn't properly flash the bootloader? In any case, is there any chance of getting at the files now before a wipe?

What confuses me, is why I cannot flash w/ a STOCK image. Aren't they signed? Even with a locked bootloader, couldn't it in theory let the right images in?

Also, I'm normally in a windows environment, but due to my machines all being down, I'm on the work MacBook Pro instead. So unfortunately I can't try WugFresh's rootkit -- although I'm not sure it would help w/ a locked boot loader.

So... the questions are:

1) Is there a way to flash to a stock OTA image w/o losing data?

2) Or if that's not possible, is it possible to get the data from the phone?

3) Or I'm out of luck and I shouldn't waste any more time trying to recover what's lost?

(Btw, I didn't lose everything -- e.g. I have photos, sms and call logs backed up. WhatsApp used to be backed up, but it seems like both the 3rd party solution and WhatsApp themselves have stopped supporting some sort of offline backup. So mainly just concerned about files in Downloads or Documents or something -- everything else I've made sure was "on the cloud".)
[Nexus 4 Q&A, Help & Troubleshooting] ariesgodofwar:
First you might try going into Recovery (assuming you can) and wipe the cache partition, then reboot and see if that fixes it. I have had this glitch occur during an OTA update before (It might have been the 4.4 update actually), and wiping the cache and rebooting fixed it every time.

I am trying to understand what happened and what you did exactly. You have a locked bootloader, aren't rooted, and on stock. You are saying OTA and that you tried to flash via flash-all. Are you using the term OTA and referring to the image files in the tarball as the same thing? OTA is the zip file which only contains the files necessary to go from one version to the next higher version. The .tgz factory image file has all of the image files for a complete build. You would not have been able to flash them with a locked bootloader however. Is that what happened here? You tried to flash the img files on a locked bootloader?

Are you able to boot into Fastboot? (Power off your Nexus 4, and reboot it into fastboot mode by holding the volume down button and power.) If so, will your computer recognize your device? You should install Minimal ADB and Fastboot: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 on your Mac and see if it will recognize your device.

If you can get it recognized in Fastboot, you can then just use the fastboot oem unlock command in a terminal window. If you can get the bootloader unlocked, you can then flash the image files properly to recover the device. Here are some instructions: http://www.androidcentral.com/how-unlock-nexus-4-bootloader (***This will wipe your device and you will lose your data if you have to go this route***)
[Nexus 4 Q&A, Help & Troubleshooting] tofumaster:
A solution!

Okay, just to update anyone following this thread.

I sideloaded this: http: // www . androidpolice . com /2013/11/21/the-nexus-4-finally-gets-4-4-heres-how-you-can-flash-the-kitkat-krt16s-ota-manually-root-or-unlock-not-required/

And it worked. But I haven't slept in over 24 hours, so... I think I'm going to sleep now (have to be up in another 4...). Will post more details later (or answer any questions).
[Nexus 4 Q&A, Help & Troubleshooting] tofumaster:
More details

Okay, not much to add, but sometimes these details can be helpful in the future for other people.

When I first posted this, I was past the point of diminishing returns (e.g. where anything you do creates more problems than fixes them). So I was thinking down the wrong path.

ariesgodofwar pointed out that I was trying to apply a the Factory Image over the phone which was NOT the OTA image (which contains only the things it needs to do an update). This clued me in. The OTA update is always a patch. And I'm glad the factory images did not apply because inside the .tgz is a userdata.img which would have wiped all my data anyhow. So... lucky that did not happen.

Instead, I found a signed OTA update (at Android Police) and then used the adb "sideload" technique to apply it. Fortunately, it looked like either nothing was patched successfully the first time, or it happily skipped fully patched files (e.g. maybe it was a mix between 4.3 and 4.4 which was why it was stuck in a boot-loop) and never told me about it on the logs.

Anyhow, it seems to have patched okay, and then went back to the Recovery Menu where I did another Cache Partition Wipe just in case before rebooting. After that, it went to optimizing apps and everything worked as expected. :victory:

In the link above, there's another link that shows you exactly how to get it into the Recover Menu but here it is anyhow: http: // www . androidpolice . com /2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/

(btw, how on earth did I post links in the 2nd post???)
[Galaxy S 5 Android Development (Snapdragon)] supermaster:
Well thought i'd share Stock Firmware for Samsung Galaxy S5 G900F lollipop v5.0 United Kingdom BTU, i know many of us don't have the time to wait for the file from sammobile in order to download. So here is the link and the original file with all whatever the Original Stock Firmware has in store for you:

The Stock firmware release date is:

2015-08-01	United Kingdom	5.0	G900FXXU1BOH4	G900FOXA1BOH4

Download

https://mega.nz/#!NVMkDJgK!vKr24G68OwTudWojzr1HM6kNxFAyXAkV_hOAyZodzUU

If it helps feel free to hit Thanks :)
[Galaxy S 5 Android Development (Snapdragon)] supermaster:
The Stock firmware release date is:

2015-08-01	United Kingdom	5.0	G900FXXU1BOH4	G900FOXA1BOH4
[Moto X Q&A] Tusharc2:
Hello there ! i am using moto x 2013 .. with custom rom installed ( resurrection remix ) and android version 5.1.1 .. there is a problem .... there are many apk which are not installing .. it says "App not installed " i have note 3 i tried to install all those apk files they were working on that mobile .. Help me what to do ?
[8525, TyTN, MDA Vario II, JasJam ROM Development] m.abdulqader:
Hi All,

I am looking for a cab file for the keyboard of WM6 black satin

Thanks in advance
[8525, TyTN, MDA Vario II, JasJam ROM Development] anothersmith:
Muns colored keyboard skin

Don't have the Black Satin Keyboard skin but I've got Muns Colored keyboard skin. I like it better seems you can see the keys better.
[8525, TyTN, MDA Vario II, JasJam ROM Development] FinaLMFamily:
Thanks! It's really nice.
[8525, TyTN, MDA Vario II, JasJam ROM Development] 1chico:
thanks i

like that
[8525, TyTN, MDA Vario II, JasJam ROM Development] ai6908:
is this the one you looking for?
[Sprint LG G3] churchey360:
Anyone know if there is a ROM that supports layers lol?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] moshezf:
Good
[Android Q&A, Help & Troubleshooting] Saberkhan750:
Hi,recently, on Android l, i unlock bootloader and my bionz and x-Reality is out of order.

I flash android4.4.2 build 757 and back bionz and x-Reality.

I want to stay on 4.4.2 and i want kcal(advanced color control)

What to do, what not to do?

Plz plz plz

I am very sad

Plz plz plz
[Samsung Gear VR] Tiamath99:
I just bought the gear vr for my note 4 and i was wondering if i could have comoatibilty problems with the X note custom rom I am currently using.

Thanks in advance
[Samsung Gear VR] Rayan:
Not all custom roms work with the Gear VR. First of all such rom MUST be based on Touchwiz and have a specific kind of kernel. In my case I'm using FireKat v13 along with AEL Kernel. Working great with the VR.
[Samsung Gear VR] gnash.s:
I'm using PopRocks rom on my Note4 and the gear didn't work with the stock kernel in PopRocks rom (stuck at the Health and warning screen in GVR). But it works perfectly with the Emotion kernel (v1.18).
[Samsung Gear VR] vermadas:
I have a SM-N910T and right now I'm using FireKat and AEL kernel, but it looks like, with Netflix requiring Lollipop, I'll need to upgrade soon. PopRocks seems like what I want, I'm just worried that I'll be missing the Adreno GPU driver fix that they pushed in 5.1.1 (which T-Mobile doesn't have yet...) This is what pushed me to use FireKat in the first place, since I was having lots of performance and compatibility issues with Gear VR after upgrading to stock Lollipop.

Does performance seem okay on your setup?
[Samsung Gear VR] gnash.s:
Yeah, I was also on FireKAT since the v1 and jumped on to PopRocks from v1. PR has been pretty stable and smooth. With the emotion kernel, I'm using the Thermal controls and the under-voltage setting as well to keep the Note cooler while using it in GearVR. I usually dirty flash from different versions and if I see any issues, then I clean flash again. Even with the xposed (I need it for exchange bypass) I would say it is pretty stable.
[Samsung Gear VR] sfsilicon:
Can you share your Emotion kernel? I'm on poprocks v9 right now and just want to get GearVR running again. Used AEL on FK which worked fine.

If I do a Nandroid back-up of just the kernel before install of Emotion, I should be able to restore and get back to stock right?

Looking into cooling mods using a fan so I can play longer. Thinking of buying a backcover and doing a fan mod, so I don't need to cut the cover. Reading up where it gets hot the most for fan positioning. ;)
[Samsung Gear VR] gnash.s:
Yeah, but I would probably make a full nandroid backup just in case if something goes wrong.

Sure, I just downloaded directly from the link in the emotion kernel thread, using the v19 rc1.

Note 4, 5.0.1

https://www.mediafire.com/folder/rvxdm018fdm1o/EMOTION_KERNELS_NOTE4#17x02pnhs2ype

Thread

http://xdaforums.com/note-4/orig-development/tw-kernel-emotroid-team-t2990557

Cheers
[XDA Assist] wizbabz:
I am using a Galaxy Note Lte (SHV-E160S) it was working slowly lately so decided to root it to improved it performance. After rooting i Installed an application called SYSTEM APPS REMOVER which help me remove some unwanted apps (like T-Store, S suggest and many other Korean apps) on my phone because i am not using them and they keep on using my data. After going through this process i decided to Factory Reset. Now comes the problem after successfully factory reset it. Went i got to the configuration of language stage the phone keep on freezing and the screen won't respond but the back and menu keys are all working perfectly. Guys i just wanted to ask is the anyway i can skip that stage or any help will be appreciated. Thank you
[XDA Assist] Vivek_Neel:
Hi , thank you for using XDA assist.

Looks like there is no forum specifically for your device. But you may try to post your question here http://xdaforums.com/android/help to get the required help from the expert.

Good luck.
[Nexus 9 Q&A, Help & Troubleshooting] wojwem19:
As in title. Running atm stock 5.1.1 with elementalx kernel ( tried going back to stock one ). At best get 5 h SoT but mostly 4 ( from what I can see people get on average 7-8 hours. Tried clean flashing it once again, tried lollipaloza ( meh ). In addition to that I think the performance of my N9 is pretty weak ( gets laggy on home screen, switching between apps, some games ). Any suggestion about fix ( maybe matter of ROM or kernel? )In worst case scenario will probably just send it back to HTC service.

Cheers
[Nexus 9 Q&A, Help & Troubleshooting] jd1639:
SOT is very dependant on what else is going on with your device. I seriously doubt there is anything wrong with your device and I wouldn't waste your time or HTC's returning it. Those who are getting longer time are doing the following:

Location off

Touch sounds off

Screen dimming on manual and low

To name a few

Google battery life xda. There are many threads on how to get better battery life on XDA. Kernels and roms are not magic bullets.
[Nexus 9 Q&A, Help & Troubleshooting] wojwem19:
DELETED
[Nexus 9 Q&A, Help & Troubleshooting] wojwem19:
Those are screenshots taken 1 min ago of my battery.

http://imgur.com/a/9sH1B

The battery isnt the biggest problem thou ( as long as it keeps 1 day on 1 charge its k for me, ofc would love it to be around 7-8 hours instead of 4.5h ) the biggest problem is my experience about performance of my N9, even thou it is supposed to be much more powerfull device than N5 it just does not feel at least as smooth as N5. It feels way more laggy than N5. Maybe this is how N9 rolls. Does yours N9 like have 2-3 sec delay after pressing home button to return to main screen? boot up 2 mins + ( everytime )? 2-3 sec delay after oppenning apps? You bassiclly feel like it is choking with simple tasks such as returning back to home screen. Cause on my N5 all of those things are instant thats why I am wondering whats a problem here.

1. Gonna try disabling location ( most of time it was on GPS only )

2. I've got touch sound off straight after took it out of box ( it annoyed me )

3. Well my screen is most of a day on like 15% of brightness and when I am in a bed it is min
[Nexus 9 Q&A, Help & Troubleshooting] wojwem19:
Just found it while flicking through Q&A posts in N9 section . This is exactly what I experince.
[Nexus 9 Q&A, Help & Troubleshooting] metaphz:
Yes, everyone experiences this unless they only have the stock GApps installed and nothing else. Eventually the device will become laggy like that after a week or two of a fresh flash of the Nexus images.

It is in my humble opinion that it is not software, but a hardware issue. The device has a 64bit CPU and 64bit OS. That in it self is a good thing, but coupled with the fact it only has 2GB of RAM is where the issue lies. If the N9 had 3GB of RAM we would not be experiencing these issues.
[Nexus 9 Q&A, Help & Troubleshooting] wojwem19:
Yea, you are probably right. Just wanting to add my 2 cents. I've followed some of the advice found here on XDA. A lot of people recommended switching to Dirty Unicorns. So did I. Must admit that it rotated my experience by 180°. My N9 finely feels smooth.
[Nexus 9 Q&A, Help & Troubleshooting] metaphz:
There are customs ROMs on many devices that can give you some visual *tweaks* to give the illusion of faster performance. When it comes down to the bottom line no ROM can add a GB of much needed RAM.

I'm not picking on the N9, I love the device and there isn't another tablet I would rather purchase. Google said they were not making a 2015 Nexus tablet which is fine by me, but it would have been nice to come out with a 2015 of the N9 with 3-4GB of RAM...
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] dl12345:
Anyone have any insight into why my AOSP build isn't completing the boot process? Up to the end of the attached logcat, it seems to be the same as @ChrisJ951's previously posted logcat on a build that boots correctly.

I've rebuilt multiple times after doing a make clobber, repo sync, re-apply patches, etc., but nothing seems to work. Host is Fedora 21, openjdk 1.70_79...
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] DHGE:
What if you try to build without SELinux and double check proper fstab?

It worked here (no touch driver in first release) on my Tablet Z4.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] ChrisJ951:
delete /system/etc/thermalmanager.xml and should boot fine.

The thermalmanager.xml file is messed up and shuts down the phone around 45C (for reference the stock firmware does it around 85C)
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] dl12345:
That didn't seem to do anything unfortunately. I have, however, partially solved the problem. It appears that, for some reason I've not yet identified, the "on nonencrypted" event is not being sent by the vold daemon and as a result, the "class_start main" is not being called in init.rc. This results in a partial boot. I put a temporary hack into init.kitakami.rc to explicitly call class_start main after the "setprop vold.post_fs_data_done 1"

# Touch
mkdir /dev/socket/tfsw 0770 system system

setprop vold.post_fs_data_done 1
class_start main
# Touch
mkdir /dev/socket/tfsw 0770 system system

setprop vold.post_fs_data_done 1
class_start main

After this, the system boots.
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] ChrisJ951:
Unsure why that would happen. I didn't have that issue in any of the builds I did.

Also just to confirm, does your build support SIM card support?
[Xperia Z4/Z3+ Q&A, Help & Troubleshooting] dl12345:
Problem resolved. The build guide is incomplete. Flashing the cache partition is required.

fastboot flash cache cache.img

The "on nonencrypted" event in init.rc is invoked by do_mount_all() from system/core/init/builtins.c when all partitions in fstab are mounted successfully after the mount_all directive is given init.kitakami.rc.

Not flashing the cache partition caused the mount_all to fail and therefore the event was not generated and the class_start main not called.

I confirm no baseband.
[Nexus Player Q&A, Help & Troubleshooting] jprev:
Is anyone aware of a way to get past blackout restrictions on an android TV device? From what I've read you can get around it on a phone using several different methods of spoofing the GPS data/IP data, but I cannot find any information about how to do this with android TV or if it is even possible. Has anyone tried or had any luck with this? Would like to get it working with my nexus player and my shield TV.
[Nexus Player Q&A, Help & Troubleshooting] GabbyWC:
A smart DNS service such as Unotelly should be able to do what you're looking for. They offer an 8-day free trial so you can test their service out without having to pay first. Once you've registered with them, enter the two closest DNS servers in to your router's control panel and the settings should take effect for all the devices on your home network. http://help.unotelly.com/support/so...watch-your-home-team-and-blue-jays-if-you-are
[Nexus Player Q&A, Help & Troubleshooting] jprev:
I've tried unlocator but it doesn't work because it doesn't alter the GPS data... I wonder if unotelly is any different...
[Nexus Player Q&A, Help & Troubleshooting] GabbyWC:
None of the current Android TV boxes have GPS mechanisms inside of them so there's no need to worry about that. It's quick and easy to create a trial account with UnoTelly so try it out and see if it solves your problem with MLB.TV blackout restrictions.
[Nexus Player Q&A, Help & Troubleshooting] jprev:
Interestingly, this worked while unlocator did not! Thanks a lot!
[Nexus Player Q&A, Help & Troubleshooting] GabbyWC:
I'm happy to hear that it worked for you. Can you check to see which version of the MLB.TV app is installed on your Android TV device? v1.3.4 of MLB.TV on my Nexus Player only shows a black screen when I try to load video streams and I'd like to know if anyone else here is experiencing this. http://xdaforums.com/nexus-player/help/mlb-tv-v1-3-4-app-loading-video-t3189553
[Nexus Player Q&A, Help & Troubleshooting] jprev:
I'll have to look but I am currently using a shieldtv and not a nexus player (my nexus player is currently relegated to a shelf due to issues with a lot of apps)
[General Questions and Answers] alhadee12:
Is it a problem giving a potential buyer the IMEI number?
[8525, TyTN, MDA Vario II, JasJam General] mcmexican:
Got my answer

Thanks
[Huawei MediaPad X2] Khiuli:
Hello there!

I'm looking into buying a new phone and those 2 phones in the title called my attention. I'm coming from a Z Ultra so both of them look great to me.

The LeTV Max seems like the better alternative, but let's run down the specs of both of them (mediapad x2 on the left and letv max on the right)

CPU:

Kirin 930 (4x 2GHz and 4x 1.5GHz) x Snapdragon 810 (4x 2GHz and 4x 1.5GHz)

RAM:

3GB x 4GB

Screen size:

7" x 6,33"

Screen resolution:

1200x1920 x 1440x2560

Back Camera:

13MP x 21MP

Battery:

5000 mAh x 3400 mAh

As expected, the LeTV Max wins most of the categories but do they make that much of a difference? Would the +1GB of RAM be a good addition? The screen resolution bump is also pretty interesting, since the MediaPad x2 is going at a 323 ppi and the LeTV Max is at 464. The monster battery on the MediaPad x2 also gets me happy, and knowing that it's not pushing out as many pixels as the LeTV Max (despise the screen size difference) makes it look like it will last longer. Coming from a Z Ultra, the only thing that I really NEED on a camera is flash (the Z Ultra's camera is ok at best) but I don't really require that much quality since I rarely use it.

What do you guys think? For the people that already got a MediaPad x2, are you happy with it? Would you change to a LeTV Max if you had the chance?
[Huawei MediaPad X2] Flavio:
Screen size is everything so I would go for the X2.

Plus you have support from XDA for the X2.

I am actually considering upgrading to an 8.0 inch MediaPad M2!
[Huawei MediaPad X2] Khiuli:
That's exactly what I had in mind. When I was buying the Z Ultra I was able to test and research it better since it was from a known brand. But for the X2 I'm having trouble coming across more specific informations. What you said is what I'm looking for.

The LeTV seems like a pain to repair and it's design looks boring. The specs were buying me but it's pretty much what you said, it's the combination of everything ( and the x2 looks pretty as hell). The only down side for me would be not having a water proof phone like the Ultra but it's something I can get over since it's not a priority for me.

I'll still wait for IFA to see if anything else comes up but the X2 is a strong participant in my choice ( and it's one of the few choices I can actually buy where I live). Thanks for the tips!

If I were going for that, I would just go with one of those cheap 6" phablets with 720p screens, haha. The M2 is pretty overkill for me ( really pretty but still). I can still fit my Ultra on my pockets nicely so the X2 should be good, as far as size goes.
[Huawei MediaPad X2] ajsmsg78:
I looked at the LeTv when searching for large phablets. It's smaller screen size and puny battery turned me off. All these spec wars mean nothing. 1080p vs 2k in a small screen means nothing. 3gb vs 4gb in an Android phone mean nothing if I don't see a performance boost. The X2 is without a doubt the best all around large phone/tablet out there right now. Huawei is a more well known brand especially now that they are making the next Nexus phone.
[Huawei MediaPad X2] Khiuli:
Yea, it's what I thought but when you get almost no reviews and comments about a phone, the specs are the only thing I can use for a guide on this. Huawei is a known brand, just not like Sony. The Z ultra had tons of reviews and feedback when it came out, but I could only find 1 review and many unboxings/ hands on. Thanks for the help!