Related
I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux
You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
nikhilsnigam said:
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
Click to expand...
Click to collapse
What twrp version are you using?
Piyush lalwani said:
What twrp version are you using?
Click to expand...
Click to collapse
latest official twrp
nikhilsnigam said:
latest official twrp
Click to expand...
Click to collapse
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
I did that already. after flashing supersu immediately then also stuck at boot screen. tried with modded twrp too 3.0.2.22
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
okay now after few trial and error method i have come to the conclusion that this happens only after unencrypting the device. after eunencrypting it wont boot any other roms except those which have been already backed up.
So,
can i flash roms on encrypted device? I mean i test a lot of roms and i change frequently.
I guess no, right?
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Piyush lalwani said:
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Click to expand...
Click to collapse
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
nikhilsnigam said:
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
Click to expand...
Click to collapse
In nodded recovery too?
Piyush lalwani said:
In nodded recovery too?
Click to expand...
Click to collapse
going to try with modded recovery this time
nikhilsnigam said:
going to try with modded recovery this time
Click to expand...
Click to collapse
Yeah give a try
Piyush lalwani said:
Yeah give a try
Click to expand...
Click to collapse
how does modded recovery helps in this btw?
hope it works
OK So I am able to flash any rom with encrypted storage and latest modified twrp.
This is working for me right now but still haven't found solution why it wouldn't work on unencrypted storage.
Thank you.
This guide solved everything
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940
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
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
eid_elageeb said:
After installing oos beta 8 nougats I made encryption and I made pin code but after restarting the phone when I write the pin code it gives me wrong pin and also gives me wrong pin when trying to open twrp , any solution please??
Click to expand...
Click to collapse
You need modified TWRP 3.0.2-28 to get TWRP working with Beta 8. I had the same issue witrh my installation.
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
strumaticjoker2 said:
Also you need to make sure to remove your lock screen, then you will be able to use TWRP
Click to expand...
Click to collapse
even without protection, twrp asking pw, need to erase use data and system.
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
eid_elageeb said:
I solved the problem by using oneplus 3 toolkit " Force Decryption Device" option and it works well, Thank you for your help guys
Click to expand...
Click to collapse
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
yiphoming said:
I got the same issue, cannot decrypt the internal storage.
I am using TWRP3.0.2.1-28
What is your action, just run "Force Decryption Device" by using Toolkit v.3.6
and what recovery are you using ?
Thx
Click to expand...
Click to collapse
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
eid_elageeb said:
First I flash the stock recovery by toolkit and then make force decryption device and then I flash twrp 3.0.2.1-28 and It works, but you should to know that everything on your phone will be erased
Click to expand...
Click to collapse
No luck, can erase the storage, but it is still in encrypted.
yiphoming said:
No luck, can erase the storage, but it is still in encrypted.
Click to expand...
Click to collapse
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
rarog said:
It doesn't work though, if you installed dirty and just upgraded from MM. TWRP keeps asking for password and doesn't accept it, even if I change to password (else using PIN) in the system.
Click to expand...
Click to collapse
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
AcmE85 said:
I came from OOS 3.2.8 running already with F2FS and did a dirty flash to the Nougat Beta.
All with the -1.28 TWRP and have no issues going into TWRP and it accepts my pin.
Click to expand...
Click to collapse
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
rarog said:
This is the way I went, just yet being on ext4. Could it be a difference, if you flash or if you just boot TWRP? I'm only booting instead of flashing, so I retain my recovery, as I didn't see the new Oxygen recovery for OOS4 in the wild yet.
Click to expand...
Click to collapse
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
LS.xD said:
I'm using latest modified TWRP 3.0.2-28 + OOS Beta 8. I have a protected lockscreen (fingerprint / pin) and pin is needed to start the device.
I flashed TWRP, wiped everything and changed "DATA" filesystem to "F2FS" and flashed the rom (clean installation)
I have full acces when using TWRP.
No need to force decryption or anything...
Click to expand...
Click to collapse
Do you also get the dm-verity bootscreen?
AcmE85 said:
You probably need an older version for ext4. The last one working on ext4 when I did the switch to f2fs was -1.25 if I remember correctly.
After the switch to f2fs I had to flash 1.28 or the recovery wouldn't accept my pin anymore.
Click to expand...
Click to collapse
Hm... Interesting, do you have a link? And perhaps a link to a thread with all the available versions? I searched, but found only several tutorial threads with just one or another version linked, no thread for specific modified version.
AcmE85 said:
Do you also get the dm-verity bootscreen?
Click to expand...
Click to collapse
As far as I know - no.
When would this error message pop up?
LS.xD said:
As far as I know - no.
When would this error message pop up?
Click to expand...
Click to collapse
Right at boot before or after the screen which shows that the bootloader is unlocked.
AcmE85 said:
Right at boot before or after the screen which shows that the bootloader is unlocked.
Click to expand...
Click to collapse
No such error message for me
LS.xD said:
No such error message for me
Click to expand...
Click to collapse
Did you flash SuperSU?
AcmE85 said:
Did you flash SuperSU?
Click to expand...
Click to collapse
Yes, 2.78 SR5
I have done format userdata in fastboot but my phone still shows up as encrypted. Flashed 3.0.2-1.28 and I still get a password screen when booting to recovery. Not really sure what else I can do.
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, the instructions to do that are here. You will lose your data and you'll have to set up your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb reboot bootloader
3. fastboot boot twrp-daisy-3.2.3-0.img
4. Hit "Cancel" if you're prompted for a decrypt password
5. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
6. Run the install in TWRP to permanently install TWRP across both slots
7. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
, Guava.
adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!
tutankpusch said:
adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!
Click to expand...
Click to collapse
Oops - ad "/sdcard" to the end of that command. Missed that. I'll update the OP.
I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!
KezraPlanes said:
I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!
Click to expand...
Click to collapse
Decryption is a Xiaomi issue...what do you mean by fixed version?
d1ngh said:
Decryption is a Xiaomi issue...what do you mean by fixed version?
Click to expand...
Click to collapse
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X
d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...
KezraPlanes said:
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X
Click to expand...
Click to collapse
Try adb push while TWRP is booted. It should get you past the pre-load issue.
actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
but it seems everything is working fine
brunoliveh said:
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...
Click to expand...
Click to collapse
When you're in the TWRP UI tap "Install" and select the twrp file you pushed (if you used the command above it should be in /sdcard)
tutankpusch said:
actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
Click to expand...
Click to collapse
There isn't a cache partition on A/B devices, that error is fine.
d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory
brunoliveh said:
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory
Click to expand...
Click to collapse
If there's already stuff there you'll need to specify the filename as well
Great news!
-Is full encryption working?
-I don't want to loose magisk... how can i preserve it?
d1ngh said:
Try adb push while TWRP is booted. It should get you past the pre-load issue.
Click to expand...
Click to collapse
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know
KezraPlanes said:
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know
Click to expand...
Click to collapse
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.
d1ngh said:
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.
Click to expand...
Click to collapse
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Edit: Hooking up USB and I can access storage. Copying stuff over just in case.
KezraPlanes said:
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Click to expand...
Click to collapse
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.
d1ngh said:
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.
Click to expand...
Click to collapse
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Switch active slot
---------- Post added at 09:23 PM ---------- Previous post was at 09:23 PM ----------
KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Try to Switch active slot