Related
I have a rooted (Superuser 3.1.3) TF101 with TWRP 2.7.0.1. I HAD Katkiss 4.3 installed. One day the tablet locked up and then starting bootlooping. I went into recovery, wiped everything, did factory reset, format /system.
Then I tried to reflash Katkiss 4.3_020, it failed with "set_perm: some changes failed". I then tried katkiss 4.4.2_023c - it failed with a similar error message. Tried flashing stock (US_epad-user-9.2.1.27) - same thing. The first part of the error message for all three ROMs is the same set_perm failure. The next couple of lines gives different error messages depending on the ROM. Generally something like: "E: error executing updater binary in zip".
Now I have a tablet with no ROM on it (when I tried to boot it hangs at the ASUS screen). I can get into the TWRP recovery menu just fine - I can flash other things like superuser or gapps without error. But any ROM I try to flash gives the set_perm error.
Any thoughts?
Chris
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Thanks but...
Easyflasher doesn't seem to work for me anymore (odd because it is what I first used to root/update my TF101). It runs and declares success - but nothing gets pushed to my device. Tried both SBK1 and SBK2. Using universal naked 0.72 and 0.73 on win7 64 bit.
I tried to find an older version of TWRP like you suggested - but I couldn't. Seems they want you to use "goo manager" from the play store... which doesn't work for me since I can't boot... And the goo website doesn't list an older TWRP for my device.
In any case, the latest TWRP seems to work in every other respect. I read somewhere that superuser can set an "immutable" bit that can survive a wipe? If true - could that be my permissions problem?
Chris
stuck on load screen
*Detection* said:
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Click to expand...
Click to collapse
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
ldwhyte said:
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Click to expand...
Click to collapse
ChrisG12 said:
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
Click to expand...
Click to collapse
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
ldwhyte said:
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Click to expand...
Click to collapse
Ok - back to my problem - I installed a new recovery and get the same error. The two recoveries I have tried are TWRP (2.3 and 2.7.0.1) and cwm-6.0.2.1-notouch-hybrid. Both seem to work fine (and I had no trouble previously with my device running TWRP and Katkiss 4.3).
After a crash I needed to reinstall a ROM. I've copied four ROMs to my sdcard (Katkiss 4.3, Katkiss 4.4.2, Omni 4.4.2, and stock asus). I've tried all 4 ROMs with both recoveries. I get the same error when I try to install the zips. Usually it is "set_perm: some changes failed". Though stock asus zip fails with a different message "Assert failed: package_extract_file(“blob”, “/tmp/blob”)".
Any ideas on what is keeping a recovery from installing the zip? Note they can install other zips fine (i.e. other recoveries, superuser, gapps, etc.). But not the ROM.
ChrisG12 said:
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
Click to expand...
Click to collapse
No it's not, but I can't get anything onto the SD card, only the ext card and I CWM will not mount it to flash from. if I'm missing something and I sure I am, Im greatful for any help, and thanks again..
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
You could have an faulty emmc firmware or your emmc reached end of life.
You are from europe? I know someone who can fix it for you.
You can also read the faq on my github userpage for more information about your bug.
kozyn said:
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
Click to expand...
Click to collapse
Once I had same problem with Motorola xoom and guess what was realy the problem. It was the external SD memory remove it then flash the stock rom.. If problem persists see with Andi
Thank you for your response. To me it also seems like faulty emmc. I have check the frequently asked questions on your blog and the description there exactly matches with what I'm experiencing on my device. Yes I am from Europe, Czech Republic. I have already tried to get in touch with two people who have the proper tooling to flash the firmware (JTAG). Hope I get some response fast and the solution is going to work. Still if you have someone in the CZ that you can recommend I'm grateful for any advice.
@zidane: All of the above steps where performed without external SD card.
kozyn said:
@zidane: All of the above steps where performed without external SD card.
Click to expand...
Click to collapse
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
zidane01 said:
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
Click to expand...
Click to collapse
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
kozyn said:
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
Click to expand...
Click to collapse
sounds like that you have a faulty emmc. same what android-andi said.
@kozyn Hi buddy.. have the same thing on a p5110 -- emmc is in read only mode and I can't seem to PM Andi for some contacts.
Can you help me recover this galaxy tab2 pls? Appreciate your time
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.
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude