Related
I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2
Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.
where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.
Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app
hi friends
LG G3 D855 - Android 5.0-ROOT
I want to install the CUSTOMROM. I installed TWRP. I restart the phone, I see Secure Booting Error! Cause: boot verify certification.
Then the phone turns off, the warning light starts to burn ...
I wear again, remove the battery, the phone works.
-
I want to Twrp to install custom ROMs ..
1. I installed Kitkat
2-Root
3-I installed TWRP.
4-Phone I rebooted, it s work for the ... (TWRP working)
5-. I install custom ROMs and bump with TWRP
6- I restart the phone, I got the error again (Secure Booting Error! Cause: boot verify certification.)
I restart the phone, remove the battery, but I always get the same error.
I install android 5.0 with Lgtools, phone is working. But I want to install custom ROM. How do I make
????
i believe the error may be with the kernal. boot into twrp and try flashing one of these and report back
->http://forum.xda-developers.com/lg-g3#kernels
kp_q said:
i believe the error may be with the kernal. boot into twrp and try flashing one of these and report back
->http://forum.xda-developers.com/lg-g3#kernels
Click to expand...
Click to collapse
when i install TWRP , ı have Secure boot error
ftekinsen said:
when i install TWRP , ı have Secure boot error
Click to expand...
Click to collapse
????????????
??? help pls
i fix it i can help about this topic anybody ...
Please post your solution; I just rooted and flashed TWRP, and now I cannot reboot into recovery.
FIXED
Heres a solution to your problem... http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
ftekinsen said:
i fix it i can help about this topic anybody ...
Click to expand...
Click to collapse
Would love to hear the fix. Happening to me today.
Thanks!
How to fix it? Can you tell me the step?
I really have the problem like you, want use custom rom but can't reboot in recovery mode
ftekinsen said:
i fix it i can help about this topic anybody ...
Click to expand...
Click to collapse
hey i have this issue on att g3 installed twrp through auto rec now boots to security error screen. how can i fix this?
Since you have twrp just flash a kernel or a new rom through twrp.
Cool thanks man. I was kinda stuck there. I couldn't get my pc to see the phone, had to wait for a micro sd card to put the kernel on. Thanks a lot
Sent from my LG-D850 using XDA Free mobile app
Hello Friend
I just have same problem like you + the when I connect the G3 to my computer it did not recognize it
many tanks for your help
This worked for me
this - http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
LG G3 LS990 - ZVB - Rooted + TWRP - Flash Stock Recovery Only
Hi, I am looking for flashing stock recovery on my LG G3 Sprint LS990. I believe the same method will work. I am currently running on stock ZVB ROM rooted and TWRP installed as recovery. In the download folder for LS990-ZVB http://downloads.codefi.re/autoprime/LG/LG_G3/LS990/stock_partitions/ZVB, there is no recovery image file, but in ZVA folder there is. I am just wondering if I can flash ZVA folder's recovery image using Flashify to my ZVB ROM LS990 and if that will work.
My LS990 is rooted and currently have TWRP. i get secure boot error when the phone reboots after accepting Android updates installation that come automatically. I believe installing stock recovery will resolve this issue and allow to install Android updates I do not want to going back to stock completely, that will unroot my phone and again I have do all these staffs.
Anyone can help to advise, will be appreciated. Thanks.
Worked for me
It's not english, it is portuguese Brazil, but it works.
youtube.com/watch?v=gHAA5e2FQbU&index=1&list=LLtlXyuPzN6skeex-P2apfrQ
autorec does the job for me.... thanks dev
Secure Boot Error 1003
ftekinsen said:
i fix it i can help about this topic anybody ...
Click to expand...
Click to collapse
Ian having this issue I really would like help resolving.
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
I think I've seen that in order to install TWRP on the V500 is similar to how on my VK810 variant, at least the part that requires downgrading your bootloader. If it's like the VK810, it has to be the bootloader from 4.2.2. I'm sure there's TWRP threads in these sections, specifically for the V500 that give the details and files.
I'd love to know a way too. I just rooted which went great, but I have the V50020f and don't want to do another thing until I see what happens in this thread. After years of flashing and rooting I finally hard bricked my Lenovo Yoga 10 and this is my replacement tablet, so I don't want to chance it at all. Until I read a concrete solution for this build I'm staying where I am.
That wall of text is really hard to read @[email protected]!c, when I first saw it I was too tired to try and decipher it so ignored it. Now I've had another look.
Have you tried downgrading to an older firmware which people have had success with?
I had trouble when I first got this tablet but kept reading the forum and found a method to downgrade, it isn't pretty but eventually it worked. As I'm new to this device I'm not overly familiar with the different official firmware versions so I'm not exactly sure what you've got.
My tablet was more complicated as the LG tool put the Chinese, no Google apps, version on for me as that is where it was bought. So I had to downgrade so I could get apps from the Play Store to flash my recovery!
So patience and research will reward you.
[email protected]!c said:
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
Click to expand...
Click to collapse
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
I know it didn't work for the OP, but coming from bone stock v50020f, I successfully rooted using ioroot25r1, updated Supersu through playstore, then using flashify i installed TWRP 2.8.7.1 (newest I think). Once booted into TWRP recovery, I wiped cache, data, and system, and then installed AOSP Marshmallow. All went smooth as silk, no problems at all. Now I can finally stop being jealous of my wifes Nexus 7!! Hope this helps some.
vettejock99 said:
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
Click to expand...
Click to collapse
Thanks.!
i have just used twrp manager apk from playstore (similar to flashify) to get TWRP 2.8.7.1 on stock v50020f, rooted using ioroot25r1 on a mac, with updated Supersu through playstore. just had to run the apk twice as it failed first time, and have booted into twrp recovery.
Had the same problem with the recovery but worked by rooting and flashing recovery with flashify.
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
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