Before I go reporting this to TWRP, have any other T217S owners tried to upgrade to TWRP 3.1.1 and experienced a boot loop? Reverting back to 3.1.0 fixes the issue for me. Just want to make sure it's not just me. If someone else has the same issue I'll go ahead and report it.
Tried with TWRP itself and via the Play Store app, both experienced the same issue. The download appears to be intact. If you get a boot loop just reflash 3.1.0 and all will be well.
I have I tried to use it today to install lineage 14.1, which has been a frustrating process
Related
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?
I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.
Hey guys,
I apologize if this has been asked and resolved a thousand times already. I've searched through this sub-forum and the threads on it didn't seem to have a solution that worked for me.
The issue: I just recently flashed CM 12 Nightly and Gapps, along with changing recovery from CWM to TWRP. I flashed TWRP via Odin, then installed CM 12 and Gapps via TWRP. I was able to get into CM 12 ONCE and it worked just fine, but when I restarted my phone after the initial flash, it now just constantly boots into TWRP.
To clarify for those that might wonder: I can get into TWRP and download mode just fine. I just...can't get beyond them.
What I've tried: I found these instructions - http://forum.xda-developers.com/showpost.php?p=21301573&postcount=3
However I can't get ADB to find my device as I can't actually boot it into the OS. If I should be going about this a different way then please let me know.
I've also tried reflashing the recovery, reflashing the ROM and Gapps, reflashing my old ROM and Gapps, wiping Dalvik, cache, and data partition (both via TWRP and Odin), pulling the battery and starting as normal, booting into download mode and then rebooting from there.
All of the above has got me no luck so far.
If any of you have any suggestions then I would be very grateful. Cheers.
I managed to get back into my phone by flashing my carrier's stock ROM via Odin, worked a treat.
Time to start again!
Hello,
I've been trying to flash /e/ or carbonOS with no success. I flashed the stock OS (Newest Android 10), booted, configured, and enabled USB debug, rebooted to recovery, booted into twrp (3.3.0), installed twrp, rebooted into the installed twrp; this is where my first problem is, I cannot mount /system. I can wipe it. Once I format everything and try installing either /e/ or CarbonOS; neither boot. Once I reboot out of twrp, I get the error that says there is no OS installed.
I know I'm doing something worng, so any help is appreciated
Is anyone else experiencing this issue? and is there a fix for this issue?
Thanks
Will
xer01ne said:
Hello,
I've been trying to flash /e/ or carbonOS with no success. I flashed the stock OS (Newest Android 10), booted, configured, and enabled USB debug, rebooted to recovery, booted into twrp (3.3.0), installed twrp, rebooted into the installed twrp; this is where my first problem is, I cannot mount /system. I can wipe it. Once I format everything and try installing either /e/ or CarbonOS; neither boot. Once I reboot out of twrp, I get the error that says there is no OS installed.
I know I'm doing something worng, so any help is appreciated
Is anyone else experiencing this issue? and is there a fix for this issue?
Thanks
Will
Click to expand...
Click to collapse
I believe issue is because carbon is for pie not Q.
You'll have to roll back to August pie to flash any of those ROMs. There are no available 10 ROMs yet.
I'm assuming devs are waiting for a TWRP update.
Otherwise we'd see some by now
I have MIUI_XiaomiEU_Stable_10.3.4.0_FIXED installed for a few month. The phone was working but was occasionally restarting spontaneously.
I had this problem also on stock rom.
Today the phone rebooted into twrp recovery and will not boot into system again.
When turned on it boots to twrp. I can als manually get it to boot to fastmode.
I can properly boot to system after I boot into fastboot and do "fastboot boot twrp-3.3.1-dees_troy-daisy.img" .
Any advice on how to fix it ?
What go corrupted ?
Can I fix it by flashing twrp-3.3.1-dees_troy-daisy.img ?
p.s I had the same problem 6 weeks ago. I wiped everything and flashed stock rom using Miflash. I want to avoid it and keep my data if possible.
I'm not sure what's causing the issue, as it might be ROM related, because you said yourself that you had spontaneous reboots on MIUI. But I believe the TWRP you are using might be part of the issue. You should use Offain's version of TWRP found here: https://androidfilehost.com/?a=show&w=files&flid=291011
Use the latest version to avoid bugs. Somehow the 'official' version of TWRP doesn't work properly. Cheers.
Hey guys, I was trying to install Los using TWRP latest version and everything was fine, but when I try to flash Gapps and reboot, instead of boot into system automatically go back to TWRP, someone can help me with this?