Hello,
I installed cm 11 using cyanogenmod installer.
I have had a lot of problems with recovery since I installed rom manager and CWM.
When the phone said there was a system update, it couldn't install it because of CWM.
However, after finally re-installing TWRP successfully, it couldn't install the update. It said something about it bot finding the md5.
Here us the recovery log.
I would really like to know what is happening.
Thanks in advance.
Related
I was on ViperX 3.2 this morning and I got the OTA update message, so I downloaded and installed 3.2.1, 3.2.2, 3.2.3 in succession. Problem occurred when I got the 4th message. Selected install now. Aroma installer said it was flashing ViperX 3.2.1. Rebooted and got the same 3.2.4 update available message. I check system and apparently it didn't update. So I try installing the zip from ROM manager manually, that didn't work, installs 3.2.1 again. Tried booting into recovery, installs 3.2.1 without even going to recov. (I just get the Team Win window and then couple of lines of md5 checksum not found, etc and then straight to aroma) Went to the bootloader, flashed TWRP again, booted into recov again and same thing. What's going on here? Anyone else facing this issue? Can't seem to find anything online.
When you installed an ota you have to delete it from the download folder on the sdcard
Mr Hofs said:
When you installed an ota you have to delete it from the download folder on the sdcard
Click to expand...
Click to collapse
Aff, didn't know that. Thanks!
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
tenpin416 said:
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
Click to expand...
Click to collapse
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
DMF1977 said:
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
Click to expand...
Click to collapse
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
tenpin416 said:
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
Click to expand...
Click to collapse
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
DMF1977 said:
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
Click to expand...
Click to collapse
After doing some reading I think the abort is caused by having the older ics bootlaoder.ive never had to update one before so im a bit hesitant. ..do you know if I update and try to switch back to my original restore or to a different rom (other than cm 10) Will I have to change the bootloader back again or will I run into a greater chance of problems in the future?
Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards
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 had a couple questions regarding rooting the opportunity Find 7a. First off I have ColorOS v 2.1.5i and everytime I try to install TWRP onto it nothing happens, even though the computer says it has been flashed successfully. I restart my phone into recovery mode and the oppo recovery is still there. You guys have any ideas?
Also when I had the older version of colorOS, I could install TWRP but then SuperSU would never work. It kept saying the binaries weren't installed properly. Any ideas on that ?
Your guys help would be appreciated since I really wna root this phone
Thanks
Try fastboot boot nameofrecovery.img it should boot directly into twrp then
I couldn't root my phone in Color Os 2.0.8i untill i reflashed the rom and installed latest twrp then it asked me for root and i pressed ok.
Yea I tried what jthatch12 told me do and it worked and superSu finally installed properly