Related
Hi guys, just sharing my experience with kernels which don't have CWM integrated as default recovery.
Latest versions of Voodoo - 5.x - converts /system to ext4.
The standalone version of ClockworkMod, the one flashed by RomManager, does not support ext4. However, as explained by supercurio himself, the kernel needs to have 3e recovery which allows you to execute the update.zip (standalone ClockworkMod recov.) with wrappers necessary to mount ext4 partitions as ext4. With 2e recovery, partitions are mounted as j4fs, hence bad and failed flashes.
If the kernel has CWM integrated, then all is fine, you can flash without worries.
If you already know this, good for you
While accurate, wrong forum.
MikeyMike01 said:
While accurate, wrong forum.
Click to expand...
Click to collapse
Not wrong at all You have to be into development and flashing to care about CWM and Voodoo
But lets let the mods decide
Hi !
With Vooodoo 5.x, ClockWorkMod support Ext4 both when run from Rom Manager and as the default recovery.
Working scenario :
- Starting a backup from Rom manager
- Restoring a backup from CWM recovery alone
- Installing a sdcard zip from Rom Manager
etc.. 100% compatibility.
Well, there is no non-working scenario, I cannot give you example of them
Notes:
- If you reboot in recovery (adb reboot recovery), you get the Voodoo Red CWM recovery. This one contains the "voodoo lagfix" menu, as a help to configure it.
- If you use CWM from Rom Manager, you get the Green CWM, compiled and updated by Koush.
As precised, both work the same way with Ext4 now. To get this result, I wrote wrappers allowing Ext4 support without the requirement of a modified CWM.
PS, to the OP: I suggest you specify the version for those who are not working.
Every current and final version of Voodoo is
supercurio said:
Hi !
With Vooodoo 5.x, ClockWorkMod support Ext4 both when run from Rom Manager and as the default recovery.
Working scenario :
- Starting a backup from Rom manager
- Restoring a backup from CWM recovery alone
- Installing a sdcard zip from Rom Manager
etc.. 100% compatibility.
Well, there is no non-working scenario, I cannot give you example of them
Notes:
- If you reboot in recovery (adb reboot recovery), you get the Voodoo Red CWM recovery. This one contains the "voodoo lagfix" menu, as a help to configure it.
- If you use CWM from Rom Manager, you get the Green CWM, compiled and updated by Koush.
As precised, both work the same way with Ext4 now. To get this result, I wrote wrappers allowing Ext4 support without the requirement of a modified CWM.
PS, to the OP: I suggest you specify the version for those who are not working.
Every current and final version of Voodoo is
Click to expand...
Click to collapse
OK, my non-working scenario is like this:
I installed Darky's JPU with Voodoo v5.0.2. Installed xcaliburinhand's kernel with Voodoo lagfix 5.0.1. Loaded CWM recovery and tried to install something - no go - and when it worked (i dont know how) my system did not boot.
This happened not once, not twice but 3 times trying to flash things which if flashed from the kernel integrated CWM did not give me any kind of errors or brake my system.
supercurio said:
Notes:
- If you reboot in recovery (adb reboot recovery), you get the Voodoo Red CWM recovery. This one contains the "voodoo lagfix" menu, as a help to configure it.
Click to expand...
Click to collapse
xcaliburhand's kernel has the completely useless 2e recovery.
MikeyMike01 said:
xcaliburhand's kernel has the completely useless 2e recovery.
Click to expand...
Click to collapse
indeed useless, but if supercurio is right, the ClockworkMod recovery that I have on the sdcard should handle the system without issues.
Note: I flashed the recovery few times just to be sure that is not corrupted or whatever.
This is a kernel issue but I get similar results with voodoo disabled. Test for yourself.
Stephenv1971 said:
This is a kernel issue but I get similar results with voodoo disabled. Test for yourself.
Click to expand...
Click to collapse
OK, will do.
That means the ROM dev now has to update to latest CWM in order to write to ext4? I think we are using 2.5.1.0....
I think this is also why some people say that theme mods doesn't stick.
killer23d said:
That means the ROM dev now has to update to latest CWM in order to write to ext4? I think we are using 2.5.1.0....
I think this is also why some people say that theme mods doesn't stick.
Click to expand...
Click to collapse
The situation is like this: xcaliburhand's 2.2.1 kernel might have problems and CWM will not work if the ROM is powered by this kernel. However, if you have a different kernel and you see the same problem, let us know. The thread will remain like it is until someone tries to load standalone CWM and flash something with it on a different kernel.
MikeyMike01 said:
xcaliburhand's kernel has the completely useless 2e recovery.
Click to expand...
Click to collapse
Yes, 2e recovery is a mistake, because it allows you to execute the CWM update.zip alone.
without wrappers, which means it will destroy your Ext4 partitions, mounting them as j4fs.
Voodoo for Froyo come with 3e recovery.
supercurio said:
Yes, 2e recovery is a mistake, because it allows you to execute the CWM update.zip alone.
without wrappers, which means it will destroy your Ext4 partitions, mounting them as j4fs.
Voodoo for Froyo come with 3e recovery.
Click to expand...
Click to collapse
This explains it Editing OP
killer23d said:
That means the ROM dev now has to update to latest CWM in order to write to ext4? I think we are using 2.5.1.0....
I think this is also why some people say that theme mods doesn't stick.
Click to expand...
Click to collapse
For the ROM dev, there is no need to do anything special about recoveries.
Keeping 3e is a better idea because 2e can cause troubles and thanks to default CWM recovery (powerful!) 2e is useless.
Anyway thanks for pointing out this potential issue with non-standard kernels!
I prepare a new Eclair release at the moment
Maybe I should add this kind of checks to prevent anyone executing an CWM update.zip directly, from the 2e recovery menu.
So, basically xcaliburhand has to fix this.
icezar1 said:
This explains it Editing OP
Click to expand...
Click to collapse
Yep For the OP:
only non working scenario is running CWM from a 2e recovery.
But if your Voodoo kernel has CWM built in, you cannot start 2e recovery manually.
MikeyMike01 said:
So, basically xcaliburhand has to fix this.
Click to expand...
Click to collapse
He has 2 options:
- restoring 3e instead of 2e
- insert a built-in CWM.
I'm reachable for help
icezar1 said:
Hi guys, just sharing my experience.
Latest versions of Voodoo converts /system to ext4.
The standalone version of ClockworkMod, the one flashed by RomManager, does not support ext4. However, as explained by supercurio himself, the kernel needs to have 3e recovery which allows you to execute the update.zip (standalone ClockworkMod recov.) with wrappers necessary to mount ext4 partitions as ext4. With 2e recovery, partitions are mounted as j4fs, hence bad and failed flashes.
Click to expand...
Click to collapse
Lol no it does not need 3e recovery.
the wrapper are installed by Voodoo code during the boot.
Only in case of if the kernel doesn't have built-in CWM, 3e is recommended, for Voodoo kernel builders because 2e can allow running direct CWM update.zip - without wrappers -
If the kernel has CWM built-in 2e or 3e don't matter.
for reference, how to use the injector:
https://github.com/project-voodoo/lagfix/tree/stable/voodoo_injector
supercurio said:
Lol no it does not need 3e recovery.
the wrapper are installed by Voodoo code during the boot.
Only in case of if the kernel doesn't have built-in CWM, 3e is recommended, for Voodoo kernel builders because 2e can allow running direct CWM update.zip - without wrappers -
Click to expand...
Click to collapse
Yeah yeah, figured that out still editing the post
So I have been on ext4 for a few days using quantum 2.5. Everything was working as expected there with clockworkmod 2.5.1.0 and 2.5.1.2 installed and available. This morning, I tried flashing the new midnight rom, but my file was corrupted so I went back to Mammon's Bonsai4All 1.0.4 with an ext4 kernel. Now, I can't get back into cwm 2.5.1.2. Bonsai4All should have a working recovery redirect, so I'm guessing I need to reinstall 2.5.1.2. The problem is, I can't flash the prepare.zip to ext4 with 2.5.1.0. So the question is, what do I need to push to the phone to get the modded recovery back? I have the prepare.zip and all other files from the onelickext4 1.3 and I'm not afraid of adb or using the terminal on my phone.
Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk
If you boot into CWM then go to advanced then reboot recovery that should put you in 2.5.1.2
Beat me to it.
mysteryemotionz said:
Boot into recovery. Goto advance. Select reboot recovery. That should bring you to v where you wanna be. If it don't then its time to odin
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
The problem is, that when I reboot recovery, it brings me back to 2.5.1.0. I have a working phone right now, so I don't feel like using Odin again, yet.
It seems like there should be a way to get the correct recovery back on the phone with the terminal or adb. I've only been using android since October, so it is taking some work to learn how everything is done in the android world. Luckily, I went to school for programming on linux, but I'm a little rusty.
found this tidbit in an the ext4 thread over at ppcgeeks
Please note that until other ROMs add support (namely the new recovery binary in /system/bin/recoveryfiles) I cannot guarantee recovery will function properly
Click to expand...
Click to collapse
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
edit: It works! I'm getting errors from missing bitmap files, but that should be pretty simple to copy over as well.
Bonsai4All 1.0.4 does not support ext4. I'm surprised your phone even boots, which leads me to believe that you may still be rfs.
DiGi760 said:
found this tidbit in an the ext4 thread over at ppcgeeks
So I'm going to try pushing the recovery file from the prepare.zip and see if that works.
Click to expand...
Click to collapse
Midnight has those files already
Sent from my SPH-D700 using Tapatalk
You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2
siphuyoda said:
You could download the QuickBoot app from the Market. Selecting Recovery from within the app automatically boots the phone into Clockwork 2.5.1.2
Click to expand...
Click to collapse
He can't boot up so how would he get a app
Sent from my SPH-D700 using Tapatalk
You all misunderstand.
I can boot just fine. I was on Quantum 2.5 and switched to Bonsai4All 1.0.4, which was pre-ext4. I installed the ext4 kernel at the time of flashing, so the phone works.
No matter how I got into recovery after installing Bonsai4All, it went to 2.5.1.0. That includes using quickboot or reboot recovery from within recovery. And I can't flash anything with 2.5.1.0 since it won't flash to ext 4.
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
I too have epic experience 2.0.07 working with ext4. I actually have the same problem he's having so I'm gonna try his method. It boots up fine and and works but can't get into CW 2.5.1.2. Funny thing is I can still flash zip files through regular CW. Probably because they're not roms. I've checked through adb and and it says I'm using ext4. I can also tell the differance to. My quadrant score is like 1536. I know quadrant it ain't real world but the dev of midnight rom has a video in his blog showing the differance. I'm pretty close to what he got.
Sent from my SPH-D700 using XDA App
musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
The new Dual Kernel maybe? It bridges the gap between the two file systems.
musclehead84 said:
Check.to make sure you do indeed have ext4 working by using adb shell. I just don't see how the phone booted on bonsai if you have ext4 installed.
Sent from my Evo killer
Click to expand...
Click to collapse
You can make other DK28 roms work with ext4 by flashing an ext4 compatible kernel after flashing the rom. If I had just tried to flash bonsai without an ext4 compatible kernel, it would freeze at the samsung screen and I would have to Odin out of it. I made that mistake once already when I stopped paying attention to what I was doing.
It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles
plus I keep seeing "E:can't open /cache/recovery/log" while in ClockworkMod Recovery 2.5.1.0 - and when I do the Reboot Recovery as people have said to make it go to 2.5.1.2, it still just hangs at the SAMSUNG splash...
I found SPH-D700-DK28-8G-REL.tar.md5 and flashed that and now I'm back in business - **phew**
Cobaltikus said:
It says (solved) but I don't see the solution. guess that means I'm still an android n00b.
Stuck at SAMSUNG screen (Help!)
I had CWM3 and EXT4
I flashed Quantum Rom 2.7
tried to flash Nebula Rom 1.6 but it didn't take cuz of EXT4
I flashed ReRFS.Format.ROM.DK28-signed.zip to bring me back to RFS
reboot - hangs at SAMSUNG splash
reboot back into recovery, now 2.5.1.0
tried flashing Nebula Rom 1.6 - but reboot still hangs at SAMSUNG
tried flashing Quantum Rom 2.7 - but reboot still hangs at SAMSUNG
tried Odin, but I don't know what to do with Odin except flash the DK28 modem, so I did that, but it didn't help
so I'm basically trying a bunch of crap without knowing what I am doing, and as fun as this is - I'm kinda stuck - just going in circles
Click to expand...
Click to collapse
Clarification on how I solved my problem is below. I had a usable phone the entire time, I just didn't have the cwm I needed.
It almost sounds like a your problem is a kernel issue, except you have it with so many roms. There may have been an error in the file system conversion somewhere that is causing you trouble. You don't usually get the "E: can't do whatever" error if your cwm is compatible with your file system.
My suggestion to you would be to Odin back to a good image. You do it basically the same as doing the modem. Uncheck everything on the left. Put your .pit in the pit section. Put your .tar file (or .tar.md5) into the box that says pda (the first box). Then, plug your phone in and flash.
After that, you can run the one-click root and recovery to get root and cwm 2.5.1.0 back. Then you can start playing again. Remember, if you use ext4 then you must have an ext4 compatible kernel. If you use rfs, you must use an rfs compatible kernel. You can use any rom on ext4 if you flash an ext4 kernel immediately after you flash the rom and before you reboot the phone. If you forget to do the kernel, you will hang at the samsung screen. Some roms are ext4 or rfs only, and some have a dual file system kernel. Currently, you can mix and match any dk28 kernel with any dk28 rom. Don't try to mix kernels and roms from different builds, though.
Now for further clarification on how I got 2.5.1.2 back when using a rom that didn't have it baked in:
DiGi760 said:
How I fixed it:
1. Remount as rw
2. Copy /system/bin/recoveryfiles/recovery and /system/bin/recoveryres/* from the prepare.zip to my phone.
3. Remount as ro
And voila! Now I can get into 2.5.1.0 and 2.5.1.2.
Click to expand...
Click to collapse
I guess my solution was about as clear as mud. In order to do this, it helps to be somewhat comfortable using a command line.
I used the prepare.zip that was a part of the original ext4 conversion to get the recovery files. When you open the prepare.zip it has the standard flashable zip structure and is organized according to where the files are supposed to end up on your phone. Open the zip, open the system folder, open the bin folder and copy the folder named "recoveryres" to your sd card. Then open the "recoveryfiles" folder and copy a file named "recovery" to your card as well. Put these files somewhere easy to find, like a folder named "cwm" at the root of your card.
Next, use a terminal emulator to remount your phone to rw so you can write to the protected areas. Most of our roms included a small remount script, so all you have to do is type "remount rw" without the quotes. Later you will use "remount ro" to make things read only again.
Now, you're going to copy those files that you got from the prepare.zip to their proper places on your phone. You did leave them somewhere easy to find, right?
Copy "recovery" to /system/bin/recoveryfiles/ and copy the "recoveryres" folder to /system/bin/. You may have to watch and make sure it doesn't skip any files when copying the recoveryres folder.
After that, remount ro and you are done.
Hi All,
I've been looking for an answer and have not found one yet.
I have an existing NAND build (MDJ cyanogen 7) of android that I flashed via magldr 1.11. I know I can update magldr to 1.13 safely without messing deleting the the nand rom i have already. But if I want to install Clockworkmod 1.3 onto the nand will I lose my existing rom need to reflash my rom again or does magldr know to flash clockworkmod onto another area of nand that wont overwrite my existing rom?
also with clockworkmod it says:
Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
it says to use the 150MB partition just wanted to see if anyone else using mdj's cyanogen 7 is using the same thing?
Your help is greatly appreciated
ascrackoo1 said:
Hi All,
I've been looking for an answer and have not found one yet.
I have an existing NAND build (MDJ cyanogen 7) of android that I flashed via magldr 1.11. I know I can update magldr to 1.13 safely without messing deleting the the nand rom i have already. But if I want to install Clockworkmod 1.3 onto the nand will I lose my existing rom need to reflash my rom again or does magldr know to flash clockworkmod onto another area of nand that wont overwrite my existing rom?
also with clockworkmod it says:
Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
it says to use the 150MB partition just wanted to see if anyone else using mdj's cyanogen 7 is using the same thing?
Your help is greatly appreciated
Click to expand...
Click to collapse
Yes you will lose your current rom, so do a cwm backup first. After flashing the partition for cwm, you will get a kernel error on first boot, so boot into AD Recovery and restore the boot, system and data backups and all is back to normal. As for the partition size, use the same size as you did for the sd version. The guide suggests a 400mb partition for an unsquashed desire hd build, but I used the 250mb partition on my current rom and all is perfect.
PS! Please don't post questions in the ROM Dev section, there's a reason why there is a Q&A section.
ClydeB1 said:
PS! Please don't post questions in the ROM Dev section, there's a reason why there is a Q&A section.
Click to expand...
Click to collapse
+1
Its so frustrating, why on earth would anybody post a question topic in here when we have dedicated Q&A forum??
It should be obvious to anybody that this is a "dev" forum for posting developments not for asking questions.
Since the rom was originally flashed via DAF, will CWM still allow me to do a backup?
Was hoping for a guide, it's so confusing.
No, from what I understand you don't have CWM installed yet, so you can't use it now. Use titanium backup (market), and then flash cwm so you can use it in the future.
ascrackoo1 said:
Since the rom was originally flashed via DAF, will CWM still allow me to do a backup?
Was hoping for a guide, it's so confusing.
Click to expand...
Click to collapse
It seems confusing at first but it is not really that difficult.
StephanV said:
No, from what I understand you don't have CWM installed yet, so you can't use it now. Use titanium backup (market), and then flash cwm so you can use it in the future.
Click to expand...
Click to collapse
Correct, on first flash of cwm it will erase all data/roms etc on NAND. You will not be able to backup the rom if it was initially flashed via daf. As StephanV says, use Titanium Backup or MyBackup Root to back up your data/apps etc and you can restore them after.
Once you have cwm installed and have flashed a new rom and set it all up, then you can do a cwm backup.
So if i use cwm then I can only flash zip based roms from that point on? I cant use the daf ones anymore then.
You can still use daf, but each time you run a daf file it will remove the cwm recovery partition and you will need to reflash it to use cwm again.
I'm finding that if i flash cwm ontop of a daf rom the rom becomes unbootable. and the only way to get it to work again is use a cwm version of the rom.
ascrackoo1 said:
So if i use cwm then I can only flash zip based roms from that point on? I cant use the daf ones anymore then.
Click to expand...
Click to collapse
i'm not sure about the rom you are using but i was able to back up a few different roms with cwm which i installed using daf. this is what i did:
1. create a folder on sdcard name "cwm" (you can name it whatever you want). i actually have a folder for each clockwork recovery version.
2. put the zImage and initrd.gz for cwm (version 1.0,1.1,or 1.2) in the folder you just created. (do not flash anything at this point)
3. boot into magldr and go to services, boot settings, ad sd dir and select the directory you just created
4. now in magldr menu boot ad sd, and you should hopefully boot into clockwork
5. go to backup and restore and backup your rom. if you try cwm 1.2 and it doesn't work try 1.0 to back it up, you can then update to 1.2 again and it will still restore just fine.
6. before restoring your rom, install cwm1.3 and choose a partition size bigger than the size of the system.img of the rom that you backed up. clockwork backs up your rom in your sdcard->clockworkmod->backup. it creates a folder with the timestamp.
7. now you can follow the steps from the clockworkmod thread to load cwm1.3 and restore from there.
ClydeB1 said:
You can still use daf, but each time you run a daf file it will remove the cwm recovery partition and you will need to reflash it to use cwm again.
Click to expand...
Click to collapse
ascrackoo1 said:
I'm finding that if i flash cwm ontop of a daf rom the rom becomes unbootable. and the only way to get it to work again is use a cwm version of the rom.
Click to expand...
Click to collapse
dont bother 'installing' clockwork, just put the two files on your sd card, then go into your MDJcyanogen rom folder on the PC, open (in notepad) flash.cfg and it will look something like
boot ya|boot|ro filesize+1M boot.img
misc ya 1M
recovery ya|ro 3M
cache ya 3M
system ya filesize system.img
userdata ya|asize|hr allsize
the partitions 'recovery' and 'misc' will allow cwm to work, they arent needed for this rom, they are only there for compatibility however if you plan on flashing to a different rom using sd card/cwm, (rather than simply using cwm to do backups of MDJcyanogen) you will want to edit the
system ya filesize system.img
and maybe set it to one of teh recommended cwm sizes, example
system ya 150M
this is because the original line
system ya filesize system.img
will set a system partition of the same size as the MDJcyanogen system.img, (about 130meg) but if your next rom has a bigger system.img, when you try load it from cwm it wont fit, so wont work. by setting it to 150 (or whatever you want) you are allowing for different size system.img in various roms.
Whenever you flash a nand rom, so long as you edit the flash.cfg and make sure those two partitions, misc and recovery (and maybe cache too, i do) are there, then cwm will work.
how do u get 1.13
sbgleeko said:
how do u get 1.13
Click to expand...
Click to collapse
Go to nand development and its in the thread called (quite cunningly) "magldr 1.13 released "
A link or a file, either would be great. I keep finding CW 3.x and 2.5.1.0, but never 2.5.1.2 for Epic. Please, someone point the way.
Many thanks.
To get to .2 boot into clockwork go to advanced and reboot recovery. That should put you into .2
Sent from my SPH-D700 using XDA App
This thread is where you need to go. Get the one-click ext4 zip. Inside it is a file called prepare.zip. Flash prepare.zip to add 2.5.1.2 to your phone if the rom you have doesn't already have it. Then, if you death-grip into recovery, you will see 2.5.1.0. Select advanced->reboot recovery to reboot into 2.5.1.2.
Thank you guys. I do need to flash since I never have flashed 2.5.1.2 prior.
I also found a similar file inside the viper 4.0.2b ROM package.
Follow up question, inside the flash, in addition to the recovery files, I see:
/system/etc/mke2fs.conf
/modules/ext4.ko
/modules/jbd2.ko
I presume these are for ext4. I plan to stay with RFS for now. I was looking for 2.5.1.2 because I want to use the latest Bonsai ROM (coming from stock DK28) and it seems to call for it, even with RFS. Will these extra files cause any issues later?
Thanks again.
I don't think that is going to work with Bonsai! 2.0.0 or > howeverif it does work please post your results in the bonsai4all thread
Sent from my SPH-D700 using Tapatalk
Top Nurse said:
I don't think that is going to work with Bonsai! 2.0.0 or > howeverif it does work please post your results in the bonsai4all thread
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks for pointing this out. I mis-read the post. In the original post, while beneath the "Latest News", it is written that RFS not supported in V2.0, immediately below that, under "Next Release News", it is written that "No more RFS...". Based on "Next Release", I thought it would be the version after the current. That, along with the instructions on the second post for RFS, I falsely figured...
I guess it's all for not.
I am stuck at SAMSUNG anyhow (after Reboot Recovery from 2.5.1.0). Can't get to 2.5.1.2...
Edit: On the Stuck on SAMSUNG issue, I re-flashed the latest 1-click from HERE, then re-flashed the .2 prepare/flash first .zip, and all is good. I can get into .2 now.
So the big question is whether you can create a swap disk with 2.5.1.2?
Sent from my SPH-D700 using Tapatalk
I flashed 2.0.1 with no problem using 2.5.1.2 but i was already converted to ext4. Flashing it would put you on ext4 and add cwm3
now that I know how to update it to 2.5.1.2 my question is-
should I?
I have no real reason to do so. I don't intend to do any further modifications to my ROM, just going to stick with the pre-rooted 2.2 I have. Would there be any benefit to updating CWM in this case?
The only reason to get 2.5.1.2 was to be able to flash to ext4. And then cwm 3 simplified the conversion to ext4. If you don't intend to convert to ext4, then there is no reason to get anything other than 2.5.1.0.
nixo31 said:
I flashed 2.0.1 with no problem using 2.5.1.2 but i was already converted to ext4. Flashing it would put you on ext4 and add cwm3
Click to expand...
Click to collapse
It adds ext4 and negates the need for cwm3 iirc.
Sent from my SPH-D700 using Tapatalk
I rooted my phone. I flashed it. and i was attempting to put in iced glacier. I messed up one of the steps -.-
On the clockworkmod recovery i backed up my phone.
I restored it then hit reboot now.
I've waited for a while.. But all i'm getting is the mytough 4g screen >.<
Any ideas?
boot back into recovery and clear cache, advanced>dalvik cache, and data
cybereclipse said:
boot back into recovery and clear cache, advanced>dalvik cache, and data
Click to expand...
Click to collapse
I think I am in the same boat as the OP.
I rooted the Mt4g, backed up stock Sense Froyo with Clockworkmod 3, then installed Cyanogenmod 7 with Clockworkmod 3.
I want to revert back to the stock Sense Froyo. I simply did a restore in Clockworkmod 3 to my Sense Froyo backup, and now all it shows is the white Mt4g screen.
Will clearing the cache and data before restoring the Sense Froyo be my fix too?
Thanks. OP, didnt mean to take over your thread but I think we are having the same issue so didnt want to make another thread.
The version of ClockworkMod Recovery you are using MATTERS. It MATTERS VERY MUCH.
Froyo based ROMs, including Stock and Iced Glacier, must be backed up, restored, and installed with CWMR Version 2. Gingerbread based ROMs such as CM7 must be backed up, restored, and installed with CWMR Version 3.
A higher number does not mean better. There are filesystem differences between Froyo and Gingerbread that require the correct tools.
There is a custom version of CWMR for the MT4G that can handle both types of filesystems (assuming you haven't already used the wrong tools) -- it is called version "3.0.0.6" -- you can look for it on the Development Sub Forum.
Thanks for your reply. Unfortunately I did not know that information at the time when I created the restore file.
When restoring with Clockworkmod 3 failed, I flashed Clockworkmod 2 and restored the recovery made by 3 using 2. Its working so far... It did show one or two errors when I restored.
cybereclipse said:
boot back into recovery and clear cache, advanced>dalvik cache, and data
Click to expand...
Click to collapse
So i'm new to all of this.
I don't want to make the wrong move.
I've got CWMR v3.0.0.5
Just to be clear. I go into CWMR. Do i wipe cache partition, then wipe dalvik cache, wipe data.. then restore again? or reboot system now?
OR do I need to flash CWMR 2 or 3.0.0.6? If so. How do i do that without going through rom manager? I'm noob.
Thanks!
Frankasaurus said:
So i'm new to all of this.
I don't want to make the wrong move.
I've got CWMR v3.0.0.5
Click to expand...
Click to collapse
That is incompatible with Iced Glacier. You can't use 3.0.0.5 with Iced Glacier, or with the Stock ROM. Ever.
In addition, clearing /cache and /data and the Dalvik cache (which is inside of the /data partition, so won't actually do anything if /data is also reformatted) will not solve your problem. Because ....
The partition with the problem is /system -- which is where the ROM lives. That partition is now in EXT4 format, which a Froyo-based ROM cannot access. The Froyo kernel boots (from the /boot partition) and gets errors when it looks in /system.... and reboots. Hence, your boot loop.
Your easiest fix would be to install CM7 so that you have a functional Android OS on your phone. THEN ..... after getting CM7 running, flash a version 2 image of CWMR from ROM Manager (included in CM7), then boot it, and install Iced Glacier.
jggimi said:
Your easiest fix would be to install CM7 so that you have a functional Android OS on your phone. THEN ..... after getting CM7 running, flash a version 2 image of CWMR from ROM Manager (included in CM7), then boot it, and install Iced Glacier.
Click to expand...
Click to collapse
Sounds like that's the course of action. Any threads leading to how to install CM7 in my situation? I'm watching youtube videos on different things trying to learn the best option. But I don't really want to trust tho
From Recovery 3.0.0.5, mount your SD card for use with USB (in the mounts and storage menu) and transfer a CM7 .zip to the card. Get it from http://mirror.teamdouche.net/?device=glacier
Factory wipe / System Reset from the main menu of Recovery, and install the .zip as you did Iced Glacier.
----
CM7 does not include Google Apps. If you were intending to actually =use= the ROM instead of using it temporarily as part of a rescue process, you will likely want them. The .zip can be found at http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip -- install from Recovery after installing CM7.
----
Boot CM7. You'll find ROM Manager in the App drawer. Use it to Flash a version 2.x CWM Recovery -- look under "All ClockworkMod Recoveries" at the bottom of the ROM Manager main screen.
Long press the power button. Select Reboot. CM7 will prompt you for what kind of boot. Select Recovery.
Do another full wipe/factory reset. Install Iced Glacier .zip as you did previously, and reboot.
jggimi said:
CM7 does not include Google Apps. If you were intending to actually =use= the ROM instead of using it temporarily as part of a rescue process, you will likely want them. The .zip can be found at ... -- install from Recovery after installing CM7.
Boot CM7. You'll find ROM Manager in the App drawer. Use it to Flash a version 2.x CWM Recovery -- look under "All ClockworkMod Recoveries" at the bottom of the ROM Manager main screen.
Click to expand...
Click to collapse
So the second zip is only if I want to keep the CM7 ROM? If I do, then I use that zip to get Google Apps?
Also, before I look under "All ClockworkMod recoveries" will I have to install CWM recovery 3.0.0.6 or 2.x first?
In that case. I'll do some research on CM7 too. Idk if iced glacier is better or CM7. Maybe it just depends on preference?
Frankasaurus said:
So the second zip is only if I want to keep the CM7 ROM? If I do, then I use that zip to get Google Apps?
Click to expand...
Click to collapse
Correct.
Also, before I look under "All ClockworkMod recoveries" will I have to install CWM recovery 3.0.0.6 or 2.x first?
Click to expand...
Click to collapse
3.0.0.6 could be used instead of a 2.x version. But it requires its own manual install. Based on the questions in this thread, I'm not recommending CWM Recovery 3.0.0.6 at this point, as you folks do not have a functioning Android system and would have to modify the 3.0.0.6 install procedures. There's only so much knowledge a person can absorb at once. Get your phones working, first.
In that case. I'll do some research on CM7 too. Idk if iced glacier is better or CM7. Maybe it just depends on preference?
Click to expand...
Click to collapse
It is =entirely= a matter of personal preference. There are plenty of people who prefer one over the other. There are also those who prefer neither, and are using yet again another ROM. Poke around in the forum threads here to get a feel for what people think.
jggimi said:
3.0.0.6 could be used instead of a 2.x version. But it requires its own manual install. Based on the questions in this thread, I'm not recommending CWM Recovery 3.0.0.6 at this point, as you folks do not have a functioning Android system and would have to modify the 3.0.0.6 install procedures. There's only so much knowledge a person can absorb at once. Get your phones working, first.
Click to expand...
Click to collapse
sweet. So i'll go with the 2.x version then. In that case, I won't have to install it? it'll just be there?
I'm not at home so I can't try any of it out yet. Just trying to learn as much as i can first
ROM Manager should be able to pull the image from the Internet. CM7, even without Google Apps, should automagically connect your phone and its number and its data plane to T-Mobile's network.
zomg. this is sweet. Thanks for all your help!!! I'm gonna keep CM7 for now. I installed the google app zip. Any suggestions on where to start exploring? The main thing that i wanted to root my phone for was to take screenshots. threads? Bah. so much to explore!
So if on 3.0.0.6 and wanting to go from CM7 to IG, you recommend going into "all clockworkmod recoveries", switching over to a 2.0 version (does it matter which?), and then doing backup, wipe, install?
No. 3.0.0.6 is a unique, one-off version that supports both ext3 and ext4 file systems, and deals correctly with both Froyo and Gingerbread ROMs.
If you were on 3.0.0.5, and wished to install a Froyo ROM, you would back up first, before flashing a 2.x Recovery. Think about it.
HTC Glacier CM7 #5
jggimi said:
No. 3.0.0.6 is a unique, one-off version that supports both ext3 and ext4 file systems, and deals correctly with both Froyo and Gingerbread ROMs.
HTC Glacier CM7 #5
Click to expand...
Click to collapse
So I can just go directly into recovery from Rom Manager and backup/wipe/install Iced Glacier?
Yep. Please see the threads on it in the development sub forum.
HTC Glacier CM7 #5
jggimi said:
Yep. Please see the threads on it in the development sub forum.
HTC Glacier CM7 #5
Click to expand...
Click to collapse
Been reading them, but there is 371 pages in the nighlies thread, and 54 pages in the RC7 thread...I'm bound to miss a thing or two, I'm human
But thank you!
The 3.0.0.6 threads. Much lighter reading.
HTC Glacier CM7 #something