yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
Twrp doesnt back up userdata, because it writes the backup to /userdata. Once you copy all your files to your PC, verify that they actually copied. I usually just pick and choose a few random files and open them on the PC just to make sure they are good copies.

After that, I would factory reset my phone by flashing the factory images. Just don't use the line fastboot flash userdata, bc this will cause you to only have 32gb of internal storage available if my memory serves correctly. If you only have a 32gb phone, it won't hurt anything, but simply running the previous command of fastboot erase userdata should be sufficient.

I'm off work today, so I'll try and keep checking back in case you have any other questions or need anything else.

---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------

Here is a link to Heisenberg's thread, if you scroll down to step 9, it should be the info you need to return to stock. There's lots of good info through his posts though.

http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page469
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Of course, yeah, that makes sense, I didn't think of that. I just don't know enough about the recovery process, but this is a good learning experience, if an unfortunate one.

I'm at work and in the process of copying everything now, so I'll do that first, then try to get it back up and running. I just verified that some of the files I've copied are fine, so that's great. I already tried flashing the stock factory images and it didn't resolve the booting issue. I remember reading the line from Heisenberg's guide about running fastboot flash userdata and the problems it causes on 64GB devices, which mine is, so I won't be running that anyway, but I'll follow the instructions from step 9 to update to the latest 6.0.1 build and see how it goes.

That would be great, thanks, I really appreciate your help. It might take me a few hours to copy everything (if I can even get it done while at work, might be something to finish at home), but I'll update with progress.
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
Restoring to factory *should* fix the issue. If you flash the latest factory marshmallow image and still have an issue, I would lean towards it being a hardware issue. I've seen where a few 5x's are suffering from a hardware issue after taking the 7.0 OTA, but I don't think it extends to our device.

Just quote me or pm me if you run into any issues. Help is what XDA is all about.
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Yep, that's what I thought when I tried it last time. Sadly, no dice. Got everything backed up, followed the steps in step 9 to flash the Marshmallow factory image and it's still the same - shows the "Your device software cannot be checked for corruption" screen, then the Google logo, then reboots and does that repeatedly, never getting to the loading animation.

At this stage, is there any point in wiping userdata (not by running fastboot flash userdata, I know) just in case there's something weird on that partition causing the issue? It's the only constant I can think of, barring a hardware issue, which is obviously out of my control.

I'm stuck at work and can't go home due to a storm, so I'll be here for a while yet. Might as well do some troubleshooting. :)
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
If you haven't formatted it, yeah, it may help by wiping it. Have you at any point used twrp at any point recently to backup/restore your efs partition.

If you got everything backup up, I'd reset the whole phone back to factory, incl user data.
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
No problem, will do. What's the best command to wipe it? Yep, I took a backup of the EFS partition before rooting the phone, as per Heisenberg's guide. It was on MHC19Q then, though, not sure if that makes a difference.

Edit: Sure, I'd be happy to do a full reset, just not sure how. I know there's a Factory option in the bootloader, but I think I remember reading somewhere on xda not to use it, can't remember why. I'll look for the post.
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
Do you have twrp still? There's an option in there when, you select wipe, then advanced wipe, and the select userdata and swipe.

If not, I believe the command to do it via fastboot is:

Fastboot format userdata

Let me double check that real quick, but using the format command is safe, it's fastboot flash that can be problematic.

* Edited the command.

---------- Post added at 11:58 PM ---------- Previous post was at 11:50 PM ----------

Alternatively, your bootloader is unlocked and you would rather just reflash twrp(if you're back on stock recovery) to wipe the userdata partition, that should work to. Just use the wipe menu like I described in my other post to wipe it w twrp.
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Nope, TWRP was wiped when flashing the factory images. I ran fastboot format userdata and something has changed, but the main issue remains. It now gets to the loading animation relatively consistently, but freezes after about 3 seconds, then reboots, and continues in the same loop. For testing, I reflashed the 3.0.2.0. TWRP and now, in Advanced Wipe, there's no userdata option, just Davlik/ART Cache, System, Data, Internal Storage and Cache. Kind of makes sense, though, as it's already been formatted by fastboot format userdata, but not sure if it should still appear as an option or not.
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
My fault, internal storage is what twrp calls userdata. If you have the time, try reflashing the system files w fastboot. And in the same session as flashing (prior to reboot) run the format userdata command, then reboot. Just as a precaution, since if you have something in there that was corrupting system. If you attempted to boot w the issue still on the storage, it could have recorrupted it.

I would try and format all but system in twrp before reflashing,
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Ah, OK, no problem, thanks for clarifying. Yep, I have time - this storm doesn't look like it's ending any time soon. So just to make sure I know what I'm doing, I'll wipe all the partitions from TWRP-Wipe-Advanced Wipe first, then run the following commands to re-flash MTC20L;

fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot format userdata
fastboot reboot

Does that sound about right?
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
You can probably start at the "flash boot" line, if you've already tried this before. None of the wipes will touch radio or bootloader.

If you haven't already flashed those, then yes, that sounds correct to me.
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
OK, all done, and, alas, still the same. Freezes on loading animation, then reboots. Repeat ad infinitum. I can post the log of commands and output if that would help, but I'm sue it's nothing you haven't seen a thousand times.

Starting to look like a hardware issue? Does TWRP have any utilities to fix file system errors, like chkdsk does for Windows? I noticed a few "Repair file system" options, but haven't run them yet because I don't know what they do.

Thanks again.

Edit: Should mention, I did start at flash boot.
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
There are those options, but unless something crazy has happened, you shouldn't need to use them. The other thing that it could be, if you restored the efs partition w twrp, that can create an issue. There's a command to erase it and let the system rebuild it. Gimme a few and I'll see if I can track down the exact command. These phones seem to be really picky about partitions, more so than previous phones I've owned (nexus 4, 5, 6 and 7(2013)) with vendor files and such.

---------- Post added at 01:37 AM ---------- Previous post was at 01:30 AM ----------

You should be able to run that using twrp, then mount adb mode (or some button similar to that)
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Nope, I haven't tried to restore the EFS partition, only took the backup as...well, a backup, and I've always used TWRP 3.0.2.0., never any of the later builds, so it shouldn't be that either.

Is it worth trying any of the file system utilities, or should I just give up and contact Huawei? Something seems to have gone rather seriously wrong.
[Nexus 6P Q&A, Help & Troubleshooting] Nemosfate:
from what ive seen and what i am currently dealing with on my 6p it seems there are some hardware issues. never had an issue i couldnt fix in fastboot or adb till now. literally tried everything i know and suggestions from here and other dev friends with no luck.

reading about yours Mark it seems to me personally it may be hardware.
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
Hmm, I'm kinda out of ideas. Link me the logcats and I'll see if I can find anything out of the ordinary.

I'm a bit in agreement, though. If flashing factory doesn't fix it, and it didn't involve installing anything new or experimental, it's probably going to be a hardware fault.
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Yep, that's what I'm thinking too.

Interestingly, I just picked it up reboot it so that I could export the logcat and saw the "Encryption unsuccessful" message on the screen. Tapped "Reset phone" and it restarted and started doing the same thing again. Maybe it finally got past the loading animation to encryption, then failed. I'm exporting the logcats now, but it's pretty slow, file size is increasing 1KB at a time every few seconds, it's been running for 20 minutes and is only 1.6MB. I'll upload as soon as I have it. Just waiting to leave the office once this has finished. If it's not done in 10 minutes, I'll abort it and run it at home, then link it once it's done.
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
OK, I finally realised that logcat is doing a continuous log rather than just reading and writing the existing log info, so I selected Reboot Bootloader from the bootloader, the phone restarted, then froze at the animation again, then restarted, showed the "Erasing..." message, restarted, and is now stuck at showing the loading animation, which has currently been up for about 10 minutes.

On the positive side, it's not freezing; on the negative, I have no idea WTF it's doing or what it erased. But I have nothing on it to lose anyway, so who cares.

Logcat is back to 1KB per 2 second logs again, so I presume it's not actually doing anything at this stage and is just looping the animation, so I've quit logcat and attached the 2.7MB output.

Not quite sure where to go from here now, I don't even know if this is real progress or just a different symptom of the same problem.

Just heading home, but I'll be online for quite a while yet. Thanks to all again for your help.
[Nexus 6P Q&A, Help & Troubleshooting] Nemosfate:
in my boot looping situation, i tried literally everything that has been mentioned on top of what i knew to try on my own. After fastboot every command as in flashing a factory image with a clean slate even clearing and formating userdata, i could on rarely get recovery to boot and stay up before bootlooping. so i tried Wugs toolkit for the simple fact of i cant type as fast as the kit can push commands. didnt work until i left the phone to kill the battery itself the night before last. yesterday when i got my 6p and plugged it in, letting it charge for awhile, i was able to flash Benzo rom and gapps. hopes up , booted normally, looped after 5 minutes. but came back up and ran like it should for a couple hours. powered down, plugged it in to charge overnight. wake up this morning to boot loops. not a damn thing of this makes sense, with mine nor a few of the other 6ps looping on here. before anyone asks i was running twrp 3.0.2-2 so i dont think that was an issue and ive since updated to 3.0.2-3. waiting on google to email me back to see if the "specialist" have any different option to try to flash it back to life and stay correct. if so ill post here
[Nexus 6P Q&A, Help & Troubleshooting] MarkB16:
Just out of curiosity, what caused your original problem? Do you know?

I was way too tired on Friday morning and actually left my phone connected to my office PC and was halfway home before I realised. When I left, it was just looping the loading animation. I came in today and tested it, and it's no further forward - has the same issue as previously. Start up, "Your device software can't be checked for corruption", Google logo, reboot. Does the same no matter what I try, and rebooting to the bootloader doesn't cause the "Erasing..." message again - I have no idea what caused that in the first place.

helioXverse, or anyone else, any final ideas that I can try before contacting Huawei? Was the logcat of any use?
[Nexus 6P Q&A, Help & Troubleshooting] Nemosfate:
I honestly have no idea what cause my loops. I was browsing craigslist and just randomly started looping. Same way you said yours is with the software can't be checked screen and the white Google logo. Google has emailed me but they have only said to try the same Fastboot commands we all know how to do. So far at least.
[Nexus 6P Q&A, Help & Troubleshooting] D-m-x:
I've had the same happening to my 6P 2 Weeks ago. I plugged it in to charge it in the other Room while watching TV. Later i found it looping, I've tried everything, from Factory Images to EFS, different Android Versions, different TWRP, Stock Recovery etc.

Eventually i gave up and called the Play Store and ordererd a Exchange.

What actually got my attention was the fact that the Phone hung up during the Decryption Process of the Internal Storage since my Phone was encrypted prior to the defect. I tried it with the Encryption removed, i could flash things and so on, but not actually get past the Google Logo.

At first i thought it was a stuck Power Button but now my assumption is faulty Internal Storage.

Last few Weeks/Days I've seen quite a few Topics of exactly that phenomenon, over at Reddit also. Otherwise i have no Idea what this is, since my Phone wasn't even in use when it died.
[Nexus 6P Q&A, Help & Troubleshooting] Mauijpm:
Last week I installed allo and upon phone number verification my phone went into bootloop. After it looped a couple times, it started back up into the os (The most recent version of N - all received over OTA). I thought Allo just caused the problem so I uninstalled it. Every now and then afterwards it would just reboot, like taking a screenshot or doing something like checking an email. Every time after though, it would boot into the OS. On Sunday, after I got off a phone call, it rebooted and got stuck in a bootloop. I could never recover it. I could only get back into Fastboot / Bootloader. I tried reflashing stock. I tried going back to M. Nothing worked. I contacted Google Fi (that's who I bought it through). They tried to get me into recovery. Once they saw that I couldn't do that, they shipped out a replacement phone. They didn't even ask anything beyond getting me to recovery. I think this is a a fairly widespread problem and the only fix seems to be phone replacement.
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
Sorry. I've been really busy with work and my toddler. I'm a bit perplexed, I honestly don't know what could cause these issues aside from a hardware fault. This has been the first nexus phone that I've seen multiple people have issues not able to be corrected by flashing factory images.
[Nexus 6P Q&A, Help & Troubleshooting] D-m-x:
Yeah, my guess also. At first or seemed like a Soft Brick but like I said in my earlier post I guess the Internal memory is somehow faulty.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] Nemosfate:
thats been my thought, faulty internal storage or something getting extremely corrupted with N. i see nothing else that could cause it as i mean the phone has been working flawlessly up until this. i had to RMA mine, now half scared to try anything haha, though i will :D:D:D:D
[Nexus 6P Q&A, Help & Troubleshooting] helioXverse:
I don't think rooting/flashing has anything to do with the issues. There were several people w stock, locked bootloader phones that had issues after the N OTA. It will probably come down to being a bad batch of emmc chips or something like that, though I have a feeling we will never truly know the reason.
[G3 Q&A, Help & Troubleshooting] xRageMachine:
Hello,

first of all, thanks for taking your time to read this.

>> Ill start by explaining my problem and list my diag. method.

So my problem is that my LG G3, that i bought used about 2 weeks ago, its an European Version (D855) and i am SURE that my ISP supports the bands that my phone does (800Mhz/1800Mhz, so band 3 and 20). THe problem is that whenever i have 3/4G selected, not 2G, the phone has contant restarts. The restarts happen on any AOSP based ROM (the only ones ive tried using), examples are CM13, CM12.1, LiquidSmooth, etc... On the default LG D855 ROM (installed with the LG PC suite) it simplly looses connection any time i use 3/4G, it does not restart but it does not have a stable connection. In the case of the custom ROMs the restarts happen anywhere between a second after boot or 5-10 minutes. Ive tried reinstalling CM multiple times, and have also tried reinstalling the european official ROMs, both 5.0 and 6.0. I DO have the correct APNs set. I have tried setting it to LTE only in the secret menu, did not change the resaults.

What do you think can be the problem, is this a HW problem or possibly a firmware, IMEI problem?

Thanks

//Sorry for my horrible english :p
[Galaxy E5, E7 Q&A, Help & Troubleshooting] rakshushetty:
Guys i am not able to find any ROM to my device. Please suggest me some good ROMs. Thank you.!!
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Nadeem1122:
http://xdaforums.com/galaxy-e-series/orig-development/rom-cyanogenmod-13-galaxy-e5-e500h-t3290755

u can install it...
[Galaxy E5, E7 Q&A, Help & Troubleshooting] ovi.dire:
The link you provided mentioned a ROM for SM-E500H. Does it also work for SM-E500F??
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Nadeem1122:
yes
[Galaxy E5, E7 Q&A, Help & Troubleshooting] rakshushetty:
Yes i think. But for me i stuck in boot loops so i reinstalled stock ROM
[Galaxy E5, E7 Q&A, Help & Troubleshooting] ovi.dire:
I tried to install "CM 12.1 & gApps" downloaded from link found in youtube. But there was "error msg" at the time of installing "gApps". However, I am trying again with the link provided here. Will give feed back soon.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] rakshushetty:
I stuck in boot loop
[Galaxy E5, E7 Q&A, Help & Troubleshooting] ovi.dire:
I tried in my SM-E500F. But error is shown when wiping existing OS data using TWRP recovery. "cm-12.1-20151124-UNOFFICIAL-e53g" file is installed successfully. But error is also shown when installing "gAAP.zip". So overall result is "NOTHING"...

:(
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Angga Rizky:
This is for E500H variant bro, u cant install it on E500F
[Galaxy E5, E7 Q&A, Help & Troubleshooting] rakshushetty:
But some tried for E500F , it worked. For me stuck in boot loop.
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Angga Rizky:
What country u have?

---------- Post added at 04:55 PM ---------- Previous post was at 04:52 PM ----------

Nope, you can't install it bcz E500F have 4g but E500H not. So there is different kernel and firmware on that package. Expect u can edit it
[Galaxy E5, E7 Q&A, Help & Troubleshooting] rakshushetty:
I think there is no CM released for E500F. When they may release?
[Galaxy E5, E7 Q&A, Help & Troubleshooting] Angga Rizky:
Just wait till samsung give marhsmallow to E5 haha. I want make cm13 for e500f. Just put replace kernel and firmware e500f to cm13 for e500h. But i dont know how to repack or unpack boot.img and etc
[Galaxy S 4 Mini Android Development] obaidmuneir:
crDroid Custom Features:

* Volume panel timeout

* Clear recents location

* Lock app on recents panel

* SlimRoms custom lockscreen shortcuts

* SlimDim

* Navbar on/off

* Hardare keys on/off (in devices supported)

* Sound panel option om power menu

* Superuser indicator (Notification, Statusbar icon or no indicator)

* Force expanded notifications on expanded statusbar

* Power menu and notifications tiles

* Four tiles per row

* Vibrate on tiles touch

* Disable quick settings on secure lockscreen

* Ambient display with a bunch of options

* ADBlocker

* System apps remover

* IME advanced settings

* Network traffic meter

* RAM bar in recents panel

* Battery saver enhancements

* Non intrusive incoming call

* Option to disable battery saver orange bars

* Swipe behavior

* Touch outside behavior

PS: All CyanogenMod features also inside

Always Have a full functional Backup. Just in case!

DOWNLOAD

serranoltexx

serrano3gxx

gapps

First time installing crDroid to your S4 Mini, or coming from another ROM:

- Make sure you're running a proper working Recovery (CWM or TWRP)

- Copy GApps and crDroid zip to your internal SDCard

- Boot into Recovery

- Wipe system,data and cache

- Flash crDroid zip

- Flash GApps zip

- DO A DATA WIPE / FACTORY RESET

- Reboot

Upgrading from earlier version of crDroid:

- Copy crDroid ZIP to your internal SDCard

- Boot into Recovery

- Wipe system and cache

- Flash crDroid zip

- Flash Gapps

- Reboot

Don't expect any support if you:

- are not running stock crDroid-kernel

- have installed any mods such as Xposed!

- have modified system files

Video Review by [MENTION=242801]amd[/MENTION] - Click Here

Thanks to:

- Google

- CyanogenMod

- [MENTION=5161352]JustArchi[/MENTION]

- SlimRoms

- [MENTION=4790322]kufikugel[/MENTION]

- AOSPA (Paranoid Android)

- OmniRom

- NamelessROM

- [MENTION=1552717]0xD34D[/MENTION]

- [MENTION=2332422]temasek[/MENTION]

- [MENTION=3332811]faux123[/MENTION]

- [MENTION=4195844]show-p1984[/MENTION]

- [MENTION=3795148]neobuddy89[/MENTION]

- [MENTION=4684315]flar2[/MENTION]

- [MENTION=3418703]Tasssadar[/MENTION]

- [MENTION=1289361]Mazda[/MENTION]

- [MENTION=4478519]Cristiano Matos[/MENTION]

- [MENTION=4764217]davidteri91[/MENTION]

- [MENTION=4258086]firebird11[/MENTION]

- [MENTION=4080951]Benowit[/MENTION]

- [MENTION=4933230]jejecule[/MENTION]

- Many others... (if you're feeling upset being out of the thanks list just send a PM )

And Many More...

Our Team:

Fathurrehman Ara

Beb Zainul Abidin

Mas Koe

Mas Paresto Adi

Aditya Kumar

Nana iyke

Hameed Musaraf

[MENTION=7512364]anutalores[/MENTION]

[MENTION=5906864]obaidmuneir[/MENTION]

Maximium Team

Android Matrix Development

crDroid G+ community

AMD G+ community

https://github.com/crdroidandroid​
[Galaxy S 4 Mini Android Development] obaidmuneir:
Screenhots
[Galaxy S 4 Mini Android Development] glkanth77:
Bro can u make a build for 9191(duos)
[Galaxy S 4 Mini Android Development] obaidmuneir:
am so sorry but i dont have this device
[Galaxy S 4 Mini Android Development] glkanth77:
But I can test it if u make a build
[Galaxy S 4 Mini Android Development] obaidmuneir:
testing doesnt matter ,i have tested but signal not coming up , for this i need to own this device or need very patience user
[Galaxy S 4 Mini Android Development] csendre:
You need to run the ril patch in k2wl's serranodsdd repo before starting the build and it will work. I made a test build of crDroid for the duos a while back and worked with no issues
[Galaxy S 4 Mini Android Development] obaidmuneir:
wow i never see i will try

Thanks before :)
[Galaxy S 4 Mini Android Development] pickandrew:
Hello, this ROM is stable or in beta version? Bugs? Thank you!
[Galaxy S 4 Mini Android Development] obaidmuneir:
Currently there is no bug if you found any report here

Thanks