Related
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
Hey guys,
I'm having some trouble with flashing a new ROM and now I've soft-bricked my device.
I was trying to flash from CROMi to CM11 so I wiped data, cache, dalvik using TWRP. But when i tried to flash CM11 M9, i would get the "failed" error. I tried flashing other ROMs but same result - "FAILED".
So I thought maybe it was the recovery. I downloaded a CWM recovery (in .zip) and tried to flash it. FAILED!
I tried to restore my device using the "Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery" method from this post. Since it is basically flashing the stock ROM, naturally it fails.
Now I'm out of ideas. How can I save my tablet?
Thanks for your help guys!
PS: I'm trying to install CMW via fastboot. When I press power + vol down, I get to the screen with "RCK, Android, Data Wipe"; I dont see the USB icon. How do i boot into fastboot?
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
berndblb said:
You are in fastboot mode when you see the three icons. Read the tiny script.
Except for CM11 M9 you did not give us anything to work with.
Give us the version numbers of:
- CROMi-X you were running
- your bootloader
- your recovery
My best guess is you are trying to flash something with an incompatible recovery, but that's just a wild guess.....
And stop flashing willy nilly until you know what's going on. You can brick this tablet if you try hard enough, you know....
Click to expand...
Click to collapse
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks!
oh.herro said:
Hi berndblb!
I'm also having this problem and I see that you're quite active in the TF700 forum that you could help me out. I wouldnt say I'm an expert but I have tinkered with phones (mostly Samsung and Nexus devices) in the past so I am familiar with ADB, terminal commands, flashing ROMs, etc.
I'm running TWRP 2.6.1. I was running CROMi-X (not sure which version) and wanted to flash OmniROM. However, TWRP would show "error flashing zip" and "failed" in red. I tried flashing a few other zips including TWRP 2.7.1.1 and CWM (I readTWRP is not compatible with some ROMs) and I would still get the error and "failed".
So now, I can't boot into the OS to flash a recovery via fastboot or via CWM Rom Manager, nor can I flash anything in TWRP. I also attempted to flash TWRP 2.7.1.1 via terminal command
HTML:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4[HTML]. I loads but it doesnt install when i restart my device.
What do you think I should try next? I'm getting pretty desperate at this point. Is my device bricked-bricked or can i salvage it?
Thanks![/QUOTE]
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
r3dal3rt said:
Hey bern,
Thanks for the reply.
My tablet got really slow so I decided to flash CM 11 M9, which is what I use on my Note 3.
I'm running TWRP 2.6.1.0. Not sure which CROMi I was running because I can't boot into Android. I did a data wipe prior to (attempting to) flashing CM11 and now it boots straight to recovery.
I read that TWRP is not compatible with CM11 and that I should flash CWM. But TWRP fails when I try to flash anything so I'm thinking I should attempt ADB sodeload or terminal command and load that way?
Thanks again
Edit: I downloaded CM11 M9 for tf700. I also tried various nightlies in case my original download was corrupt. It ends in failure
Click to expand...
Click to collapse
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
lj50036 said:
Right now the most important thing is the bootloader version ....
On the bootloader screen upper left there is a bootloader version in really small print ...
This is what we need to know ...
Thx Josh
Click to expand...
Click to collapse
Exactly.
I also would like to know how you performed the wipe you mentioned. The tablet booting only and straight to recovery would indicate that you used 'Wipe Data' from the bootloader???
Also, do not use ROM Manager. It does not work well with the Transformers and can cause a lot of problems.
I have a feeling another user is going to benefit from your excellent unbrick guide, Josh...
Aren't you glad you wrote it?? [emoji12]
lj50036 said:
Can you enter fastboot at all ?
Thx Josh
Click to expand...
Click to collapse
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
No boot to recovery ?
No bootloader ?
No nvflash blob backups ?
If that is the case then you are not looking good ...
There is no way out of this one ...
We need fastboot or recovery one or the other ..
Sorry for the bad news ....
Thx Josh
oh.herro said:
Hi Josh. All i get is the Asus starting screen and "your device is unlocked". Power + vol down doesn't not take me to bootloader.
Click to expand...
Click to collapse
I agree with lj - not looking good. [emoji17]
Do you have adb access when it boots to the Asus splash screen?
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon
Q&A for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Does TWRP 2.8 (latest version 2.8.7.0) okay to start out with? Meaning, if we are at the latest version of stock (ASUS build JOP40D.US_epad-10.6.1.27-5-20130902; Android 4.2.1) and we are going to flash a custom rom for the first time, the latest versions of TWRP won't brick our devices?
It could be that I'm just confused because there were lots of older versions that reference individual Android builds (JB vs ICS). And people would say "if you have X version of Android, use Y version of TWRP or you're gonna brick it".
Can't enter twrp but everything ok
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
I got sent here, so I'll try again.
I'm a little confused now, because I can't understand what is happening to my tablet. Let me explain step by step what I did, maybe one of you can figure out what is wrong.
I was running CM11 M12 with TWRP 2.8.1.0 and wanted to try the new Android 5.1. I decided to go with the latest Omnirom and found out I needed at least TWRP 2.8.5.0.
So first step would be to update TWRP. When I got at the TWRP website I read that there was something new in TWRP 2.8.4.0, so I decided to first go from .1 to .4 and then go to the latest .7. An upgrade to .4 went fine through Fastboot. Then I thought I could try the new in GUI recovery flasher, but I didn't understand it properly so I chose to go safe and flash the .7 through Fastboot.
I guess that's where I went wrong. The tablet went to recovery just fine, but in TWRP it couldn't access anything anymore. "Unable to mount" on everything. Internal storage was 0. It didn't boot to the ROM anymore.
So after some tinkering, not really sure what I did anymore, I got my access to the FS again. I had the CM11 M12 ROM still in the MicroSD, so I ran the "install ROM procedure" for that one and it booted again.
Only now I don't seem to have a recovery anymore. I can get into Fastboot, but when I send the "fastboot -i 0x0b05 flash staging twrp.blob" the tablet hangs itself. Holding power revives it and it boots to CM11M12 again. I tried to flash different TWRP versions (.4 .5 .6 and .7) but no sigar.
Does anyone have an idea how to get my recovery back?
Edit0: I tried to install the TWRP manager from the store and get a recovery from there, but the app doesn't work. It hangs when I try to tap on the "Recovery version to install" option.
Edit1: I followed the link in the post above and solved it. Next thing I did was flashing the .6 TWRP recovery and it stuck. Time to wrestle with some new roms! Thanks!
Edit2: Back to square one. The TWRP can't see anything in my internal storage. Is my storage memory going dry? "Unable to mount ###" shows up for every partition.
Edit3: And now it can see in my internal memory again... Hardware failure?
2.8.7.0 on tf300t reboot/shutdown does not work
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
for me it's the same..
thanks in advance
edy
aoesp3 said:
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
anjeu67 said:
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
Click to expand...
Click to collapse
Nope. I am using lastest TWRP(2.8.7.0) now.
Hello
Can someone help me please?
For the moment i have TWRP 2.8.0.1 and i want to update it to 2.8.7.0.
First of all, i tried to update it with twrp manager.
So i open twrp manger
The install recovery screen opens and i choose for "Install Recovery".
Then i'm redirected to jmz software and then i got next screen:
Forbidden - you don't have permission to access /tf300t/ on this server.
What i'm i doing wrong?
tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
Same here... what gives?
Same here also.
ecb116 said:
Same here... what gives?
Click to expand...
Click to collapse
Same problem here,, no answers?
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.