THERE WERE AT LEAST TWO REPORTS OF SYSTEM FAILURE AFTER THIS UPDATE, BOTH HAD LAGFIX ENABLED.
!!!BACKUP BEFORE PROCEED!!!
This guide is to help those who would like to test tegrak's kernel but have dowbts about losing ability to flash zip files from CWM. This will also help those who would like to have simple root solution, and 2e recovery on froyo.
a) If you want to have simple root solution, one click lagfix and 2e recovery. Tested with Doc's v9.1.4 but should work on any rom including stock
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market and install root from the app's menu
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
a) If you already rooted your phone
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
All this process replaces your 3e recovery with 2e recovery image and as tegrak's kernel does not overrides original recovery image your CWM will be untouched by tegrak's kernel, and you will successfully have combination of two recoveries (CWM and Tegrak's) To access CWM you can chose "reboot in recovery" from the Rom Manager menu or from Tegrak lagfix menu, and to access tegrak's recovery, press home button when you see tegrak's kernel introductory window while booting up your phone.
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
g00ndu said:
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think it's too advanced and dangerous for novices that mostly visit general. Also both described things 2e recovery and tegrak's kernel are from the area of development, this is all about customizing rom. I dont agree that it should be in general.
Thanks a lot!!
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
hensk said:
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
Click to expand...
Click to collapse
As I understand this fix didn't work for you, could you share to others what and how has failed?
Sent from my GT-I9000
no, no mate, just did not know that there is
thread like this,with fix solution
hensk said:
no, no mate, just did not know that there is
thread like this,with fix solution
Click to expand...
Click to collapse
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
brack11 said:
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
Click to expand...
Click to collapse
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
g00ndu said:
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
brack11 said:
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
Click to expand...
Click to collapse
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
g00ndu said:
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
brack11 said:
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
Click to expand...
Click to collapse
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
g00ndu said:
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
Click to expand...
Click to collapse
Yes, I used a few times to flash different modems and r64 theme.
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
fomofo said:
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
Click to expand...
Click to collapse
Did you have lagfix enabled? As I can say from my own experience.now - this hack is DANGEROS if you have lagfix enabled. To say more any manipulations with recovery while on onenand fix - DANGEROUS AND LEAD TO LOOSING ALL PARTITIONS
Sent from my GT-I9000
brack11 said:
Did you have lagfix enabled?
Click to expand...
Click to collapse
No, I have used the "hack" recovery 2e method with success right up until JPY, but JS3, and now JS5 does not work.
It seems to me (just learning Android), that it doesn't have write permissions to the /sbin directory, which is what the recovery script needs.
Recovery 2e works with CF-root, but I already have root, and rather not overwrite the stock kernel.
Ok, yesterday I have thoroughly tested my workarounnd for installing rom. I hade Doc's 9.6 downloaded 9.8 reboot into recovery using rommanager option, wiped cach partition, wiped dalvik, wiped data, flashed 9.8, wiped data again, and flashed again, rebooted, restored titanium backups, flashed tegrak's kernel, flashed update for recovery 2e from within tegrak's kernel, then rebooted into 2e recovery, flashed new modem (JVE) and flashed theme r64, rebooted, everything works as it should no errors no hangs no loops.
Does this still work?
Related
I fixed recovery for the Continuum users so that you have your own button mappings. It isn't integrated into the kernel yet, but I'm going to attempt to get that fully working (I have it partially working atm). Until that is fixed, you get the update.zip method for CWM. So, to accomplish this, you'll need to download two things. First, you need the update.zip file, which is placed on the root of the SDCard (/sdcard/update.zip) and the second item is the recovery kernel, which is flashed via Odin (v1.3). It is now integrated into the kernel and it has been updated to the EC09 kernel. This package will flash both recovery and kernel (so you don't loose CWM when the system boots). Note that if you are still on DL17, you should use the archive packages below. What you will need is this file, and you will want to flash it via Odin (or extract it and use Heimdall).
Open Odin, click the PDA button and browse to and select the continuum_recovery.tar.md5 I400_CWM.tar.md5 file that you downloaded. Remove the battery from your phone, and hold down the volume down button while plugging in the USB cable that is attached to your computer. Make sure you have the drivers installed, if not, you'll need to install them before you continue. Flash the file by clicking start if the phone is detected in Odin. Once it completes successfully, all you need to do is boot to recovery and apply sdcard/update.zip and you'll be in CWM. I decided upon black background with cyan text. This can still be changed if you wish, but I like it
Here are your button mappings:
Camera button/Grip sensor - Select Item (applies to cwm and stock recovery)
Volume Up/Down - Scroll up/down in the list (applies to cwm and stock recovery)
Power Button - Select Item
Menu Button - Does nothing
Home Button - Go Back
Back Button - Go Back
Search Button - Hide Text
I'm still trying to figure out how to get buttons to show up for the touchkeys. For now, they're blank, so just press in the approximate location on the screen for them. We may or may not be able to get buttons there at some point. Also, when you initially boot to recovery, there will be a message about update.zip being gone. Ignore the message as it seems to be a bug. As long as you copied the update.zip from this thread to your SDCard, you should be fine. Enjoy.
If you like my work, feel free to donate to me. Alternatively, sign up for Dropbox via my referral link Also, remember that none of this would really be possible without the generosity of DroidXcon, so you could donate to him as well.
Archive said:
Recovery Kernel
Download - CWM 2.5.x
Download - CWM 3.x
Click to expand...
Click to collapse
Thank you so much imnuts
It works like a charm
and btw, i love the color scheme, lol
This is awesome! Im extremely happy to see great dev work still going on for the continuum!
I'm going to update the update.zip soon then as well to the latest CWM 3.x that we have for the Fascinate as well. Then, maybe look into replacing stock recovery again and hoping it works this time.
im having major problems well maybe not major but i installed cwn but after i rebooted and tried to install a softkey update.zip i lost my cwm and every thing i try to do i cant get cwm back
You have to apply the update.zip every time
Sent from my SCH-I400 using XDA Premium App
I do and I get the discolored screen then it send me to the stock recovery and when I try to install the update.zip it says update.zip not found when I know it's there
Sent from my Rooted Space Time Continuum w/h a 2600mAh battery
Mine says the update isn't found either but it still works for me. I dunno about the discolored screen. I'm sorry :/
Sent from my SCH-I400 using XDA Premium App
i figured out what i was doing wrong i renamed the file to update.zip when i should have left it at just update lol oh well you live and you learn
Ohh lol. The .zip is the type of file it is
Sent from my SCH-I400 using XDA Premium App
Noob question. Is the recovery kernel were supposed to download along with the update.zip an actual kernel?
Sent from my SCH-I400 using XDA App
And what exactly is the difference between this CWM and the original CWM?
Sent from my SCH-I400 using XDA App
ntien said:
Noob question. Is the recovery kernel were supposed to download along with the update.zip an actual kernel?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
You need to flash the recovery kernel via Odin, and it is an actual kernel. The update.zip is a fakeflash recovery. It basically kills the currently running recovery and starts up CWM recovery in its place.
ntien said:
And what exactly is the difference between this CWM and the original CWM?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
The difference is that this recovery has the correct button mapping, where the update.zip that Adrynalyne posted was using the Fascinate's button layout, so things didn't work as expected.
so i can't have both this version of the clockwork recovery mod and the peanutbutta jelly time kernel at the same time?
ntien said:
so i can't have both this version of the clockwork recovery mod and the peanutbutta jelly time kernel at the same time?
Click to expand...
Click to collapse
Yes you can. Recovery is a full kernel, it just boots using a different file and set of commands, and it doesn't start up the android system once booted and provides just a minimal environment. The recovery kernel and standard kernel lie on two separate partitions, and in actuality, this recovery kernel is the standard kernel as well.
New CWM update.zip file. Like we did for the Fascinate about a month or so ago, I'm going to try to get everything moved over the CWM 3.x and Edify Scripting. Here is a new update.zip file to be able to use the most up-to-date version of CWM. I'll also try to keep this file updated as Koush and the rest of the CM team update CWM.
Instructions
1. Download me
2. Rename file to update.zip and put it on the root of your SD Card, overwriting the previous update.zip
3. Boot to recovery and apply update.zip
I may give replacing stock recovery entirely again another shot as well, eliminating the need for the update.zip entirely, but no promises. Also note that nandroid backups made with the previous update.zip file will not work with this version of CWM. If you like having the nandroid backup available, redo your backups so you have them for the new CWM.
Deleted cause it was a stupid question
imnuts said:
New CWM update.zip file. Like we did for the Fascinate about a month or so ago, I'm going to try to get everything moved over the CWM 3.x and Edify Scripting. Here is a new update.zip file to be able to use the most up-to-date version of CWM. I'll also try to keep this file updated as Koush and the rest of the CM team update CWM.
Instructions
1. Download me
2. Rename file to update.zip and put it on the root of your SD Card, overwriting the previous update.zip
3. Boot to recovery and apply update.zip
I may give replacing stock recovery entirely again another shot as well, eliminating the need for the update.zip entirely, but no promises. Also note that nandroid backups made with the previous update.zip file will not work with this version of CWM. If you like having the nandroid backup available, redo your backups so you have them for the new CWM.
Click to expand...
Click to collapse
I guess I should read the whole thing before wondering why I can't restore an old backup with the new CWM
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God
Hey imnuts, every time I try to restore my phone with this clockwork, it screws up my phone saying it cant mount this stuff etc. it worked with regular recovery and old clockwork, but the new clockwork messes up my phone when I try and restore my phone. Im running the DL17 ROM (not the new edify one)
Sent from my SCH-I400 using XDA Premium App
ntien said:
Hey imnuts, every time I try to restore my phone with this clockwork, it screws up my phone saying it cant mount this stuff etc. it worked with regular recovery and old clockwork, but the new clockwork messes up my phone when I try and restore my phone. Im running the DL17 ROM (not the new edify one)
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
...Did you not even see my post right above yours?
So im planning to go back to 2.1 or 2.2 and sense, so how im going to do this? ( I have #203 Nightly)
After that, will i need to root again, and is it possible to overclock stock wildfire ROM and how? (Install new kernel??)
If youre asking why go back to sense, I just happen to need stableness for next 4 weeks and want to see how much I can tweak Sense. Going back to cm7 in november probably
Mipe
Just install like a new ROM. One such stock rooted Froyo can be found here:
http://forum.xda-developers.com/showthread.php?t=877977
The only different thing is that this will have to be flashed in Clockworkmod 2.x. (I guess you must know how to flash Radio's in CM7, so its not a big issue)
And yes, to OC, you will have to install a custom kernel like this one:
http://forum.xda-developers.com/showthread.php?t=995301
3xeno said:
Just install like a new ROM. One such stock rooted Froyo can be found here:
http://forum.xda-developers.com/showthread.php?t=877977
The only different thing is that this will have to be flashed in Clockworkmod 2.x. (I guess you must know how to flash Radio's in CM7, so its not a big issue)
And yes, to OC, you will have to install a custom kernel like this one:
http://forum.xda-developers.com/showthread.php?t=995301
Click to expand...
Click to collapse
I also found that i have cwm backup from original rom that I can restore. Does this also restore previous radio or kernel or do I have to do it manually?
it will not touch the radio, but it will restore the stock kernel. (Or whichever kernel you had installed when you took that backup)
3xeno said:
it will not touch the radio, but it will restore the stock kernel. (Or whichever kernel you had installed when you took that backup)
Click to expand...
Click to collapse
I got a problem. I want to get original Sense by restoring backup from CWM. Mine works, but has a pattern that i dont remember and a email wich i dont remember either. Does anyone happen to have a backup of a wildfire without password or could someone advice something else? I tried RUU but my win7 x64 is causing trouble, or the drivers.
Just flash the stock froyo ROM I listed in the first post I made in this thread (http://forum.xda-developers.com/showthread.php?t=877977). If you don't know how to get Clockworkmod 2.5.0.x, then:
- Download this attachment, place on your SDCard:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
- Flash the zip (update1.zip) using your existing Clockworkmod 5.0.2.0
- Device will reboot and will start Clockworkmod 2.5.0.7
- Perform Data Wipe and Choose Install Zip from SDCard, select the ROM Zip file, and let it install.
3xeno said:
Just flash the stock froyo ROM I listed in the first post I made in this thread (http://forum.xda-developers.com/showthread.php?t=877977). If you don't know how to get Clockworkmod 2.5.0.x, then:
- Download this attachment, place on your SDCard:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
- Flash the zip (update1.zip) using your existing Clockworkmod 5.0.2.0
- Device will reboot and will start Clockworkmod 2.5.0.7
- Perform Data Wipe and Choose Install Zip from SDCard, select the ROM Zip file, and let it install.
Click to expand...
Click to collapse
For the rooted ROM it says No Hboot | No Radio, what does that mean?
jediknight111 said:
For the rooted ROM it says No Hboot | No Radio, what does that mean?
Click to expand...
Click to collapse
Just what is says. It does not include the Bootloader (HBoot), and it does not include the baseband (Radio). So, for these two components, what you are having on your device at this moment will remain. (ie - They will not be updated when you flash the ROM)
3xeno said:
Just what is says. It does not include the Bootloader (HBoot), and it does not include the baseband (Radio). So, for these two components, what you are having on your device at this moment will remain. (ie - They will not be updated when you flash the ROM)
Click to expand...
Click to collapse
I Installed the Rom from recovery, but all I get is the HTC logo and the startup tone then it switches off and I get the same thing again. Help please!
Edit: It's working now but I cannot force move apps like I could do before. Why is that?
jediknight111 said:
I Installed the Rom from recovery, but all I get is the HTC logo and the startup tone then it switches off and I get the same thing again. Help please!
Edit: It's working now but I cannot force move apps like I could do before. Why is that?
Click to expand...
Click to collapse
Because it is a Completely Stock HTC Factory ROM with no support for it.
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Most don't recommend Rom manager, I would just stick with Rogue.. I had no problems with it..
Bobby O'S Epic Touch....
indigo0086 said:
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Click to expand...
Click to collapse
Get rid of ROM manager it doesn't flash recovery right on this phone..and koush doesn't care to fix it...don't ever use the touch one either... Get a kernel with cwm in it at use mobile Odin to install....if using a GB ROM use the el26 if using a ics ROM don't use any recovery unless u hate your phone and want to brick it
Sent from my SPH-D710 using Tapatalk 2 Beta-5
indigo0086 said:
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Click to expand...
Click to collapse
Just stick with Rogue's. ROM Manager has been the source of a TON if bricks lately (mostly to do with CWM Touch). If you absolutely can't use Rogue you can use the stock CWM from EL26.
http://db.tt/rBZNsGaj
But really I'd stick with Rogue...
And ROM manager doesn't actually install recovery on the phone. When you flash a recovery in it it creates a temporary recovery for you to boot into. But ya, don't even bother messing with ROM manager for all the reasons everyone else has stated.
Epix4G said:
Get rid of ROM manager it doesn't flash recovery right on this phone..and koush doesn't care to fix it...don't ever use the touch one either... Get a kernel with cwm in it at use mobile Odin to install....if using a GB ROM use the el26 if using a ics ROM don't use any recovery unless u hate your phone and want to brick it
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I totally agree here with the ROM Manager danger... When I had trouble in the past on a GB ROM, Koush didn't respond to any of my help requests.
I haven't had any issues lately, but in all fairness I do like the fact that ROM Manager will automatically reboot the phone into recovery, create a backup, and then boot back into Android. Also, I can delete or rename existing backups from right within Android with RM. I have restored the backed-up images with no issues too...
I've been on ICS since Calk's 1.0 FC06 ROM, and I have been fortunate enough to know to stay away from the touch recovery
You can delete or rename backups in android from any file manager app, most custom roms have the reboot mod to get to recovery and its a few clicks to backup and reboot to phone from recovery Rom Manager doesn't do anything special you can't do with your fingers and your trusting an app to do something for you instead of doing it yourself and making sure its done right
Sent from my SPH-D710 using xda premium
thanks for the feedback, I won't bother with rommanager anymore than lol. Also Can I use Rogue to flash Cyanogenmod and other roms, Some people are saying to use certain clockworkmod versions and saying rogue has caused bricks.
So, I have flashed CWM Recovery and CWM Touch Recovery onto my Epic 4G Touch. Rom Manager says both are installed. However, when I boot into recovery, I get the stock recovery. I've searched and searched and all I have found are people who aren't pushing the right buttons and others with junk answers that are no help at all, like instructions on how to flash the recovery.
Even if I reflash using Rom Manager or any other recovery installer, it boots to the stock recovery. It's as if any changes to the file system are being completely ignored.
The weird thing is, if I flash StockCWM-EL26 or rogue_ET-recovery-1.2.2-FB27-rc0 using Odin/Mobile Odin and get to whichever one I flashed once, then either the phone won't boot at all or subsequent reboots result in the stock recovery once again.
To reiterate, I have *no* problem booting the phone and I have *no* problem getting to recovery... it's the wrong recovery, but still.
Oh, and I'm using HyDrA ROM.
Wrong forum. Report your post & ask mods to move your thread here.
MistahBungle said:
Wrong forum. Report your post & ask mods to move your thread here.
Click to expand...
Click to collapse
That forum is for the Epic 4G. My phone is not the Epic 4G, it is the Epic 4G Touch.
Try here then (doesn't belong here regardless).
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
^^^^^ this been there done that
patrao_n said:
WARNING do not use rom manager. Use odin or mobile odin. You have a high risk of bricking using rom manager. Take a look at some how-to's in this section.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
As I said, it either works once and never again or never at all no matter what I use to flash it.
Venum's Hydra rom? Wow, talk about a flash back..
Anyway, have you tried the el26 kernel one click?
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Would you mind listing the steps of flashing and items being flashed?
Only reason a custom won't stick is that you're flashing something behind it. In my mind at least..
First Time
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Wipe.
Flash HyDrA twice as per instructions.
Flash GApps.
Flash Multi-DPI Play Market while I'm at it.
Reboot.
Setup ROM.
Attempt to get to Recovery - got stock recovery.
Decided to try again without wiping. Same results.
Decided to try something:
<Download Mode>
Flash EL26 CWM Recovery - Phone no longer boots to OS. Can only get to CWM Recovery or Download Mode.
<Recovery Mode>
Made a NAND backup of /system and /data.
Flash HyDrA twice as per instructions.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Restore the NAND backups.
Reboot.
Attempt to get to Recovery - got stock recovery.
Another thing:
<Download Mode>
Flash Rogue recovery.
Reboot.
Attempt to get to Recovery - got Rogue recovery - So far so good.
Flash CWM Touch Recovery - Recovery takes effect immediately.
Reboot.
Attempt to get to Recovery - got Rogue recovery - Interesting, but I can only access the external SD card from Recovery.
Flashed back to EL26.
Reinstalled HyDrA.
Restored the NAND backups.
(The Touch Recovery version is 5.8.1.5).
ROM Manager
Attempt to flash either CWM Recovery or CWM Touch Recovery.
Reboot.
Attempt to get to Recovery - got stock recovery.
Here is a list of my apps if you want that, too.
https://www.dropbox.com/s/k67l6mb294ruyug/apps-list.txt
I'm hesitant on trying anything else because it's a pain to restore it if I can't boot to the OS.
Just went back to Venums thread.
:edit: Briefly reading the thread, you'll need to have and AOSP kernel to run the Rom, so no, EL26 will not work.
:2d edit: This is out of the second post in that thread. - *If you are restoring a nandroid that you backed up via the above process, you will need to wipe cache and dalvik, then flash an AOSP ICS kernel or the ROM wont boot because it is backed up with the EL26 kernel. Then reboot.
Hydra comes with FD26 kernel. As per the OP.
I don't know, and haven't tested, if Hydra will run with EL26 cwm. But you need to add that to the last step.
But that's why you're going back to stock. It's part of the package.
Please, please, please; STOP using Rom Manager to flash a recovery.
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
egingell said:
No, but I don't imagine it would be any different than the Odin flash.
At any rate, I have an addendum. Flashing Rogue 1.2.2, the one that works - I can't get 1.5.0 to work at all (no boot, no recovery, only download mode), doesn't magically disappear, but it doesn't mount my external SD card and I can't open System Settings/Storage - I just can't win.
Click to expand...
Click to collapse
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
MoHoGalore said:
I see a AOSP/TWRP repack by Times Infinity in the Kernel Repo that you could try, But I have not read the Hydra thread to see if Venum had tested this prior to discontinuing support.
Click to expand...
Click to collapse
I downloaded one, I haven't tried it.
I take it back, I did try it, but it wouldn't install. FF18 Rev2, for the record.
MoHoGalore said:
bilgerryan said:
The easiest thing to do is find the EL29 auto boot recovery... goes straight into recovery after you flash it thru Odin.. check RWilco's repository
Click to expand...
Click to collapse
From what I'm gathering from his OP, he wants to have a custom after flashing Hydra.. Gonna have to be an AOSP repack to run with a custom. I didn't really gather that until he listed the flashing steps he's doing.
Click to expand...
Click to collapse
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
egingell said:
I downloaded one, I haven't tried it.
Right. And I would have no problem just reflashing EL26 /w CWM if it would actually boot into the OS.
Click to expand...
Click to collapse
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
MoHoGalore said:
Yeah, anything that's not an AOSP kernel/recovery isn't gonna work. So, if Time's aosp repack doesn't work, you'll have to run the included kernel.
Click to expand...
Click to collapse
Odin wouldn't install it, if that makes a difference. It's not that the install failed and I had to start over, again.
Well, since my touch isn't my daily use phone at the moment, I'll test that setup tonight.
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
egingell said:
I decided to try the One-Click of the FF18 v2 kernel and it flashed successfully.
However, as with Rogue, I only have no external SD card and no access to Settings/Storage. TWRP is pretty, but if I can't use my SD card, I'd rather use the stock kernel.
Click to expand...
Click to collapse
My apologies on not getting back with you on this last night.
But the SD issue is also seen on the repacks with JB. Depending on when and how FF18 v2 was built (without source at the time?) could be similar to the issues with current repacks.
I'd have to refer those issues/questions to Agat or Garwynn..
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app