yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 1S] soubhikmullick:
ive installed this rom and found that there are quite a few bugs in it which are :

1. Proximity sensors turn display off but still tender to function which results in notification panel opening and calendar app popout.

2. Many apps dont seem to work after installation and FC is thrown.

3. Dialer doesnt function all the time and not able to call to people after the OS runs for an hour.

4. NOT ABLE TO RECIEVE CALLS , as the person calling gets a SWITCH Off feedback from operator ( very annoying)

5. Calling is a major bug in this and is not advisable for far travellers

6. Annoying soft reboots when multiple apps are open and you're multitasking with them (3 apps trigger this)

Pros : amazing fresh Ui, lollipop tag and amazing kernel that offers Interactive governor. Rest is pretty much the same.

Conclusion : new build of lollipop 5.0.2 hence the bugs. I would just wait for a few more days or weeks for a better and improvised version comes out

Now switched back to miui v6 6.3.2.0 by syhost and is the most stable and perfect OS for redmi 1s right now.
[Xiaomi Redmi 1S] surajdhanuki:
Please go through other threads before posting a review. Except for the first bug, every other bug u said works flamelessly.

Stop scaring people with wrong info. First learn to flash properly.
[Xiaomi Redmi 1S] soubhikmullick:
I had flashed to rom twice and had downloaded two different times each file, and had confirmed the same with my friend.

The apps that throw FC in my test were BOOM BEACH, BUS SIMULATOR, REAL RACING 3.

No wrong info provided. If you don't get it then you're lucky.
[Xiaomi Redmi 1S] manoranjan2050:
Plz write correct review this not review this your problem .... Call working ... App working fine ... I have open up to 15 app no problem and no lag
[8125, K-JAM, P4300, MDA Vario General] kergen:
I cracked the screen on my O2 xda mini s, so I bought a replacement screen from Ebay. I followed the step-by-step instructions in the service manual, and managed to get it to start, however, the screen is unresponsive, and fades to white when pressed, then fades back to the O2 logo when released. Can anyone recommend a good place to send it to be repaired?

Any help appreciated...
[Xperia Z3 General] finoqq84:
As all have noticed at Xperiablog, Sony is pushing their Xperia exclusive apps to the Play Syore public , first was the background defocus and the Ar effect.. Now even the Album app and their famous walkman app (music). This use to be one of their selling point on Xperia series. Is Sony relly selling off their mobile division? Or something happening inside the mobile phone division.? Lets discuss..
[Xperia Z3 General] Qdezi:
Just for faster apps-updating without upgrading their server, I think!
[Xperia Z3 General] viking2.0:
Yes this is what motorola does too for faster app updates
[Xperia Z3 General] Entropy512:
Yeah. It means nothing unless those apps are installing on non-Sony devices with full functionality.

Samsung has done the same for years. There were numerous apps that would only show if the build fingerprint was correct for a Samsung device, and those apps would fail catastrophically if you used tricks to download them on non-Samsung devices/firmware. (For example, running an AOSP derivative that had a Samsung fingerprint for Play Store compatibility - a number of apps such as the firmware updater for Samsung's Miracast dongle relied on framework components and having a shared UID with the system, and would not even install due to signature mismatches with the system.)
[General Questions and Answers] Element_115:
I downloaded a custom boot animation ( the stock Android Lollipop one) but when I installed it (using ROM Toolbox Pro) , it was blank. I previewed the animation in the app and got "Failed loading the animation. " How do I make it work?

Device: LG Optimus L70 D321

Carrier:Cricket

It is rooted.

Android version: 4.4.2

Stock ROM.
[General Questions and Answers] TheIcE65:
The boot animation is probably broken, maybe due to a bad download.

Just try this one and give me feedback :)

Don't forget to hit the 'thank' if I was helpful!

Here's the link : http://xdaforums.com/crossdevice-dev/sony/mod-android-5-0-lollipop-boot-animation-t2911728
[General Questions and Answers] Phurkus:
some just dont seem to work even after it says it is compatible with your device. .-. i can tell you from experience, some are just a pain in the a**, just look for another OP
[General Questions and Answers] Element_115:
I think you were right. I got the new file and it works :)
[Nexus 7 (2013) Q&A] masterchiefb117:
Ok so here goes my issue. I just got my Nexus 7 2013 in the mail yesterday. I bought it specially to install in my Mitsubishi Lancer. Well going thru the motion that nay flasher would go thru I got machine environment setup (drivers, adb/fastboot, wugs program).

I unlocked thru Wugs OEM unlock procedure then followed with root + custom recovery

Thats where my problems start. Root was not sticking correctly/at all. I got all kinds if error thru TRWP about it unable to mount emmc, boot, userdata, system,....

I have restored thru Wugs program several timers now. I have full access to the tab as far as ADB and Fastboot. I have tried

Phliz Rcovery

CWM

TRWP

In All recoverys I get errors that I cannot mount any partitions and reads 0MB available. I have found cf-auto root to root my Nexus 7 so at least theres that but Im trying to flash either Timurs Kernel or Elemental but cant due to recovery cannot mount anything.

What I have done so far...

OEM Unlock -Pass

Wugs root + custom recovery - failed due to mounting issues

cf-auto root - Pass

Fastboot Erase: System -w, system, userdata, boot, recovery, cache - Pass

Fasboot format: System -w, system, userdata, boot, recovery, cache - Pass

stock recovery factory reset/cache wipe - Pass

At this point am i just SOL and just return my tab ( got it thru Groupon for $149.99 brand new) or is there hope and maybe im just not getting it right which i doubt as I did the same for my Nexus 6 and unlocked/rooted.

--------------

I dont know if this will help but my Tab came in out of box 5.0.1. When booted up an update for 5.0.2 was available so I took it.
[Nexus 7 (2013) Q&A] masterchiefb117:
here are some screenshots to help better explain. These are off TWRP and CWM. Also got a pic of my computer telling me that im on a wrong system setup even though I havent changed anything.,
[Nexus 7 (2013) Q&A] masterchiefb117:
So I went ahead and did flashed stock recovery. I am able to wipe cache and factory reset. Im still wondering if it just any custom recovery Im flashing that is preventing any kind of mounting.
[Nexus 7 (2013) Q&A] masterchiefb117:
Starting to see a trend now. Anyone who somehow if you got your tab with 5.0.1 out of the box and either updated to 5.0.2 you may run into issues with custom recovery not being able to mount partitions and what not.
[Nexus 7 (2013) Q&A] masterchiefb117:
Posting as much info as I can to see if anyone can help me as well as the thread either above me or below with trwp issues. So i tried loading up CM Installer as usually thats my sure fire way to install a custom rom should something be wrong on my end. CM Installer went thru the motion of getting everything setup and right after is indicates to plug in device for prepping and flashing a service warning comes up saying that

"Firmware unsupported for your device at this time"

Then big blue button to close application. So Im not sure what do at at this time as I am currently exhausting all my resources and Google maybe be getting tired of all my Nexus 7 search request.

Also update on what other "procedures" that I attempted

Download terminal from Play store. Tried setting sd as full mount - FAILED

^^ this actually made my tab go full retard as boot up and then kept booting into recovery(TWRP) and if I tired to reboot system or shutdown it would just boot back into TWRP. I had to use WUGS to full flash stock.

Same when trying chmod commands to force mount or force -rw

Booted into recovery and attempted to "ADB Shell" in recovery. Commands were recognized but denied due to mounting issues.

As much abuse I send to it I can still recover from it. I am kinda concerned that if I abuse it to much I may break it. Heres a weird thing

I tried cf-autoroot and watched the commands go thru and saw that cf-auto root can mount /system and /data and declare full mount and root device. After that you see that it puts files in their respected places
[Nexus 7 (2013) Q&A] masterchiefb117:
So looks like twrp updated there recovery today gonna see if this fixes anything
[Nexus 7 (2013) Q&A] masterchiefb117:
Well the the TWRP 2.8.6.0 didn't work either. I'm not sure what to do at this point as I've tried as many things as I can google and can't figure it out. I'm afraid that if try to claim replacement by group on I may get another tab that is similar to this which means I may have problems progressing forward with my goals.
[Nexus 7 (2013) Q&A] fragon69:
I'm in the same boat, I was surprised to see that the cf autoroot went through without a *****.

I also tried to flash a 4.4.4 image and it wouldn't boot up or go past the google logo.

If anyone has any insight to this,it would be greatly appreciated.

I'm going to try flashing from otg when my cable comes in. I'll report back after.
[Nexus 7 (2013) Q&A] TrentB:
Having the same issue too. Unboxed mine today, and went to look how to root, I can unlock it fine but whenever I go in recovery I can't do anything. Android still boots fine...
[Nexus 7 (2013) Q&A] masterchiefb117:
Did your tab out the box come 5.0 or higher. Seems like anyone who got there tab recently had 5.0 or later factory installed. Also with bootloaders you cannot go back when you pass a certain update in this case you if you ever hit 5.0.1 or higher then you cannot go back to anything 4.x.x. Also depends on what your tab shipped with
[Nexus 7 (2013) Q&A] masterchiefb117:
Yeah same here. I wanna get a video of me trying to complete everything. I mentioned this earlier but I am thinking thinking that any tab recently received and has 5.x.x out of box may have a problem. I'm trying to get devs to look I to this but all I'm getting is just get another tab or buy a used one. It doesn't solve the fact that you can still pick up a new one in stores and the ones coning out now are on 5.x.x I'm not trying to buy a second tab from Craigslist when I have a brand new first owner tab in front of me. **sigh first world problems.
[Nexus 7 (2013) Q&A] masterchiefb117:
When you setup your nexus did were you on 5.0.1 and asking for update when you were done with setup
[Nexus 7 (2013) Q&A] TrentB:
Yeah, I got mine from Groupon too. 5.0.1 out of the box. Running it now on 5.0.2 stock and it is OK so I may put off rooting for a while until it gets settled.
[Nexus 7 (2013) Q&A] rsusami:
DEVICE build DATE2014.12 later

android.googlesource.com/kernel/msm.git/+/fa842060088619d2de9986c5c5d588d0f40534e3%5E%21/

.......TWRP2.8.6 no FIX X(

View attachment 3231340
[Nexus 7 (2013) Q&A] masterchiefb117:
Hmmmm I just checked mine and its 2015/02. I got another yesterday and that one is 2015.01. FML looks like new Nexus 7 coming out made a revision.
[Nexus 7 (2013) Q&A] fragon69:
Yea mine was from 2014.12, from groupon too
[Nexus 7 (2013) Q&A] masterchiefb117:
Kinda weird that Groupon selling nexus on deals a d they for some reason no work right. Lol
[Nexus 7 (2013) Q&A] texag:
One more with same issue

Bought from Groupon as will, came with 5.0.1. Haven't updated to 5.0.2 yet.

Unlocked bootloader and installed TWRP. It cannot mount anything (tried 2.8.6.0, 2.8.2.2, 2.8.1.0).

I hope this is a fixable issue. Would hate to return the tablet.
[Nexus 7 (2013) Q&A] masterchiefb117:
Looking at other forums reporting that all Nexus 7 bought from Groupon having the same problems. I bought 2 more, 1 from Frys and another from Best Buy. They are also having issues. Something that they are shipping with them that is making it a problem.
[Nexus 7 (2013) Q&A] texag:
In a way, its good to see this is a widespread issue with the new batch.......hopefully it will get more attention and someone can fix it.
[Nexus 7 (2013) Q&A] rsusami:
self build boot.img for 4.4.4

anago.2ch.net/test/read.cgi/android/1424008707/104

ux.getuploader.com/Nexus7_root/

twrp fix

anago.2ch.net/test/read.cgi/android/1424181336/716

www1.axfc.net/u/3421025.dat
[Nexus 7 (2013) Q&A] Killah1994:
I think this guy might have something going on here!

I followed the link , and seems we might have a bricked recovery (if that even sounds right)
[Nexus 7 (2013) Q&A] TrentB:
Care to elaborate. I looked at the link on my phone but it seems to all be in a foreign language. Bricked recovery as in software or hardware?
[Nexus 7 (2013) Q&A] texag:
Google Translation:

channel ★ smartphone version ★ ■ Back to bulletin board ■ all 1- latest 50

[ROM] baked Nexus 7 (2013) root5 © 2ch.net

151: 147: 2015/03/29 (Sun) 11: 34: 15.69 ID: ExA459GX

>> 149

How can you tell me may be set change?

152: Nameless @ stomach full. : 2015/03/29 (Sun) 12: 04: 24.70 ID: F1zNSgnT

>> 151

Begs leave the gear mark Once you swipe from left

153: Nameless @ stomach full. : 2015/03/29 (Sun) 12: 17: 09.14 ID: BGqU9cGT

>> 146

I'm feeling do you have taken up the kernel commit mill MultiROM.

Kernel is like this of TWRP-MultiROM (deb).

Linux version 3.4.0-Bricked-TWRP-Edition-g0f7854f (tassadar @ tyene) (gcc version 4.7 (GCC)) # 1 SMP PREEMPT Thu Mar 5 17:12:30 CET 2015

In, of me g0f7854f Since this a.

ttps: //github.com/Tasssadar/android_kernel_google_msm/commit/0f7854f7c9fa23651a904f77675518038e85ce67

When say that it is not now healed, hmm?

Android5 the people of pre-installation, do not healed really?

154: Nameless @ stomach full. : 2015/03/29 (Sun) 12: 37: 54.73 ID: R // xbEyi

>> 150

∧_∧

('· Ω ·) hate Dosu

Ha ∨ / ~ ヽ

Bruno [Three Bruno |

(L | <_ Bruno

| * |

Ha, __ |

"" ~ "" "" "" ~ "" ~ "" ~ ""

155: Nameless @ stomach full. : 2015/03/29 (Sun) 13: 49: 55.44 ID: A / eyqQvd

Any of ListROM but've got to boot loop when MultiROM Apude.

In addition, stock, and occur regardless dregs ROM.

156: Nameless @ stomach full. : 2015/03/29 (Sun) 14: 08: 46.70 ID: YjczSraJ

>> 153

Make sure that you can mount in TWRP_multirom_flo_20150328.img.

Finally ... you can flash the Recovery.

But you can DL from official guy is not healed.

ttp: //dl.twrp.me/flo/

157: Nameless @ stomach full. : 2015/03/29 (Sun) 14: 47: 57.15 ID: BGqU9cGT

>> 156

Confirmation Thank You.

And I is not using only MultiROM,

Because the guy who is not a MultiROM did not know what it is which is the kernel of the repository, you do not have push.

keep sending so as to correct After you how I do tell me.

158: Nameless @ stomach full. : 2015/03/29 (Sun) 19: 53: 53.04 ID: irr9KvTc

>> 156, 157

I also / data mount could be confirmed

○ TWRP_multirom_flo_20150328.img

× TWRP_multirom_flo_20150212.img

× openrecovery-twrp-2.8.5.0-flo.img http://techerrata.com/browse/twrp2/flo

× twrp-2.8.6.0-flo.img http://dl.twrp.me/flo/

159: Nameless @ stomach full. : 2015/03/30 (Mon) 00: 53: 34.68 ID: jTUtU9VW

How do not update it's as it is the 2013 of the root haze from 4.4 but I want to raise to 5.0.2

http://tf-android.hatenablog.com/entry/2013/11/19/144132

Article is old, but I think good in the application of this approach

160: Nameless @ stomach full. : 2015/03/30 (Mon) 01: 59: 58.36 ID: SmwZtgDF

>> 159

I would have rolled a ZIP that can be installed from a little to find if TWRP.
[Nexus 7 (2013) Q&A] garrmack:
Its all in Japanese. Something about a KitKat boot image that is either a fix or a problem... Does anyone here have the balls to try flashing the boot image rsusami posted? Rsusami can you provide more description about what you posted?
[Nexus 7 (2013) Q&A] TrentB:
Looks like his first post linked to a updated piece of code for some hardware change made by Asus if I am understanding it right.

mmc: add 5.0 emmc support

bug: 17968808 Kernel change for new eMMC v5.0 parts for FLO/DEB

Change-Id: Ia18152457fe3ff70401b199c267fa37374b9d544
Signed-off-by: hsuan-chih_chen <hsuan-chih_chen@asus.com>
diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index dc4b125..ea1eca7 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -293,7 +293,7 @@
}

card->ext_csd.rev = ext_csd[EXT_CSD_REV];
-	if (card->ext_csd.rev > 6) {
+	if (card->ext_csd.rev > 7) {
pr_err("%s: unrecognised EXT_CSD revision %d\n",
mmc_hostname(card->host), card->ext_csd.rev);
err = -EINVAL;
[Nexus 7 (2013) Q&A] sojhinn:
Whatever he has created is working. Just tried the 4.4.4 boot.img and it looks like its booting up. Cant figure out how to use his twrp fix. Any help with that would be useful.

Just booted in and 4.4.4 is working with one of the nexus 7's that were having issues from groupon. As for the twrp issue. It says that the file is too big.

---------- Post added at 04:59 AM ---------- Previous post was at 04:44 AM ----------

GOT IT TO WORK!!!!!

Here's the twrp file you need: TWRP_multirom_flo_20150328.img

I can't post the link because im too new. But search in google and you will find it first link.

Good luck all!
[Nexus 7 (2013) Q&A] LostIn_Space:
I also have a new nexus 7 ( build date 2014/12) that came with 5.0.1 installed.

It will not mount anything into recovery using toolkit...

I have not tried anything else.
[Nexus 7 (2013) Q&A] TrentB:
Just to clarify you flashed the boot image followed by the twrp fix image?
[Nexus 7 (2013) Q&A] sojhinn:
If you want to use 4.4.4 flash the boot image after you've installed kitkat. After the boot.img install, you can install TWRP using the above search.

If you want to use lollipop and twrp use the search I did above, but ignore installing the boot.img.
[Nexus 7 (2013) Q&A] TrentB:
So sojhinn was correct.

I downloaded the TWRP_multirom_flo_20150328.img from here: http://d-h.st/ixVD

Flashed it with

fastboot flash recovery TWRP_multirom_flo_20150328.img

and TWRP mounts everything beautifully.

Edit: The initial state of my device was (5.0.2 with 4.04 bootloader, rooted with CF autoroot, CWM recovery (non functional))
[Nexus 7 (2013) Q&A] sojhinn:
Nice! And thats the same link I used.
[Nexus 7 (2013) Q&A] TrentB:
Cyanogenmod mod nightly is booting as I type this.

Success!
[Nexus 7 (2013) Q&A] Killah1994:
seems like you guys found a fix, before i head to the post office i'd like to try this. Where do i get this "modified" 4.4.4 boot img. Or do i just flash the TWRP_multirom_flo_20150328.img on 5.0.2 stock?

[Update]

Okk so I've basically updated to 5.0.2 , used cf-auto root, then fastboot flash recovery TWRP_multirom_flo_20150328.img , and as you can see I'm now in recovery with no errors whatsoever!

[Update 2]

When installing any ROM disable "inject multirom after installation" & after installation just hit reboot system (don't hit "MultiROM: Inject curr. Boot sector) once you hit reboot you should be fine!
[Nexus 7 (2013) Q&A] TrentB:
I am not entirely sure what the purpose of the modified 4.4.4 boot.img was.

Master Chief, you should update the first post with the "instructions" I outlined in mine so other people don't have to dig.
[Nexus 7 (2013) Q&A] garrmack:
Fixed TWRP comes from here: [MOD][MAR 28] MultiROM v32
[Nexus 7 (2013) Q&A] sojhinn:
The point of the 4.4.4 boot.img is to be able to "downgrade" to kit Kat. The new nexus 7s don't allow for an older install of the os.
[Nexus 7 (2013) Q&A] TrentB:
Ahh, that makes sense. I was able to flash old bootloader and OSes but nothing ever booted.
[Nexus 7 (2013) Q&A] masterchiefb117:
I will I was so mad that we couldnt get it fixed that I surplussed my nexus tabs :(
[Nexus 7 (2013) Q&A] fragon69:
The multirom recovery worked perfectly for me. Thanks!
[Nexus 7 (2013) Q&A] masterchiefb117:
So after testing like crazy I can confirm myself, I used flash image on device setup. I can fully mount everything and flash at will.

:D
[Nexus 7 (2013) Q&A] Killah1994:
Just here to confirm that the new TWRP_multirom_flo_20150406.img on [MOD][APR 07] MultiROM v32a is indeed working!
[Nexus 7 (2013) Q&A] LostIn_Space:
Has anyone tried this with 5.1 ? Just got the update and rooted with cf-auto root.

Edit: It worked just fine for me with 5.1
[Nexus 7 (2013) Q&A] HampTheToker:
Anyone have that modified 4.4.4 boot.img? I went to the link that rususami provided, but I wasn't able to find it.
[Nexus 7 (2013) Q&A] JoshAdd87:
I'm having hard time following the instructions as written in the OP.

I used cf-auto root, then flashed TWRP_multirom_flo_20150328. I booted into recovery mode and there were no errors for mounting. At this point I thought I was a go for using Wugs toolkit to install 4.4.4. I was apparently wrong as I am greeted by the Google screen again.

What exactly am I missing here?
[Nexus 7 (2013) Q&A] Killah1994:
Your basically missing a modified boot img, to boot 4.4.. Unfortunately we don't have it, it was mentioned but dissolved!
[Nexus 7 (2013) Q&A] HampTheToker:
I found the boot.img in the Japanese thread after a second look. It was buried in some horrible google translation on a different page than the one linked to by rususami.

I just got my Nexus 7 from Amazon a couple days ago, so I'm going to give it a couple more battery cycles before attempting to downgrade to 4.4.4 again. Here's the link to the boot.img that I uploaded to my Dropbox: https://www.dropbox.com/s/8o0kqablv16oiys/boot.zip?dl=0

If anyone else has success with it, do let us know. I'm more curious about whether or not we'll be able to flash a custom kernel after downgrading.

Edit: the boot.img is in a zip, but that's all that's in it. There's no updater script or anything, so this isn't recovery flashable. You'll need to extract it and use fastboot in bootloader mode. I know most of you would have figured that out easily, but I'm putting it out there just in case.
[Nexus 7 (2013) Q&A] Brahim93:
Thanks a lot, it's working like a charm ! You deserve more UP vote ! :good:
[Nexus 7 (2013) Q&A] MrAwesome75:
FINALLY!!!!!!!!!!!!!

I literally spent 24 hours over the last 3 days trying to figure this out. Nexus 7 WiFi seemed like such a good deal for a little device I could flash different ROMs and play around with. If I had known it would be this much trouble, I wouldn't have gotten it. Most of my time searching for solutions was spent reading old forums that didn't really apply to my situation or newer threads that were similar, but not the same. It didn't seem like anyone else in the world had this problem and I didn't even know how to describe it, so I didn't even know what to search for.

The good news is, I got it to work thanks to this thread and I am now running CyanogenMod on Android 5.1.1. If I couldn't get CM working I don't know what I would have done. I probably wouldn't keep the tablet if I couldn't send it back to Amazon.

Thank you for starting this thread and sticking to it. I just got my tablet on Thursday and I was ready to send it back.
[Nexus 7 (2013) Q&A] HampTheToker:
^Really....

I'm still running stock 5.1, and I'm totally happy with it.
[Nexus 7 (2013) Q&A] MrAwesome75:
Amazon, also...

I got my N7 from Amazon; I got one from Groupon for my brother and mine from Amazon at the same time and the boxes say they were both manufactured in December of 2014. Mine (from Amazon) shipped with 5.0.1 and had the same hassle trying to root and use a custom recovery. I haven't opened his yet, but I know it has more to do with when they were made than where they were purchased.
[Nexus 7 (2013) Q&A] vaximily:
I've tried every combination I can think of... this modified boot.img gets it to boot to factory 4.4.4 but as soon as I install CM (tried 10.2 and 11) from TWRP or from fastboot, I get corrupted boot screens (either just black or crazy distrorted blue screen).

Maybe I'm doing something out of order? I've tried it in every order I can think of, wiping everything along each step of the process.