yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 2 Questions & Answers] Riyanx55tu:
1)The only option left is connect the phone to PC or Laptop etc...in fast boot mode then open mi PC suite(make sure u have installed adb drivers of xiomi) then once detected click to flash option on the right Connor of the PC suite and it will ask for

Global ROM or Developer rom(click to global) and wait until it flashes... It is only only way which I restored my redmi 2 when it was totally bricked.

2)if u had not flashed LP ROM of Miui then try to flash Phillz Recovery by jav team and flash the rom. I hope it should fix ur device. or Give away to service center.

The Twrp backup of my phone only contains firmware were I just delete the old ROM first then I restore the firmware then I reboot to recovery again and flash the global kk rom...it works like charm. No need to flash all with fastboot so that's the best option I have.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
Thanks again.

I had tried flashing with MiPCSuite in the past but have now tried it again. It does see the phone, (Shows Flash wt88047) and give the options to flash either Stable or Beta firmware. Choicing either will make it download the firmware and then, when it tries to flash, it stops after just a few seconds with the error "couldn't flash device"

When searching I have found reference to Phillz recovery but so far could not find it for my device. I will search for that again and try to find the right version. Will post the results here.
[Xiaomi Redmi 2 Questions & Answers] Riyanx55tu:
http://www.mediafire.com/?vkg0b4q0m8ka1cl

Phillz recovery.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
Thanks again.

Unfortunatly a new problem has occured.... I can not boot into recovery any more.

If I flash twrp with Flash-TWRP.bat script, my phone reboots to twrp (the script handles that) but if I close twrp down, it is not possible to boot to recovery anymore (pressing VOL UP + POWER and VOL UP + VOL DOWN + POWER don't work) I can still get into twrp by running the .bat script but unfortunatly Philz recovery does not work with that script.

When trying to boot into philz recovery using fastboot (fastboot boot recovery.img where recovery.img is philz recovery) I get the error:

FAILED (remote: dtb not found)

Strange enough, using a twrp recovery it does work... (but twrp does not work anymore with the vol up and power button.....)

Very unfortunate because I had some hope that Philz would be a little more advances so it could fix my partitions...
[Xiaomi Redmi 2 Questions & Answers] Venkatesh:
Philz isn't compatible with your bootloader. For device mismatch follow below thread.

http://en.miui.com/thread-178314-1-1.html

Since your device is 2014813, you should try wt86047 roms. Anyways, your partitions are corrupted and there's less chance of getting it work. Boot up twrp and flash any other new custom roms and check.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
Yes.. again it is for the 88047 and not my phone....

I found some roms that are 100% for my phone so I desided to take that step last (see below).

Yes. I have now all correct versions for my phone. Will write my results at bottom of message.

This is indeed what I think has happened. My partitions are corrupted and the miui stock roms are not able to repair it.....

This is what I have done after your advice:

First of all, I installed the wt86047 stock recovery and then tried to install the original miui. This unfortunatly failed. (the stock recovery just gives a "failed" notice and nothing more)

Then I tried to install the following roms using twrp (wt86047-TWRP3.0.2-0_LP):

HM2014813_Redmi2TD_THUNDER_MiUi7-6.1.28

HM2014813_Redmi2TD_THUNDER-MiUi7-6.3.31

sMiUI_v8_wt86047_6.9.1_YRTTFC

xiaomi.eu_multi_HM2014813_V7.0.9.0.KHJCNCI_v7-4.4

All tries again failed. updater process ended with error 7 or signal 11 and the cache and system partitions where "unable to mount" / zip unable to install.

Then I tried searching for some custom roms and must say... it's hard to find them for my 2014813 / 86047. Most of the custom roms are made for the other models. (this must also be the reason why several people report the "unable to mount system / cache error... flashing the wrong roms....)

So all I could find where following roms wich are 100% for my device (I was able to find some that are reported to work on both but I want a 100% sure fit now....)

wt86047_images_6.9.1_20160805.0000.29_4.4_cn_59a99f5e10

wt86047_images_V6.5.3.0.KHJCNCD_4.4_cn_3c57a69a64

wt86047_images_V7.1.2.0.KHJCNCK_20151209.0000.6_4.4_cn_3df2accecd

wt86047_pro_images_V7.5.2.0.LHJCNDE_20160629.0000.25_5.1_cn_160c620370

And now another the interesting thing.... they all failed, but not with the same error.

The first 3 (non pro ?) failed with the mismatching device error. (are there different versions of the wt86047 ???? probably I can overcome this by disabling the 2 lines....)

The last failed with "error: flash tz error" (this is MiFlash 2016.08.30)

When trying that same rom with MiFlash 2016.04.01 the error is "unspecified error (0x80004005: FAILED (remote: failed to write partition))"

So I disabled the 2 lines in the flash_all.bat files (the check for the mismatch) and I tried flashing all 3 that gave the mismatch error again.

Now flashing in MiFlash fails but with the error: "flash tz error" / failed to write partition

So my conclusion so far....

Partitions are corrupted and show in twrp as ext4 with a size of 0mb and are not mounted.

I apperantly messed up my phones partitions flashing the wrong rom. Flashing original roms or custom roms, either with twrp or miflash / fastboot does not work anymore.

Anyone know how to fix partitions ? Can I manualy resize them ? Any other ideas welcome
[Xiaomi Redmi 2 Questions & Answers] Venkatesh:
Custom roms are same for 2014811 and 2014813 models. You can try any rom but it shouldn't contain any firmware files. Try custom roms from redmi 2 section, all are compatible with your device model.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
ok. I am not 100% sure how I can know / see / find if it contains any firmware files but I gave it a try.

Downloaded 4 (random) roms and tried to flash them with twrp 3.0.2.0:

Tesla-wt88047-6.0.1.EMP.v2.1-BETA-20160509-1435

MK51.1-wt88047-201604121722-UNOFFICIAL

tipsy-wt88047-5.1.1.Final_hangover.v2.3--20160715-1939

ZEPHYR-OS-6.0.1-20160901-wt88047

The first 3 fail.... Several things in the log:

Unable to mount cache and system

This package is for device: HM2014811, HM2014812, HM2014813, etc (up to version 112)

This devices is wt86047

Updater process ended with Error: 7 Error when installing zip file

Since HM2014813 and wt86047 are the same... I don't get why that line is there and the process immediatly fails after this check. The package check is however shown in white and the error in red so maybe the device check does not belong to the error.....

The ZEPHYR-OS-6.0.1-20160901-wt88047 image only failed on the mount error. More specific:

mount: failed to mount /dev/block/bootdevice/byname/system at /system: invalid argument

unmount of /system failed: no such volume

Flashing SuperSU

mount: failed to mount /dev/block/bootdevice/byname/system at /system: invalid argument

unmount of /system failed: no such volume

script succeeded: result was [ ]

And then again the can not mount cache and system error (invalid argument)

Maybe another rom that I should try ? Anything else I can try ??

tia !
[Xiaomi Redmi 2 Questions & Answers] Venkatesh:
Try to mount partitions and formar them from twrp. But i feel you can't do much except playing with partitions. Try some tutorials on formatting corrupted android device partitions.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
I have tried that before. If I select "mount" in twrp it does not want to mount. The phone "fibrates" and thats all that happens.

I tried formatting and even changing from ext4 to some other type.

All seems to fail because it does not want to mount.....

Will do a search for that and give it a try, thanks.
[Xiaomi Redmi 2 Questions & Answers] Exo721:
i using twrp 3.0.1 and it works fine

Sent from deep sea
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
Hello Exo,

I can not find 3.0.1 for my 2014813. I did find 3.0.0.1 but that failed to download from the source where I found it.

I have however tried with both 3.0.0.0 and 3.0.2.0 and the stock recovery, all fail.

For twrp I have made a video of what is actualy happening and where I think the problem lies...

twrp with cache and system directories

[MENTION=4523093]Venkatesh[/MENTION] - Still working on the "corrupt android partitions". Will update here as soon as I have done it. I will however start with a clean PC just to rule out that anything is wrong with the ADB drivers so it will take a few hours / days.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
Update: Tried booting into edl mode to try to flash using edl. Unfortunatly no luck. The phone does not want to boot into edl mode.

Also tried fixing my partitions. I get reasonably far.... I get into the adb shell, I was able to figure out some other things but unfortunatly, when running e2fsck I get some errors that go above my head. Hopefully someone can tell me what to do next.... (process copied below)

tia !

============ adb shell copy paste ============

~ # umount /cache

umount: can't umount /cache: Invalid argument

[Cache was not mounted....]

[ran the next command to find out what I had to fix]

~ # mount

rootfs on / type rootfs (rw,seclabel)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=968148k,nr_inodes=154348,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=968148k,nr_inodes=154348)

pstore on /sys/fs/pstore type pstore (rw,relatime)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

/dev/block/mmcblk0p30 on /data type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk0p30 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

~ # cat /etc/fstab

/dev/block/mmcblk0p24 /cache ext4 rw 0 0

/dev/block/mmcblk0p23 /system ext4 rw 0 0

/dev/block/mmcblk0p30 /data ext4 rw 0 0

/dev/block/mmcblk0p25 /persist ext4 rw 0 0

/dev/block/mmcblk0p1 /firmware vfat rw 0 0

/dev/block/mmcblk1p1 /external_sd vfat rw 0 0

/usb_otg auto rw 0 0

[I desided to start with trying to repair cache]

~ # e2fsck -fv /dev/block/mmcblk0p24

e2fsck 1.42.9 (28-Dec-2013)

ext2fs_open2: Bad magic number in super-block

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

[what followed where bad magic numbers.....]
[Xiaomi Redmi 2 Questions & Answers] Riyanx55tu:
U might be able to delete and create partitions via fastboot (pc) manually but be careful it can damage the device...try some tutorials from YouTube...it might be the only way to create partitions and mount system and cache... Or give away to a service centre. I wonder how ur device got bricked like that... I'm still playing with my device since 2014 nd works without any problems. (Had bricked too many times but still I find easy ways to restore it... And yet it didn't corrupt my partitions).

---------- Post added at 04:20 AM ---------- Previous post was at 04:04 AM ----------

http://elinux.org/Android_Fastboot

I hope this would give u some instructions.
[Xiaomi Redmi 2 Questions & Answers] nachtwacht:
Thanks to all that helped.

I have officialy given up. I do not want to go to deep into creating partions etc. myself afraid to do more damage than good. I therefore desided to sell the phone for parts or someone that is better at this might be able to fix it.

Since fastboot and twrp is still possible there probably still is a way but knowing close to nothing about linux etc. it's just costing me to much time to make it worth it.

Thanks again ! If I hear that it is fixed and how it was fixed I will give an update for future readers since I know through my google searching there are much more people out there that experiencing the same problem.
[Xiaomi Redmi 2 Questions & Answers] Nebulon22:
Still waiting for the problems solver.. Unfortunately i have the same case.. Some one told me its your emmc ic fault.. but i hope it's not..
[Xiaomi Redmi 2 Questions & Answers] ramar123:
Were you able to get to a solution, i am at the same superblock error while fsck situation
[Xiaomi Redmi 2 Questions & Answers] ali.f:
Try flashing newest twrp 3.1.1 or 3.2.1. Before flashing rom or custom rom flash firmware by nicknitewolf on lineage os thread.

https://xdaforums.com/redmi-2/development/rom-lineageos-14-1-t3529286
[BlackBerry Priv] cwolfxuk:
As per the title really. Following the update to aag111 it appears that the front camera is dead. Apps cannot see it, the camera app has switch camera greyed out.

Also, previously if I had headphones in then it would warn if I wanted to increase volume then let me do it. Now it is impossible to go over half volume if something plugged in.

Ideas?
[BlackBerry Priv] ToniCipriani:
Download BlackBerry Virtual Expert, and run the camera test in it. Also try doing a hold power down 32 second reset?
[Greenify] DarsVaeda:
Hi,

when using aggressive doze on a rooted Nexus 4 with Android 6.0.1 in my GPS tracking app (I tried several), even though whitelisted, the tracking stops after a few minutes.

The apps still show as tracking thus I suspect the GPS itself gets killed and provides no signal/values anymore.

Is it a bug or a feature?

Thanks for the great work :)
[Greenify] TNSMANI:
Uninstall Greenify and check.
[Greenify] DarsVaeda:
If I disable aggressive doze it works.

If I uninstall the app too of course.
[Greenify] oasisfeng:
This is a limitation of the doze mode itself enforced by Android. I'm afraid there's no way to workaround that.

A new Tasker plug-in is added in 2.9.5 beta 1 to toggle Aggressive Doze. Hope this could do some help here.
[Greenify] DarsVaeda:
Ah no problem, I thought it might be something like this. I'll just disable aggressive doze while using the app.

The tasker plugin would do this automatically for me, did I get this right?
[Greenify] daniel.mota:
Shouldn't it be enough to disable "Doze on the go" to maintain the gps sensor on?

I have this same problem, and the only way to allow a foreground sports tracking app to access the gps data is to disable both "Agressive doze" and "Doze on the go"...
[Greenify] oasisfeng:
No. As someone tested before, the stock Doze also disables GPS.
[Greenify] madxxcow:
Hello,

I had the same behaviour. I tested something this morning : added to whitelist my navigation app + LocationServices + FusedLocation.

And while I was on the road, the gps worked till I arrived. In the agressive doze log I see that the device did'nt went in Doze during that time.

Don't know if this is directly related, I'll give it another try tonight.
[Greenify] madxxcow:
Didn't work tonight, lost gps signal. Something else prevented doze this morning.

Will give a try to the beta and the toggle.
[Greenify] RFrancis:
Any news on the subject? I get GPS signal lost while using maps...
[Greenify] madxxcow:
I'm now using the beta + Tasker to prevent doze when my navigation apps are on. Works great.
[Greenify] RFrancis:
Could you export the profile
[Greenify] madxxcow:
Here is an example for Google Maps.
[Greenify] GroovyGeek:
You should probably re-enable aggressive doze with an exit task. This does not seem to be one of those system settings that will auto restore when the task terminates. Also note that this profile will not trigger if Maps or your GPS app is in the background. I am debating whether aggressive doze is worth the hassle.
[Greenify] eng3:
I've been having the same issue for a while. I use Locus Maps to record tracks on airplanes (so it may run for 12hrs) and it turns off GPS. Sometimes its hard to tell if its lost because of Doze or I simply lost the signal.

Also, it is plugged into a power source (charging) so I believe Doze should be disabled while charging.

I see above mention of "Tasker". What is this?
[Greenify] DB126:
The simple solution is to avoid aggressive doze which is tagged 'experimental' and is known to cause some odd device/radio/app behaviors.
[Greenify] eng3:
I'm sorry, I should have clarified. I was broadening to Doze itself as I thought I read that it will also disable GPS (but not as fast or "aggressively").

My behavior has been a little different. I notice that if I run maps navigation at the same time as recording my track, there is no issue. but if I just record my track, then it not be able to prevent GPS from stopping.

Perhaps this should go in another forum, I'm just not sure which
[Greenify] DB126:
Try running a GPS Status app (example) concurrent with your tracking app. Aside from helping to keep the GPS 'awake' most have a variety of useful features and functionality.
[Greenify] eng3:
I have tried that but it does not seem to work. I'll have to check the GPS status options to see if there's something for keeping it awake.

I have noticed that if I run Navigation (not just Maps) in parallel, then the GPS will stay awake.
[Greenify] DB126:
- as previously noted make sure Aggressive Doze is disabled as it can break cross-app/component communications

- also add you tracker app to 'white list' of you haven't done so already

- good chance Google Maps (any navigation app) is using wakelocks to keep GPS active

- assume all is well when you disable Greenify

- if true you many need to step away from Greenify or consider another app with similar functionality like Force Doze
[Greenify] eng3:
Yes, I've tried disable aggressive doze (and greenify all together).

It is whitelisted

The issues still occurs when I disable Greenify
[Greenify] DB126:
Obvious not a Greenify issue. Need to address issue with stock doze; Greenify can't help keep an app awake.
[Greenify] tricke:
I'd like to add to this with some tests I've done. I use an app called Mytrails for GPS tracking.

With aggressive doze and doze on the go and the app not whitelisted, the app won't track at all with the screen off. If you turn off doze on the go, it tracks intermittently, with gaps between wake points. If you whitelist and have aggressive doze and doze on the go, the app tracks all the time, but fails to receive GPS data while the screen is off resulting in straight lines between wake points (ie it has no position data when asleep). If you turn off doze on the go, all tracking functions work.

I'd prefer to leave doze on the go on since the battery saving is considerably better. It seems that if the GPS services could be whitelisted, it might work. Anyone know if this can be done?
[Greenify] DB126:
Not with the current capabilities of Greenify. Nor do I think the situation will change going forward, at least on Android 6.x based ROMs. Doze on the go impacts the significant motion sensor whose output is shared by all apps. I don't believe apps utilizing GPS services could be effectively parsed.
[Greenify] tricke:
Thanks. It would be best if the GPS service could be whitelisted, but if that's not possible, it would be great if somehow Doze on the go could be automatically turned off when MyTrails (or any gps tracker) starts and automatically turn it back on when the app exits
[Greenify] DB126:
You can do that with Tasker or another automation app that interfaces with Greenify.
[Greenify] rooman62:
I'm new to Tasker but I would like to use it to prevent the system killing satellite tracking during my jogging. Can you give me a hint on how please?

Android 7, Samsung xcover 4
[Greenify] guptapunjabi:
You should consider using Tomtom, if you have storage space to spare on your device. Freemium version 1.17.1. With it, you download the maps on your phone. I use Google Maps to check traffic, then Tomtom for routing. You can download maps of pretty much any useful country.

Easier on your battery, too.

I added Tomtom to the whitelist, and have never had issues. I have Aggressive Doze and Doze on the Go enabled. Used it in NA, Europe, and Africa.
[Greenify] guptapunjabi:
What Superuser app are you using? This may be the problem. I have found that when my apps become buggy, laggy, weird, and my phone starts to overheat, it's due to a bad SuperSU install or version. I usually find this out after spending weeks trying to troubleshoot one or two apps that just seem to be unable to do their job properly.

If you're using SuperSU, install SuperSU 2.82SR5.It fixes all battery leaks and bugs. Link is below.

http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
[General Questions and Answers] Rahil0597:
So, here's the story. I have Nexus 6P and Moto X Play. On both phones, earlier I was using Resurrection and Cyanogen Rom. But due to launch of Reliance jio (Since in India Reliance Jio is giving unlimited calls, message, and even Unlimited 4G data), I have to come on Stock versions. Because, to run Reliance Jio sim, VoLTE patch is necessary. Stock rom giving me VoLTE patch, and I am able to use Calls and data features, but on Custom Roms, only data is working at limited speed. And last 3 months, cyanogen didn't integrated VoLTE support. So, is there any way to patch the VoLTE patch to Moto x Play custom rom?????? See, only in 20days, I used 150+gb data... Please, VoLTE patch.....
[T-Mobile Note 7  Questions & Answers] unholydoragon:
Hi,

Was wondering what people think of the recall. Seems like if they do do a recall, we would have to ship the phone in for a week at least. This would be very inconvenient and I'd rather just return the phone now before 14 day t mobile policy.

Any thoughts on if Samsung would give a freebie or maybe just give a new phone somehow? Otherwise, returning the phone seems to be the best idea and buying it again after the issue is "fixed"

Any idea if t mobile will make us pay 50 dollar restocking fee on this?
[T-Mobile Note 7  Questions & Answers] SlakWReX:
I would say if you're not havingany issues there is no need to return unless you're worried of future issues. I won't be returning because I have no issues and my phone was manufactured 2 weeks ago. Also tmobile will not charge rsf
[T-Mobile Note 7  Questions & Answers] borijess:
You think we will have the option to change color of phone in recall?
[T-Mobile Note 7  Questions & Answers] bkeaver:
Im going to go out on a limb and say no but I could be wrong...
[T-Mobile Note 7  Questions & Answers] MacTheRipperr:
I really don't want to return my device because there is no problems with it like everyone else is having. But I'm going to give T-Mobile a call and see what my options are.
[T-Mobile Note 7  Questions & Answers] Ducter:
I didn't grab the 7, decided to wait for whatever the Nexus will be because really, tho the note series has always been pretty good locked up and knox not being able to be reset later for full functionality has finally turned me off, with that said tho, if you have a note 7 by all means exchange it. It's in no way worth a gamble, whose to say what could happen if it caught fire, exploded or whatever. Your safety or your families is nothing to take a risk with and saying it has been fine so far is just plain stupid. Everything and everyone will always say it was just fine until it's not. If something was to happen and someone hurt and you knew about the issue yet ignored it you are pretty much a piece of *$@# in my opinion. Samsung would not issue a recall and face the negative press unless it was something they truly deemed necessary.