Some months ago I was flashing nightly and non stable zip. If you loose AOSP keyboard, Ok. At some point, after IOKP 4.3.1. flash, not beanstalk or even hellkat which I could not install, ALL ROM FAILED, all gapps idem.I only had a backup of IOKP and it isntall. TWRP 2.6.4.0 .img flashed by Odin 1.85 saved me once.
This time I felt unstability over several processes and only gave one order, reboot recovery. It all blaked, samsung in an out
Tried .tar of phielz touch, CMW. TWRP above refered showed itself but whem I thought the backup was over, it seems the OS was missing...
Now after flashing The new version of TWRP for t0lte I got nothing.
I know nothing of programming, code or whatsoever.
If somebody could give some suggestions that can help...:crying:
Related
I rooted my One and installed the latest version of TWRP on it last night and tried to flash CM 10.2 Stable on it. I kept getting the "Failed" message so I went ahead and made a stupid move and wiped EVERYTHING including internal storage. I ADB pushed Gummy ROM and a couple different versions of CM 10.2 but I keep getting "E:Unable to open zip file. Error flashing zip '/sdcard/ROM.zip'" Can someone tell me what I'm doing wrong? It's nearly 11am and I've gotten no sleep trying to find out how to fix this.
EDIT: PROBLEM SOLVED! All of the files I downloaded were corrupted. After redownloading them on a different computer the ROM flashed fine.
Hello,
I want to mess around with WinSuk's great work (and the androidarmv6 team), but I'm a bit lost with recoveries.
I can't check right now, but I think the phone currently has 4EXT, or maybe an old CWM.
I've always used CWM, but I've been trying TWRP on my Moto G for a while and I like it better I think.
Will this TWRP 2.2.2.0 http://forum.xda-developers.com/showthread.php?t=1886046 work?
Do I absolutely need this CWM 6.0.2.8 http://forum.xda-developers.com/showthread.php?t=2474662?
Or is this one http://download.androidarmv6.org/_builds/liberty/recovery-liberty.img more up to date?
Thanks!
Edit:
I have tried all of them, and I cannot seem to install cm-11-20140726-NIGHTLY-liberty.zip
E:Error in /sdcard/cm-11-20140726-NIGHTLY-liberty.zip
(Status 0)
I have wiped and formatted everything before trying, I have also tried with cm-11-20140725-NIGHTLY-liberty.zip, I checked the md5sum both on my disk and on the phone, everything is ok.
It did work once, I think it was with the recovery linked in the thread, but then flashing gapps gave the same error.
Djon_ said:
It did work once, I think it was with the recovery linked in the thread, but then flashing gapps gave the same error.
Click to expand...
Click to collapse
I tried again with everything, and I was able to install the ROM with the recovery from androidarmv6.
But now it gives me the same error for the gapps, complaining about /misc missing in the logs.
Well I finaly did it!
Installed cm-11-20140726-NIGHTLY-liberty.zip with recovery-liberty.img from androidarmv6 and gapps-4.4-tocache-20140605.zip with cwm-6.0.2.8-UNOFFICIAL-liberty.zip.
It's still booting, and I haven't tested TWRP but the thread is more than one year old so I probably won't.
I was only able to flash the CM11 Nightlies using the recovery-liberty.img from androidarmv6.org builds, but as of 9/6/2014 it seems to no longer be there.
I also found that flashing CM11 Nightlies required that version of recovery, but in order to flash gapps, I needed to use 6.0.2.8 from WinSuk, otherwise I would get an error.
Hi there, i'm writing this in hopes of someone reading it who give me some pointers.
i was running for the last years on CM 10.2.1 but i thought it was time for an update. update to CM 11.2 worked but my installed apps were making some weird troubles so i decided to do a factory reset and there my trouble started.
i flashed to boot.img in fastboot, cleared cache with fastboot cmd
format \system, \data, \cache and of course dalvik
flashed rom CM 11.2 (from official cyanogenmod site) via recovery sideload
rebooted and as my thread title says was stuck on CM boot sequence
i tried different CM roms, but always the same result. system wont end the bootup.
i even suspected a problem with CMW v6.0.4.8 and flashed TWRP from the CM 12.1 thread here in the forum.
so in short i can flash boot.img, recovery, different roms but in the end can't get it to work.
i would really appreciate some hints what i could do differently or maybe were i go wrong.
if you need more info i'm happy to supply them to you.
Thanks in advance.
solved by installing a TWRP backup and boot.img what i found on a german android site.
i was also able after that to install CM 12.1 unofficial and its running now. but i'm totally stumped what caused this weird problem to begin with. doesn't really matter now, i'm relieved it worked in the end.
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Swarion said:
Hello i wanted to Flash Lineage Os on my s2 but ran into some problems. I came from omnirom with twrp 2.7.1.0 installed.
So the flash process hung itself up i tried again and it didnt work.
Well i suppose the bootloader is unlocked cause i flashed omnirom right.
Since i already deleted omnirom i cant check now with the dialpad.
So I thought about updating twrp but since its not after 2.8.4 i cant flash .img files.
I would prefer to flash it without heimdall cause i have only strangely configured computers available.
So I tried to flash twrp 3.0. 4 or something like this which I found as a zip file the installation runs just fine says it was successful but after rebooting to recovery it is 2.7 again.
I dont necessarily want to update twrp if i can flash lineage but i guess i have to?
Are there any recommendations for a lost soul.
All the best
Sorry for the false place for this maybe someone can move it to the right spaxe thx
Click to expand...
Click to collapse
Please follow one of the guides available, like this one, or the one in my signature.
You have to be aware that twrp 3 requires kernel isorec support, so you must have a kernel that supports isorec, and also you must have a 1GB system partition to be able to install any nogut or mm rom.
thank you so much managed to find this guide before you answered.
anyway thanks so much my s2 is running lineage smoothly and now we saved some piece of electronics of garbage to early the planet and me are thanking you so much for every one having the same problem as me go with philz touch recovery and then flash the twrp you want from there
all the best
Help!
I'm trying out a series of ROMs and now am faced with a puzzle. After wiping CM13 (system and all), I'm trying to flash an @amaces AOSP Marshmallow build, but TWRP is giving me grief saying it can't flash an older OS over a newer one.
It says the previous CM13 OS was dated 2017 (I don't think so....) while the one I am trying to flash is dated 2016 (yes, the @amaces ROM was posted in 2016).
So...I thought I had truly wiped the system. How can it know anything about a "previous" ROM?
Edit: Ugh. So I think this is because the CM12 and CM13 ROMs changed the partition table? Or they changed something and I need to get back to stock. Unfortunately my stock backup is gone (8gb). I've looked at all the various restores and they rely on files that no longer exist or are behind so many layers of pop-ups and -unders that it doesn't seem safe to wait and hope the download will eventually start. Succulent has a series of flashable zips to "restore" a tablet to stock, but if there has been a partition change, will his zips fix that?! I have the nooktablet_1_4_3_update.zip, but have no idea if that is even useful. It certainly can't be flashed with CWM or TWRP.
Edit-Edit: OK, I learned something(s). Apparently the issue was the version of TWRP I was using. I tried an older version and I was able to flash one of @amaces ROMs, but I also did manage to take the tablet back to stock using nooktablet_1_4_3_update.zip. It turns out that you can't flash that successfully with TWRP--at least not the versions I had. But I did have CWM 6.0.5.1 from succulent as altboot on my SD card. That was able to flash the zip and restore to stock. Good to know since everything else is gone. And, yes this time I also made a CWM stock backup and put it somewhere safe