Related
Warning: whether you preform these steps correctly or incorrectly, you may be left with a device which cannot be recovered to a previous state. Because this process operates on the recovery partition it leaves you with little room to recover if flashed incorrectly, especially if your normal Android mode doesn't boot.
(although realistically you can just flash ESPRIMG.zip from HBOOT to recover, or fastboot)
So here it is ladies and gentlemen: Clockwork 3.0.0.5, based on a git version pulled/compiled on January 6th, 2011 from the CyanogenMod 7.x (CM7) repository. So what's new? Nothing that I can tell! Not sure why it deserves version 3.x, but I guess changing the text color and background is considered a 'major upgrade'.
This is provided in .img format - NOT an update.zip format. That means you'll have to flash it to your recovery partition using flash_image. Obviously that means you first need root AND S-OFF. No, I won't tell you how to root your phone or what S-OFF is.
Instructions:
Code:
$ su
# flash_image recovery recovery-cw3-test1.img
'flash_image' isn't included intentionally - if you're smart enough to know how to flash this properly and understand the risks, then you might be smart enough to know where to get 'flash_image'.
How'd I do it? Top Secret - I'd have to kill you if I told you.
Download link: [REMOVED - use one from CM7]http://dl.dropbox.com/u/14943973/recovery-cw3-test1.img
Need to revert back to 2.5.0.1? Flash this: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Enjoy it? Thank me!
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
SKAm69 said:
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
Click to expand...
Click to collapse
Not from me, sorry. I don't see any point in supporting the legacy method, especially when this version of CW doesn't give any readily-apparent advantages to the older one.
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
JAWheat411 said:
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
Click to expand...
Click to collapse
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash at this point
MusicMan374 said:
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
But the only new features you see would be the new color?
Ace42 said:
But the only new features you see would be the new color?
Click to expand...
Click to collapse
Pretty much yeah. It was orange instead of green. Some of the menus had different names, easier to understand for noobs, but they had the same content. But don't flash it until it's more functional.
Sent from my T-Mobile myTouch 3G Slide
Ok well can someone post an older Clockwork recovery.img so we can reflash it? We can't use this one to do anything.
MusicMan374 said:
It IS a test build.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
I was at work when I uploaded the image and because of that I only briefly tested it. The errors at the beginning aren't critical, but I'll look into the overall functionality being broken, at some point tonight.
Hence this being a "TEST".
Thanks
I appreciate that. I like beta testing new things. It does seem to have a few more functions. I just couldn't revert back.....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Flash this to go back to 2.5.0.1: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Actually.. i see a new option to partition SD card straight from the recovery menu... this is a very useful feature... and i think thats why it deserves that build jump from 2.5 to 3.0..... but at this point... it is in an UNUSABLE state.. i understand it is a test build... but i cannot test anything because it crashes on every single option you can possibly choose... will go back to 2.5 and wait for a stable, or at least more functional test build... hope to see some improvements soon... I do not doubt that you guys can have this thing up and running in no timee.. its a good starting point.. Keep the work going... looking forward to it...
was anyone else hoping for a terminal like in good ol' amon_ra? I was...
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
elry567 said:
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Thnx
Sent from my T-Mobile myTouch 3G Slide using XDA App
mymomma8 said:
it crashes on every single option you can possibly choose
Click to expand...
Click to collapse
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
I don't think that file was cw3 I flashed it and still have 2.5 (file by musicman)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
MusicMan374 said:
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Click to expand...
Click to collapse
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
guitarist5122 said:
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
mymomma8 said:
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
Click to expand...
Click to collapse
Alright thanks it works now!
Is it possible to make a custom ROM from an already running system? Some manufacturers don't update their phones (believe me, there are those minor companies that don't care at all), and users would be stuck to their stock ROM.
Soo, is it possible? Will copying all files from the root partition to the PC, modify with the usual tools, then zip, then flash, work?
Just curious
It's possible to work with a nandroid if that's what you mean, yes.
By the way, you shouldn't underclock your Optimus. That'll drain more battery, trust me, I did the same.
Noejn said:
It's possible to work with a nandroid if that's what you mean, yes.
Click to expand...
Click to collapse
How about not using a nandroid backup? I was thinking this would work because I had a look at the contents of the root directory of the phone, and then I had another look at a custom rom zip on my computer. I may sound stupid saying this, but I'm just curious xD
By the way, you shouldn't underclock your Optimus. That'll drain more battery, trust me, I did the same.
Click to expand...
Click to collapse
I've left the values as it is, but I forgot to update my sig. Anyway, thanks I uses the same power if the voltage isn't changed, right?
EDIT: About the ROM thing, I get it now. Never saw those .img files til now. Trying it out
OK so this probably sounds backwards from what everyone would expect. I've been using attn1's Liberated 2.2.2 FR008 rom and adding/removing apps to suite my needs. But now I want to REMOVE usb & wifi tethering! Sounds crazy but this phone is for a kid. I don't know much about developing. I'm guessing these features are built in to the OS, if so do I need to just get a custom settings.apk that doesn't give the tether options OR is there an apk i can remove (many of the apks in that rom have name that I'm not sure what they do so I left them in)? Any help would be really appreciated!
smokinbanger said:
OK so this probably sounds backwards from what everyone would expect. I've been using attn1's Liberated 2.2.2 FR008 rom and adding/removing apps to suite my needs. But now I want to REMOVE usb & wifi tethering! Sounds crazy but this phone is for a kid. I don't know much about developing. I'm guessing these features are built in to the OS, if so do I need to just get a custom settings.apk that doesn't give the tether options OR is there an apk i can remove (many of the apks in that rom have name that I'm not sure what they do so I left them in)? Any help would be really appreciated!
Click to expand...
Click to collapse
I guess you'd just have to get a new rom which does not have those options (none that I know of), but I still don't see why you need those options removed. Even if it is for a child, it doesn't really make a difference. The options can still be there and just not be used.
didnt the stock 2.1 NOT come with tethering? Its been a while, but I think thats how I remember it. So couldnt you just revert to a 2.1 rom?
CallMeAria said:
didnt the stock 2.1 NOT come with tethering? Its been a while, but I think thats how I remember it. So couldnt you just revert to a 2.1 rom?
Click to expand...
Click to collapse
Yes, the original AT&T 2.1 ROM did not have a tethering app.
tpbklake said:
Yes, the original AT&T 2.1 ROM did not have a tethering app.
Click to expand...
Click to collapse
Right, but I can't figure out how to remove the junk apps ect. from the RUU before flashing it like I can with a custom just by deleting apk's from the .zip file. Any ideas?
theonew said:
I guess you'd just have to get a new rom which does not have those options (none that I know of), but I still don't see why you need those options removed. Even if it is for a child, it doesn't really make a difference. The options can still be there and just not be used.
Click to expand...
Click to collapse
And just how do you leave the options there and be sure they will not be used??
I'm no dev but i think if you flash back to ATT 2.1 Rom and re-root to get super user i think you'll be abel to delete your ATT softwear with titanium backup... but I'm not sure. I hope this works for you
smokinbanger said:
Right, but I can't figure out how to remove the junk apps ect. from the RUU before flashing it like I can with a custom just by deleting apk's from the .zip file. Any ideas?
Click to expand...
Click to collapse
you can use adb to remove the apk's from the /system partition while the phone is in recovery after you flash the stock 2.1 RUU. You may have to reflash clockwork recovery after this, not sure if it will revert to stock recovery or not. Also, not sure on this one but you can check out the 2.1 Liberated Rom in the dev section and see if it has tethering enabled or not. Trying to remember this off the top of my head but its been so long since Ive done anything 2.1...
Yes, running the 2.1 RUU will remove Clockwork. So the full process would be to run the 2.1 RUU on the phone, then once done, run Unrevoked again on the phone. At this point I would recommend taking a Nandroid backup so you can revert any changes you make (i.e., if you have problems after deleting one of the apps).
Then you need to use adb to remove apps while the phone is in Recovery mode.
The downside of this (compared to just leaving the phone with stock 2.1 after using the RUU) is that Unrevoked automatically gives you root access in the ROM, which may or may not be what you want.
drumist said:
Yes, running the 2.1 RUU will remove Clockwork. So the full process would be to run the 2.1 RUU on the phone, then once done, run Unrevoked again on the phone. At this point I would recommend taking a Nandroid backup so you can revert any changes you make (i.e., if you have problems after deleting one of the apps).
Then you need to use adb to remove apps while the phone is in Recovery mode.
The downside of this (compared to just leaving the phone with stock 2.1 after using the RUU) is that Unrevoked automatically gives you root access in the ROM, which may or may not be what you want.
Click to expand...
Click to collapse
Root access to the rom is fine. But if I remove apks using adb aren't they still in the boot.img making it possible to simple do a system wipe/ hard reset and thus bring back all the junk apps in the stock 2.1 rom??
With all the DEVS on here it seems like there is a cleaner way to do all this...
smokinbanger said:
Root access to the rom is fine. But if I remove apks using adb aren't they still in the boot.img making it possible to simple do a system wipe/ hard reset and thus bring back all the junk apps in the stock 2.1 rom??
With all the DEVS on here it seems like there is a cleaner way to do all this...
Click to expand...
Click to collapse
No. System wipe would not revert the apps.
So i've upgraded my SGS2(uk device) to the european ICS LPQ i think.
and ive notice that i'm now unable to install apk's manually on the device.
i can install via ADB so not all lost,
has anyone else come across this problem?
also should i flash the UK ICS when it is available
ZonyX said:
So i've upgraded my SGS2(uk device) to the european ICS LPQ i think.
and ive notice that i'm now unable to install apk's manually on the device.
i can install via ADB so not all lost,
has anyone else come across this problem?
also should i flash the UK ICS when it is available
Click to expand...
Click to collapse
Might be a silly thought, but have you enabled the unknown sources option...?
Lee
yep thats been done,
under Security > Unknown Sources is ticked
doesnt seem to be anyother settings that i could've missed either.
Hmm. Odd bug then. I can't help (or confirm) yet as I'm doing a system dump before flashing (LPH to LPQ, full wipe + internal sd format). Copying everything from my internal sd to the pc takes a little while, it was nearly full...
You've tried the nasty shotgun approach of clearing caches and fixing permissions...?
Lee
edit
wrong thread
Working fine here. I did a wipe before install as it wouldn't work the first time I flashed.
Working fine here. I didn't wipe.
The only thing I noticed is that some apps, previously installed, didn't work. I uninstalled them and reinstalled them from the internal SD Card.
Do you have Root? Depending on how you flashed your phone, you may have lost root access and thus some apps that require root may not install.
i agree it is an odd "bug" not sure why it would do this.
when the install application screen comes up, only the cancel button is responsive.
also i can confirm i have root - i flashed CF_root strait after.
flash the stock XXLPQ kernel, and you will be able to install
try said:
flash the stock XXLPQ kernel, and you will be able to install
Click to expand...
Click to collapse
wont i then lose root?
Have you tried unmounting SD card and then mounting it, I had a few issues like that and that fixed it for me.
Sent from my GT-I9100 using XDA
richfreestone said:
Have you tried unmounting SD card and then mounting it, I had a few issues like that and that fixed it for me.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
yes i have tried this, and also did the fix permissions thing in CWM
Not too sure if your issue is related, but you can try the following trick.
http://forum.xda-developers.com/showpost.php?p=23907529&postcount=259
Hope this help.
in case you loose root
ZonyX said:
wont i then lose root?
Click to expand...
Click to collapse
Flashing back the stock kernel will actually solve the problem. For the case of rooting your phone, you can use:
http://forum.xda-developers.com/showthread.php?t=1501719
Got stock kernel on, and rooted my phone using that method. Everything works fine.
Credit goes to Rachmat3 for the guide.
Help guys. I rooted a buddys fascinate. Had a backup but I accidentally wiped that too.
We were comparing phones and I had him run Quadrant and using ROM Toolbox I had him slide his CPU all the way up. Phone reboots now about a minute after you boot into the phone. Not enough time as its still loading/media scanning to get to the app and turn sliders back down.
I thought ADB would work through CWM and I could pull the app but that didn't work.
I flashed the same kernel (KGB over a touchwiz ROM) on top of it hoping it would reset but no luck.
What are my options?
reflash the rom
droidstyle said:
reflash the rom
Click to expand...
Click to collapse
i have. it still reboots about a minute after booting - i assume because ROM Toolbox is still there trying to set CPU?
Edit: also, i'm a little surprised i wasn't able to ADB through recovery? It was on the same laptop i rooted it with so I'm sure the drivers are there. Wire is OK as I was browsing the SD card.
Edit #2: ok i'm losing my eyesight. last night i saw a link to a stock eh03 kernel I was going to try. I figure if the kernel doesn't support OC'ing, i could get in. uninstall the app and flash the KGB kernel back. can you point me to the stock kernel or at least one w/out OC'ing support?
(hes running TSM EH03 btw)
Edit #3: ok found the stock kernel http://forum.xda-developers.com/showpost.php?p=19865577&postcount=140
now i just need to get off work.
damn i feel like a dip****.
Sputnikk23 said:
i have. it still reboots about a minute after booting - i assume because ROM Toolbox is still there trying to set CPU?
Edit: also, i'm a little surprised i wasn't able to ADB through recovery? It was on the same laptop i rooted it with so I'm sure the drivers are there. Wire is OK as I was browsing the SD card.
Edit #2: ok i'm losing my eyesight. last night i saw a link to a stock eh03 kernel I was going to try. I figure if the kernel doesn't support OC'ing, i could get in. uninstall the app and flash the KGB kernel back. can you point me to the stock kernel or at least one w/out OC'ing support?
(hes running TSM EH03 btw)
Edit #3: ok found the stock kernel http://forum.xda-developers.com/showpost.php?p=19865577&postcount=140
now i just need to get off work.
damn i feel like a dip****.
Click to expand...
Click to collapse
So you three fingerd into recovery, wiped data, reflashed TSM and still no dice? If so, then follow section 2 of my guide.
droidstyle said:
So you three fingerd into recovery, wiped data, reflashed TSM and still no dice? If so, then follow section 2 of my guide.
Click to expand...
Click to collapse
Recovery, and just flashed TSM over whats there. BOots into phone but not enough time to get to ROM Toolbox to turn down sliders.
Trying to avoid losing his data/text messages/contacts.
Sputnikk23 said:
Recovery, and just flashed TSM over whats there. BOots into phone but not enough time to get to ROM Toolbox to turn down sliders.
Trying to avoid losing his data/text messages/contacts.
Click to expand...
Click to collapse
your going to have to wipe data unfortunately...hopefully his contacts are synced with google and apps backed up with titanium backup. You could try pulling the sd card and putting in a pc to get contacts, pictures...etc, but the phone is going to need a data wipe.
droidstyle said:
your going to have to wipe data unfortunately...hopefully his contacts are synced with google and apps backed up with titanium backup. You could try pulling the sd card and putting in a pc to get contacts, pictures...etc, but the phone is going to need a data wipe.
Click to expand...
Click to collapse
where are contacts stored then?
and you don't think flashing a non-OC'able kernel will do the trick?
Sputnikk23 said:
where are contacts stored then?
and you don't think flashing a non-OC'able kernel will do the trick?
Click to expand...
Click to collapse
Edit* Not sure where the contacts are stored, somebody can hopefully chime in there.
Also one thing you could try is going into the sd card via pc and deleting the rom tool box app in system/app folder. I have not tried this before...so it may or may not work! You can try flashing the stock kernel, but Im not sure if that will do anything either. Never really been in this situation since I keep all my stuff backed up.
droidstyle said:
No because the kernel dont overwrite the app data...your OC app(rom tool box) still has the voltage script written in the initd folder and the stock eh03 kernel is capable of being OC'd...so nothing will change there.
Click to expand...
Click to collapse
DAMN IT.
Voltages? I didn't change voltages. Just CPU Sliders. Think the nstools reset zip might work?
Also, I followed you guide to flash TSM, so I'm pretty sure its running CWM 2.5.1 (its all red). Shouldn't I be able to adb in through recovery and take out the init.d script/modify text values for the CPU/Pull the ROM Toolbox apk/etc?
Edit: YES YES YES.. sd card via PC.. but.. how do I get to the /system/app through SD card on PC while in recovery. All I get is the SD card contents?
Sputnikk23 said:
DAMN IT.
Voltages? I didn't change voltages. Just CPU Sliders. Think the nstools reset zip might work?
Also, I followed you guide to flash TSM, so I'm pretty sure its running CWM 2.5.1 (its all red). Shouldn't I be able to adb in through recovery and take out the init.d script/modify text values for the CPU/Pull the ROM Toolbox apk/etc?
Edit: YES YES YES.. sd card via PC.. but.. how do I get to the /system/app through SD card on PC while in recovery. All I get is the SD card contents?
Click to expand...
Click to collapse
Im sorry I meant mhz not voltage lol...
scratch the sd card idea, you cant access the system from pc.
If you are familiar with adb, then yes I believe what you said above will work. One thing tho, stock kernels do not support init.d scripts. So if your on the stock kernel, the rom toolbox app must be applying the OC on boot. I think your best shot is to pull the RTB.apk via adb.
droidstyle said:
Im sorry I meant mhz not voltage lol...
scratch the sd card idea, you cant access the system from pc.
If you are familiar with adb, then yes I believe what you said above will work. One thing tho, stock kernels do not support init.d scripts. So if your on the stock kernel, the rom toolbox app must be applying the OC on boot. I think your best shot is to pull the RTB.apk via adb.
Click to expand...
Click to collapse
I haven't tried stock kernel yet. So if it doesn't support init.d, and thats how its being set - seems a valid theory that flashing it would get me back into being able to boot OK.
Whats RTB.apk?
And any ideas as to why I can't adb in when in recovery? Just a driver issue you think? I used the same laptop to root his phone so i figured drivers would be good, so I didn't explore that much last night. USB Mount worked OK obviously.
Sputnikk23 said:
I haven't tried stock kernel yet. So if it doesn't support init.d, and thats how its being set - seems a valid theory that flashing it would get me back into being able to boot OK.
Whats RTB.apk?
And any ideas as to why I can't adb in when in recovery? Just a driver issue you think? I used the same laptop to root his phone so i figured drivers would be good, so I didn't explore that much last night. USB Mount worked OK obviously.
Click to expand...
Click to collapse
(ROM TOOL BOX. APK) lol
If rom tool box is setting the OC at boot and not using init.d script, then no flashing a stock kernel wont fix it.
The samsung driver you used wont work with adb, you need the nexus google driver. A simple Google search will pull it up.
Fyi, the next time you run into issues, a full detailed writeup on the devices setup and exact methods used to get there would help alot.
droidstyle said:
(ROM TOOL BOX. APK) lol
The samsung driver you used wont work with adb, you need the nexus google driver. A simple Google search will pull it up.
Click to expand...
Click to collapse
Hmmm.. Maybe I made a false presumption (being the owner of a Nexus S 4g, totally pimped the hell out btw) that I already had those drivers. Thank you man. You pointed me in the only possible right direction.
Edit: http://forum.xda-developers.com/showthread.php?t=1459905 <-- according to that the stock kernel doesn't do OC?