[11 JAN] -=MDJ's CyanogenMod 7 v. 2.2 + ClockWorkMod Recovery BACKUP
There are several problems getting MDJ's CyanogenMod 7 v2.2 with ClockworkMod on our HD2....
even i was the one struggling around a day to get it work...
Somehow i got managed to boot without any problem
So, for all those my frineds having boot-problem with MDJ's CynM 7 v2.2 on ClockWorkMod.. I am uploading "BACKUP"......
1) MAGLDR 1.1 - Just flash your HD2 NAND with 150MB System Layout of CWM
Copy content of "copy_to_sd_root" to the root of your memory card
2) Extract the Backup file below to root of your card, thats what mine backup
It should look like - "SD_Card_Root\clockworkmod\backup\2011-01-12.11.01.12"
3) Insert memory card into HD2 and Reboot MAGLDR
Boot ClockworkMod Rec, goto Backup & Recover menu,
Select Recover Option
Select "2011-01-12.11.01.12"
Press CALL button to recover the backup
4) Once successful, you should be aable to boot MDJ's CyanogenMod 7 v2.2 without any trouble
Credit goes to All Our Developers
Not much help
Problem still persists, not able to boot into the recovery mode even following your steps. when we choose option 1. Boot AD SD, it comes back to the same menu without doing anything. Need the complete step by step info.
razaknk said:
Problem still persists, not able to boot into the recovery mode even following your steps. when we choose option 1. Boot AD SD, it comes back to the same menu without doing anything. Need the complete step by step info.
Click to expand...
Click to collapse
flash CWMOD over magldr without this ROM on your phone, then get into recovery from magldr.
Then go to backup/restore, and restore the backed up version he gives you here,
after the restore restart the phone and load android from NAND and it should boot fine.
he basically just provided a booting version of the ROM in the form of a ROM backup, so if you can't get into recovery at all reflash MAGLDR and then reflash CWM from the the CWM thread then do as I stated above.
que?
From what u have said where have you seen people getting stuck in the CWM boot? for me it was htc boot screen after magldr
razaknk said:
Problem still persists, not able to boot into the recovery mode even following your steps. when we choose option 1. Boot AD SD, it comes back to the same menu without doing anything. Need the complete step by step info.
Click to expand...
Click to collapse
You also need to put the initrd.gz and the zImage files on to your SD-card, if you don't, you won't boot into Clockworkmod.
I've attached the files to this post.
really good, can you please a version with more than 150mb ? in germany language ``Einstellungen`` and not normally ``Settings``
got a ...."MD5 Mismatch!"
Im confused. MDJ releases CWM versions of his CM7 now. Why does this thread even exist?
Its not rocket science. Flash CWM, and then flash MDJ's CM7 via CWM
Yea but still having issues
Sent from my T-Mobile G2 using XDA App
No, it's not rocket science, but it's still giving these problems for many people. I've flashed thousands of time between all the phones that I've used and flashed for friends - never have I had the problem that I do trying to get this one ROM flashed.
yea i have the same problem cant flash this rom
*IF* time allows tonight I'll try doing a task29 then re-flash MAGLDR and work my way up. Just ironic that I can flash anything else I want via ClockworkMod and not have any trouble.
THE ROM **DOES** install if I use the DFT NAND installer - but what good is the ROM without the GAPPS? Without ClockworkMod you can't install them! (If someone knows a way, please share with us!)
Clockwork Mod is bugged!!!
I don't think it's the actual program, but the SD card (which is prone to corruption on repeated reads and writes). I've spent most of the week trying to get it to work consistently. I'm a programmer and understand all of this stuff, but it's a pain in the ass!!! The amount of threads and posts about this is amazing. Sometimes it's worked for me, mostly it hasn't. Most of the time it crashes or there are 'forced close' or errors in Android.
Saying that, most of the kernel updates and such, work flawlessly. It might be worth using it just for those alone. I prefer the ADB method in Windows. It's done in seconds, and the phone needs one re-boot........
CWM has left my phone, I can do without the lost hours trying to get it to work.
Just flash the NAND version and enjoy Android....
What is the benefit of this over MDJ's CWM version included in the original thread? His CWM version works perfectly for me and is in fact the fastest build I've ever used (based on experience not benchmarks)
Would love to try this build but as with most (or some) I'm having problems with just his builds. First if I download the nand build all the exe,cfg,txt files are corrupt or something. WinRar gives me a big old warning. If I try to use the CWM it will get to the first boot screen and stay there. This is not my first rodeo and I have no problem loading any other ROM but MDJ's.
Thanks for your efforts, but this should be posted in the MDJ thread, or at least titled differently. It's just confusing. It looks like a separate release.
ajchandler said:
What is the benefit of this over MDJ's CWM version included in the original thread? His CWM version works perfectly for me and is in fact the fastest build I've ever used (based on experience not benchmarks)
Click to expand...
Click to collapse
The benefit is for those persons who can not install via ClockWorkMod without getting hung up on the HTC HD2 boot screen.
razaknk said:
Problem still persists, not able to boot into the recovery mode even following your steps. when we choose option 1. Boot AD SD, it comes back to the same menu without doing anything. Need the complete step by step info.
Click to expand...
Click to collapse
whatever orangekid is saying is write,
if you are not able to boot into Boot AD SD...
that means you havnt seems to be copied the zImage & Initrd.gz
Download Here CLW-SD v3.XXXX
Extract zImage and initrd.gz to root of your SD
AirforcProductions said:
From what u have said where have you seen people getting stuck in the CWM boot? for me it was htc boot screen after magldr
Click to expand...
Click to collapse
Yeah bro,
your problem is same as what i had, i.e, HTC boot screen reboots....
Just go with step in post 1
Will solve your issue
ameyanaik said:
whatever orangekid is saying is write,
if you are not able to boot into Boot AD SD...
that means you havnt seems to be copied the zImage & Initrd.gz
Download Here CLW-SD v3.XXXX
Extract zImage and initrd.gz to root of your SD
Click to expand...
Click to collapse
Its not that we can't flash the ROM, it's that we can't get past the bloody splash screen once we have flashed!
Related
First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL. (There's another link in the forum to do this, I can't find it at the moment)
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Galaxy S i9000 as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
If you can't seem to get ROM Manager off the market, you can get it from my homepage:
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just installed! Working great!
Installed with ROM manager. Works like a charm! Thanx alot Koush!
works fine
works like a charm
Installed, everything working without problems.
To install roms with clockwork we need roms in *.zip format? Where to get them?
Sent from my GT-I9000 using Tapatalk
Just got my phone
will try it after charging ]
YOU ARE THE MAN
thank you and thanks all Xda devs and members
hmm ... I know this might sound stupid but, acually GSG is my first android phone, though I know how to flash roms with odin and how to apply update.zip and all that but what is the difference between this and ClockworkMod Recovery ?? and does it use the same components as odin ? (I mean CODE, CSC, MODEM and Pit) ?
Stickied. Closing the other one. Not sure why you would start a new thread instead of modifying the old one though...
Thanks Koush your the man. Coming from a htc magic I hate this odin bull
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
Click to expand...
Click to collapse
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
kalpik said:
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
Click to expand...
Click to collapse
Ahhh... I guess I'm not very used to this "Internal SD Card" thing... there was the update.zip I used to root the phone there and I only checked my regular External SD.
Everything is fine now, sorry for bothering.
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Click to expand...
Click to collapse
I had the same issue. Must have been the update.zip, but I didnt remove it, just pressed the other option, went into manual recovery mode, rebooted went into rom manager and backed up my files. Worked a charm
Does this mean there will be no more work on a permanent recovery solution?
I have the Korean version M110S - and it does not have the standard recovery (it is crippled - no apply:update.zip). Is there and abd command to "apply update.zip" ?
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
This may sound stupid, but I'm kinda new to Android modding (SGS is my first droid, moving here from WiMo on SE-X1) and.... What is Clockwork?
So if I ever needed to send this phone in for warranty purposes, I could just flash the backup of my stock ROM in and I should be good to go?
does this method works for captivate and vibrant???
edit: just install/ captivate and vibrant option available.
Rithina said:
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
Click to expand...
Click to collapse
Worked for me with mimocan ext4 fix
This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.
Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself
Teamwin Recovery Project for A100 version 2.2.2.1 -godmachine81 release-
SOURCES: Available via Github
Download and Install via the official supported method by TWRP
Install Goo Manager app from Play Store, Open Goo Manager, In the Menu in top right corner go to "Install OpenRecovery Script" Follow Instructions On screen
Download Automated Installer (Windows / Linux):
Linux Installer - 2.2.2.1
Windows Installer - 2.2.2.1
Download IMG:
TWRP v2.2.2.1 main mirror
Download Flashable Zip: (Upgrade Only)
TWRP 2.2.2.1 Flashable Upgrade
Updated TWRP release features:
Uses a custom recovery kernel based off of my v1.5 standard kernel with most unneeded features taken out, i.e. governors, schedulers, networking, misc devices, and most things not needed for recovery operations
Kernel and TWRP includes patches aimed at brick prevention
Resolution is set at native 1024x600
Very fast actions and touch response
Backward compatibility with previous releases of TWRP
Compatibility with all Ice Cream Sandwhich and Jelly Bean ROMs for the A100(HoneyComb should be compatible too, however currently untested)
All previous features from TWRP that you may be familiar with are included
Mount Point Information:
External Storage - mountpoint= /external_sdcard
Internal Storage - mountpoint = /sdcard
Instructions:
Automated Installation (Windows/Linux):
Most importantly you need to have all drivers required for adb and fastboot working on your OS, this shouldn't be a concern for linux users, however it may be for Windows users as it is picky about adb drivers.
Download the above Automated Install .zip file for your operating system
Extract the contents of the Zip to a location on your PC's hard drive
Change to the extracted directory's contents.
Run the installer; On windows you may just double click the install-windows.bat file, on linux you need to run the install-linux.sh script
example linux installation commands:
Code:
cd a100_twrp_installer_linux
Code:
bash ./install-linux.sh
Read the on screen information of the progress. If you get any errors you will need to resolve the issue or try one of the following alternative install methods.
If you need more detailed installation instructions please read the INSTALL file included inside the .zip
Manual installation:
Download the .img file for the recovery
Connect your A100 device to USB on your PC
While your A100 is booted in either Android or Recovery just enter the following into your PCs command prompt/shell:
Code:
adb reboot bootloader
Now flash the image - at the command prompt/shell enter:
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img
Reboot the device - again from the command prompt/shell:
Code:
fastboot reboot
Enter Recovery mode - While tablet shuts off, hold the Vol - (down) button until you see the screen saying "loading recovery kernel"
Checkout the new TWRP build and enjoy!
Flashable Upgrade Instructions: (flash just like you would any other .zip, but here are instructions anyway)
Download the Flashable ZIP above
Save to a location on your tablets internal or external memory
Boot to recovery
Choose the file a100_twrp_upgrade_2.2.2.1.zip in the install menu
Swipe to install
Wait and DO NOT Disconnect your A100!
When finished, go back to Main menu - choose Reboot - and Reboot Recovery
Enjoy the Official 2.2.2.1 TWRP Release!
If you would like to help out with the continuance of my kernel development and other goodies for your Acer Iconia Tab please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
pio_masaki said:
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
And don't forget that i forgot the download link!! lol **fixed haha
Broken links, so you can correct it.
Fransis88 said:
Broken links, so you can correct it.
Click to expand...
Click to collapse
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
linuxsociety said:
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
Click to expand...
Click to collapse
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Fransis88 said:
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Click to expand...
Click to collapse
So let me know how you like it. Also if you happen to be a linux user, I have wrote an automated installer script for linux, Xbow59 is currently writing a windows batch script for installation, I currently have the Linux installation working though if you'd like to test/try it out just let me know. Windows users can look forward to an automated solution within a day or so
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
Click to expand...
Click to collapse
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
linuxsociety said:
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
Click to expand...
Click to collapse
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
Click to expand...
Click to collapse
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
nim.whit said:
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
Click to expand...
Click to collapse
yep what pio said:
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
I had forgot all about this, even though it is in my unreleased linux auto installer. If by chance you are using linux, I have an installer that will do this all for you the right way, I just haven't posted it yet because I don't have the windows installer fixed
you can either download the linux installer git repo and just extract it to a directory named twrp_install or similar; just run sudo bash ./install-linux.sh after you are in the install directory. https://github.com/godmachine81/Acer-A100-TWRP-Installer/zipball/linux <<current linux installer for a100 twrp
Or you can clone the repo
Code:
git clone https://github.com/godmachine81/Acer-A100-TWRP-Installer.git
then checkout the linux branch:
Code:
git checkout linux
then install:
Code:
sudo bash ./install-linux.sh
The git method requires you have git installed, you will probably just want to install from the zipball method if you don't already have git
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
nim.whit said:
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
Click to expand...
Click to collapse
Once that's removed or renamed it will stop, one time deal.
Tapatalked from my A100 - Jellytime X B6
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
linuxsociety said:
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
Click to expand...
Click to collapse
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
pio_masaki said:
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
Click to expand...
Click to collapse
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
linuxsociety said:
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
Click to expand...
Click to collapse
The ics Acer zips are known brickers but it happens for a reason I'm not very clear on. HC will also brick it.
Basically there's a chance it will run the zip, attempt to flash everything, however for some reason it will fail to flash system or boot correctly, but does replace the bootloader. What I'm not clear on is why it fails on system or boot but succeeds on bootloader, or why recovery doesn't error flashing it.
Once this situation occurs you get locked out of both recovery and system by the bootloader, no adb or fastboot access to correct it.
Using the information I've gathered on this I've been working on a method to restore to stock if needed, but its going slow as I have to triple check everything before I even test it. Its a long and annoying process but should result in a 100% factory stock system.
Tapatalked from my Galaxy S II.
Installed and working perfectly!
Fransis88 said:
Installed and working perfectly!
Click to expand...
Click to collapse
Great Francis88, mind I ask which method of installation you chose?
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
swarby2 said:
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
Click to expand...
Click to collapse
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
SÜPERUSER said:
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
Click to expand...
Click to collapse
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
swarby2 said:
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
Click to expand...
Click to collapse
Flashing the recovery will not wipe anything except the recovery partition obviously. When you boot to twrp you will be able to access the internal storage by going to Mount and press the Mount usb storage twice. And the one x should be detected on your pc.
But when you're done with the backup you will wipe all partitions with the Format data option as described in the thread I linked yesterday. So backup all important data to your computer.
Thank you so much! I'm up and running!