I originally used TWRP 2.8.4 to backup stock and flash CM12/gapps.. I've had issues using 2.8.4 to push files (permission denied errors). I went back to 2.8.3 and problems went away.
My question is, should recoveries work fine in 2.8.3 with backups made with 2.8.4?
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.
I used twrp 2.8.7 recovery to do backup. It keeps failing with error 255. I used superSu 2.52 Beta.
Any cure for it.
Copy & paste from the TWRP thread:
I have a weird issue and need some serious help. I flashed TWRP 3.0.0.1 last night via ODIN and my ROM wouldn't boot anymore. It gets to the boot animation screen then goes on forever. I tried fixing it by going to the TWRP version I was using before but I still faced the same issue and tried 3.0.0.0 as well and it still happens.
I am actually using a T-Mobile Marshmallow ROM and did the adoptable storage feature so that's what I'm assuming caused the issues since I couldn't unmount it before the problem popped up so I reformatted with it still in the system. Using a TMO rom with the ATT recovery worked previously so I don't think that's the problem. I also tried the CAN recovery and the TMO recovery and nope.
I also full factory wipe + wiping system + data + cache but didn't fix it as well. Some roms work like DN4 but I would rather go back to the rom I was using previously.
Anyone know what's up and how to fix this problem?
Biff corrected the issue in version 3.0.0.1....g
https://dl.twrp.me/t0lteatt/
3.0.0.1 bootloops for me too, I just flashed 2.8.7.0 instead while I wait for an update
I found out that 3.0.0-1 is 8.5M in size, making it too big to be flashed into Recovery. I had to flash 3.0.0-0 since it was 8M.
What I noticed with Version 3.0.0.1 is that it wipes out the modem as well when you do a wipe.
The reason Why, I tried it and got a Boot-loop, so I went back to 3.0.0.0 and it boot loops until I re flashed the modem.
I then Tested it again, same thing, so I went to Philz Touch Recovery and still boot-looped until I flashed the modem again.
I could be wrong, but that is what I noticed.
I am very happy to use 3.2.4 but suddenly i flash 3.5.2 and flash twrp(may be this twrp only made for 3.5.2)
But when i restore my old 3.2.4 backup... my twrp gone and nothings comes??
but i rooted my phone via Toolkit2.5
so i want to back 3.2.4 ..
anyone give me a guide??
cz 3.5.2 twrp give me lots of pain.. full of bugs... after flash rom reboot not work .. and many more...
Nilshalok said:
I am very happy to use 3.2.4 but suddenly i flash 3.5.2 and flash twrp(may be this twrp only made for 3.5.2)
But when i restore my old 3.2.4 backup... my twrp gone and nothings comes??
but i rooted my phone via Toolkit2.5
so i want to back 3.2.4 ..
anyone give me a guide??
cz 3.5.2 twrp give me lots of pain.. full of bugs... after flash rom reboot not work .. and many more...
Click to expand...
Click to collapse
I'm not sure if this is considered the proper way to do it, but this is what i did to fix the same issue you had. I was previously on FreedomOS running 3.2.4, of which i had a nandroid backup of. Also, it should be noted that you'll need a working ADB setup on your desktop for this to work.
Download the following files to your computer:
TWRP 3.0.2-1 from the twrp website at: https://dl.twrp.me/oneplus3/twrp-3.0.2-1-oneplus3.img.html
TWRP 3.0.2-19 (the one that supports flashing 3.5.2)
Stock OxygenOS 3.2.4 ROM from OnePlus at: http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.4/
Once you have all that downloaded, open a command prompt and go to whatever directory you have the TWRP images downloaded in. Reboot your phone into fastboot, and connect it to your computer. Run the following command to boot into TWRP:
fastboot boot (whatever the TWRP 3.0.2-19 version is named).img
This should boot you into TWRP recovery. Transfer the TWRP 3.0.2-1 image that you downloaded from the TWRP website to the phone as well as the stock OxygenOS 3.2.4 zip. Do a wipe of everything but the internal data, just like you would when doing a clean install of a ROM. Install the stock Oxygen OS 3.2.4 ROM. Immediately after that, flash the TWRP 3.0.2-1 image (you can do this in TWRP by going to Install-->install image, and then select the img file of the TWRP 3.0.2-1 img that you transferred earlier). This will flash the recovery. Reboot the phone and you should be able to go directly into the 3.0.2-1 recovery like normal. Inside there, restore your existing nandroid back, reboot.
Nilshalok said:
But when i restore my old 3.2.4 backup... my twrp gone and nothings comes??
but i rooted my phone via Toolkit2.5 so i want to back 3.2.4 ..
Click to expand...
Click to collapse
it is NOT WORKING - they are working on a fix for it hopefully soon
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
I have two questions. What is causing this problem? And second, any way I can use fastboot to downgrade firmware 3.2.6, so that I can at least access my internal storage and back it up. I got loads of data in there.
Djalaal said:
I haven't had any software update for about 1.5 months. I was on Resurrect Remix ROM Nougat, firmware 3.2.6, and on TWRP 3.0.1 (or 3.0.0 I'm not too sure). Today I tried updating. Things went wrong. Here are my steps:
1. Wiped everything except internal storage.
2. Updated recovery to twrp-3.0.2-1.28 within recovery itself. Used the file given on the ROM thread https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-m-t3399960?nocache=1.
3. TWRP couldn't decrypt my phone even with the right password.
4. Downgraded TWRP back to 3.0.1. Decryption worked.
5. Updated firmware & modem to version 4 within recovery. Used the files given on the same ROM thread.
6. Updated recovery again to twrp-3.0.2-1.28, this time via fastboot.
7. TWRP couldn't decrypt. Tried trwp 3.0.3 from the official twrp site as well. Same problem.
8. Downgraded TWRP back to 3.0.1. Recovery didn't even start. Phone freezes.
Hi I made that too with this rom! (https://forum.xda-developers.com/oneplus-3/development/rom-resurrection-remix-5-8-0-oms-t3527344) I think it is that 3.0.3 TWRP that did it! I hawe to wipe everything but i got it working! with these instruction https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ Method 2 worked for me but it wipes all! there seemed to be instructions for not loosing all but i cant test it
Click to expand...
Click to collapse
I have found a solution. Even without decrypting /data, you can still get into recovery (except you can't read your data partition). This is key. What I did is simply use recovery sideload to flash the old 3.2.6 firmware (apparently flashing works even without decryption), use fastboot to flash twrp 3.0.1, and backup all my data to the computer via mtp. Then I completely wiped everything, flashed the new firmware and recovery, and decryption worked.