I have installed latest carbon rom on my device. (d5803 z3c) I installed twrp and when i downloaded rom installer it asked which recovery i had, i put twrp.....downloaded gapps and boot into recovery, but when i went to recovery it was cyogen one so i didnt carry on.
also when i downgraded firmware to 4.4.4 when i installed the carbon rom its now 5.1 or something so would the gapps for 4.4.4 still work ?
Just taking a while to get my head round all this has i aint messed about with phones for a couple of years so abit rusty now.
Related
Where can i download the latest CWM Recovery for CM12?
I just finished installing Official Cyanogenmod 12 (CM12) but i just realised i can't get into recovery coming from CM11 there must be a new version kicking around somewhere for CM12 for Xperia Z1, Iv'e tried searching on Google and XDA but i can't find a compatible CWM recovery to install to work as i know there compatibility issues...i'm on 5.02 Lollipop CM12 so i dunno what version of CMW recovery to try as it seems folk online like to say things are indeed the latest just to get views and hits by downloading there crapware
I hope someone here can help
there is no CWM but there are images to flash to get TWRP or Phil-Z (CWM with touch control)
http://forum.xda-developers.com/xperia-z1/general/recovery-solution-lollypop-roms-t3000822
need help
i don't know what i
should do.
So my Problem is I'm getting a wrong recovery when I reboot to it. It's
not the one I had before. My previos recovery was twrp . i flashed the
newest validus Rom for xperia z and it worked( lollipop). But i noticed a bug so i
wanted to get back but it didn't worked because the recovery was
gone. So i tried to install one via some apps .it didn't worked . I only got
a recovery with stock options nothing else. Then I flashed back to
stock 4.4.2 and from that to cm 11 with lightning kernel ( lightning
kernel has twrp which is the one which used before).It worked out fine
but then i tried to flash the resurretion remix it worked but as i wanted
to Boot into twrp to flash Google apps i couldn't because this
cyanogen mod recovery was there again, out oft nowhere . i searched
for hours but couldn't find a solution. How do i get rid oft this recovery
and can get the Team win recovery back on lollipop.
Help would be very appreciated.( sorry for gramma errors, english is
not my mothertongue,i know it's anoying to read that all the time )
Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....
Anyone?
my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere
Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use
Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then
Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.
Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.
Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.
I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good: