Nexus 5x in google logo. Cannot flash factory image - Nexus 5X Q&A, Help & Troubleshooting

I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.

eNVy said:
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
Click to expand...
Click to collapse
post a screenshot from cmd here to see the error you get from fastboot...

kopfik said:
post a screenshot from cmd here to see the error you get from fastboot...
Click to expand...
Click to collapse
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.

eNVy said:
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
Click to expand...
Click to collapse
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)

kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Shouldn't you be using the latest twrp 2.8.7.2? Ive had issues flashing roms without using the latest version. You could also have issues with older versions of twrp and encryption. Id suggest wiping data from twrp and then flashing the factory image from bootloader.
Sent from my Nexus 5X using Tapatalk

Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp

I think to be able to really do anything you need to get into bootloader and have fastboot recognize the device. Make sure the files from 6.01 are all correct and you're flashing in the right order. Follow the guide item #8 http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 If you can get the system.img and vendor.img flashed and then lock the bootloader it will wipe everything to factory, internal storage included. If you do that you must have stock recovery.img flashed as well. If downloading system.img hangs reboot and try it again.

kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Sorry, I was using v.2.8.7.2.

mnehring said:
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
Click to expand...
Click to collapse
I got it to work. I just had to change the USB port.
Why don't you try a different USB port or a different cable. Or even try on a different computer.

Related

I accidentally wiped the system and now there is no OS installed. Am I screwed?

I was trying to install superzen but I accidentally wiped the OS. Am I screwed? Is there anything I can do, or is this looking like I bricked the phone?
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Go there and look at section 3.2. MAKE ABSOLUTELY SURE that you grab the correct firmware for your device (WW or CN, 550 or 551). As far as I can tell, unless you made a NANDROID backup in custom recovery prior to wiping system, this would be your only way back to working order.
Are you currently unable to get back to a custom recovery? Can you not just successfully flash superzen now?
Level99 said:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Go there and look at section 3.2. MAKE ABSOLUTELY SURE that you grab the correct firmware for your device (WW or CN, 550 or 551). As far as I can tell, unless you made a NANDROID backup in custom recovery prior to wiping system, this would be your only way back to working order.
Are you currently unable to get back to a custom recovery? Can you not just successfully flash superzen now?
Click to expand...
Click to collapse
Thanks for the reply, it seems that my computer can't recognize my phone through adb, i can get into recovery, but my phone is just not recognizable. I should mention that it was earlier, and I installed supersu with cwm tethered.
EDIT: I can't use fastboot for twrp.img, it says I don't have permission and now I can't even access recovery because I'm stuck in a bootloop.
UPDATE: Ok so fastboot recognized the phone but I do not have permission to load twrp.img
Have you got this sorted now?
timbernot said:
Have you got this sorted now?
Click to expand...
Click to collapse
no, every time I try to flash twerp with fastboot, I get this error
"writing recovery failed <remote: permission denied>"
EDIT: HOLY HELL GUYS I FIXED IT! It turns out, my usb cord didn't work for some reason, tried another one and it works fine. Doing adb sideload right now.
venom55520 said:
no, every time I try to flash twerp with fastboot, I get this error
"writing recovery failed <remote: permission denied>"
EDIT: HOLY HELL GUYS I FIXED IT! It turns out, my usb cord didn't work for some reason, tried another one and it works fine. Doing adb sideload right now.
Click to expand...
Click to collapse
YaY !:good:

Recovery error when flashing rom

Hi y'all,
I did two days of thread research but haven't found anything similar to my problem so far, so here it goes...
Running stock xperia android 5.1.1 14.6.A.0.368, UB, twrp, rooted with flashtool, adb and fastboot on pc (win10)
Wanted to take a try on a custom rom but that didn't go so well.
First thing I did was flashing rom (Resurrection-Remix-LP-v5.5.9-20151120-amami.ftf.zip) from recovery after a full wipe.
I typed over the recovery results:
(after the RR ascii art)
patching system image unconditionally...
detected filesystel ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
flashing superSU...
detected filesystel ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
unmount of /system failed; no such volume
script succeeded: result was [0.200000]
updating partition details...
...done
Got into a bootloop, lost recovery etc, so installed original firmware with flashtool, acquired root & recovery again and restored data from a nandroid backup.
After that I did a few other attempts, and tried to install a kernel but I'm not sure how to install the kernel that's in the ResRemix thread.
http://forum.xda-developers.com/son...eria-z1c-resurrection-remix-lollipop-t2996231
kernel:
https://github.com/SlimRoms/kernel_sony_msm8974
What did I miss?
Fanks!
lialotta said:
Hi y'all,
I did two days of thread research but haven't found anything similar to my problem so far, so here it goes...
Running stock xperia android 5.1.1 14.6.A.0.368, UB, twrp, rooted with flashtool, adb and fastboot on pc (win10)
Wanted to take a try on a custom rom but that didn't go so well.
First thing I did was flashing rom (Resurrection-Remix-LP-v5.5.9-20151120-amami.ftf.zip) from recovery after a full wipe.
I typed over the recovery results:
(after the RR ascii art)
patching system image unconditionally...
detected filesystel ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
flashing superSU...
detected filesystel ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
unmount of /system failed; no such volume
script succeeded: result was [0.200000]
updating partition details...
...done
Got into a bootloop, lost recovery etc, so installed original firmware with flashtool, acquired root & recovery again and restored data from a nandroid backup.
After that I did a few other attempts, and tried to install a kernel but I'm not sure how to install the kernel that's in the ResRemix thread.
http://forum.xda-developers.com/son...eria-z1c-resurrection-remix-lollipop-t2996231
kernel:
https://github.com/SlimRoms/kernel_sony_msm8974
What did I miss?
Fanks!
Click to expand...
Click to collapse
Try a full wipe, if you didn't already, (system, data, and caches), then try again. I've flashed RR more than once, and no trouble. I guess if you want, (but I don't think you have to), you can extract boot IMG from the RR zip, and use fastboot to 'fastboot flash boot boot.img', (or use Rashr), but I think RR comes with CM recovery, so make sure you get a TWRP IMG and 'fastboot flash recovery (twrp filename).img' right after, so you can get into recovery to flash the ROM.
Not sure what went wrong, but just make sure you have the right RR file for your phone and try again. It should be OK.
levone1 said:
Try a full wipe, if you didn't already, (system, data, and caches), then try again. I've flashed RR more than once, and no trouble. I guess if you want, (but I don't think you have to), you can extract boot IMG from the RR zip, and use fastboot to 'fastboot flash boot boot.img', (or use Rashr), but I think RR comes with CM recovery, so make sure you get a TWRP IMG and 'fastboot flash recovery (twrp filename).img' right after, so you can get into recovery to flash the ROM.
Not sure what went wrong, but just make sure you have the right RR file for your phone and try again. It should be OK.
Click to expand...
Click to collapse
I tried it as well with the Z1C CM12 rom, and had the exact same response in recovery. And i'm pretty sure the roms are both right. Any idea on what [unmount of /system failed; no such volume] means or how I could figure out to solve it?
lialotta said:
I tried it as well with the Z1C CM12 rom, and had the exact same response in recovery. And i'm pretty sure the roms are both right. Any idea on what [unmount of /system failed; no such volume] means or how I could figure out to solve it?
Click to expand...
Click to collapse
Don't know much technically, but seems like it's just saying there's no /system to unmount, (maybe since it didn't flash properly to begin with). What's your TWRP version?
levone1 said:
Don't know much technically, but seems like it's just saying there's no /system to unmount, (maybe since it didn't flash properly to begin with). What's your TWRP version?
Click to expand...
Click to collapse
I have TWRP 2.8.7.0, all the other recovery functions work fine though. I just find it weird I get the exact same response after flashing two completely different rom zips. Any thoughts on that?
coeurdefleur said:
I have TWRP 2.8.7.0, all the other recovery functions work fine though. I just find it weird I get the exact same response after flashing two completely different rom zips. Any thoughts on that?
Click to expand...
Click to collapse
Very strange. I've seen others report same thing, but it usually is just attributed to bad flash or bad download, and works after another try. One thing I guess you could try is after full wipe, go to 'mount', and check system. Also try different recoveries, etc... Have you updated your bootloader through Emma? Then you can use new recovery.
levone1 said:
Very strange. I've seen others report same thing, but it usually is just attributed to bad flash or bad download, and works after another try. One thing I guess you could try is after full wipe, go to 'mount', and check system. Also try different recoveries, etc... Have you updated your bootloader through Emma? Then you can use new recovery.
Click to expand...
Click to collapse
I went into recovery, and 'system' was indeed unchecked. So thought that was the problem, checkmarked it and flashed again, but I still get the exact same response as before, somehow it the 'mount system' option unchecks itself everytime.
I downloaded Emma, and saw that there two firmwares available for my device: 14.5.a.0.270 and 14.5.a.0.236, so both older than what I'm running currently (.368). I'm not sure how to update my recovery through Emma though, any help on that maybe?
lialotta said:
I went into recovery, and 'system' was indeed unchecked. So thought that was the problem, checkmarked it and flashed again, but I still get the exact same response as before, somehow it the 'mount system' option unchecks itself everytime.
I downloaded Emma, and saw that there two firmwares available for my device: 14.5.a.0.270 and 14.5.a.0.236, so both older than what I'm running currently (.368). I'm not sure how to update my recovery through Emma though, any help on that maybe?
Click to expand...
Click to collapse
.236 is newest, (check the numbers in the middle). To update bl with Emma, just connect phone and look at the drop-down menus. One of them is 'ta update'. You can do it whether you update rom or not. Once your bl is updated, use fastboot or Rashr app to flash a compatible recovery img, (I can link you one if you want), then you can enter new recovery by starting with phone off, then pressing power and volume down at the same time. Release both when you get vibration. Try to flash your rom again from there.

TWRP bootloops

I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices

Completely wiped my phone, can't get stock ROM unto it...

I wiped the internal storage on my phone by mistake and now my phone has no OS or ROM to flash it back on. I tried to sideload with TWRP but the feature wouldn't start. I flashed the stock recovery and tried to sideload it there but I get an "error: protocol fault (no status)"... I tried to mount storage on TWRP but that feature didn't seem to work on it either. It's a good thing that I still have my OnePlus One to use, but I would appreciate your help!!
Sent from my A0001 using Tapatalk
I had the same issue the first time I tried to add side load the stock rom, I tried it again and it worked. my suggestion is to try the side load again. Make sure your using the full rom zip.
k.s.deviate said:
I had the same issue the first time I tried to add side load the stock rom, I tried it again and it worked. my suggestion is to try the side load again. Make sure your using the full rom zip.
Click to expand...
Click to collapse
I tried like a thousand times on both stock and TWRP to no avail. When I reflashed TWRP and tried to sideload one last time it told me that I needed ADB version 1.0.32 which is what I should have because I installed the "15 seconds ADB Installer v1.4.3" from the stickied guide here on the OP3 forums... Anyway, I got access to the TWRP folder and the internal storage by just being in the TWRP recovery, not sure if it was always like that, but I just dragged and dropped the ROM and other flashables onto the phone... lol Maybe I was freaking out too much to notice, but why would anyone sideload anything if you could just drag and drop stuff while in TWRP and just flash? Maybe reflashing TWRP fixed something or I was using an older beta OP3 version before, I re-downloaded everything.
Sent from my A0001 using Tapatalk
I screwed up when I tried to update to 3.2.0 OOS. I were rooted so the installtion failed and I restored a corrupt backup with TWRP that resulted in a stuck boot logo.
I did this too fix this. boot into fastboot (if you still can) then make sure its connection properly. "fastboot devices". Then in your ADB folder place a TWRP.img and type "fastboot boot twrp.img" wait like 10 seconds, it will seem like it doesn't work but if you are a functional TWRP img it should boot up just fine. Select allowed modifications and then you can also access storage. There is a post on the oneplus forums where you can download signed full zips of the ROMS. download any of them. I will past in the post if I can find it later. Not home atm. Just copy the .zip onto the phone and then do a factory reset and flash the full rom and then reboot should work just fine. You don't need too flash TWRP just boot it if you still wanna keep stock recovery.
rickyx32 said:
I wiped the internal storage on my phone by mistake and now my phone has no OS or ROM to flash it back on. I tried to sideload with TWRP but the feature wouldn't start. I flashed the stock recovery and tried to sideload it there but I get an "error: protocol fault (no status)"... I tried to mount storage on TWRP but that feature didn't seem to work on it either. It's a good thing that I still have my OnePlus One to use, but I would appreciate your help!!
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Bro don't worry.
All you gotta do is to download a stock image.
Boot into fastboot.
Then use a toolkit like this one.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Then use his toolkit to download and boot in twrp.
Now copy paste a full signed zip onto the phone by connecting it to your PC .
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Do a system and cache clean.
Flash the zip and make it boot before rooting it.
Done..!!
Joyo-rocker said:
Bro don't worry.
All you gotta do is to download a stock image.
Boot into fastboot.
Then use a toolkit like this one.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Then use his toolkit to download and boot in twrp.
Now copy paste a full signed zip onto the phone by connecting it to your PC .
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Do a system and cache clean.
Flash the zip and make it boot before rooting it.
Done..!!
Click to expand...
Click to collapse
It worked bro thanks I was having data issues too before and now it all just works.
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
It worked bro thanks I was having data issues too before and now it all just works.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
No prob bro...!

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

Categories

Resources