Related
Hi,
So I unlocked the bootloader on my phone and rooted it successfully (I believe). In the bootloader screen it shows as being unlocked. I am able to use Root Explorer with no problem, as well as Titanium Backup.
I flashed the latest TWRP for this phone (from Original Android Development). It seemed to have flashed fine. The only problem is that I can't really do anything from within recovery. It can't seem to 'see' my internal storage. I don't think mounting it results in anything. It is seeing 0 MB.
Does anyone know what the issue might be? It is TWRP 2.8.2.0 touch recovery.
Thanks in advance for your help.
tonyfiore75 said:
Hi,
So I unlocked the bootloader on my phone and rooted it successfully (I believe). In the bootloader screen it shows as being unlocked. I am able to use Root Explorer with no problem, as well as Titanium Backup.
I flashed the latest TWRP for this phone (from Original Android Development). It seemed to have flashed fine. The only problem is that I can't really do anything from within recovery. It can't seem to 'see' my internal storage. I don't think mounting it results in anything. It is seeing 0 MB.
Does anyone know what the issue might be? It is TWRP 2.8.2.0 touch recovery.
Thanks in advance for your help.
Click to expand...
Click to collapse
If you go into advanced you can manually mount and unmount, give that a try.
Thanks. I had tried that but it still showed 0 mb. It has to be the recovery because I can see all of my files, rooted or otherwise, from Root Explorer.
Sent from my Nexus 6 using XDA Free mobile app
tonyfiore75 said:
Thanks. I had tried that but it still showed 0 mb. It has to be the recovery because I can see all of my files, rooted or otherwise, from Root Explorer.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
maybe this will help you out.
http://forum.xda-developers.com/showthread.php?t=2380913
edit: you're going to want to use the proper system images for this device
https://developers.google.com/android/nexus/images#shamu
Not sure if you'll need the binaries as well
https://developers.google.com/android/nexus/drivers#shamu
Thanks for all that, but I don't understand. It's only twrp recovery that can't see the file system. Root Explorer can see everything. That doesn't sound like the file system is messed up, does it?
Sent from my Nexus 6 using XDA Free mobile app
After reading this thread, I realized I have the same problem as you. What I noticed is that its showing up as 0mb because the device is still encrypted. In order to fix this boot up into the OS. Set a screen lock PIN or password. Make sure you save it as requiring password on startup. Then bootup into TWRP and it should ask you for your password to decrypt. Put in the correct password and your files should show up again...At least that's how it just fixed my problem lol
Man, you are a frigging genius! I was wondering why TWRP was asking me for a password. And I did think to myself for a second, "I wonder if it's not letting me access my files because I didn't provide the correct password". But I never chose a password. I chose a PATTERN. How the hell was I supposed to enter in a pattern? Anyway, I did what you suggested. I entered in a pin, went to recovery, and all was well. Very interesting experience. Thank you SO SO SO much. I was literally pulling my hair out. Oof! What a day!
Sent from my Nexus 6 using XDA Free mobile app
Haha, you're very welcome! Last night I flashed TWRP just for the hell of it in case I ever needed it in the future. I didn't even bother to check out if it worked. Once I saw this thread, I booted up the recovery and noticed the same exact thing as you. I had a pattern as well. Anyway, goodluck!!
If you have a pattern lock, it's currently done by assigning numbers to the 'dots' in a matrix.
Code:
123
456
789
A capital 'L' would be 14789
If you don't set a password, it should decrypt automatically
Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
Click to expand...
Click to collapse
He did set a password. It was a pattern lock and it was set so that it was required at startup. Only problem is, TWRP doesn't have an option to use a pattern to decrypt the device.
---------- Post added at 03:29 AM ---------- Previous post was at 03:23 AM ----------
Zer0_Cool said:
If you have a pattern lock, it's currently done by assigning numbers to the 'dots' in a matrix.
Code:
123
456
789
A capital 'L' would be 14789
If you don't set a password, it should decrypt automatically
Click to expand...
Click to collapse
Cool! Never knew that. So I guess you can use still decrypt it if you have a pattern lol
Holy crap, I didn't even think that the pattern could be entered numerically. What a dope I am. I should have attempted that. Then again, I never thought of it. Oh well. Great to know. Thanks to everyone who helped me out. All of your contributions to the thread are greatly appreciated. I was sweating a bit there. Now I can go to sleep happily instead of angrily confused. I'm sure this will help someone else out down the line. Thanks everyone!
Feedback
Hey guy's,
OK, this samething just thappened to me for the second time since having my N6. The only way I could resolve it was a factory reset. :victory:
Trust me ever since I made the jump from Lollipop to Marshmallow I've had a lot of aggro.
But I'm now rocking Stock Marshmallow with TWRP and Root. Happy Days!! :highfive:
I know that this is an INSANELY old thread, but I just lost about an hour and most of the hair I had left, tearing it out over this issue. And I'd like to suggest -- well, BEG, actually, PLEAD -- for an small UI change that would go a long way to make this problem go away:
The first thing I see in my TWRP (which is 2.0.3-0) is the screen which says:
_______________________________________________________
Mount |
Decrypt Data |
Enter Password |
|
|______________________________________________________ |
....
and so I spend an hour + wrestling with the fact that I **KNOW** I never applied a password to this phone. Now if only the UI said instead:
_______________________________________________________
Mount |
Decrypt Data |
Enter Password |
(this is the PIN you enter to boot your phone and unlock it) |
|
|______________________________________________________ |
....
No normal person who didn't know it in advance would ever imagine that this "password" is just the phone PIN.
Note to dev: you might also include (perhaps as a footnote? lol) the information that 1. a lock pattern represents a PIN as well (and therefore a password); and 2. if no PIN has been set, then the user needs to reboot and set one in order to use TWRP (because, as we all know, one should not engage in unprotected recovery )
@sbpetrack: It's unlikely that the TWRP developers are going to see this thread. You might want to post your change to their Github Issues Log.
Twrp 0mb
I am new to flashing. I just sucessfully flashed twrp on my yureka .I booted into twrp and while taking backup it was showing as internal storage 0mb. What to do next. I donot have any pattern lock but just swipe to unlock.
@prashanth95: You might want to ask that question in the forum for your device. While I commend you for searching for a thread before making a new one, this is the Nexus 6 section. It's unlikely we're going to be of much help because the devices are totally different.
Hi frend
Hi, I also had such a problem. In fact it was very simple. I have Xperia z3 dual. Here's what I did: you need to manually do a form with TWRP:good::good: Wipe / Format data Yes Good Luck
sarkhan88 said:
hi, i also had such a problem. In fact it was very simple. I have xperia z3 dual. Here's what i did: You need to manually do a form with twrp:good::good: Wipe / format data yes good luck
Click to expand...
Click to collapse
format data saved my day
thanks a tom
its not asking for an password for me
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
morphixxp said:
After reading this thread, I realized I have the same problem as you. What I noticed is that its showing up as 0mb because the device is still encrypted. In order to fix this boot up into the OS. Set a screen lock PIN or password. Make sure you save it as requiring password on startup. Then bootup into TWRP and it should ask you for your password to decrypt. Put in the correct password and your files should show up again...At least that's how it just fixed my problem lol
Click to expand...
Click to collapse
I have installed TWRP 3.2.1-1 for the OnePlus 5t, flashed LineageOS 15.1 onto there, February 4th edition.
Now, when i try to update it, it doesnt show any space, and its not asking me for an Password, what now?
please help!
forceartz said:
its not asking for an password for me
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
I have installed TWRP 3.2.1-1 for the OnePlus 5t, flashed LineageOS 15.1 onto there, February 4th edition.
Now, when i try to update it, it doesnt show any space, and its not asking me for an Password, what now?
please help!
Click to expand...
Click to collapse
This is an N6 thread [emoji6]
It's not mounting internal storage, so it shows 0MB. I'm not current in the OP5 + Oreo combination, so you should check the OP5 forum to see if you need to use Codeworkx or maybe Blu Spark TWRP.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I am trying to check for updates but I am not seeing the recent update that is being pushed out yet, so I was wondering if someone managed to capture the OTA file
Here are the details:
Firmware Version: MSM8960PRO_BP_23255.138.89.00R
Kernel Version: 3.4.42-gb476356 hudsoncm @ ilclbld99 # 1 Tue Aug 25 07:43:11 CDT 2015
System Version: 222.27.5.ghost_row.Retail.en.US
Build Number: LPA23.12-15.5
Pulled this off my phone: https://mega.nz/#!a4Mz2BiQ!VSxGh6g2oLviQ5yO9bhlh9-MCVBTf3GE7vzYZ3ZYvw0
But I haven't been able to apply it, even after using fastboot to flash stock system partition. All the hashes fail comparison.
All my attempts at taking this have failed as well, I even reflashed stock 5.1 from Motorola and tried. Have you tried sideloading this?
crpeck said:
All my attempts at taking this have failed as well, I even reflashed stock 5.1 from Motorola and tried. Have you tried sideloading this?
Click to expand...
Click to collapse
Yes, I think it is a bad OTA. It failed at me as well.
Benoe said:
Yes, I think it is a bad OTA. It failed at me as well.
Click to expand...
Click to collapse
My phone won't even start now. I disabled and uninstalled xPosed and flashed the stock recovery, and restarted and it let me download and install the update. Then I check my phone and it won't start. I get the boot screen with the rotating globe, then just a black screen. Scouring the forums for a fix.
I've tried re-locking the bootloader but can't seem to get that to work now that I've moved to 5.1. The method I used previously just fails. It looked like unlocked bootloaders were failing on the update.
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
adamkaye said:
My phone won't even start now. I disabled and uninstalled xPosed and flashed the stock recovery, and restarted and it let me download and install the update. Then I check my phone and it won't start. I get the boot screen with the rotating globe, then just a black screen. Scouring the forums for a fix.
Click to expand...
Click to collapse
I hate to say this, but, did you try powering it off & back on? Ever since 5.1 whenever I've reloaded the firmware the initial boot always locked up on me.
someone has succeded with the update here:
http://forum.xda-developers.com/moto-x/general/official-moto-x-stagefright-patched-libs-t3200734/page7
crpeck said:
I've tried re-locking the bootloader but can't seem to get that to work now that I've moved to 5.1. The method I used previously just fails. It looked like unlocked bootloaders were failing on the update.
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
I hate to say this, but, did you try powering it off & back on? Ever since 5.1 whenever I've reloaded the firmware the initial boot always locked up on me.
Click to expand...
Click to collapse
I do have an unlocked bootloader on my XT1053 Dev Edition, so maybe you're right, unlocked BLs can't upgrade? Damn shame. I ended up having to format the system partition and completely sideload the stock 5.1 ROM from scratch. Such a pain. I'm holding off on upgrading for now. Either going to get a new phone soon anyway or start flashing ROMs. I never felt the need to flash anything fancy on here since stock Android + Moto's tweaks + some Xposed/GravityBox magic were perfect for me, but I may have to flash something that has Stagefright built in.
I should add, at this point, I'm just glad to have a working phone. I'm no magician with this stuff, and there was a point last night where I thought I had completely bricked my phone.
Check out the link in post #7 above - it worked for me.
got the ota today on my phone. is it Marshmellow?
Got it earlier this week.
No, it is not Marshmallow. Marshmallow should be version 6.
Was this question rhetorical? The details are listed in the release notes.
There's some radio related firmware in there for anyone interested. Sometimes that's helpful for people with radio issues.
---------- Post added at 12:07 PM ---------- Previous post was at 12:04 PM ----------
It'd be nice if there was a method to upgrade modem firmware without needing the entire update.zip. That was certainly always a pro with Samsung devices. Odin was nice but Chainfire's Mobile Odin was noice.
Hello, looking for help.
My daughters Ze551kl had an ota update error resulting in a true cyclic bootloop from asus bootup screen to op system which reboots in about 1 second after flashing the op system background.
I cant unlock the bootlock. No operating system access.
I tried to restore with adb sideload and i get response on a pc and the phone that it installs ok, but the bootloop remains. I put 1531 on via adb and i did get the correct files from asus. I have done this several times. No change.
I can't flash because the bootloader is locked and i cant find an adb bootloader level unlock. Does this exist?
What do you folks recommend?
I cannot install twrp or do flashing of recovery. I can get to fastboot and the recovery options. I have cleared the cashes.
Thanks for any advice.
---------- Post added at 11:32 AM ---------- Previous post was at 11:16 AM ----------
Hello, almost forgot, do i need to unlock the bootloader?
If the abd transfer has worked and installed the new version, but the bootloop remains, what else can be done? Is this a partition or hardware problem that showed itself during the update process?
You may have bricked it. Personally, I'd send it to Asus, if it's still in warranty, and let them fixit.
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Fybere said:
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Click to expand...
Click to collapse
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
http://www.carbontesla.com/2016/11/downgrade-rollback-huawei-p9-nougat-to-marshmallow-europe/
Brontok said:
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
Click to expand...
Click to collapse
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
You`re welcome. DC Phoenix is good, but you have to pay in order to use it, right ? That`s my problem, I cant pay since all my money comes from my dad . In your case I would probably try to update via huawei updater and HiSuite. As far as I`ve seen, that method has been most reliable for the majority of users.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
DC Phoenix worked for me, I found myself in the same position as you (no dload, reocvery, e-recovery only fastboot) and thought my phone was unrecoverable for good. Tried every method possible. in the end bit the bullet paid the fee for DC Phoenix had my phone running in 20 minutes.
Hopefully some smart cookies can develop some freeware that works the same way.
Z-Blade said:
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
Click to expand...
Click to collapse
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
In the same situation
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
mjcaballero said:
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
Click to expand...
Click to collapse
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
Z-Blade said:
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
Click to expand...
Click to collapse
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Thanks
Fybere said:
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Click to expand...
Click to collapse
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
i have problem to
..
---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------
please i try to install twrp but not work
---------- Post added at 12:38 PM ---------- Previous post was at 12:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
what you chose i dont know i buy buy the DC PH..
HOW
---------- Post added at 02:38 PM ---------- Previous post was at 02:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
PLEASE
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
i install tswp last but not work
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
ppppplease
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
oooooooo
Sorry for my post if its already been addressed: I have XT1900-1 (Google Fi)- I have found a hundred threads all over the net but so many vary and files claimed to be with it are not with it.
I want to return to stock full complete return of phone- I made a mistake somewhere while installing Pixel Sense- and somehow TWRP is not installed, I have to Fastboot- and when i get there it asks for a password to decrypt data to flash anything. I cant make any changes, flash anything at all. I dont remember setting a password...Ive read that i need to wipe everything and go back to stock?
Little lost here, This is the first time ive attempted to alter a phone in 3-4years so im a bit out of touch-
As mentioned Its a XT1900-1 From google FI- I think i have a stock rom- Found this--(XT1900-1_PAYTON_FI_9.0_PPWS29.69-26-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
TWRP doesn't support fingerprint, then you need remove fingerprint from system settings. Or flash stock FW without 'fastboot erase userdata' command.
Not sure but worth a try
I have read somewhere on XDA about using your screen lock password ,or pin for this...... I hope this helps
I just hit cancel and it lets you in but if you're trying to back stock, why do you want TWRP?