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.
Related
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:
Hey All,
Yesterday I started looking at flashing a custom ROM onto my Galaxy Mega (I9205) but I'm having real issues. I've tried multiple ROMs and recoveries and I run into errors every time. Hopefully I'm being a moron and have missed a step somewhere but I really don't think that's the case. I've trawled these forums to see if I can work out why this might be happening but with no luck.
The procedure I've used so far:
Use ODIN to flash custom recovery (tried both CWM and TWRP from http://forum.xda-developers.com/showthread.php?t=2369998)
Factory Reset, clear cache and dalvik cache.
Install ROM from recovery (I've tried PAC-man, CyanogenMod and LiquidSmooth.)
Errors have ranged from generic failures to "incorrect device" type messages and "Status 7".
A curious issue I ran into was with PAC-man. When I tried to flash the meliusltexx version, the install script detected my device as the melius3g. I can say categorically that my device is the I9205 NOT the I9200. I removed the assert section from the updater script and although the script now runs, it fails later in the process.
I've attached a log from the last attempt I made. This was using TWRP to flash pac_meliusltexx-nightly-20140306.
Thanks for any advice in advance.
I'm not the best at helping at problems, but I give it a try.
I noticed you used the TWRP from a pretty outdated thread.
Silesh.Nair has a few download links in his signature, which leads to the most updated recovery.
Also Philz Recovery (the one I use the most) has a separate thread.
Have you tried those recoveries too? Maybe you should flash them through odin first, and then install the roms.
Brilliant that did it. Used Philz recovery and ROMs are now installing correctly. Where do you find info on things such as the latest recoveries? I've been searching and the most up to date I came up with were the ones mentioned in the original post.
Thanks a lot for your help - glad it turned out to be something simple.
demented_goose said:
Brilliant that did it. Used Philz recovery and ROMs are now installing correctly. Where do you find info on things such as the latest recoveries? I've been searching and the most up to date I came up with were the ones mentioned in the original post.
Thanks a lot for your help - glad it turned out to be something simple.
Click to expand...
Click to collapse
We are here to help. Glad I helped! I had the same problem, and I found Philz recovery the original development (Philz Recovery Have fun with flashing, and don't forget:
We are here to help you
I was just on the MJ9 firmware had no problem flashing other roms using TWRP. I read that TWRP was having issues flashing ND7 and seen that using Philz was the best thing to use, so I downloaded Philz and saved it, uploaded it to my external SD card along with the other required files for ND7. Rebooted to the recovery formatted the internal storage,dalvik and cache. First thing I did was try to install Philz. I instantly got failed and this message "assert failed: getprop (ro.product.device") I thought it had something to do with the Kitkat update. But, then I read on the forum that one user was having trouble installing Philz also and the user installed the ND7 first then Philz and it installed. So, I decided to try that. The update installed just fine but Philz still gave me the same error. I decided to try to install the radio that gave me the same error. I already had Liquid smooth 4.4 downloaded on my SD card and that wouldn't flash either but the gapps installed. I have installed the newest version of TWRP still no luck. I can't even use Airdroid to transfer to either SD card or internal storage (Later found out its an app problem). What else can I do to get the ball rolling?
DCVR 614 said:
I was just on the MJ9 firmware had no problem flashing other roms using TWRP. I read that TWRP was having issues flashing ND7 and seen that using Philz was the best thing to use, so I downloaded Philz and saved it, uploaded it to my external SD card along with the other required files for ND7. Rebooted to the recovery formatted the internal storage,dalvik and cache. First thing I did was try to install Philz. I instantly got failed and this message "assert failed: getprop (ro.product.device") I thought it had something to do with the Kitkat update. But, then I read on the forum that one user was having trouble installing Philz also and the user installed the ND7 first then Philz and it installed. So, I decided to try that. The update installed just fine but Philz still gave me the same error. I decided to try to install the radio that gave me the same error. I already had Liquid smooth 4.4 downloaded on my SD card and that wouldn't flash either but the gapps installed. I have installed the newest version of TWRP still no luck. I can't even use Airdroid to transfer to either SD card or internal storage (Later found out its an app problem). What else can I do to get the ball rolling?
Click to expand...
Click to collapse
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
gr8nole said:
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
Click to expand...
Click to collapse
That installed and worked. The ND7 Radio also installed. How do I fix the getprop asserts?
gr8nole said:
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
Click to expand...
Click to collapse
Okay, I got liquid smooth installed along with the gapps. Thank you for all your help. What can I do to get this get props corrected?
DCVR 614 said:
Okay, I got liquid smooth installed along with the gapps. Thank you for all your help. What can I do to get this get props corrected?
Click to expand...
Click to collapse
It is already fixed now that you have a proper i605 recovery installed.
Sent from my SCH-I605
gr8nole said:
It is already fixed now that you have a proper i605 recovery installed.
Sent from my SCH-I605
Click to expand...
Click to collapse
OH! Thank you so much. I appreciate your help!
I know this has been mentioned elsewhere for other Xperia Models, typically newer than the Z U, but I am running in to an issue where my two z ultras are trying to use the same mac address.
I wondered if there was a device specific work around for the z ultra and / if this is being addressed.
Running the latest nightly CM12 builds.
Cheers in advance.
http://d-h.st/agR
Download this zip and flash, it is a fix for when the mac address changes after flashing a custom rom.
Regards
Hi,
Thanks for the post, but unfortunately I am getting a package verification error and a footer error when I attempt to flash the package in recovery.
You are using cyanogenmod recovery, right? If so, you have to use TWRP or CWM to flash it, cm recovery have signature check and you can't turn it off, all custom recoveries have it disabled by default.
Regards
Thanks for the heads up teddy. I was using CM recovery. Installed TWRP and flashed the zip/update. However, CM12 goes tits up with TWRP every time I update CM12 and only seems to play nice with CM recovery. Gapps seems to be the issue with none stop force stops. Seems in order for this to work I have to flash TWRP, flash the mac address zip and then flash CM recovery back every time I want to update via nightly.
You can flash TWRP to the FOTAKernel partition if you don't want to flash it everytime you update rom and if you flash it, it should work like CM recovery and it will be booting instead of CM recovery. Just download an app called Rashr and install TWRP from the app I assume the fix is working for you, isn't it?
Regards
I did use rashr to install TWRP and that's when the issues arose.
Unfortunately the nightly update came through after installing TWRP so I did the update for 30th and the phone was in an unusable state via gapps force closes as mentioned. So I flashed back to CMr via the update and haven't installed the update yet.
Until I have a workable solution to the recovery issue I won't be proceeding. It will be too much hassle each time the updates arrive.
I don't think that gapps are force closing because of the recovery installed, that would be weird. Have you tried flashing another gapps? Because I have also used CM12 with TWRP and gapps and I haven't got that sort of problems, even now I am using CyanideL (CM12-based) with TWRP and on my configuration it is OK. I will try using CM12 nightlies with TWRP tomorrow and I will write you back if I found a solution
Regards
Yes, I was using the signed gapps dated late last year, but when I came across the issue I reflashed the whole of CM12 with the more recent ones dated April I think. I still had the same problem, which is when I read up and saw it was attributed to using a non-CM recovery and reset everything back to CM12 nightly + CMr, I did however keep the most recent gapps. Let me know how you get on.
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