yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] archz2:
My phone is rooted. I am using Lenovo A7000 phone with AOSP 6.0 by Risma Ermaya.

I have formatted my SD card as internal storage using the default feature of marshmallow.

Few months back, I started facing the issue of Facebook and Messenger updates. Whenever I used to update my facebook or messenger from the playstore, these apps stopped opening and used to crash. But after I used to restart my phone, these applications ran fine. A week ago, I installed instgram for the first time in this phone. Similar thing happened with it too. After installation from Google Play store, it did not open. However, after restarting the phone, everything went well.*

Yesterday, I was updating facebook, I got the error 403. I cleared up data of my playstore app after forced stopping it, removed all my google accounts from the phone, and rebooted the device. After rebooting, the error was still showing up in the playstore. Feeling frustrated, I forced stopped Google Play services framework application, cleared it data and rebooted my phone. But, the problem was still there.

I have got into deeper trouble now. My microSD card has become write protected. I did not remove my SD card at all since months. It is of sandisk brand and has class 10.*

I cannot take screenshots. I cannot download any file from chrome browser. I cannot download images sent to me by my friends through whatsapp.*

I cannot even copy one file in its folder to another folder in the memory card. I have tried using the default file explorer and Solid Explorer application. I have just 587 MB remaining in my phone. However, I can access any file I want to. My videos and music are playing just fine.*

I am also able to delete any files within the file explorer, so that I can make a nandroid backup of my files in TWRP. Even TWRP does not allow me to delete my music and videos within the SD card. What should I do to fix this trouble? I do not want to format my SD card as it has lot of important data. Even if I connect my phone to my PC and try to copy the files, the process hangs after few seconds and Windows explorer hangs which is displaying the content in my SD card. I am running windows 8.1.

I have also tried unmounting and remounting my sd card using the in built feature of Marshmallow, but this trick still doesn't solve my trouble.*

I have also tried clearing cache and dalvic from TWRP but still no progress. I feel that facebook is the culprit because while clearing cache in TWRP, it gives the error that it could not clear cache from com.facebook.katana folder.
[Tilt, TyTN II, MDA Vario III General] Yannn:
Hi ... i'have just baught a htc kaiser "orange" (better price !)

before i've a htc P3600 ... they are so diffrent !!!

i've seen that a new version of google navigator is free to download : 2.5

Is anyone have test it on the kaiser ?
[Tilt, TyTN II, MDA Vario III General] tokomoto:
I have and it froze and never worked for me..it's ashame, it look so nice!
[Tilt, TyTN II, MDA Vario III General] AllTheWay:
Did you download NETCF 2.0

It is required to be installed for Google Navigator to work.
[Tilt, TyTN II, MDA Vario III General] mmone3:
The last time I used google navigator it used direct3d and if it still does its going to run really slow because there is no hardware support on the kaiser yet.
[Tilt, TyTN II, MDA Vario III General] AllTheWay:
Yes I tried it and it ran really really slow...not very responsive.
[AT&T Note 7  Questions & Answers] chrispyutec:
Does anyone know how to move pictures from 1 album to another?

Example: I take a pic of my truck and then that pic automatically goes to the album named camera, now I want to move that pic from "Camera" to my album named "My Truck"

The other Note series I could just hold the pic down and then move it or I could select the pic and click menu and select which album I want to move it to.

I appreciate any help I could get.
[AT&T Note 7  Questions & Answers] JMat76:
If you select the pics you want to move and then hit the 3 dot menu it gives you the option to copy or move to another album.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.

Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.

FORM:This info is found in the bootloader

Bootloader -

Baseband -

Variant -

CPU -

EMMC -

DRAM -

Console -

Qfuse status -

Download Mode -

This is found in bootloader - barcodes

Manufacture date -

Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"

I was able to fix the bootloop with these EXACT steps - OR*

*I have not been able to fix my device*

I have tried methods - *METHODS WILL BE IN POST #2*

My device is

Bootloader - 3.58

Baseband - 3.72

Variant - VN2

CPU - 0x20001

eMMC: 32GB Samsung

DRAM: 3072 HYNIX LPDDR4

Console - NULL

Qfuse status - Enabled

Download Mode - Disabled

Manufacture data - 11-13-2015

Methods tried - 1-21
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
reserve 2
[Nexus 6P Q&A, Help & Troubleshooting] sixgunmojo:
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.

I would also like to see this issue resolved just for my own personal satisfaction. Good luck.

Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Thanks, that would be useful. I'm thinking of how to incorporate that in a simple enough way that people don't accidentally provide incorrect information.
[Nexus 6P Q&A, Help & Troubleshooting] busbeepbeep:
FORM:This info is found in the bootloader

Bootloader - angler-03.54

Baseband - angler-03.61

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 64GB Samsung

DRAM - 3072MB HYNIX LPDDR4

Console - NULL

Device : Locked

Qfuse status - Enabled

Download Mode - Disabled

Manufacture date - 10/20/2015

Brief description of where the bootlooping started -

Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.

On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.

I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.

Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.

I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Your device isn't recognized by adb/fastboot?
[Nexus 6P Q&A, Help & Troubleshooting] busbeepbeep:
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.

This is what I get:

adb devices: reports blank

fastboot devices: report serial #

adb reboot bootloader: reboots bootloader

adb reboot recovery: error: no devices/emulators found

fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s

fastboot reboot: reboots and goes into white logo loop
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Try this tool to make things a little easier, and more automated for now. Wugs
[Nexus 6P Q&A, Help & Troubleshooting] busbeepbeep:
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Boot into bootloader manually then try to run something
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.

So now I'm wondering if the issue may lie in the efs partition.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
What eMMC is your device using, if you don't mind?
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
64GB Toshiba
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Just to clarify, you were able to get your device to boot?
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Originally i had no issues I flashed factory images from Pure Nexus June build Via Fastboot. Rebooted the phone and took the OTA through the phone and then flashed TWRP 3.0.2-1 (the Newest one) and through TWRP flashed SuperSU 2.76 then FDR the phone before setting it up. All was fine and perfect. I made a backup and then factory data reset my phone Saturday and then restrored the backup. No go, Bootloop city. Got home did most of what was mentioned and nothing happened. Flashed PN through TWRP 3.0.2-1 and flashed my stock rom that came with the phone in Feb (29Q) and restored my EFS (I backup my EFS after any Android version change). The phone booted perfectly. no issues since. Took me about 2 hours total once i got home and was able to start using ADB and Fastboot commands.

---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------

Also i forgot to add my info....

BL: 03.58

Baseband: 3.72

Varient: Angler-VN2

CPU: 0x20001

eMMC: 64GB Toshiba

DRAM: 3072MB Samsung LDDR4

UNLOCKED

Qfuse status: ENABLED

Off-mode-charge: Enabled

Download Mode: DISABLED

I also forgot, I was enrolled in the beta program obviously since i took the OTA through the phone.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Alright, thanks for clarifying. Didn't want to accidentally add something to the second post haha.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Sigh.... Well if they send mine back unfixed I'll give that a whirl.

---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------

I knew it was twrp
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Don't fret! You'll get it going, if they don't. You have a huge team on your side, bud.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Yes I have
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Please try the DD commands in post 2
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
I was able to run DP5 but had no data or dim card being detected at first, then i restored my efs partition and it started working fully. I was at work when i posted that long post.

I just saw that note there's a fix, thank goodness. Kudos to everyone that thought TWRP was the culprit! I wonder if it also corrupted the vendor too because in a few tests we did, vendor was bad.

---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------

I don't need to, my device is back in N running fine. I have a MM backup I made with 3.0.2-0. I am able to restore my efs partition from that as long as it is with 3.0.2-0.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Actually if Huawei sends it back to me unfixed I'm screwed as I flashed stock and locked it before I sent it back...
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
I relocked mine accidently at one point, I was able to flash an unlocked boot.img and get it going. Hopefully you'll share my luck.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Link to that? Lol

And how did you flash that locked?
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
I used Wug's toolkit for most stuff. Just use the advanced tab. It's more like doing things manually. But, with buttons instead of lines of code lolol.

Select that your device is bootlooped on the right hand side of the program, and go from there.
[Nexus 6P Q&A, Help & Troubleshooting] Andromjb:
Confirmed working. :good:
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Right but that just flashed a stock image....or do I check off no force encrypt... But then what?
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Glad that it's working.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Check no force encrypt. Run through the automated fix, or do each partition manually, then try to do the dd lines.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
ok i'm missing the part that checks off allow oem unlocking AFTER you boot into the os....

cause if its locked fastboot wont flash anything... only option is to sideload. What am i missing here.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Yea, did you ever boot into a working phone after you locked the bl? I didn't so I was able to unlock again with the GUI step.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
so fastboot oem unlock command worked? even though you locked it and didn't boot into the os?
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Yea, I might have just gotten lucky, but I was able unlock after locking. I was desperate and thought locking might help for whatever reason xD
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
I might be able to fastboot boot twrp image and run the dd commands also.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
We'll figure something out!
[Nexus 6P Q&A, Help & Troubleshooting] netwokz:
This worked for me also. No more brick. Thank you oh so much.
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
THANK YOU SOOOO MUCH!

Wasn't having problems with Nougat, never tried it, but did have issues and tried to restore an older 3.0.2-0 backup. THIS WAS THE ONLY THING THAT WORKED! You are amazing! Thank you for the research and keeping up with it!

Now hopefully my call issues that started this whole mess have been resolved. To be continued...
[Nexus 6P Q&A, Help & Troubleshooting] tyea:
Didn't work for me. The first adb shell command seemed to execute something, the second didn't seem to do anything. I didn't get an error, but all the adb commands scrolled down after I copy pasted the second shell command
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
I tried it three ways, sadly don't know which way worked.

I tried it with command prompt, then copy and pasted.

I also tried switching to ADB Shell in command prompt, and manually typed it in.

And lastly, for good measure, I went in to TWRP Advance -> Terminal and typed it in.

Try those just to double check. Also, it appeared the only difference was modemst1 and modemst2. All three times, nothing appeared to happen. They both said something like "no more space". But in the end, after doing those three trys and flashing Dirty Unicorn & associated vendor image, it worked.

Also, I never went to nougat, so MAYBE that had something to do with it, although I think like it's been mentioned, it was a restore issue with 3.0.2-1. Good luck!
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
That means you either copied it wrong, or you were already in shell so the "adb shell" part became redundant.
[Nexus 6P Q&A, Help & Troubleshooting] netwokz:
The second command has a capital "s" in shell. change that to lowercase and it will work fine.

---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------

Looks like 3.0.2-2 is up on their website. https://dl.twrp.me/angler/
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Have you seen a changelog anywhere? The one on that site didn't appear to be updated.
[Nexus 6P Q&A, Help & Troubleshooting] netwokz:
https://twrp.me/devices/huaweinexus6p.html that's the only changelog I have seen. And no it hasn't been updated yet.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Yea, that's all I found too.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Ok, so I take it that the EFS erase method in adb works for those of us in bootloops trying to downgrade Nougat to MM?

So far OP and a couple others mentioned they are in a different situation (not Nougat related) but the adb method fixed it for them. What about the rest?

I'm not at home so eagerly waiting to go back and find out.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Not surprised by this. Correction of my EFS partition fixed my phone instantly. Been saying the u thought the EFS might play a role in all of this. It will be good to have an update TWRP soon.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
The rest of who? Isn't everyone here bootloop in? Or are you meaning everyone who did go to nougat? It should work for everyone.
[Nexus 6P Q&A, Help & Troubleshooting] tyea:
I got both commands to run properly, but I still have the bootloop. What version of TWRP is supposed to be installed, when we run these adb shell commands, or is it just necessary to be able to run adb?
[Nexus 6P Q&A, Help & Troubleshooting] netwokz:
I think it's just so you can use adb. I used 3.0.2-0. what did you do after those commands?
[Nexus 6P Q&A, Help & Troubleshooting] tyea:
I tried three approaches. First time I used twrp to reboot system. Second time I used adb reboot command. Third time I used twrp to format data, rebooted recovery, factory reset with twrp, rebooted to bootloader with twrp, flash-all latest Android MM factory image. I got the bootloop, so I went into stock recovery and factory reset, yet I still have bootloop.
[Nexus 6P Q&A, Help & Troubleshooting] netwokz:
That's weird. after I ran the commands I flashed the latest twrp(3.0.2-2), then booted to recovery. Then wiped everything, including internal storage. Rebooted to recovery. Flashed PureNexus vendor image then PureNexus then the vendor image again. Then rebooted and was good.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Yes I meant those who did go to nougat. So far OP and a few others stated they had bootloops due to a different reason, mainly just TWRP and not because they were trying to downgrade. I'm asking what about those who had bootloops while downgrading from Nougat to MM.

For downgrading Nougat to MM, some narrowed down to TWRP and/or vendor partition error. So for now, those who encountered bootloops due to just TWRP are able to fix the problem. So I'm asking what about the others, if the fix works for them, means I can eliminate the Vendor issue of Nougat.

I'm still a few hours away from home, so I can't try the fix yet. Would be nice to know that the fix is 100% working for people bootlooping from downgrading Nougat.
[Nexus 6P Q&A, Help & Troubleshooting] toadths:
My method to fix was as follows (prior phone state was bootlooping on a factory image of DP5):

1. Follow these instructions http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

Assuming you have adb/fastboot set up start from step 8 and include the command

$ fastboot erase vendor

Then follow the instructions down to the end of step 11 (don't forget to flash your vendor)

2. Open up a command prompt and execute the adb commands specified in previous posts to rewrite EFS

3. Restored factory image previously used one more time for the hell of it using batch file

4. PROFIT?!

I don't think it's necessary to use DP5 guys that's just the one I had handy at the time.

EDIT: derps
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Alright! So the EFS method worked for me as well. Out of bootloop at long last!
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
I posted it works for Nougat bootloops earlier. :P

---------- Post added at 07:32 AM ---------- Previous post was at 07:31 AM ----------

Glad you got it working man.
[Nexus 6P Q&A, Help & Troubleshooting] vacaloca:
For other devices, erasing EFS partition would cause either a zero'd IMEI or non-working/different MAC address BT/WiFi radios. That being said, presumably anyone that had the EFS bootloop issue was because they restored their EFS partition from the non-working TWRP 3.0.2-1, so they should be able to restore the backup back after either downgrading to 3.0.2-0 or upgrading to 3.0.2-2.

I guess my question is, if zero'ing out the EFS to recovering from the bootloops, are any other side effects present before restoring the original EFS? Or maybe this is not a concern because the backup was available and was restored anyway.

Edit: I restored my original EFS backup made with TWRP 3.0.2-0 once more using TWRP 3.0.2-2, and no issues, so seems like the bug indeed has been fixed.
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Please do keep us posted, mine is at Huawei right now.

Thanks!
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
so has anyone on N gone back to MM using either 3.0.2-0 or 3.0.2-2 now via flashing a rom from recovery ?
[Nexus 6P Q&A, Help & Troubleshooting] ajgftw:
I recovered from the brick situation using the instructions in the recent post from twrp featured on XDA.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Got an email from them yesterday saying they had received my phone and as soon as they validate warranty they will commence repairing my phone. They also said the next email will be the tracking number when they said it back. I have not got anything else or a y calls from them.
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
Thanks for the update.

I honestly blame myself for the situation I'm in.

The TWRP devs and XDA community are awesome; it all boiled down to my impatience :p

Instead of waiting 2 days for the fix that was almost guaranteed to come, I panicked and immediately sent it off after only 1 day of troubleshooting.

Lesson learned.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Mine bricked last Friday. I wasn't that impatient I needed a phone lol. I mailed mine out Tuesday
[Nexus 6P Q&A, Help & Troubleshooting] mearjunsha:
Thanks a lot.

:D:D:D

This is just great. Thank you. The nightmare is no more. thanks again.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Why would you even want to risk that? Just flash the factory image of MM and avoid all risk. This is why people got into this mess in the first place with restoring backups and such over N.

"Shortcuts only breaks necks."
[Nexus 6P Q&A, Help & Troubleshooting] jblack41510:
This worked for me. Thanks alot.

When I restored my twrp backup, my pin wouldn't work once my phone booted up.

Went in twrp file manager and deleted the security files.... Phone back to normal now.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
This had nothing to do with restoring over N for me it was the twrp version with the -1 regardless of what you had on your phone.