hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
ravn83 said:
hey guys,
i have a big problem.
i unlocked my one+ 3 2 weeks ago and installed twrp and cm13. all worked fine.
yesterday i read the news from cm the first devices will get offical cm14.
so i donwloaded the first rom and updated my phone (without a wipe!).
the cm14 starts good and all worked fine.
But, i find out, i can´t hear a phone call.
so, i want to go back to the twrp to restore my backup of cm13.
the problems begins....
i can´t boot twrp. i see the bootloader screen and after switching the screen to recovery (normaly) i got a black screen (seems like to shut off the screen).
then i tried to reinstall it, nothing.
after a full evening of trying i wiped it (factory reset) from android 7.
after the reboot i got the same problem. -> black screen after bootscreen Android won´t start, recovery won´t start.
then i downloaded a toolbox and installed the stock recovery -> no change -> black screen.
then i tried to find a stock image als *.img format to flash it with all (kernel and recovery, etc) with fastboot, but i didn´t find an image.
my last try was to make a full wipe with "fastboot -w". but this won´t work too.
so, now my phone will only boot into fastboot and thats it.
i need urgend help.
can anyone tell me what i can do? how can i install any os and wipe via fastboot and with no recovery?
thx a lot for your help.
ravn
Click to expand...
Click to collapse
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
DiMatador said:
Lots off people are getting this problem and trust me for some reason people post steps to fix this that are complicated for people who are just getting to playing around with TWRP.
Look, download the original TWRP recovery from here, https://dl.twrp.me/oneplus3/ the one you need is the 3.0.2-1 . I used it and I got back to MC13 From MC14.1 which by the way is now working pretty good. Once you fastboot flash recovery .this 3.0.2-1 recovery you can actually use it with MC14.1 as am doing right now. In any case. flash recovery >factory reset > adb your MC13 Zip to the phone > reboot...
Remember All Of This Steps Are Always Taken At Your Own Risk !!
Best of luck!!! [emoji6]
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
to flash only the new recovery will not help.
tomorrow i will try to flash, wipe (with "fastboot -w" and copy the zip file.
Will the copy install the cm13 version? or do u mean sideload to have the cm13 zip for the twrp to flash?
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
superiscch said:
Try to flash the modified twrp. Check the official topic for cm 14, it is linked over there
Edit: this one http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
@superiscch just provided you with the TWRP that works. This is what i did !
Flash the recovery provided on the link >boot to the new recovery, you well see the version at the top left corner as 3.0.2-1 > factory reset > adb sideload the MC 13 ....... Reboot system > than add your choice of google apps to the sdcard root > reboot to recovery > flash google apps from with recovery than reboot, you would be golden. After, if your interested just flash the TWRP from the original twrp team. Cuss the one you just installed is modified, it be your choice !!
Sent from my ONEPLUS A3000 using Tapatalk
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
ravn83 said:
Hey guys,
thx for your replay. i will try it after work.
but i have one question ... what do u mean exactly with " adb your MC13 Zip"?
do u mean to transfer the zip to install with twrp or is there a command to install the zip to the systempartition?
Click to expand...
Click to collapse
Okay... Look, once you have flash the modified recovery and you reboot. You be able to boot to your OS. Than you have to simple options 1. Load the CM13 ZIP file to your sdcard which you can use for installing with recovery
2. Boot into recovery and side load the MC 13 ZIP file into your phone using adb...sideload would be using adb
ADB... adb sideload <name of file> without the brackets...
Good luck man
Sent from my ONEPLUS A3000 using Tapatalk
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
ravn83 said:
Thx a lot guys, now it works and in installed my phone successfully.
it was the wrong twrp version.
now, the weekend is save :silly:
Click to expand...
Click to collapse
Alriiiight !!
Sent from my ONEPLUS A3000 using Tapatalk
Related
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
vipimg said:
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
Click to expand...
Click to collapse
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
hrishi21007 said:
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
Click to expand...
Click to collapse
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ??
Mine's bricked.
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
aakarshak said:
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
Click to expand...
Click to collapse
This is what I was trying to say i was not sure about it i didnt do it yet just waiting for a solid one
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
vipimg said:
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
Click to expand...
Click to collapse
I jst flashed the cwm recovery and its working fine
Yes i was about to tell u to flash CWM recovery
aakarshak said:
I jst flashed the cwm recovery and its working fine
Click to expand...
Click to collapse
which one... is it 64 bit or the old one ????
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i am also trying to flash the same thru fastboot but every time i am booting to recovery it shown cynogen's recovery.
update cm recovery is already unchecked in Dev option.?
any help
Rooted my phone, bricked it, and now went back to default Lollypop
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
After flashing dont start ua phone
Go to recovery mode directly!
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
I hv updated my yureka yesterday manually to cm12 and device is running very smoothly..bt I faced an issue while charging the phone..it was taking around 4hrs of time and phn heating a lot .. I was thinking to revert back to kitkat which was also working f9 for me without any heating issue bt I came to know it is not passible to go back.. I was bit tensed regarding heating issue bt suddenly I see my lumia 520 charger and I charged yureka with that charger and u won't believe charging speed is increased and phn was nt heating up at all.. I don't knw what is issue with charning in lollipop bt nw I am very relaxed ...
original 12S zip links
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can u post links to original CM12S zip u mentioned above...?
vipimg said:
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Click to expand...
Click to collapse
I bricked mine... So i dont recommend rooting after upgrading to cm 12
kailashnj said:
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
Click to expand...
Click to collapse
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
Are you sure this worked for you,cause basically you are just saying that you did the normal rooting procedure that we did when we had kitkat,just that you used a 64 bit recovery this time
Stock recovery for CM 12
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can you tell you you flashed the cm12 recovery ???
i cannot find it inside the cm12 update zip file.
abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
I did install the rom from the fastboot method still it did not work. I am fed up of the CM12 rom.
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
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...!
Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
please help me!
infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....
Which TWRP are you flashing and what rom were you on before the speed bump
NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.
Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!
tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.
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