Hello,
I would appreciate help, please.
I have been with cyanogenmod for about 18 months, I was using a recent nightly for CM10.2 (11th January I think) . On a whim, I thought I might have a peek at Omnirom to see what the KitKat fuss was about.
I downloaded the necessaries (correct nightly rom, correct gapps, supersu), made a backup, did the wipes and installed the zips.
However, omnirom gets stuck in a bootloop. No worries, I've been here before, do a battery pull, reboot into recovery and do a recovery.
My problem is that rebooting into recovery gives me twrp, not cwm, and there's no way to restore my backup. I can enter download mode.
I assume I now need to use Odin to somehow reflash cwm to allow me access my backup and do a restore. The backup exists on my external sdcard01.
If someone can either explain or direct me to the appropriate instructions, I would be really grateful.
Thanks in advance.
Ok, think I've fixed it. I'll leave this explanation in case anyone does the same daft thing.
Odin will indeed flash cwm over twrp, so that's what i did.
From there, simple case of restoring the backup from sdcard.
Panic over.
Don't know if twrp supports it but is something like an USB mode available? If so you could copy a kernel with cwm over and flash it. Otherwise you have to use odin as far as i know.
Sent from my GT-I9100 using xda app-developers app
The twrp was included in the omni kernel. If you want to restore next time back then just download a kernel like kitkat compatible kernel with cwm and flash it with recovery. If you want to do it harder and more dangerous and you dont have a kitkat backup then flash siyah kernel.tar with odin.
Kk backup need kk compatible kernel i believe.
Twrp has usb support. But i suggest for everyone always have an sd card or internal storage with some kernels and roms so if you screw up and you dont have a pc at the moment then you can always flash some older one and download the rom you want and flash again.
Verstuurd vanaf mijn GT-I9100 met Tapatalk
Related
Hello,
I got some strange errors:
When doing a backup with cwm recovery 4.0.1.4/5 some or all apps stored in .android_secure get deleted and i have to restore them with Titanium Backup!
And I've noticed, that the old cwm 4.0.0.2 gets opened when booting to recovery via rom manager (and pressing volume/home buttons)!
(Even manual installing the new recovery won't change this, except that with 4.0.0.2 backups work)
Why is the old recovery always restored? Oo
I'm running newest villian rom with that nymphentamine kernel in version 2.0.0.5
I came from villian rom 2.1 with the cf-root 4.1 kg3 kernel installed, but did a full wipe!
Hope you could understand my problem, my English isn't the best :-(
//EDIT:
Even flashing kernel with odin won't fix my problem!
Another try to explain my problem:
I flash a new cmw version with rom manager (or odin or video the old 4.0.0.2 cwm) and as soon as i restart the device the old recovery gets restored and i don't know why! there is no update.zip or something wich could install the old recovery again!
Please help me, i'm getting mad with this!
Sent from my GT-I9100 using Tapatalk
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
radici said:
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
Click to expand...
Click to collapse
Tell people who you fixed it FFS!
how did you fixed ?
radici said:
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
Click to expand...
Click to collapse
Please help , I'm having exactly the same issue.
OS is booting correctly, but I'm not able to enter in any recovery mode, neither in CWM or TWRP..: confused:
radici said:
FIXED, NM.
Click to expand...
Click to collapse
These forums become useless if the knowledge is not captured. It is awesome that you fixed it, but please let us know briefly HOW you fixed it!!
sparkdroid said:
These forums become useless if the knowledge is not captured. It is awesome that you fixed it, but please let us know briefly HOW you fixed it!!
Click to expand...
Click to collapse
Same issue here too' please share how you fixed it.
Hi all, I'm looking forward to your help. Current state of my phone is a bootloop straight into TWRP with failed installs of Kitkat/gapps and failed restore of my backup. Here's a step by step of what I've done.
1. Opened Goomanager, updated TWRP using the button (current version 2.6.3.0)
2. Downloaded AOKP kitkat nightly and pa gapps - download completes and MD5 hashes check out
3. Used goomanager "flash zips" interface to attempt flash, with factory reset option and backup option selected
4. Came back to find my phone stuck at TWRP with failed flash
5. Tried to flash again manually, using the standard TWRP flashing page
6. Failed again.
7. Decided to cut my losses and restore the backup created when I first attempted to flash via Goomanager
8. Restore fails.
9. Phone fails to load system, reverts into TWRP when it fails.
10. So now I can't restore my old android system and I can't flash a fresh one.
Where do I go from here? Is my version of TWRP dodgy and giving bad flashes? Should I downgrade it via adb? My phone was fine until an hour ago, so I don't think it's a hardware issue. Many thanks for your help. Tom
Did you try to flash a stock rom via Odin (in case you can get to dl mode) or via recovery (you need to get a flashable stock rom for that). I have not experience with twrp though, maybe you could also try philz recovery (I think I read somewhere that kitkat had problems with twrp).
Sent from my GT-I9300 using xda app-developers app
Twrp let me recover my backup after I pulled the battery rather than just use twrps reboot option. So at least I have a functioning phone now. Odin was always my last resort, but I have a mac so finding someone's pc to use is a bit annoying/embarrassing. I'm going to try re-downloading the kitkat rom and see if that fixes it, but it seems unlikely considering it passed an MD5 check after download. Thanks for taking the time to reply.
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Tom-Tom07 said:
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Click to expand...
Click to collapse
thats what I read as well. the Slim team for instance recommends Philz and not TWRP if I am not wrong
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..
Hi all
How exciting it is to see that so many people are so involved in improving or fixing their mobile devices.
I got some sort of a virus on my Samsung Galaxy S3 so decided to try to wipe it clean and load a more up-to-date version of Android on it. It had 4.3.?. On a Windows 7 PC, I downloaded the Skipsoft Unified Android Toolkit (version 1.4.5). I think now I didn't need to but probably succeeded in rooting my S3 with Kingo ROOT.
Next, using the toolkit and Odin, I think I succeeded in flashing the recovery-twrp-2.7.1.0-i9300.tar custom recovery.
My phone would only boot up with the stock Android.
I took me a while before I learnt about entering the recovery mode by holding the volume up, home and power-on buttons simulateously.
In the recovery mode, I used Wipe, Advanced, ticked all of the boxes and wiped everything on the phone.
Then, using the toolkit and Odin again, I flashed the same recovery-twrp-2.7.1.0-i9300.tar custom recovery I'd flashed before.
I still can't boot my phone. If I choose Reboot from twrp (v2.7.1.0) and then either System or Recovery, I just get, "No OS installed! Are you sure you wish to reboot?"
I can still enter either download or recovery modes but the latter is something of a hit and miss affair.
Using File Manager in the twrp I can see lots of files and directories so guess I managed to flash something.
Also, using Terminal Command I see that my prompt is a "#"so think I'm still rooted.
I know something about Unix and programming mainframe computers but am not an expert with mobile devices. I'd be so grateful if someone could please advise me as to what to do?
Mike
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Haha yes^ this guy is right
You might have to flash stock rom if you somehow wiped efs, most of the time custom roms doesn't include efs with them
Turga said:
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Click to expand...
Click to collapse
Thanks for your response, Turga and snkmv, below. I didn't know what efs was so looked it up on the net and found this worrying but expert explanation from ryanrazer and Rukbat in androidcentral ( http://forums.androidcentral.com/as...erstanding-cwm-backups-efs-partition-etc.html )
In twrp's recovery mode on my phone and using File Manager, I see that the directory /efs is empty (all files are shown in File Manager, right, including invisible files?)
I'd prefer to try to flash a custom ROM which includes efs rather than the stock ROM. Do Temasek or CM13 include efs or does another, reliable custom ROM?
Thanks again folks
Mike